In den Logs gibt es keine Erwähnung von Abmeldung oder etwas Ähnlichem auf Gladys-Seite, ich denke, wir entfernen uns ein wenig vom ursprünglichen Problem => Geräte, die nicht über Gladys steuerbar sind.
Für das nächste Mal, da es mir jetzt tot erscheint, brauchen wir die Gladys-/MQTT-/Zigbee2MQTT-Logs.
Gleiches Problem bei mir, keine Sensordaten mehr, aber Z2Mqtt 8080 ohne Probleme erreichbar. Ich habe den Dienst deaktiviert und dann wieder aktiviert, und alles war wieder in Ordnung.
Trotzdem manchmal etwas eigenwillig, dieses Ziegbee??
Vielleicht sollten wir eine Service-Überwachungsfunktion integrieren und den Service automatisch neu starten, falls keine aktuellen Daten aktualisiert werden…
Vor allem müsste man verstehen, woher dieses Problem kommt, da ich selbst nicht davon betroffen war (obwohl meine zigbee2mqtt-Installation mit 52 Geräten schon recht « umfangreich » ist).
Ja, aber hier geht es um Gladys und MQTT statt um Zigbee. Gladys interagiert nicht direkt mit dem Zigbee2MQTT-Container.
Gleiches gilt für @guim31, nicht betroffen.
Kann jemand, der das Problem hatte und den Container nicht gelöscht hat, seine vollständigen Logs exportieren und sie (vielleicht privat) an @AlexTrovato @VonOx @cicoub13 und mich selbst schicken? 
Um eine vollständige Logdatei von Gladys zu exportieren:
Es ist ein relativ wichtiges Problem, wir müssen verstehen, was schief läuft
Danke!
Von meiner Seite gibt es nichts zu melden.
Kein Problem mit meinem Update
Falls das hilft, hier ist mein Log direkt vor einem manuellen Neustart und direkt danach:
> Zigbee2MQTT:warn 2023-02-14 11:13:05: Nachricht von nicht unterstütztem Gerät mit Zigbee-Modell 'undefined' und Herstellerbezeichnung 'undefined' erhalten
> Zigbee2MQTT:warn 2023-02-14 11:13:05: Bitte siehe: 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: Nachricht von nicht unterstütztem Gerät mit Zigbee-Modell 'undefined' und Herstellerbezeichnung 'undefined' erhalten
> Zigbee2MQTT:warn 2023-02-14 11:23:39: Bitte siehe: 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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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: Nachricht von nicht unterstütztem Gerät mit Zigbee-Modell 'undefined' und Hersteller 'undefined' erhalten
> Zigbee2MQTT:warn 2023-02-14 11:51:02: Bitte siehe: 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', Nutzlast '{"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', Nutzlast '{"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: Nachricht von nicht unterstütztem Gerät mit Zigbee-Modell 'undefined' und Hersteller 'undefined' erhalten
> Zigbee2MQTT:warn 2023-02-14 11:53:39: Bitte siehe: 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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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: Nachricht von nicht unterstütztem Gerät mit Zigbee-Modell 'undefined' und Hersteller 'undefined' empfangen
> Zigbee2MQTT:warn 2023-02-14 12:23:40: Bitte siehe: 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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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: Nachricht von nicht unterstütztem Gerät mit Zigbee-Modell 'undefined' und Herstellerbezeichnung 'undefined' erhalten
> Zigbee2MQTT:warn 2023-02-14 12:33:25: Bitte siehe: https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html
> Zigbee2MQTT:warn 2023-02-14 12:33:25: Nachricht von nicht unterstütztem Gerät mit Zigbee-Modell 'undefined' und Herstellerbezeichnung 'undefined' erhalten
> Zigbee2MQTT:warn 2023-02-14 12:33:25: Bitte siehe: 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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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: Nicht mit MQTT-Server verbunden!
> Zigbee2MQTT:error 2023-02-14 12:38:27: Nachricht kann nicht gesendet werden: topic: 'zigbee2mqtt/bridge/state', Nutzlast: '{"state":"offline"}
> Zigbee2MQTT:info 2023-02-14 12:38:27: Trenne Verbindung zum MQTT-Server
> Zigbee2MQTT:info 2023-02-14 12:38:27: Beende zigbee-herdsman...
> Verwende '/app/data' als Datenverzeichnis
> Zigbee2MQTT:info 2023-02-14 12:38:50: Protokollierung in Konsole und Verzeichnis: '/app/data/log/2023-02-14.12-38-50' Dateiname: log.txt
> Zigbee2MQTT:info 2023-02-14 12:38:50: Starte Zigbee2MQTT Version 1.30.1 (Commit #eb878d3)
> Zigbee2MQTT:info 2023-02-14 12:38:50: Starte zigbee-herdsman (0.14.89)
> Zigbee2MQTT:info 2023-02-14 12:38:52: zigbee-herdsman gestartet (wiederaufgenommen)
> 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: Derzeit sind 6 Geräte verbunden:
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0x00158d0007f83209 (0x00158d0007f83209): WSDCGQ11LM - Xiaomi Aqara Temperatur-, Feuchtigkeits- und Drucksensor (EndDevice)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0xa4c138af175ed9f2 (0xa4c138af175ed9f2): TS011F_plug_1 - TuYa Smart Steckdose (mit Stromüberwachung) (Router)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0xa4c1388f14e47818 (0xa4c1388f14e47818): TS011F_plug_1 - TuYa Smart Steckdose (mit Stromüberwachung) (Router)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0x00124b00251263cd (0x00124b00251263cd): SNZB-02 - SONOFF Temperatur- und Feuchtigkeitssensor (EndDevice)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0x00124b0024fc27b9 (0x00124b0024fc27b9): Nicht unterstützt (Unbekannt)
> Zigbee2MQTT:info 2023-02-14 12:38:53: 0x54ef4410003e9fc5 (0x54ef4410003e9fc5): VOCKQJK11LM - Xiaomi Aqara TVOC Luftqualitätsmonitor (EndDevice)
> Zigbee2MQTT:info 2023-02-14 12:38:53: Zigbee: Hinzufügen neuer Geräte deaktivieren.
> Zigbee2MQTT:info 2023-02-14 12:38:53: Verbindung zum MQTT-Server bei mqtt://localhost:1884 herstellen
> Zigbee2MQTT:info 2023-02-14 12:38:53: Verbunden mit MQTT-Server
> Zigbee2MQTT:info 2023-02-14 12:38:53: MQTT publish: topic 'zigbee2mqtt/bridge/state', Nutzlast '{"state":"online"}'
> Zigbee2MQTT:info 2023-02-14 12:38:53: Frontend auf Port 0.0.0.0:8080 gestartet
> Zigbee2MQTT:info 2023-02-14 12:38:53: MQTT publish: topic 'zigbee2mqtt/0x00158d0007f83209', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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 gestartet!
> Zigbee2MQTT:warn 2023-02-14 12:39:29: Nachricht von nicht unterstütztem Gerät mit Zigbee-Modell 'undefined' und Herstellerbezeichnung 'undefined' erhalten
> Zigbee2MQTT:warn 2023-02-14 12:39:30: Bitte siehe: 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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"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', Nutzlast '{"child_lock":"UNLOCK","current":0,"energy":3.35,"indicator_mode":"off/on","linkquality":145,"power":0,"power_outage_memory":"restore","state":"ON","voltage":227}'
Danke für deine Logs! Das sind die Logs von Zigbee2mqtt, nicht von Gladys, oder?
Ein manuelles Neustarten löscht die Logs nicht, also ist es immer noch spielbar, solange Sie die Logs und das Datum des aufgetretenen Fehlers angeben!
Für mich ja @pierre-gilles, das sind definitiv Z2M-Logs. Zumindest ist es ziemlich klar, er kann nicht mehr mit dem MQTT-Server kommunizieren, kurz vor dem Neustart.
Entweder ist es mit dem Neustart verbunden, oder es ist mit Gladys verbunden.
Hallo zusammen,
Ich hatte dieses Problem auch schon mal. Ein Stoppen/Neustarten des Dienstes hat die Dinge wieder in Ordnung gebracht. Auch wenn ich das nicht mag.
Ich hatte dieses Problem oder ein ähnliches schon vor einiger Zeit. Ich musste den Docker neu starten.
Falls die Logs bei meiner Manipulation nicht gelöscht wurden, kann ich sie vielleicht wiederherstellen und Ihnen zukommen lassen?!
Entschuldigung, ich komme nach der Schlacht. 
@pierre-gilles
Ja, der Header ist meiner Meinung nach bei Gladys nicht derselbe 
@Noj
Kein Neustart des Containers nötig, einfach den Dienst stoppen, 30 Sekunden warten und den Dienst dann neu starten!
Ich bin gerade aus dem Urlaub zurückgekommen und stelle das gleiche Problem fest.
Mein Knopf, um die Heizung 20 Minuten im Badezimmer einzuschalten, funktioniert in Gladys nicht mehr.
Allerdings erscheinen die Zustandsänderungen in der IP:8080-Schnittstelle
Ich habe die Logs seit dem 7. Februar abgerufen. Ich sende sie Ihnen.
Ich habe mir gerade die Z2M-Logs angesehen. Wenn ich das richtig verstehe, werden beim Neustart des Dienstes alle Daten korrekt übertragen (in meinem Fall die Temperaturen von 4 Räumen), aber bei der zweiten Iteration sendet das System mehrmals dasselbe Topic (4 Mal dasselbe Zimmer: temp salon).
Ich hoffe, das hilft Ihnen, die Ursache des Problems zu finden.
Hier ist der Log seit dem Restart
Zigbee2MQTT:info 2023-03-07 17:54:42: Zigbee: Deaktivieren des Einbindens neuer Geräte.
Zigbee2MQTT:info 2023-03-07 17:54:42: Verbindung zum MQTT-Server unter mqtt://localhost:1884 wird hergestellt
Zigbee2MQTT:debug 2023-03-07 17:54:42: Verwendung von MQTT-Login mit Benutzername: z2m
Zigbee2MQTT:info 2023-03-07 17:54:42: Verbunden mit MQTT-Server
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT-Veröffentlichung: Topic ‹ zigbee2mqtt/bridge/state ›, Payload ‹ online ›
Zigbee2MQTT:info 2023-03-07 17:54:42: Frontend auf Port 0.0.0.0:8080 gestartet
Zigbee2MQTT:debug 2023-03-07 17:54:42: MQTT-Nachricht empfangen auf ‹ zigbee2mqtt/bridge/0x00212effff05527d/get › mit Daten ‹ ›
Zigbee2MQTT:info 2023-03-07 17:54:42: MQTT-Veröffentlichung: 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-Veröffentlichung: 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-Veröffentlichung: 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-Veröffentlichung: 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-Veröffentlichung: 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-Veröffentlichung: 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-Veröffentlichung: 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-Veröffentlichung: Topic ‹ zigbee2mqtt/0x000d6ffffecde87f telecde 3 boutons ›, Payload ‹ {« battery »:100,« linkquality »:255,« voltage »:3000} ›
Zigbee2MQTT:info 2023-03-07 17:54:42: Zigbee2MQTT gestartet!
Zigbee2MQTT:debug 2023-03-07 17:55:49: Empfangene Zigbee-Nachricht von ‹ 0x00158d000465ad6f temp salon ›, Typ ‹ attributeReport ›, Cluster ‹ msTemperatureMeasurement ›, Daten ‹ {« measuredValue »:1526} › von Endpunkt 1 mit groupID null
Zigbee2MQTT:info 2023-03-07 17:55:49: MQTT-Veröffentlichung: 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: Empfangene Zigbee-Nachricht von ‹ 0x00158d000465ad6f temp salon ›, Typ ‹ attributeReport ›, Cluster ‹ msRelativeHumidity ›, Daten ‹ {« measuredValue »:5046} › von Endpunkt 1 mit groupID null
Zigbee2MQTT:info 2023-03-07 17:55:49: MQTT-Veröffentlichung: 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: Empfangene Zigbee-Nachricht von ‹ 0x00158d000465ad6f temp salon ›, Typ ‹ attributeReport ›, Cluster ‹ msPressureMeasurement ›, Daten ‹ {« measuredValue »:981,« scale »:-1,« scaledValue »:9813} › von Endpunkt 1 mit groupID null
Zigbee2MQTT:info 2023-03-07 17:55:49: MQTT-Veröffentlichung: 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} ›
Gut, ich habe gute Nachrichten, nach 2 Stunden Experimentieren habe ich es geschafft, das Problem zu reproduzieren!! 
Ich bin von einer sauberen Installation auf einem Raspberry Pi 3 mit einem Sonoff Zigbee-Dongle und einem Xiaomi Aqara-Temperatursensor ausgegangen.
Ich denke, diese Einrichtung ist nicht so wichtig, aber ich wollte von einer völlig sauberen Basis ausgehen.
1. Simulation eines gestoppten MQTT-Containers (vielleicht im Update?)
docker stop gladys-z2m-mqtt
2. Neustart von Gladys (z. B. während eines Updates)
docker restart gladys
Beim Neustart startet der Zigbee2mqtt-Dienst den gestoppten MQTT-Container erneut:
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
Dann versucht es, sich mit dem Broker zu verbinden:
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/#
Bisher scheint alles gut zu sein!
Aber ab diesem Punkt ist es unmöglich, etwas zu empfangen, alles scheitert mit demselben Fehler, den alle haben:
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
Bei etwas Investigation sehe ich, dass diese berühmten Exposes in einer Variablen this.discoveredDevices im Code gespeichert werden.
Diese Variable scheint beim Empfang einer Nachricht auf dem Topic zigbee2mqtt/bridge/devices gefüllt zu werden
Was einen Log Getting config devices from Zigbee2mqtt anzeigen sollte
Aber in meinen Logs habe ich diesen Log Getting config devices from Zigbee2mqtt nicht, und ich denke, dass dieses berühmte discoveredDevices nicht initialisiert wird!
Daher kommt die Frage: Unter welcher Bedingung sendet der Zigbee2mqtt-Container Informationen über die Geräte?
Die Dokumentation erwähnt:
Was erklären würde, warum man in dieser Variable nichts erhält!
Aber ich habe Schwierigkeiten zu verstehen, wie das den Rest der Zeit funktionieren kann?
Ich habe gerade einen weiteren Neustart durchgeführt:
docker restart gladys
Und trotzdem ist es immer noch unmöglich, den Dienst zu betreiben, ich erhalte immer noch:
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 Weißt du, wann dieses Topic von Zigbee2mqtt aufgerufen wird, und welche Annahme während der Entwicklung getroffen wurde, damit es funktioniert? ^^
@pierre-gilles da der Nachricht im Thema zigbee2mqtt/bridge/devices als „retained“ markiert ist, wird diese Nachricht beim Verbinden eines MQTT-Clients mit diesem Thema vom Broker empfangen, da sie „im Stapel“ des Brokers liegt.
Normalerweise sollte Gladys beim Starten, sobald der Dienst initialisiert ist, den vollständigen Zustand der verbundenen z2m-Geräte erhalten und diese Variable entsprechend füllen.
Gut gesehen, das war das Detail, das mir gefehlt hat, ich wusste nicht einmal, dass es das in MQTT gibt! Danke.
Aber jetzt verstehe ich besser, warum es nicht funktioniert, wenn der MQTT-Broker neu gestartet wurde. Ich glaube nicht, dass wir Persistenz in Mosquitto haben, und wenn der Broker von Watchtower neu installiert wird, Gladys neu gestartet wird und Zigbee2mqtt nicht neu gestartet wird, dann ist Gladys « im Dunkeln ».
Szenario:
Ich habe das Datum des letzten Mosquitto-Updates überprüft, und das war der 30. März, genau einen Tag vor dem Gladys-Update.
Das Szenario bestätigt sich!
