Installation Z2M SkyConnect

Bonjour a tous,

Niveau

  • Débutant et moins encore :slight_smile: / Intermédiaire / Avancé

Mon problème

Débutant complet dans HA j’ai voulu évoluer ma domotique de ZHA vers Z2M.
je ne disposé que de quelques appareil donc la migration ne m’est pas insurmontable de re intégré par la suite.
(2 pont HUE pour le plus gros, tahoma, Cozytouch etc..)

j’avais essayer il y a quelque temps avant de me résoudre a rester sur ZHA faute d’y être parvenu le temps a passe et l’intégration de nouveau module (Zigbee porte garage) ou il fallait ajouter des « Quirks » pour l’intégration correct ma re décider a migrait.
j’ai donc supp tout les appareils de ZHA avant de supprimer l’addon.
Le camarade CHAGPT a beau essayer de m’aider je but complet …

1er essaie une vidéo tuto YT
2eme le tuto de Domoblog

Si vous avez besoin d’infos complémentaire n’hésitez surtout pas.

  • Config Z2m
data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt:
  base_topic: zigbee2mqtt
  server: mqtt://localhost:1883
  user: mqttha
  password: mqttha
serial:
  port: >-
    /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_ba18b297f3e1ed118e7fec5162c613ac-if00-port0
  adapter: ember
  • Journal Z2m
[12:01:38] INFO: Preparing to start...
[12:01:38] INFO: Socat not enabled
[12:01:38] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[2025-01-25 12:01:43] info: 	z2m: Logging to console, file (filename: log.log)
[2025-01-25 12:01:43] info: 	z2m: Starting Zigbee2MQTT version 2.0.0 (commit #unknown)
[2025-01-25 12:01:43] info: 	z2m: Starting zigbee-herdsman (3.2.1)
[2025-01-25 12:01:43] info: 	zh:ember: Using default stack config.
[2025-01-25 12:01:43] info: 	zh:ember: ======== Ember Adapter Starting ========
[2025-01-25 12:01:43] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash: ASH COUNTERS since last clear:
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Total frames: RX=0, TX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Cancelled   : RX=0, TX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   DATA frames : RX=0, TX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   DATA bytes  : RX=0, TX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Retry frames: RX=0, TX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   ACK frames  : RX=0, TX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   NAK frames  : RX=0, TX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   nRdy frames : RX=0, TX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   CRC errors      : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Comm errors     : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Length < minimum: RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Length > maximum: RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Bad controls    : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Bad lengths     : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Bad ACK numbers : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Out of buffers  : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Retry dupes     : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   Out of sequence : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash:   ACK timeouts    : RX=0
[2025-01-25 12:01:43] info: 	zh:ember:uart:ash: ======== ASH stopped ========
[2025-01-25 12:01:43] error: 	zh:ember:uart:ash: Failed to init port with error Error: Error Resource temporarily unavailable Cannot lock port
[2025-01-25 12:01:43] error: 	z2m: Error while starting zigbee-herdsman
[2025-01-25 12:01:43] error: 	z2m: Failed to start zigbee-herdsman
[2025-01-25 12:01:43] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-01-25 12:01:43] error: 	z2m: Exiting...
[2025-01-25 12:01:43] error: 	z2m: Error: Failed to start EZSP layer with status=HOST_FATAL_ERROR.
    at EmberAdapter.initEzsp (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:670:19)
    at EmberAdapter.start (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1533:24)
    at Controller.start (/app/node_modules/.pnpm/zigbee-herdsman@3.2.1/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)
    at Zigbee.start (/app/lib/zigbee.ts:69:27)
    at Controller.start (/app/lib/controller.ts:142:13)
    at start (/app/index.js:161:5)

Journal mosquito broker

[10:58:47] INFO: Setting up user mqttha
[10:58:48] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[10:58:49] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[10:58:49] INFO: Starting mosquitto MQTT broker...
2025-01-25 10:58:49: Warning: Mosquitto should not be run as root/administrator.
2025-01-25 10:58:49: mosquitto version 2.0.20 starting
2025-01-25 10:58:49: Config loaded from /etc/mosquitto/mosquitto.conf.
2025-01-25 10:58:49: Loading plugin: /usr/share/mosquitto/go-auth.so
2025-01-25 10:58:49:  ├── Username/password checking enabled.
2025-01-25 10:58:49:  ├── TLS-PSK checking enabled.
2025-01-25 10:58:49:  └── Extended authentication not enabled.
2025-01-25 10:58:49: Opening ipv4 listen socket on port 1883.
2025-01-25 10:58:49: Opening ipv6 listen socket on port 1883.
2025-01-25 10:58:49: Opening websockets listen socket on port 1884.
2025-01-25 10:58:49: mosquitto version 2.0.20 running
2025-01-25 10:58:50: New connection from ::1:44734 on port 1883.
2025-01-25 10:58:50: Client <unknown> disconnected due to protocol error.
[10:58:51] INFO: Successfully send discovery information to Home Assistant.
[10:58:51] INFO: Successfully send service information to the Supervisor.
2025-01-25 10:59:18: New connection from 172.30.32.1:44834 on port 1883.
2025-01-25 10:59:18: New client connected from 172.30.32.1:44834 as 6JTw0Xtko4YxcrgSgTYQw5 (p2, c1, k60, u'mqttha').
2025-01-25 11:01:40: New connection from 172.30.32.2:57568 on port 1883.
2025-01-25 11:01:40: Client <unknown> closed its connection.
2025-01-25 11:03:40: New connection from 172.30.32.2:41276 on port 1883.
2025-01-25 11:03:40: Client <unknown> closed its connection.
2025-01-25 11:05:40: New connection from 172.30.32.2:51994 on port 1883.
2025-01-25 11:05:40: Client <unknown> closed its connection.
2025-01-25 11:07:40: New connection from 172.30.32.2:59648 on port 1883.
2025-01-25 11:07:40: Client <unknown> closed its connection.
2025-01-25 11:09:40: New connection from 172.30.32.2:57438 on port 1883.
2025-01-25 11:09:40: Client <unknown> closed its connection.
s6-rc: info: service legacy-services: stopping
[10:11:17] INFO: Service restart after closing
2025-01-25 11:11:17: mosquitto version 2.0.20 terminating
time="2025-01-25T11:11:17+01:00" level=error msg="http request error: Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2025-01-25T11:11:17+01:00" level=error msg="http request error: Post \"http://127.0.0.1:80/acl\": dial tcp 127.0.0.1:80: connect: connection refused"
time="2025-01-25T11:11:17+01:00" level=error msg="Post \"http://127.0.0.1:80/superuser\": dial tcp 127.0.0.1:80: connect: connection refused"
2025-01-25 11:11:17: Saving in-memory database to /data//mosquitto.db.
[10:11:17] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[11:43:36] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[11:43:37] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[11:43:37] INFO: Starting mosquitto MQTT broker...
2025-01-25 11:43:37: mosquitto version 2.0.20 starting
2025-01-25 11:43:37: Config loaded from /etc/mosquitto/mosquitto.conf.
2025-01-25 11:43:37: Loading plugin: /usr/share/mosquitto/go-auth.so
2025-01-25 11:43:37: Warning: Mosquitto should not be run as root/administrator.
2025-01-25 11:43:37:  ├── Username/password checking enabled.
2025-01-25 11:43:37:  ├── TLS-PSK checking enabled.
2025-01-25 11:43:37:  └── Extended authentication not enabled.
2025-01-25 11:43:37: Opening ipv4 listen socket on port 1883.
2025-01-25 11:43:37: Opening ipv6 listen socket on port 1883.
2025-01-25 11:43:37: Opening websockets listen socket on port 1884.
2025-01-25 11:43:37: mosquitto version 2.0.20 running
2025-01-25 11:43:37: New connection from ::1:48500 on port 1883.
2025-01-25 11:43:37: Client <unknown> disconnected due to protocol error.
[11:43:38] INFO: Successfully send discovery information to Home Assistant.
[11:43:39] INFO: Successfully send service information to the Supervisor.
2025-01-25 11:43:40: New connection from 172.30.32.2:45778 on port 1883.
2025-01-25 11:43:40: Client <unknown> closed its connection.
2025-01-25 11:43:46: New connection from 172.30.32.1:54672 on port 1883.
2025-01-25 11:43:46: New client connected from 172.30.32.1:54672 as 0mnAOLMsjwGehGAoOMXSSc (p2, c1, k60, u'mqttha').
2025-01-25 11:45:40: New connection from 172.30.32.2:55628 on port 1883.
2025-01-25 11:45:40: Client <unknown> closed its connection.
2025-01-25 11:47:40: New connection from 172.30.32.2:43726 on port 1883.
2025-01-25 11:47:40: Client <unknown> closed its connection.
2025-01-25 11:49:14: Client 0mnAOLMsjwGehGAoOMXSSc closed its connection.
2025-01-25 11:49:37: New connection from 172.30.32.1:37840 on port 1883.
2025-01-25 11:49:37: New client connected from 172.30.32.1:37840 as 6p5pUK0DJj7rGRb8olDCi6 (p2, c1, k60, u'mqttha').
2025-01-25 11:49:40: New connection from 172.30.32.2:59492 on port 1883.
2025-01-25 11:49:40: Client <unknown> closed its connection.
2025-01-25 11:51:40: New connection from 172.30.32.2:39198 on port 1883.
2025-01-25 11:51:40: Client <unknown> closed its connection.
2025-01-25 11:53:40: New connection from 172.30.32.2:56728 on port 1883.
2025-01-25 11:53:40: Client <unknown> closed its connection.
2025-01-25 11:55:40: New connection from 172.30.32.2:58522 on port 1883.
2025-01-25 11:55:40: Client <unknown> closed its connection.
2025-01-25 11:57:40: New connection from 172.30.32.2:35430 on port 1883.
2025-01-25 11:57:40: Client <unknown> closed its connection.
2025-01-25 11:59:40: New connection from 172.30.32.2:40228 on port 1883.
2025-01-25 11:59:40: Client <unknown> closed its connection.
2025-01-25 12:01:40: New connection from 172.30.32.2:55618 on port 1883.
2025-01-25 12:01:40: Client <unknown> closed its connection.
2025-01-25 12:03:40: New connection from 172.30.32.2:59210 on port 1883.
2025-01-25 12:03:40: Client <unknown> closed its connection.
2025-01-25 12:05:40: New connection from 172.30.32.2:49676 on port 1883.
2025-01-25 12:05:40: Client <unknown> closed its connection.
2025-01-25 12:07:40: New connection from 172.30.32.2:34582 on port 1883.
2025-01-25 12:07:40: Client <unknown> closed its connection.
2025-01-25 12:09:40: New connection from 172.30.32.2:46750 on port 1883.
2025-01-25 12:09:40: Client <unknown> closed its connection.
2025-01-25 12:11:40: New connection from 172.30.32.2:34962 on port 1883.
2025-01-25 12:11:40: Client <unknown> closed its connection.
2025-01-25 12:13:38: Saving in-memory database to /data//mosquitto.db.
2025-01-25 12:13:40: New connection from 172.30.32.2:60864 on port 1883.
2025-01-25 12:13:40: Client <unknown> closed its connection.
2025-01-25 12:15:40: New connection from 172.30.32.2:57668 on port 1883.
2025-01-25 12:15:40: Client <unknown> closed its connection.
2025-01-25 12:17:40: New connection from 172.30.32.2:48650 on port 1883.
2025-01-25 12:17:40: Client <unknown> closed its connection.
2025-01-25 12:19:40: New connection from 172.30.32.2:58114 on port 1883.
2025-01-25 12:19:40: Client <unknown> closed its connection.
2025-01-25 12:21:41: New connection from 172.30.32.2:57158 on port 1883.
2025-01-25 12:21:41: Client <unknown> closed its connection.
2025-01-25 12:23:41: New connection from 172.30.32.2:40762 on port 1883.
2025-01-25 12:23:41: Client <unknown> closed its connection.
2025-01-25 12:25:41: New connection from 172.30.32.2:37014 on port 1883.
2025-01-25 12:25:41: Client <unknown> closed its connection.
2025-01-25 12:27:41: New connection from 172.30.32.2:53908 on port 1883.
2025-01-25 12:27:41: Client <unknown> closed its connection.
2025-01-25 12:29:41: New connection from 172.30.32.2:44906 on port 1883.
2025-01-25 12:29:41: Client <unknown> closed its connection.
2025-01-25 12:31:41: New connection from 172.30.32.2:53138 on port 1883.
2025-01-25 12:31:41: Client <unknown> closed its connection.
2025-01-25 12:33:41: New connection from 172.30.32.2:45838 on port 1883.
2025-01-25 12:33:41: Client <unknown> closed its connection.
2025-01-25 12:35:41: New connection from 172.30.32.2:37396 on port 1883.
2025-01-25 12:35:41: Client <unknown> closed its connection.
2025-01-25 12:37:41: New connection from 172.30.32.2:37734 on port 1883.
2025-01-25 12:37:41: Client <unknown> closed its connection.

Ma configuration


[center]## System Information

version core-2025.1.4
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.1
os_name Linux
os_version 6.6.62-haos-raspi
arch aarch64
timezone Europe/Paris
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.3
Stage running
Available Repositories 1500
Downloaded Repositories 9
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 14.1
update_channel stable
supervisor_version supervisor-2024.12.3
agent_version 1.6.0
docker_version 27.2.0
disk_total 219.4 GB
disk_used 6.9 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board rpi4-64
supervisor_api ok
version_api ok
installed_addons Cloudflared (5.2.7), Studio Code Server (5.18.1), Terminal & SSH (9.16.0), Silicon Labs Multiprotocol (2.4.5), Mosquitto broker (6.5.0), Zigbee2MQTT (2.0.0-2)
Dashboards
dashboards 2
resources 6
views 8
mode storage
Recorder
oldest_recorder_run 14 janvier 2025 à 23:56
current_recorder_run 25 janvier 2025 à 11:49
estimated_db_size 125.16 MiB
database_engine sqlite
database_version 3.47.1
___

Bonjour,
tu as un tuto sur le portail HACF:

as tu flasher ta clé skyconnect en firmware Ember ?

pour l’addon mosquitto broker, c’est server: mqtt://core-mosquitto:1883

1 « J'aime »

Merci beaucoup @WarC0zes, j’ai remplacer la ligne de code et surtout j’ai re flasher la SkyConnect, cela n’avait pas du bien fonctionner au premier coup.

Merci Z2M Fonctionne bien !

1 « J'aime »