Oui, j’ai flasher en version 8.0.2 sur le site sonoff flasher
1 « J'aime »
Ca a l’air d’être le cas, c’est noté sur un des screen au dessus.
D’ailleurs, je change rien aux réglages de la page avant de valider?
Il y a plein de réglages non grisé et je ne sais pas si je dois touché.
Ne change rien, tout est OK. Clique sur Submit 
Mais comment je m’en veux…
4 heures à tout changer, modifier, galérer alors qu’il fallait juste valider…
Et tout fonctionne.
Journal Z2M:
Starting Zigbee2MQTT without watchdog.
Onboarding page is available at http://0.0.0.0:8099/
[2025-08-08 06:18:34] info: z2m: Logging to console, file (filename: log.log)
[2025-08-08 06:18:34] info: z2m: Starting Zigbee2MQTT version 2.6.0 (commit #unknown)
[2025-08-08 06:18:34] info: z2m: Starting zigbee-herdsman (5.0.4)
[2025-08-08 06:18:34] info: zh:ember: Using default stack config.
[2025-08-08 06:18:34] info: zh:ember: ======== Ember Adapter Starting ========
[2025-08-08 06:18:34] info: zh:ember:ezsp: ======== EZSP starting ========
[2025-08-08 06:18:34] info: zh:ember:uart:ash: ======== ASH Adapter reset ========
[2025-08-08 06:18:34] info: zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2025-08-08 06:18:34] info: zh:ember:uart:ash: Serial port opened
[2025-08-08 06:18:34] info: zh:ember:uart:ash: ======== ASH starting ========
[2025-08-08 06:18:35] info: zh:ember:uart:ash: ======== ASH connected ========
[2025-08-08 06:18:35] info: zh:ember:uart:ash: ======== ASH started ========
[2025-08-08 06:18:35] info: zh:ember:ezsp: ======== EZSP started ========
[2025-08-08 06:18:35] info: zh:ember: Adapter EZSP protocol version (14) lower than Host. Switched.
[2025-08-08 06:18:35] info: zh:ember: Adapter version info: {"ezsp":14,"revision":"8.0.2 [GA]","build":397,"major":8,"minor":0,"patch":2,"special":0,"type":170}
[2025-08-08 06:18:35] info: zh:ember: [INIT TC] No valid backup found.
[2025-08-08 06:18:35] info: zh:ember: [INIT TC] Forming from config.
[2025-08-08 06:18:35] info: zh:ember: [INIT FORM] Forming new network with: {"panId":53508,"extendedPanId":[229,59,253,38,50,255,129,198],"radioTxPower":5,"radioChannel":11,"joinMethod":0,"nwkManagerId":0,"nwkUpdateId":0,"channels":134215680}
[2025-08-08 06:18:35] info: zh:ember: [STACK STATUS] Network up.
[2025-08-08 06:18:35] info: zh:ember: [INIT FORM] New network formed!
[2025-08-08 06:18:35] info: zh:ember: [CONCENTRATOR] Started source route discovery. 1248ms until next broadcast.
[2025-08-08 06:18:36] info: zh:controller: Wrote coordinator backup to '/config/zigbee2mqtt/coordinator_backup.json'
[2025-08-08 06:18:36] info: z2m: zigbee-herdsman started (reset)
[2025-08-08 06:18:36] info: z2m: Coordinator firmware version: '{"meta":{"build":397,"ezsp":14,"major":8,"minor":0,"patch":2,"revision":"8.0.2 [GA]","special":0,"type":170},"type":"EmberZNet"}'
[2025-08-08 06:18:36] info: z2m: Currently 0 devices are joined.
[2025-08-08 06:18:36] info: z2m: Connecting to MQTT server at mqtt://core-mosquitto:1883
[2025-08-08 06:18:36] info: z2m: Connected to MQTT server
[2025-08-08 06:18:36] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
[2025-08-08 06:18:36] info: z2m: Started frontend on port 8099
[2025-08-08 06:18:36] info: z2m: Zigbee2MQTT started!
[2025-08-08 06:18:41] info: z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x8c8b48fffe4fdce2/connection_state/config', payload '{"device":{"hw_version":"EmberZNet 8.0.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x8c8b48fffe4fdce2"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.0"},"device_class":"connectivity","entity_category":"diagnostic","name":"Connection state","object_id":"zigbee2mqtt_bridge_connection_state","origin":{"name":"Zigbee2MQTT","sw":"2.6.0","url":"https://www.zigbee2mqtt.io"},"payload_off":"offline","payload_on":"online","state_topic":"zigbee2mqtt/bridge/state","unique_id":"bridge_0x8c8b48fffe4fdce2_connection_state_zigbee2mqtt","value_template":"{{ value_json.state }}"}'
[2025-08-08 06:18:41] info: z2m:mqtt: MQTT publish: topic 'homeassistant/binary_sensor/1221051039810110150109113116116_0x8c8b48fffe4fdce2/restart_required/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 8.0.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x8c8b48fffe4fdce2"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.0"},"device_class":"problem","enabled_by_default":false,"entity_category":"diagnostic","name":"Restart required","object_id":"zigbee2mqtt_bridge_restart_required","origin":{"name":"Zigbee2MQTT","sw":"2.6.0","url":"https://www.zigbee2mqtt.io"},"payload_off":false,"payload_on":true,"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x8c8b48fffe4fdce2_restart_required_zigbee2mqtt","value_template":"{{ value_json.restart_required }}"}'
[2025-08-08 06:18:41] info: z2m:mqtt: MQTT publish: topic 'homeassistant/button/1221051039810110150109113116116_0x8c8b48fffe4fdce2/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 8.0.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x8c8b48fffe4fdce2"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.0"},"device_class":"restart","name":"Restart","object_id":"zigbee2mqtt_bridge_restart","origin":{"name":"Zigbee2MQTT","sw":"2.6.0","url":"https://www.zigbee2mqtt.io"},"payload_press":"","unique_id":"bridge_0x8c8b48fffe4fdce2_restart_zigbee2mqtt"}'
[2025-08-08 06:18:41] info: z2m:mqtt: MQTT publish: topic 'homeassistant/select/1221051039810110150109113116116_0x8c8b48fffe4fdce2/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 8.0.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x8c8b48fffe4fdce2"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.0"},"entity_category":"config","name":"Log level","object_id":"zigbee2mqtt_bridge_log_level","options":["error","warning","info","debug"],"origin":{"name":"Zigbee2MQTT","sw":"2.6.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x8c8b48fffe4fdce2_log_level_zigbee2mqtt","value_template":"{{ value_json.log_level | lower }}"}'
[2025-08-08 06:18:41] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x8c8b48fffe4fdce2/version/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 8.0.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x8c8b48fffe4fdce2"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.0"},"entity_category":"diagnostic","icon":"mdi:zigbee","name":"Version","object_id":"zigbee2mqtt_bridge_version","origin":{"name":"Zigbee2MQTT","sw":"2.6.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x8c8b48fffe4fdce2_version_zigbee2mqtt","value_template":"{{ value_json.version }}"}'
[2025-08-08 06:18:41] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x8c8b48fffe4fdce2/coordinator_version/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 8.0.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x8c8b48fffe4fdce2"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.0"},"enabled_by_default":false,"entity_category":"diagnostic","icon":"mdi:chip","name":"Coordinator version","object_id":"zigbee2mqtt_bridge_coordinator_version","origin":{"name":"Zigbee2MQTT","sw":"2.6.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x8c8b48fffe4fdce2_coordinator_version_zigbee2mqtt","value_template":"{{ value_json.coordinator.meta.revision }}"}'
[2025-08-08 06:18:41] info: z2m:mqtt: MQTT publish: topic 'homeassistant/sensor/1221051039810110150109113116116_0x8c8b48fffe4fdce2/network_map/config', payload '{"availability":[{"topic":"zigbee2mqtt/bridge/state","value_template":"{{ value_json.state }}"}],"availability_mode":"all","device":{"hw_version":"EmberZNet 8.0.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x8c8b48fffe4fdce2"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.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":"2.6.0","url":"https://www.zigbee2mqtt.io"},"state_topic":"zigbee2mqtt/bridge/response/networkmap","unique_id":"bridge_0x8c8b48fffe4fdce2_network_map_zigbee2mqtt","value_template":"{{ now().strftime('%Y-%m-%d %H:%M:%S') }}"}'
[2025-08-08 06:18:41] info: z2m:mqtt: MQTT publish: topic 'homeassistant/switch/1221051039810110150109113116116_0x8c8b48fffe4fdce2/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 8.0.2 [GA]","identifiers":["zigbee2mqtt_bridge_0x8c8b48fffe4fdce2"],"manufacturer":"Zigbee2MQTT","model":"Bridge","name":"Zigbee2MQTT Bridge","sw_version":"2.6.0"},"icon":"mdi:human-greeting-proximity","name":"Permit join","object_id":"zigbee2mqtt_bridge_permit_join","origin":{"name":"Zigbee2MQTT","sw":"2.6.0","url":"https://www.zigbee2mqtt.io"},"payload_off":"{\"time\": 0}","payload_on":"{\"time\": 254}","state_off":"false","state_on":"true","state_topic":"zigbee2mqtt/bridge/info","unique_id":"bridge_0x8c8b48fffe4fdce2_permit_join_zigbee2mqtt","value_template":"{{ value_json.permit_join | lower }}"}'
Journal Mosquito:
2025-08-08 06:01:36: Saving in-memory database to /data//mosquitto.db.
2025-08-08 06:01:46: New connection from 172.30.32.2:58286 on port 1883.
2025-08-08 06:01:46: Client <unknown> closed its connection.
2025-08-08 06:03:46: New connection from 172.30.32.2:42056 on port 1883.
2025-08-08 06:03:46: Client <unknown> closed its connection.
2025-08-08 06:05:46: New connection from 172.30.32.2:45616 on port 1883.
2025-08-08 06:05:46: Client <unknown> closed its connection.
2025-08-08 06:07:46: New connection from 172.30.32.2:52938 on port 1883.
2025-08-08 06:07:46: Client <unknown> closed its connection.
2025-08-08 06:09:46: New connection from 172.30.32.2:35748 on port 1883.
2025-08-08 06:09:46: Client <unknown> closed its connection.
2025-08-08 06:11:46: New connection from 172.30.32.2:60658 on port 1883.
2025-08-08 06:11:46: Client <unknown> closed its connection.
2025-08-08 06:13:46: New connection from 172.30.32.2:51070 on port 1883.
2025-08-08 06:13:46: Client <unknown> closed its connection.
2025-08-08 06:15:46: New connection from 172.30.32.2:56006 on port 1883.
2025-08-08 06:15:46: Client <unknown> closed its connection.
2025-08-08 06:17:46: New connection from 172.30.32.2:60818 on port 1883.
2025-08-08 06:17:46: Client <unknown> closed its connection.
2025-08-08 06:18:36: New connection from 172.30.33.3:60154 on port 1883.
2025-08-08 06:18:36: New client connected from 172.30.33.3:60154 as mqttjs_95498b9b (p2, c1, k60, u'mqtt').
2025-08-08 06:19:46: New connection from 172.30.32.2:40444 on port 1883.
2025-08-08 06:19:46: Client <unknown> closed its connection.
2025-08-08 06:21:46: New connection from 172.30.32.2:44772 on port 1883.
2025-08-08 06:21:46: Client <unknown> closed its connection.
2025-08-08 06:23:46: New connection from 172.30.32.2:33812 on port 1883.
2025-08-08 06:23:46: Client <unknown> closed its connection.
2025-08-08 06:25:46: New connection from 172.30.32.2:54350 on port 1883.
2025-08-08 06:25:46: Client <unknown> closed its connection.
Merci encore et toujours pour ton aide 
1 « J'aime »
Je suis ingénieur logiciel expert, mais pas dans les applications domotique et je n’ai pas trop le temps de me documenter sur le sujet alors désolé si mes questions sont naives.
De ce que je connais de jeeeom, c’est une horreur architecturale reposant abusivement sur une architecture serveur web et php ce qui doit le rendre très lourd comparé aux architectures modernes dont Home assistant doit bénéficier vu la communauté autour.
Je passe à home assistant pour rendre plus réactives les automations critiques telle que gestion éclairage (j’ai l’impression qu’il y a un délai de latence de plus d’une seconde alors que tout est optimisé dans le scénario avec Envoi des commandes en parallèle ce qui n’est pas acceptable pour de l’éclairage) et élargir la comptabilité de mes équipements wifi notamment mes clims gree sans devoir passer par Alexa
Le zigbee c’est merveilleux on trouve pleins de dispositifs compatibles à très bon rapport qualité-prix en chine.
C’est formidable d’avoir une communauté open source en mesure de créer zigbeemqtt permettant de s’affranchir des passerelles propriétaires.
A ma connaissance zigbeemqtt génère un serveur indépendant permettant d’exposer le coordinateur zigbee et ses périphériques.
Je pense mettre home assistant dans une vm sur mon pc dédié à jeeeom existant, y affecté la clé usb zigbee puis le faire gérer un serveur mqtt clone de celui existant pour jeedom puis y connecter jeedom dessus pour qu’il puisse continuer à fonctionner
La VM aurait une IP dédiée comme ça aucun risque de conflit avec le jeedom existant
De votre expérience la migration de config mqtt manager z2m est possible sans aucune perte (conservation de tous les périphériques et paramètres par rapport à l’ancien mqtt manager) ?
Si j”alloue 1,3G de RAM à ma VM home assistant ça suffira à faire tourner z2m avec une cinquantaine de module de manière stable ?
Salut
Alors jeedom c’est vieux c’est moi je n’ai plus mis les mains dedans depuis 4 ans donc j’ai un peu perdu la notion de qui fait quoi avec les X version de zigbee ou MQTT.
Ceci dit, en soit, c’est pas si grave la principe reste le même :
- Z2M gère la clé et les périphériques, Z2M étatn aussi un des plugins de jeedom, la migration est transparente (ou quasi) comme on l’évoque dans ce sujet. Z2M fait la pont avec son client MQTT.
- Le serveur MQTT ça marche avec jeedom ou HA, qu’il fait intégré à HA, à jeedom ou à part.
- HA et Jeedom lisent/écrivent dans MQTT (donc clients aussi).
Bref, la migration est facile.
Quant à la machine, 2Go c’est pas mal (pourquoi 1.3 ?), 1Go c’est trop juste. Dans tous les cas, c’est plutot z2M qui demandera un peu de mémoire, puisque c’est là que les périphériques sont connus. Le reste de la communication MQTT, c’est du json.