Dans les logs il n’y a aucune notion de déco ou quoi que ce soit côté gladys, je penses qu’on dérive un peu du problème d’origine => appareils non controllable via Gladys.
Pour la prochaine fois car maintenant ça me paraît mort, il faut les logs gladys / mqtt / zigbee2mqtt
J’ai eu ce problème, j’ai arrêté le service zigbee2mqtt, attendu 30s puis réactivé le service, cela a résolu le problème en tout cas chez moi
pareil pour moi plus de données capteur mais Z2Mqtt 8080 accessible sans problèmes, j’ai désactivé le servie puis réactivé et tout est rentré dans l’ordre.
Quand même capricieux des fois ce ziegbee ??
Il faudrait peut-être intégrer une fonctionnalité de surveillance du service et si pas de données récentes actualisées relancer le service en automatique…
Surtout il faudrait comprendre d’où vient ce problème étant donné que moi-même je n’en ai pas été victime (alors que mon install zigbee2mqtt est assez « importante » avec 52 devices)
Ouai sauf que là c’est plus gladys et mqtt que du zigbee. Gladys n’interragi pas avec le conteneur zigbee2mqtt directement.
Idem @guim31 pas impacté
Est-ce que quelqu’un qui a eu le souci et qui n’a pas supprimé le container depuis peut récupérer ses logs complètes et les envoyer (peut-être en privée) à @AlexTrovato @VonOx @cicoub13 et moi même ? 
Pour sortir un fichier de logs exhaustif Gladys:
C’est un problème quand même assez important, il faut qu’on comprenne ce qui ne va pas
Merci !
De mon côté rien à signaler.
Mise à jour sans souci de mon côté aussi
Si cela peut aider, voici mon log juste avant un restart manuel et juste après :
> Zigbee2MQTT:warn 2023-02-14 11:13:05: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
> Zigbee2MQTT:warn 2023-02-14 11:13:05: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:info 2023-02-14 11:14:32: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:14:32: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:15:11: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.16,"indicator_mode":"off/on","linkquality":91,"power":84,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:15:11: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.16,"indicator_mode":"off/on","linkquality":91,"power":84,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:17:18: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.17,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:19:33: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:19:33: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:22:45: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.17,"indicator_mode":"off/on","linkquality":91,"power":84,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:22:45: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.17,"indicator_mode":"off/on","linkquality":98,"power":84,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:warn 2023-02-14 11:23:39: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
> Zigbee2MQTT:warn 2023-02-14 11:23:39: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:info 2023-02-14 11:24:36: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.18,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:24:45: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:24:45: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:28:46: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":47.17,"linkquality":91,"power_outage_count":11,"pressure":956.9,"temperature":17.38,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 11:28:46: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":47.14,"linkquality":91,"power_outage_count":11,"pressure":956.9,"temperature":17.38,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 11:28:46: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":47.14,"linkquality":91,"power_outage_count":11,"pressure":956.6,"temperature":17.38,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 11:29:41: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.18,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 11:29:41: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.18,"indicator_mode":"off/on","linkquality":91,"power":84,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 11:29:51: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:29:51: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:31:57: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.19,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 11:34:53: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:34:53: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:37:20: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.19,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:37:20: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.19,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:39:08: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.2,"indicator_mode":"off/on","linkquality":91,"power":84,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:40:11: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:40:11: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:40:52: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:40:53: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:40:53: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:43:50: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":225}'
> Zigbee2MQTT:info 2023-02-14 11:44:24: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.2,"indicator_mode":"off/on","linkquality":91,"power":83,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:44:25: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.2,"indicator_mode":"off/on","linkquality":87,"power":83,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:45:23: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:45:23: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 11:46:10: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":47.14,"linkquality":83,"power_outage_count":11,"pressure":956.6,"temperature":17.45,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 11:46:10: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":46.79,"linkquality":87,"power_outage_count":11,"pressure":956.6,"temperature":17.45,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 11:46:10: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":46.79,"linkquality":87,"power_outage_count":11,"pressure":956.3,"temperature":17.45,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 11:46:28: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.21,"indicator_mode":"off/on","linkquality":91,"power":83,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:47:19: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 11:50:38: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:50:38: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:warn 2023-02-14 11:51:02: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
> Zigbee2MQTT:warn 2023-02-14 11:51:02: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:info 2023-02-14 11:51:40: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.21,"indicator_mode":"off/on","linkquality":91,"power":84,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:51:40: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.21,"indicator_mode":"off/on","linkquality":91,"power":84,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:warn 2023-02-14 11:53:39: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
> Zigbee2MQTT:warn 2023-02-14 11:53:39: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:info 2023-02-14 11:53:43: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":46.47,"linkquality":80,"power_outage_count":11,"pressure":956.3,"temperature":17.53,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 11:53:46: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.22,"indicator_mode":"off/on","linkquality":91,"power":84,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:55:39: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:55:39: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 11:59:10: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.22,"indicator_mode":"off/on","linkquality":91,"power":83,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:59:10: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.22,"indicator_mode":"off/on","linkquality":91,"power":83,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 11:59:46: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":225}'
> Zigbee2MQTT:info 2023-02-14 12:00:39: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:00:41: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:00:41: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:00:50: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":123,"power":0,"power_outage_memory":"restore","state":"ON","voltage":225}'
> Zigbee2MQTT:info 2023-02-14 12:01:07: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.23,"indicator_mode":"off/on","linkquality":91,"power":83,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 12:01:08: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:06:04: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 12:06:04: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":127,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 12:06:17: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":46.47,"linkquality":91,"power_outage_count":11,"pressure":956.3,"temperature":17.49,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 12:06:17: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":46.99,"linkquality":91,"power_outage_count":11,"pressure":956.3,"temperature":17.49,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 12:06:17: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":46.99,"linkquality":91,"power_outage_count":11,"pressure":956,"temperature":17.49,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 12:06:17: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.23,"indicator_mode":"off/on","linkquality":98,"power":84,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:06:17: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.23,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:08:18: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.24,"indicator_mode":"off/on","linkquality":98,"power":84,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:11:04: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:11:04: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:13:28: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.24,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:13:28: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.24,"indicator_mode":"off/on","linkquality":98,"power":84,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:15:36: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.44,"energy":1.25,"indicator_mode":"off/on","linkquality":94,"power":84,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:16:13: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 12:16:13: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":230}'
> Zigbee2MQTT:info 2023-02-14 12:20:53: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.25,"indicator_mode":"off/on","linkquality":98,"power":85,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:20:53: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.25,"indicator_mode":"off/on","linkquality":98,"power":85,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:21:39: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:21:39: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":231}'
> Zigbee2MQTT:info 2023-02-14 12:22:55: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.26,"indicator_mode":"off/on","linkquality":102,"power":85,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:warn 2023-02-14 12:23:40: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
> Zigbee2MQTT:warn 2023-02-14 12:23:40: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:info 2023-02-14 12:26:49: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
> Zigbee2MQTT:info 2023-02-14 12:26:49: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
> Zigbee2MQTT:info 2023-02-14 12:27:59: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.26,"indicator_mode":"off/on","linkquality":105,"power":85,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:27:59: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.26,"indicator_mode":"off/on","linkquality":102,"power":85,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:29:51: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":131,"power":0,"power_outage_memory":"restore","state":"ON","voltage":225}'
> Zigbee2MQTT:info 2023-02-14 12:30:16: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.27,"indicator_mode":"off/on","linkquality":102,"power":85,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:32:17: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":109,"power":0,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 12:32:17: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":116,"power":0,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 12:32:23: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":46.99,"linkquality":80,"power_outage_count":11,"pressure":956,"temperature":17.56,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 12:32:24: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":47.02,"linkquality":83,"power_outage_count":11,"pressure":956,"temperature":17.56,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 12:32:24: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":47.02,"linkquality":83,"power_outage_count":11,"pressure":955.8,"temperature":17.56,"voltage":2975}'
> Zigbee2MQTT:warn 2023-02-14 12:33:25: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
> Zigbee2MQTT:warn 2023-02-14 12:33:25: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:warn 2023-02-14 12:33:25: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
> Zigbee2MQTT:warn 2023-02-14 12:33:25: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:info 2023-02-14 12:35:37: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.27,"indicator_mode":"off/on","linkquality":98,"power":85,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 12:35:37: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.27,"indicator_mode":"off/on","linkquality":98,"power":85,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 12:37:28: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.28,"indicator_mode":"off/on","linkquality":102,"power":85,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 12:37:45: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":145,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
> Zigbee2MQTT:info 2023-02-14 12:37:45: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":142,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
> Zigbee2MQTT:error 2023-02-14 12:38:27: Not connected to MQTT server!
> Zigbee2MQTT:error 2023-02-14 12:38:27: Cannot send message: topic: 'zigbee2mqtt/bridge/state', payload: '{"state":"offline"}
> Zigbee2MQTT:info 2023-02-14 12:38:27: Disconnecting from MQTT server
> Zigbee2MQTT:info 2023-02-14 12:38:27: Stopping zigbee-herdsman...
> Using '/app/data' as data directory
> Zigbee2MQTT:info 2023-02-14 12:38:50: Logging to console and directory: '/app/data/log/2023-02-14.12-38-50' filename: log.txt
> Zigbee2MQTT:info 2023-02-14 12:38:50: Starting Zigbee2MQTT version 1.30.1 (commit #eb878d3)
> Zigbee2MQTT:info 2023-02-14 12:38:50: Starting zigbee-herdsman (0.14.89)
> Zigbee2MQTT:info 2023-02-14 12:38:52: zigbee-herdsman started (resumed)
> Zigbee2MQTT:info 2023-02-14 12:38:52: Coordinator firmware version: '{"meta":{"maintrel":1,"majorrel":2,"minorrel":7,"product":1,"revision":20220219,"transportrev":2},"type":"zStack3x0"}'
> Zigbee2MQTT:info 2023-02-14 12:38:53: Currently 6 devices are joined:
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0x00158d0007f83209 (0x00158d0007f83209): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0xa4c138af175ed9f2 (0xa4c138af175ed9f2): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0xa4c1388f14e47818 (0xa4c1388f14e47818): TS011F_plug_1 - TuYa Smart plug (with power monitoring) (Router)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0x00124b00251263cd (0x00124b00251263cd): SNZB-02 - SONOFF Temperature and humidity sensor (EndDevice)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0x00124b0024fc27b9 (0x00124b0024fc27b9): Not supported (Unknown)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0x54ef4410003e9fc5 (0x54ef4410003e9fc5): VOCKQJK11LM - Xiaomi Aqara TVOC air quality monitor (EndDevice)
> Zigbee2MQTT:info 2023-02-14 12:38:53: Zigbee: disabling joining new devices.
> Zigbee2MQTT:info 2023-02-14 12:38:53: Connecting to MQTT server at mqtt://localhost:1884
> Zigbee2MQTT:info 2023-02-14 12:38:53: Connected to MQTT server
> Zigbee2MQTT:info 2023-02-14 12:38:53: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"online"}'
> Zigbee2MQTT:info 2023-02-14 12:38:53: Started frontend on port 0.0.0.0:8080
> Zigbee2MQTT:info 2023-02-14 12:38:53: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', payload '{"battery":83,"humidity":47.02,"power_outage_count":11,"pressure":955.8,"temperature":17.56,"voltage":2975}'
> Zigbee2MQTT:info 2023-02-14 12:38:53: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
> Zigbee2MQTT:info 2023-02-14 12:38:53: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.45,"energy":1.28,"indicator_mode":"off/on","power":85,"power_outage_memory":"restore","state":"ON","voltage":228}'
> Zigbee2MQTT:info 2023-02-14 12:38:53: MQTT publish: topic 'zigbee2mqtt/0x54ef4410003e9fc5', payload '{"battery":100,"device_temperature":19,"humidity":44.81,"power_outage_count":28,"temperature":19.54,"voc":65,"voltage":3146}'
> Zigbee2MQTT:info 2023-02-14 12:38:53: Zigbee2MQTT started!
> Zigbee2MQTT:warn 2023-02-14 12:39:29: Received message from unsupported device with Zigbee model 'undefined' and manufacturer name 'undefined'
> Zigbee2MQTT:warn 2023-02-14 12:39:30: Please see: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:info 2023-02-14 12:40:53: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
> Zigbee2MQTT:info 2023-02-14 12:40:53: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
> Zigbee2MQTT:info 2023-02-14 12:40:53: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":134,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
> Zigbee2MQTT:info 2023-02-14 12:42:38: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.42,"energy":1.28,"indicator_mode":"off/on","linkquality":102,"power":82,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:42:38: MQTT publish: topic 'zigbee2mqtt/0xa4c1388f14e47818', payload '{"child_lock":"UNLOCK","current":0.42,"energy":1.28,"indicator_mode":"off/on","linkquality":102,"power":82,"power_outage_memory":"restore","state":"ON","voltage":229}'
> Zigbee2MQTT:info 2023-02-14 12:42:47: MQTT publish: topic 'zigbee2mqtt/0xa4c138af175ed9f2', payload '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":145,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
Merci pour tes logs ! C’est les logs de Zigbee2mqtt ça, pas de Gladys on est d’accord ?
Un restart manuel ne supprime pas les logs, donc c’est toujours jouable tant que vous donnez les logs et la date du bug rencontré !
Pour moi oui @pierre-gilles ce sont bien des logs Z2M. Au moins c’est assez clair, il n’arrive plus à communiquer avec le serveur MQTT, juste avant le redémarrage.
Soit c’est lié au redémarrage, soit c’est lié à Gladys.
Hello tout le monde,
J’ai déjà aussi eu ce souci. Un stop/start du service a remis les choses en ordre. Même si je n’aime pas cela.
J’avais déjà eu ce souci, ou un proche, il y a quelque temps. J’avais dû relancer le docker.
Si les logs n’ont pas été supprimés lors de ma manip, je peux peut-être les récupérer et vous les transmettre ?!
Désolé, j’arrive après la bataille. 
@pierre-gilles
Oui, l’entête n’est pas le même pour Gladys je crois 
@Noj
Pas besoin de redémarrer le container, juste arrêter le service, attendre 30s puis redémarrer le service !
Je viens de rentrer de vacances et constate le même problème.
Mon bouton pour mettre en route le chauffage 20 minutes dans la salle de bain ne fonctionne plus dans Gladys.
Par contre, les changements d’état apparaissent dans l’interface IP:8080
J’ai récupéré les logs depuis le 7 février. Je vous les envoie.
Je viens de me pencher sur les logs de Z2M. Si je comprends bien, quand on relance le service, toutes les données sont bien transmises (dans lmon cas les températures de 4 pièces)mais à la seconde itération, le système envoie plusieurs fois le même topic (4 fois la même pièce : temp salon).
j’espère que cela vous permettra de trouver l’origine du problème.
voici le log depuis le rest
Zigbee2MQTT:info 2023-03-07 17:54:42: Zigbee: disabling joining new devices.
Zigbee2MQTT:info 2023-03-07 17:54:42: Connecting to MQTT server at mqtt://localhost:1884
Zigbee2MQTT:debug 2023-03-07 17:54:42: Using MQTT login with username: z2m
Zigbee2MQTT:info 2023-03-07 17:54:42: Connected to MQTT server
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/bridge/state ›, payload ‹ online ›
Zigbee2MQTT:info 2023-03-07 17:54:42: Started frontend on port 0.0.0.0:8080
Zigbee2MQTT:debug 2023-03-07 17:54:42: Received MQTT message on ‹ zigbee2mqtt/bridge/0x00212effff05527d/get › with data ‹ ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/bridge/config ›, payload ‹ {« commit »:« cdf62ea »,« coordinator »:{« meta »:{« maintrel »:0,« majorrel »:38,« minorrel »:114,« product »:0,« revision »:« 0x26720700 »,« transportrev »:0},« type »:« ConBee2/RaspBee2 »},« log_level »:« debug »,« network »:{« channel »:11,« extendedPanID »:« 0xdddddddddddddddd »,« panID »:6754},« permit_join »:false,« version »:« 1.30.2 »} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/0x00158d000465ad6f temp salon ›, payload ‹ {« battery »:57,« humidity »:50.5,« linkquality »:255,« power_outage_count »:31,« pressure »:981.1,« temperature »:15.23,« voltage »:2935} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/0x00158d000282ed1e temp chbre elise ›, payload ‹ {« battery »:43,« humidity »:55.92,« linkquality »:200,« power_outage_count »:188,« pressure »:993.9,« temperature »:22.2,« voltage »:2915} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/0x5c0272fffe6d678b ›, payload ‹ {« linkquality »:255,« update »:{« installed_version »:587753009,« latest_version »:587753009,« state »:« idle »},« update_available »:false} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/0x00158d0001d654a8 temp bureau ›, payload ‹ {« battery »:100,« humidity »:55.02,« linkquality »:255,« power_outage_count »:9,« pressure »:988.4,« temperature »:21.82,« voltage »:3025} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/0x00158d00040967ab ›, payload ‹ {« battery »:83,« contact »:true,« linkquality »:255,« power_outage_count »:333,« voltage »:2975} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/0x00158d000464c57b temp sdb parents ›, payload ‹ {« battery »:81,« humidity »:67.97,« linkquality »:255,« power_outage_count »:53,« pressure »:998,« temperature »:27.77,« voltage »:3135} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT publish: topic ‹ zigbee2mqtt/0x000d6ffffecde87f telecde 3 boutons ›, payload ‹ {« battery »:100,« linkquality »:255,« voltage »:3000} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: Zigbee2MQTT started!
Zigbee2MQTT:debug 2023-03-07 17:55:49: Received Zigbee message from ‹ 0x00158d000465ad6f temp salon ›, type ‹ attributeReport ›, cluster ‹ msTemperatureMeasurement ›, data ‹ {« measuredValue »:1526} › from endpoint 1 with groupID null
Zigbee2MQTT:info 2023-03-07 17:55:49: MQTT publish: topic ‹ zigbee2mqtt/0x00158d000465ad6f temp salon ›, payload ‹ {« battery »:57,« humidity »:50.5,« linkquality »:255,« power_outage_count »:31,« pressure »:981.1,« temperature »:15.26,« voltage »:2935} ›
Zigbee2MQTT:debug 2023-03-07 17:55:49: Received Zigbee message from ‹ 0x00158d000465ad6f temp salon ›, type ‹ attributeReport ›, cluster ‹ msRelativeHumidity ›, data ‹ {« measuredValue »:5046} › from endpoint 1 with groupID null
Zigbee2MQTT:info 2023-03-07 17:55:49: MQTT publish: topic ‹ zigbee2mqtt/0x00158d000465ad6f temp salon ›, payload ‹ {« battery »:57,« humidity »:50.46,« linkquality »:255,« power_outage_count »:31,« pressure »:981.1,« temperature »:15.26,« voltage »:2935} ›
Zigbee2MQTT:debug 2023-03-07 17:55:49: Received Zigbee message from ‹ 0x00158d000465ad6f temp salon ›, type ‹ attributeReport ›, cluster ‹ msPressureMeasurement ›, data ‹ {« measuredValue »:981,« scale »:-1,« scaledValue »:9813} › from endpoint 1 with groupID null
Zigbee2MQTT:info 2023-03-07 17:55:49: MQTT publish: topic ‹ zigbee2mqtt/0x00158d000465ad6f temp salon ›, payload ‹ {« battery »:57,« humidity »:50.46,« linkquality »:252,« power_outage_count »:31,« pressure »:981.3,« temperature »:15.26,« voltage »:2935} ›
Bon, j’ai des bonnes nouvelles, après 2 heures d’expérimentations je viens de réussir à reproduire le souci !! 
Je suis parti d’une installation vierge sur un Raspberry Pi 3 avec un dongle Sonoff Zigbee et un capteur de température Xiaomi Aqara.
Je pense que ce setup importe peu, mais je voulais partir d’une base totalement vierge.
1. Simulation d’un container MQTT arrêté (en cours de mise à jour peut-être ?)
docker stop gladys-z2m-mqtt
2. Redémarrage de Gladys (par exemple, lors d’une mise à jour)
docker restart gladys
Au redémarrage, le service Zigbee2mqtt relance le container MQTT arrêté :
2023-04-03T06:39:52+0200 <debug> init.js:64 (Zigbee2mqttManager.init) Zibgee2mqtt: installing and starting required docker containers...
2023-04-03T06:39:52+0200 <info> checkForContainerUpdates.js:14 (Zigbee2mqttManager.checkForContainerUpdates) Checking for current installed versions and required updates...
2023-04-03T06:39:53+0200 <info> installMqttContainer.js:98 (Zigbee2mqttManager.installMqttContainer) MQTT broker is starting...
2023-04-03T06:39:58+0200 <info> installMqttContainer.js:104 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2023-04-03T06:39:58+0200 <info> installZ2mContainer.js:59 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment...
2023-04-03T06:39:58+0200 <trace> installZ2mContainer.js:63 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt : configuration file already exists.
2023-04-03T06:39:58+0200 <info> installZ2mContainer.js:78 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
Puis tente de se connecter au broker:
2023-04-03T06:39:58+0200 <info> connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker...
2023-04-03T06:39:59+0200 <debug> saveConfiguration.js:20 (Zigbee2mqttManager.saveConfiguration) Zigbee2mqtt: storing configuration...
2023-04-03T06:39:59+0200 <info> connect.js:24 (MqttClient.<anonymous>) Connected to MQTT container mqtt://localhost:1884
2023-04-03T06:39:59+0200 <info> subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
Jusque là tout semble bon !
Sauf qu’à partir de là, impossible de recevoir quoi que ce soit, tout échoue avec la même erreur que tout le monde a:
2023-04-03T06:40:17+0200 <debug> findMatchingExpose.js:32 (Zigbee2mqttManager.findMatchingExpose) Device "0x00158d0001a4c7c7" not found
2023-04-03T06:40:17+0200 <error> handleMqttMessage.js:103 () Failed to convert value for device 0x00158d0001a4c7c7: Error: Zigbee2mqqt expose not found on device "0x00158d0001a4c7c7" with property "battery".
at Zigbee2mqttManager.readValue (/src/server/services/zigbee2mqtt/lib/readValue.js:16:11)
at /src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:99:31
at Array.forEach (<anonymous>)
at Zigbee2mqttManager.handleMqttMessage (/src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:91:41)
at MqttClient.<anonymous> (/src/server/services/zigbee2mqtt/lib/connect.js:53:12)
at MqttClient.emit (node:events:513:28)
at MqttClient.\_handlePublish (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:1277:12)
at MqttClient.\_handlePacket (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:410:12)
at work (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:321:12)
at processTicksAndRejections (node:internal/process/task_queues:77:11)
2023-04-03T06:40:17+0200 <debug> findMatchingExpose.js:32 (Zigbee2mqttManager.findMatchingExpose) Device "0x00158d0001a4c7c7" not found
En investiguant un peu, je vois que ces fameux expose sont stockés dans une variable this.discoveredDevices dans le code.
Cette variable a l’air d’être remplie lors de la réception d’un message sur le topic zigbee2mqtt/bridge/devices
Ce qui devrait afficher un log Getting config devices from Zigbee2mqtt
Hors, dans mes logs, je n’ai pas ce log Getting config devices from Zigbee2mqtt, et ainsi je pense que ce fameux discoveredDevices n’est pas initialisé !
Du coup viens la question: a quelle condition le container Zigbee2mqtt envoie les informations sur les devices ?
La documentation mentionne:
Ce qui expliquerait donc pourquoi on n’obtient rien dans cette variable !
Mais du coup, j’ai du mal à comprendre comment ça peut fonctionner le reste du temps ?
Je viens de refaire un:
docker restart gladys
Et malgré ça, toujours impossible de faire marcher le service, j’obtiens toujours :
2023-04-03T07:02:30+0200 <debug> findMatchingExpose.js:32 (Zigbee2mqttManager.findMatchingExpose) Device "0x00158d0001a4c7c7" not found
2023-04-03T07:02:30+0200 <error> handleMqttMessage.js:103 () Failed to convert value for device 0x00158d0001a4c7c7: Error: Zigbee2mqqt expose not found on device "0x00158d0001a4c7c7" with property "voltage".
at Zigbee2mqttManager.readValue (/src/server/services/zigbee2mqtt/lib/readValue.js:16:11)
at /src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:99:31
at Array.forEach (<anonymous>)
at Zigbee2mqttManager.handleMqttMessage (/src/server/services/zigbee2mqtt/lib/handleMqttMessage.js:91:41)
at MqttClient.<anonymous> (/src/server/services/zigbee2mqtt/lib/connect.js:53:12)
at MqttClient.emit (node:events:513:28)
at MqttClient._handlePublish (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:1277:12)
at MqttClient._handlePacket (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:410:12)
at work (/src/server/services/zigbee2mqtt/node_modules/mqtt/lib/client.js:321:12)
at processTicksAndRejections (node:internal/process/task_queues:77:11)
@AlexTrovato Est-ce que tu sais quand ce topic est appelé par Zigbee2mqtt, et quelle était l’hypothèse faite lors du développement pour que ça marche ? ^^
Dans le code de Zigbee2mqtt, voilà toutes les conditions pour que Zigbee2mqtt re-publie la liste des devices:
(Nous sommes dans la fonction Bridge.start):
@pierre-gilles du fait qe le message sur le topic zigbee2mqtt/bridge/devices soit « retained », dès lors que le client MQTT se connecte à ce topic sur le broker, ce message sera reçu, car il est « pile » dans le broker.
Donc normalement, au démarrage de Gladys, dès que le service est initialisé, Gladys reçoit l’état complet des devices z2m connectés, et devrait donc remplir cette variable.
Bien vu, c’est le détail qui me manquait, je ne savais même pas que ça existait en MQTT ! Merci.
Mais du coup je comprend mieux pourquoi ça ne marche pas si le broker MQTT a été relancé, je ne crois pas qu’on ait de persistence sur Mosquitto, et donc si le broker est re-installé par Watchtower, puis Gladys redémarré, et que Zigbee2mqtt n’est pas redémarré, alors Gladys est « dans le noir »
Scénario:
J’ai regardé la date de la dernière mise à jour de Mosquitto, et c’était le 30 mars, pile 1 jour avant la mise à jour de Gladys.
Le scénario se vérifie !
