Merci.
Je commence juste sous HA et la je suis perdu.
Je dois recommencer l’installation depuis le début ?
J’ai acheter la Yellow, mais j’ai aussi une clé Sonoff ( SONOFF - Clé USB Zigbee 3.0 + antenne externe (V2) Réf: ZBDONGLE-E) que n’ai encore pas utiliser, elle est dans son emballage d’origine car si j’ai bien compris, elle n’était utile pour le multi protocole MQTT mais maintenant ce n’est plus le cas ?
Quel clé tu viens de flasher en multiprotocol ?
Oui, le multiprotocol est abandonné. Oubli c’est solution. Si tu veux du zigbee et matter, il te faudra deux clés, une flashée pour le Zigbee et une flashée pour Openthread ( matter ).
Je n’ai uniquement que la yellow, j’avais cru comprendre qu’elle etait multi protocole
ma configuration est :
et mon ancienne installation était :
j’avais acheté la clé sonoff pour la mettre sur mon NAS mais ce n’était pas possible et j’ai don c fait le choix de me lancer dans l’aventure HA avec la yellow
Ok, il te faut alors utiliser Silicon Labs Flasher ( module complémentaire à installer et désinstaller Silicon labs mulltiprotocol ) et installer le firmware Ember ( avec le firmware ember 7.4.3 ).
Tu as une explication sur ce post:
Super
J’ai flasher correctement et j’ai la version 7.4.4.0
-----------------------------------------------------------
Add-on: Silicon Labs Flasher
Silicon Labs firmware flasher add-on
-----------------------------------------------------------
Add-on version: 0.3.2
You are running the latest version of this add-on.
System: Home Assistant OS 14.0 (aarch64 / yellow)
Home Assistant Core: 2024.12.1
Home Assistant Supervisor: 2024.11.4
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[11:14:17] INFO: Detected Home Assistant Yellow
[11:14:17] INFO: Starting universal-silabs-flasher with /dev/ttyAMA1 (bootloader baudrate 115200)
2024-12-08 11:14:20.172 core-silabs-flasher universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=2, sdk_version='4.4.4', ezsp_version='7.4.4.0', ot_rcp_version=None, cpc_version=None, fw_type=<FirmwareImageType.ZIGBEE_NCP: 'zigbee_ncp'>, fw_variant=None, baudrate=115200)
2024-12-08 11:14:20.172 core-silabs-flasher universal_silabs_flasher.flasher INFO Triggering yellow bootloader
2024-12-08 11:14:20.476 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-12-08 11:14:20.589 core-silabs-flasher universal_silabs_flasher.flasher INFO Launched application from bootloader
2024-12-08 11:14:20.591 core-silabs-flasher universal_silabs_flasher.flasher INFO Detected bootloader version '2.0.1'
2024-12-08 11:14:20.592 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.EZSP at 115200 baud
2024-12-08 11:14:25.605 core-silabs-flasher universal_silabs_flasher.flasher INFO Probing ApplicationType.CPC at 460800 baud
2024-12-08 11:14:25.620 core-silabs-flasher universal_silabs_flasher.flasher INFO Detected ApplicationType.CPC, version '4.3.1-4f7f9e99-dirty-e3b0c442' (4.3.1) at 460800 baudrate (bootloader baudrate 115200)
yellow_zigbee_ncp_7.4.4.0.gbl
[11:15:05] INFO: universal-silabs-flasher-up script exited with code 0
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner 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
la suite c’est de refaire l’installation de Zigbee2MQTT
puis Mosquitto broker
avec les paramètres suivants :
Mosquitto broker (mdp pour tester)
le journal
[11:33:58] INFO: Setting up user mqtt
[11:33:59] 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:34:00] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[11:34:01] INFO: Starting mosquitto MQTT broker...
2024-12-08 11:34:01: mosquitto version 2.0.18 starting
2024-12-08 11:34:01: Config loaded from /etc/mosquitto/mosquitto.conf.
2024-12-08 11:34:01: Warning: Mosquitto should not be run as root/administrator.
2024-12-08 11:34:01: Loading plugin: /usr/share/mosquitto/go-auth.so
2024-12-08 11:34:01: ├── Username/password checking enabled.
2024-12-08 11:34:01: ├── TLS-PSK checking enabled.
2024-12-08 11:34:01: └── Extended authentication not enabled.
2024-12-08 11:34:01: Opening ipv4 listen socket on port 1883.
2024-12-08 11:34:01: Opening ipv6 listen socket on port 1883.
2024-12-08 11:34:01: Opening websockets listen socket on port 1884.
2024-12-08 11:34:01: mosquitto version 2.0.18 running
2024-12-08 11:34:01: New connection from ::1:37384 on port 1883.
2024-12-08 11:34:01: Client <unknown> disconnected due to protocol error.
2024-12-08 11:34:02: New connection from 172.30.32.2:53578 on port 1883.
2024-12-08 11:34:02: Client <unknown> closed its connection.
[11:34:02] INFO: Successfully send discovery information to Home Assistant.
[11:34:03] INFO: Successfully send service information to the Supervisor.
2024-12-08 11:34:10: New connection from 172.30.32.1:56281 on port 1883.
2024-12-08 11:34:10: Client 4pzGYboQ0Sn6Q9FJniJWVV disconnected, not authorised.
2024-12-08 11:34:11: New connection from 172.30.32.1:47989 on port 1883.
2024-12-08 11:34:11: New client connected from 172.30.32.1:47989 as 6iKYZX4gTAbxTPlafDRQrE (p2, c1, k60, u'homeassistant').
2024-12-08 11:34:12: Client 6iKYZX4gTAbxTPlafDRQrE disconnected.
2024-12-08 11:34:12: New connection from 172.30.32.1:44295 on port 1883.
2024-12-08 11:34:12: New client connected from 172.30.32.1:44295 as 1W9Ef7jmanSOtcyNIncNcU (p2, c1, k60, u'homeassistant').
2024-12-08 11:34:12: Client 1W9Ef7jmanSOtcyNIncNcU disconnected.
2024-12-08 11:34:12: New connection from 172.30.32.1:36007 on port 1883.
2024-12-08 11:34:12: New client connected from 172.30.32.1:36007 as 0tnFHG22qu2SpesDKR6j09 (p2, c1, k60, u'homeassistant').
time="2024-12-08T11:34:17+01:00" level=error msg="POST error: Post \"http://127.0.0.1:80/superuser\": read tcp 127.0.0.1:50010->127.0.0.1:80: read: connection reset by peer"
j’ai obtenu ce journal :
Starting Zigbee2MQTT without watchdog.
[2024-12-08 11:41:47] info: z2m: Logging to console, file (filename: log.log)
[2024-12-08 11:41:47] info: z2m: Starting Zigbee2MQTT version 1.42.0 (commit #unknown)
[2024-12-08 11:41:47] info: z2m: Starting zigbee-herdsman (2.1.9)
[2024-12-08 11:41:48] info: zh:ember: Using default stack config.
[2024-12-08 11:41:48] info: zh:ember: ======== Ember Adapter Starting ========
[2024-12-08 11:41:48] info: zh:ember:ezsp: ======== EZSP starting ========
[2024-12-08 11:41:48] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2024-12-08 11:41:48] info: zh:ember:uart:ash: Serial port opened
[2024-12-08 11:41:48] info: zh:ember:uart:ash: ======== ASH starting ========
[2024-12-08 11:41:48] error: zh:ember:uart:ash: Received ERROR from adapter while connecting, with code=RESET_WATCHDOG.
[2024-12-08 11:41:49] info: zh:ember:uart:ash: ======== ASH connected ========
[2024-12-08 11:41:49] info: zh:ember:uart:ash: ======== ASH started ========
[2024-12-08 11:41:49] info: zh:ember:ezsp: ======== EZSP started ========
[2024-12-08 11:41:49] info: zh:ember: Adapter EZSP protocol version (13) lower than Host. Switched.
[2024-12-08 11:41:49] info: zh:ember: Adapter version info: {"ezsp":13,"revision":"7.4.4 [GA]","build":0,"major":7,"minor":4,"patch":4,"special":0,"type":170}
[2024-12-08 11:41:49] info: zh:ember: [STACK STATUS] Network up.
[2024-12-08 11:41:49] info: zh:ember: [INIT TC] Adapter network matches config.
[2024-12-08 11:41:49] info: zh:ember: [CONCENTRATOR] Started source route discovery. 1248ms until next broadcast.
[2024-12-08 11:41:49] info: z2m: zigbee-herdsman started (resumed)
[2024-12-08 11:41:49] info: z2m: Coordinator firmware version: '{"meta":{"build":0,"ezsp":13,"major":7,"minor":4,"patch":4,"revision":"7.4.4 [GA]","special":0,"type":170},"type":"EmberZNet"}'
[2024-12-08 11:41:49] info: z2m: Currently 0 devices are joined.
[2024-12-08 11:41:49] info: z2m: Zigbee: disabling joining new devices.
[2024-12-08 11:41:50] info: z2m: Connecting to MQTT server at mqtt://core-mosquitto
[2024-12-08 11:41:51] info: z2m: Connected to MQTT server
[2024-12-08 11:41:51] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2024-12-08 11:41:51] info: z2m: Started frontend on port 8099
[2024-12-08 11:41:51] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2024-12-08 11:41:51] info: z2m: Zigbee2MQTT started!
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x5cc7c1fffe44b73a/connection_state/config', payload '{"device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"device_class":"connectivity","entity_category":"diagnostic","name":"Connection state","object_id":"zigbee2mqtt_bridge_connection_state","origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"payload_off":"offline","payload_on":"online","state_topic":"zigbee2mqtt/bridge/state","unique_id":"bridge_0x5cc7c1fffe44b73a_connection_state_zigbee2mqtt","value_template":"{{ value_json.state }}"}'
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x5cc7c1fffe44b73a/restart_required/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"device_class":"problem","enabled_by_default":false,"entity_category":"diagnostic","name":"Restart required","object_id":"zigbee2mqtt_bridge_restart_required","origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x5cc7c1fffe44b73a_restart_required_zigbee2mqtt","value_template":"{{ value_json.restart_required }}"}'
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/button/1221051039810110150109113116116_0x5cc7c1fffe44b73a/restart/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","command_topic":"zigbee2mqtt/bridge/request/restart","device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"device_class":"restart","name":"Restart","object_id":"zigbee2mqtt_bridge_restart","origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"payload_press":"","unique_id":"bridge_0x5cc7c1fffe44b73a_restart_zigbee2mqtt"}'
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/select/1221051039810110150109113116116_0x5cc7c1fffe44b73a/log_level/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","command_template":"{\"options\": {\"advanced\": {\"log_level\": \"{{ value }}\" } } }","command_topic":"zigbee2mqtt/bridge/request/options","device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"entity_category":"config","name":"Log level","object_id":"zigbee2mqtt_bridge_log_level","options":["error","warning","info","debug"],"origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x5cc7c1fffe44b73a_log_level_zigbee2mqtt","value_template":"{{ value_json.log_level | lower }}"}'
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x5cc7c1fffe44b73a/version/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"entity_category":"diagnostic","icon":"mdi:zigbee","name":"Version","object_id":"zigbee2mqtt_bridge_version","origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x5cc7c1fffe44b73a_version_zigbee2mqtt","value_template":"{{ value_json.version }}"}'
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x5cc7c1fffe44b73a/coordinator_version/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:chip","name":"Coordinator version","object_id":"zigbee2mqtt_bridge_coordinator_version","origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x5cc7c1fffe44b73a_coordinator_version_zigbee2mqtt","value_template":"{{ value_json.coordinator.meta.revision }}"}'
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x5cc7c1fffe44b73a/network_map/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"enabled_by_default":false,"entity_category":"diagnostic","json_attributes_template":"{{ value_json.data.value | tojson }}","json_attributes_topic":"zigbee2mqtt/bridge/response/networkmap","name":"Network map","object_id":"zigbee2mqtt_bridge_network_map","origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/response/networkmap","unique_id":"bridge_0x5cc7c1fffe44b73a_network_map_zigbee2mqtt","value_template":"{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"}'
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x5cc7c1fffe44b73a/permit_join_timeout/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"device_class":"duration","entity_category":"diagnostic","name":"Permit join timeout","object_id":"zigbee2mqtt_bridge_permit_join_timeout","origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x5cc7c1fffe44b73a_permit_join_timeout_zigbee2mqtt","unit_of_measurement":"s","value_template":"{{ iif(value_json.permit_join_timeout is defined, value_json.permit_join_timeout, None) }}"}'
[2024-12-08 11:41:56] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/1221051039810110150109113116116_0x5cc7c1fffe44b73a/permit_join/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","command_topic":"zigbee2mqtt/bridge/request/permit_join","device":{"hw_version":"EmberZNet 7.4.4 [GA]","identifiers":["zigbee2mqtt_bridge_0x5cc7c1fffe44b73a"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"1.42.0"},"icon":"mdi:human-greeting-proximity","name":"Permit join","object_id":"zigbee2mqtt_bridge_permit_join","origin":{"name":"Zigbee2MQTT","sw":"1.42.0","url":"https://www.zigbee2mqtt.io"},"payload_off":"false","payload_on":"true","state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x5cc7c1fffe44b73a_permit_join_zigbee2mqtt","value_template":"{{ value_json.permit_join | lower }}"}'
J’ai donc cette nouvelle fenêtre qui apparait
Quid quand je lance l’appairage il ne trouve aucune prise.
Oui, tout est bon, vu que Z2M a démarrer et tu as accès au menu de Z2M.
Tu a mis la prise en mode appairage ?
oui, c’est une prise AZ1 nous
Il faut maintenir le bouton physique d’allumage manuel pendant 7 secondes.
J’ai fait cette opération plusieurs fois sans succès.
Concernant ce qui fonctionnait a le « pont » Phillips hue je doit également tout réappairer pour mes 4 prises Osram par exemples ?
oui, il faut les réappairer.
Pour la gestion des protocoles
La Yellow gére zigbee grâce a sa puce intégrer.
Par contre pour Thread et Matter sur Home Assistant, installation sur la clé SONOFF ZBDONGLE par exemple.
J’ai bien tout suivi ? si oui je peux attendre ou il est préférable de le faire au début ?
C’est ça
Mais attention le multiprotocol ne veut pas dire çamaos le fait d’embarquer zigbee et thread sur le même dongle
Car bien sûr que HA est multiprotocol
je penser mettre « Thread et Matter » sur la clé SONOFF comme dans cette vidéo par exemple
Non non et non
Je pense qu’on est au moins 3 a te dire que c’est abandonné et qu’en plus c’est une mauvaise idée
Il faut donc uniquement garder le zigbee2mqtt a la puce intégrer de la Yellow.
Bonjour, tu peux me contacter, je peux t’aider. Bonne journée à toi
Bonsoir,
ok c’est gentil.
Je découvre et lis encore et je reviens vers toi.
