In the logs there is no indication of any disconnect or anything on the Gladys side, I think we’re drifting a bit from the original problem => devices not controllable via Gladys.
For next time, because now it seems hopeless, we need the Gladys / MQTT / zigbee2mqtt logs
I had this problem, I stopped the zigbee2mqtt service, waited 30s then reactivated the service, that solved the problem for me
Same for me, no more sensor data but Z2Mqtt 8080 is accessible without problems, I disabled the service then reactivated it and everything went back to normal.
Still, Zigbee can be temperamental sometimes??
We might need to add a service monitoring feature and, if there is no recently updated data, automatically restart the service…
Above all, we should understand where this problem is coming from since I myself was not affected (even though my zigbee2mqtt installation is quite « large » with 52 devices)
Yeah, except that here it’s more Gladys and MQTT than Zigbee. Gladys doesn’t interact with the zigbee2mqtt container directly.
Same for @guim31, not affected
Can someone who experienced the issue and hasn’t removed the container since then retrieve their complete logs and send them (maybe privately) to @AlexTrovato @VonOx @cicoub13 and me? 
To extract a comprehensive Gladys log file:
This is quite an important issue; we need to understand what’s going wrong
Thanks!
On my side, nothing to report.
No problems with the update on my end either
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}'
Thanks for your logs! Those are Zigbee2mqtt logs, not Gladys, right?
A manual restart doesn’t delete the logs, so it’s still possible as long as you provide the logs and the date of the bug encountered !
For me, yes @pierre-gilles, these are indeed Z2M logs. At least it’s pretty clear, it can no longer communicate with the MQTT server, just before the restart.
Either it’s related to the restart, or it’s related to Gladys.
Hello everyone,
I’ve had this issue too. A stop/start of the service put things back in order, even though I don’t like doing that.
I or someone close to me had this issue some time ago. I had to restart the Docker.
If the logs weren’t deleted during my attempt, I might be able to recover them and send them to you?!
Sorry, I’m late to the party. 
@pierre-gilles
Yes, I think the header isn’t the same for Gladys 
@Noj
No need to restart the container, just stop the service, wait 30s then restart the service!
I’ve just come back from vacation and see the same problem.
My button to turn on the heating for 20 minutes in the bathroom no longer works in Gladys.
However, the state changes appear in the IP:8080 interface.
I retrieved the logs from February 7. I’m sending them to you.
I’ve just looked into the Z2M logs. If I understand correctly, when the service is restarted, all data is transmitted correctly (in my case the temperatures of 4 rooms) but on the second iteration the system sends the same topic multiple times (4 times the same room: temp salon).
I hope this helps you find the root cause of the problem.
Here is the log since the restart
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} ›
Good, I have good news — after 2 hours of experimenting I just managed to reproduce the issue!! 
I started from a fresh install on a Raspberry Pi 3 with a Sonoff Zigbee dongle and a Xiaomi Aqara temperature sensor.
I don’t think this setup matters much, but I wanted to start from a completely clean base.
1. Simulating a stopped MQTT container (maybe during an update?)
docker stop gladys-z2m-mqtt
2. Restarting Gladys (for example, during an update)
docker restart gladys
On restart, the Zigbee2mqtt service restarts the stopped MQTT container:
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
Then it tries to connect to the 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/#
So far everything seems fine!
Except that from that point on, it’s impossible to receive anything — everything fails with the same error that everyone has:
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
Investigating a bit, I see that these so-called exposes are stored in a variable this.discoveredDevices in the code.
This variable seems to be filled when receiving a message on the topic zigbee2mqtt/bridge/devices
Which should display a log Getting config devices from Zigbee2mqtt
However, in my logs I don’t have this Getting config devices from Zigbee2mqtt log, so I think this discoveredDevices is not initialized!
So here’s the question: under what condition does the Zigbee2mqtt container send the device information?
The documentation mentions:
Which would therefore explain why we get nothing in this variable!
But then, I find it hard to understand how it can work at other times?
I just did again:
docker restart gladys
And despite that, the service still won’t work, I still get:
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 Do you know when this topic is called by Zigbee2mqtt, and what assumption was made during development for it to work? ^^
In the Zigbee2mqtt code, here are all the conditions for Zigbee2mqtt to re-publish the list of devices:
(We are in the Bridge.start function):
@pierre-gilles because the message on the topic zigbee2mqtt/bridge/devices is « retained », as soon as the MQTT client connects to that topic on the broker, this message will be received, since it is « sitting » in the broker.
So normally, on Gladys startup, as soon as the service is initialized, Gladys receives the full state of the connected z2m devices, and should therefore populate this variable.
Well spotted, that’s the detail I was missing, I didn’t even know that existed in MQTT! Thanks.
But that makes it clearer why it doesn’t work if the MQTT broker has been restarted — I don’t think we have persistence on Mosquitto, so if the broker is reinstalled by Watchtower, then Gladys is restarted, and Zigbee2mqtt is not restarted, Gladys is « in the dark »
Scenario:
I checked the date of the last Mosquitto update, and it was March 30, exactly one day before the Gladys update.
The scenario checks out!
