Zigbee Instanzen stürzen alle paar Tage ab
-
@asgothian
Vielen Dank für die präzisen Antworten.
Zum USB Stick muss ich sagen, wie im Eingangspost erwähnt, habe ich viele verschiedene gekauft. Tatsächlich kann ich mich nicht erinnern, dass hier eine Instanz auf rot gegangen wäre, dennoch hilft das nicht, wenn ich nur die Devices direkt im Raum und sporadisch einige Angrenzende steuern kann. Auch hatte ich mehrere RaspberryPi als Slave mit USB Sticks getestet, was dann aber zu anderen Problemen führte. Bis auf das Problem notwendiger Neustarts alle paar Tage bin ich mit mit der aktuellen Installation total zufrieden. Jeder Button, jeder Fensterkontakt,... alles ist perfekt zu erreichen (bis zum lästigen Abbruch
)Dein Hinweis mit Skripten bringt mich allerdings auf eine Idee. Ich könnte die CC26X2R1 an WLAN-Steckdosen hängen. Wenn ich es hinbekommen im iobroker den Zigbee-Abbruch als Auslöse-Trigger zu bekommen, könnte ich direkt den WLAN-Schalter aus und nach ~10 Sekunden wieder einschalten.
In jeder Zigbee-Instanz habe ich doch den State "info.connection". Das sollte IMHO auf FALSE gehen, wenn ein Abbruch erfolgt und als Auslöse-Trigger taugen.Ich werde das testen.
-
@andreas-s sagte in Zigbee Instanzen stürzen alle paar Tage ab:
Dein Hinweis mit Skripten bringt mich allerdings auf eine Idee. Ich könnte die CC26X2R1 an WLAN-Steckdosen hängen. Wenn ich es hinbekommen im iobroker den Zigbee-Abbruch als Auslöse-Trigger zu bekommen, könnte ich direkt den WLAN-Schalter aus und nach ~10 Sekunden wieder einschalten.
In jeder Zigbee-Instanz habe ich doch den State "info.connection". Das sollte IMHO auf FALSE gehen, wenn ein Abbruch erfolgt und als Auslöse-Trigger taugen.
Ich werde das testen.Ich empfehle dir eher heraus zu bekommen ob der Neustart per URL direkt ausgelöst werden kann - dann kannst du im Skript erst einmal verifizieren das der wieder am Leben ist und ihn dann darüber Zurück setzen anstatt ihn einfach hart Umzulegen. Letztendlich kann ein Ausfall ja auch längerfristig entstehen wenn es wirklich Netzwerkprobleme gibt. Da hilft dann ein 'power cycle' nicht.
A.
-
@asgothian
Netzwerkprobleme im IP-Netzwerk würde ich eher nicht erwarten. Die CC2642R1 sind per Kabel angebunden und immer erreichbar.Den Ansatz per direkter URL remote einen Reboot auszulösen finde ich sehr interessant.
Ich habe ein kleines Java-Skript aktiviert, dass als Trigger den Verbindungsverlust nimmt und dann den reboot per URL auslöst.Ein erster Test des Skripts (bei nicht unterbrochener Verbindung) zeigt, dass der ioBroker sofort die Unterbrechung mitbekommt und den Adapter neu startet. Nach etwas mehr als einer Minute ist alles wieder durchgestartet.
Also in der Testsituation klappt das. Jetzt werde ich Abwarten, ob es auch klappt, wenn die Verbindung verloren ist und dann der Reboot durch diesen Verbindungsverlust ausgelöst wird.2025-05-10 12:12:43.513 - info: javascript.0 (886) script.js.Javaskripte.Zigbee_3_Reboot_Test: Testbutton ausgelöst – sende Reboot-Befehl an CC2642R1… 2025-05-10 12:12:43.577 - info: javascript.0 (886) script.js.Javaskripte.Zigbee_3_Reboot_Test: Reboot-Request Status: 2025-05-10 12:13:07.881 - error: zigbee.3 (171318) Adapter disconnected, stopping 2025-05-10 12:13:07.889 - error: zigbee.3 (171318) Adapter disconnected, stopping 2025-05-10 12:13:07.894 - error: zigbee.3 (171318) Adapter disconnected, stopping 2025-05-10 12:13:07.897 - error: zigbee.3 (171318) Adapter disconnected, stopping 2025-05-10 12:13:07.900 - error: zigbee.3 (171318) Adapter disconnected, stopping 2025-05-10 12:13:07.906 - error: zigbee.3 (171318) Adapter disconnected, stopping 2025-05-10 12:13:07.909 - error: zigbee.3 (171318) Adapter disconnected, stopping 2025-05-10 12:13:07.912 - error: zigbee.3 (171318) Adapter disconnected, stopping 2025-05-10 12:13:17.951 - info: zigbee.3 (171318) Try to reconnect. 2025-05-10 12:13:17.952 - info: zigbee.3 (171318) Starting Adapter npm ... 2025-05-10 12:13:17.953 - info: zigbee.3 (171318) Try to reconnect. 2025-05-10 12:13:17.953 - info: zigbee.3 (171318) Starting Adapter npm ... 2025-05-10 12:13:17.954 - info: zigbee.3 (171318) Try to reconnect. 2025-05-10 12:13:17.954 - info: zigbee.3 (171318) Starting Adapter npm ... 2025-05-10 12:13:17.954 - info: zigbee.3 (171318) Try to reconnect. 2025-05-10 12:13:17.955 - info: zigbee.3 (171318) Starting Adapter npm ... 2025-05-10 12:13:17.955 - info: zigbee.3 (171318) Try to reconnect. 2025-05-10 12:13:17.955 - info: zigbee.3 (171318) Starting Adapter npm ... 2025-05-10 12:13:17.956 - info: zigbee.3 (171318) Try to reconnect. 2025-05-10 12:13:17.956 - info: zigbee.3 (171318) Starting Adapter npm ... 2025-05-10 12:13:17.956 - info: zigbee.3 (171318) Try to reconnect. 2025-05-10 12:13:17.957 - info: zigbee.3 (171318) Starting Adapter npm ... 2025-05-10 12:13:17.957 - info: zigbee.3 (171318) Try to reconnect. 2025-05-10 12:13:17.957 - info: zigbee.3 (171318) Starting Adapter npm ... 2025-05-10 12:13:17.971 - info: zigbee.3 (171318) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:17.972 - info: zigbee.3 (171318) Starting Zigbee-Herdsman 2025-05-10 12:13:17.979 - info: zigbee.3 (171318) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:17.980 - info: zigbee.3 (171318) Starting Zigbee-Herdsman 2025-05-10 12:13:17.983 - info: zigbee.3 (171318) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:17.984 - info: zigbee.3 (171318) Starting Zigbee-Herdsman 2025-05-10 12:13:17.986 - info: zigbee.3 (171318) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:17.986 - info: zigbee.3 (171318) Starting Zigbee-Herdsman 2025-05-10 12:13:17.989 - info: zigbee.3 (171318) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:17.989 - info: zigbee.3 (171318) Starting Zigbee-Herdsman 2025-05-10 12:13:17.992 - info: zigbee.3 (171318) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:17.992 - info: zigbee.3 (171318) Starting Zigbee-Herdsman 2025-05-10 12:13:17.995 - info: zigbee.3 (171318) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:17.996 - info: zigbee.3 (171318) Starting Zigbee-Herdsman 2025-05-10 12:13:18.004 - warn: zigbee.3 (171318) Network parameters in Config : panID=6752 channel=11 extendedPanID=a3c2a022014c1301 2025-05-10 12:13:18.004 - warn: zigbee.3 (171318) Network parameters on Coordinator: panID=6752 channel=11 extendedPanID=00124b00219fc1a2 2025-05-10 12:13:18.019 - error: zigbee.3 (171318) Starting zigbee-herdsman problem : Error while opening socket 2025-05-10 12:13:18.022 - error: zigbee.3 (171318) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-10 12:13:18.023 - error: zigbee.3 (171318) unhandled promise rejection: undefined 2025-05-10 12:13:18.023 - error: zigbee.3 (171318) undefined 2025-05-10 12:13:18.076 - info: zigbee.3 (171318) cleaned everything up... 2025-05-10 12:13:18.077 - info: zigbee.3 (171318) local config saved 2025-05-10 12:13:18.079 - info: zigbee.3 (171318) Saved local configuration data 2025-05-10 12:13:18.080 - info: zigbee.3 (171318) terminating 2025-05-10 12:13:18.082 - warn: zigbee.3 (171318) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-10 12:13:18.108 - error: zigbee.3 (171318) Failed to open the network: Error: Cannot request when znp has not been initialized yet at Znp.request (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:240:19) at ZStackAdapter.dataRequestExtended (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:1100:24) at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:746:24 at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26) at ZStackAdapter.sendZclFrameToAll (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:744:33) at GreenPower.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/greenPower.ts:591:32) at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-05-10 12:13:18.117 - info: zigbee.3 (171318) terminating 2025-05-10 12:13:18.119 - warn: zigbee.3 (171318) Network parameters in Config : panID=6752 channel=11 extendedPanID=a3c2a022014c1301 2025-05-10 12:13:18.119 - warn: zigbee.3 (171318) Network parameters on Coordinator: panID=6752 channel=11 extendedPanID=00124b00219fc1a2 2025-05-10 12:13:18.128 - error: zigbee.3 (171318) Starting zigbee-herdsman problem : Error while opening socket 2025-05-10 12:13:18.129 - error: zigbee.3 (171318) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-10 12:13:18.129 - error: zigbee.3 (171318) unhandled promise rejection: undefined 2025-05-10 12:13:18.129 - error: zigbee.3 (171318) undefined 2025-05-10 12:13:18.135 - warn: zigbee.3 (171318) Network parameters in Config : panID=6752 channel=11 extendedPanID=a3c2a022014c1301 2025-05-10 12:13:18.136 - warn: zigbee.3 (171318) Network parameters on Coordinator: panID=6752 channel=11 extendedPanID=00124b00219fc1a2 2025-05-10 12:13:18.141 - error: zigbee.3 (171318) Starting zigbee-herdsman problem : Error while opening socket 2025-05-10 12:13:18.142 - error: zigbee.3 (171318) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-10 12:13:18.142 - error: zigbee.3 (171318) unhandled promise rejection: undefined 2025-05-10 12:13:18.142 - error: zigbee.3 (171318) undefined 2025-05-10 12:13:18.153 - info: zigbee.3 (171318) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:18.153 - info: zigbee.3 (171318) Starting Zigbee-Herdsman 2025-05-10 12:13:18.584 - info: zigbee.3 (171318) terminating 2025-05-10 12:13:18.771 - error: host.iob2022 Caught by controller[1]: [2025-05-10T10:13:07.878Z] zh:zstack:znp: Socket error Error: read ETIMEDOUT 2025-05-10 12:13:18.773 - error: host.iob2022 Caught by controller[2]: [2025-05-10T10:13:07.879Z] zh:zstack:znp: Socket error Error: read ETIMEDOUT 2025-05-10 12:13:18.773 - error: host.iob2022 Caught by controller[3]: [2025-05-10T10:13:18.003Z] zh:zstack:znp: Socket error Error: connect EPIPE 192.168.178.130:20108 2025-05-10 12:13:18.773 - error: host.iob2022 Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-10 12:13:18.773 - error: host.iob2022 Caught by controller[5]: Error herdsman start 2025-05-10 12:13:18.774 - error: host.iob2022 Caught by controller[6]: [2025-05-10T10:13:18.118Z] zh:zstack:znp: Socket error Error: connect EPIPE 192.168.178.130:20108 2025-05-10 12:13:18.774 - error: host.iob2022 Caught by controller[7]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-10 12:13:18.774 - error: host.iob2022 Caught by controller[8]: Error herdsman start 2025-05-10 12:13:18.774 - error: host.iob2022 Caught by controller[9]: [2025-05-10T10:13:18.134Z] zh:zstack:znp: Socket error Error: connect EPIPE 192.168.178.130:20108 2025-05-10 12:13:18.774 - error: host.iob2022 Caught by controller[10]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-10 12:13:18.774 - error: host.iob2022 Caught by controller[11]: Error herdsman start 2025-05-10 12:13:18.775 - error: host.iob2022 instance system.adapter.zigbee.3 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-10 12:13:18.775 - info: host.iob2022 Restart adapter system.adapter.zigbee.3 because enabled 2025-05-10 12:13:32.743 - info: admin.0 (752) <== Disconnect system.user.admin from ::ffff:192.168.178.21 javascript 2025-05-10 12:13:49.499 - info: host.iob2022 instance system.adapter.zigbee.3 in version "2.0.5" started with pid 202714 2025-05-10 12:13:52.900 - info: zigbee.3 (202714) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-05-10 12:13:52.928 - info: zigbee.3 (202714) init localConfig 2025-05-10 12:13:52.936 - info: zigbee.3 (202714) --> transmitPower : normal 2025-05-10 12:13:52.950 - info: zigbee.3 (202714) delete old Backup files. keep only last 10 2025-05-10 12:13:52.954 - info: zigbee.3 (202714) --- creating device debug --- 2025-05-10 12:13:52.956 - info: zigbee.3 (202714) Starting Adapter npm ... 2025-05-10 12:13:53.007 - info: zigbee.3 (202714) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-10 12:13:53.009 - info: zigbee.3 (202714) Starting Zigbee-Herdsman 2025-05-10 12:13:54.424 - info: zigbee.3 (202714) Zigbee-Herdsman started successfully with Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2025-05-10 12:13:54.426 - info: zigbee.3 (202714) Unable to disable LED, unsupported function. 2025-05-10 12:13:54.639 - info: zigbee.3 (202714) 0x00158d000444ad85 (addr 48027): MCCGQ11LM - Aqara Door and window sensor (EndDevice) 2025-05-10 12:13:54.829 - info: zigbee.3 (202714) 0x0017880102b31fc2 (addr 18177): 8718696449691 - Philips Hue White A60 Single bulb E27/B22 (Router) 2025-05-10 12:13:54.834 - info: zigbee.3 (202714) 0x00178801030dc382 (addr 57766): 8718696449691 - Philips Hue White A60 Single bulb E27/B22 (Router) 2025-05-10 12:13:54.837 - info: zigbee.3 (202714) 0x00158d00028ecca8 (addr 19476): MCCGQ01LM - Xiaomi Mi door and window sensor (EndDevice) 2025-05-10 12:13:54.840 - info: zigbee.3 (202714) 0x00158d0003f29d41 (addr 60612): RTCGQ11LM - Aqara Motion sensor (EndDevice) 2025-05-10 12:13:54.843 - info: zigbee.3 (202714) 0x00158d00040aa64d (addr 36751): MCCGQ11LM - Aqara Door and window sensor (EndDevice) 2025-05-10 12:13:54.846 - info: zigbee.3 (202714) 0x00158d0003d2dfaf (addr 17235): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-10 12:13:54.849 - info: zigbee.3 (202714) 0x00158d0006795c22 (addr 17235): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-10 12:13:54.853 - info: zigbee.3 (202714) 0x00158d000407fd80 (addr 21659): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-10 12:13:54.857 - info: zigbee.3 (202714) 0x00158d0002f7bfb9 (addr 62255): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-10 12:13:54.874 - info: zigbee.3 (202714) 0x7cb03eaa0a002eb9 (addr 41085): AB3257001NJ - OSRAM Smart+ plug (Router) 2025-05-10 12:13:54.876 - info: zigbee.3 (202714) 0x00158d0002ca12d8 (addr 52694): MCCGQ11LM - Aqara Door and window sensor (EndDevice) 2025-05-10 12:13:54.879 - info: zigbee.3 (202714) 0x00158d000444ac77 (addr 37405): MCCGQ11LM - Aqara Door and window sensor (EndDevice) 2025-05-10 12:13:54.881 - info: zigbee.3 (202714) 0x7cb03eaa00b22528 (addr 17914): AB3257001NJ - OSRAM Smart+ plug (Router) 2025-05-10 12:13:54.883 - info: zigbee.3 (202714) 0x00158d0009d0df86 (addr 42528): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-10 12:13:54.883 - info: zigbee.3 (202714) Currently 15 devices are joined: 2025-05-10 12:13:54.885 - info: zigbee.3 (202714) Zigbee started 2025-05-10 12:13:54.918 - info: zigbee.3 (202714) DeviceConfigure 0x7cb03eaa0a002eb9 AB3257001NJ needed - Device added to Configuration Queue 2025-05-10 12:13:54.966 - info: zigbee.3 (202714) debug devices set to [] 2025-05-10 12:13:56.545 - info: zigbee.3 (202714) Failed to ping 0x0017880102b31fc2 LWB010 2025-05-10 12:13:56.703 - info: zigbee.3 (202714) Failed to ping 0x00178801030dc382 LWB010 2025-05-10 12:13:57.155 - info: zigbee.3 (202714) Failed to ping 0x7cb03eaa0a002eb9 Plug 01 2025-05-10 12:13:59.920 - info: zigbee.3 (202714) DeviceConfigureQueue configuring 0x7cb03eaa0a002eb9 Plug 01 2025-05-10 12:13:59.923 - info: zigbee.3 (202714) Configuring 0x7cb03eaa0a002eb9 AB3257001NJ 2025-05-10 12:14:04.919 - info: zigbee.3 (202714) Handled all devices Queued for configuration. -
@andreas-s sagte in Zigbee Instanzen stürzen alle paar Tage ab:
Netzwerkprobleme im IP-Netzwerk würde ich eher nicht erwarten. Die CC2642R1 sind per Kabel angebunden und immer erreichbar.
Da überschätzt du das Netzwerk gewaltig.Das ist auch nicht weiter verwunderlich. Die wenigsten machen sich darüber Gedanken das es bei einem Paket-Basierten Protokoll auch mal passieren kann das Pakete 'out of order' ankommen. Das bildet das Protokoll ab, und Dienste die darauf aufsetzen müssen damit umgehen können. Unter anderem auch darum wird z.Bsp. beim Streaming mit 'puffern' gearbeitet - so das der Client den kontinuierlichen Stream aus den Paketen zusammensetzen kann.
So etwas kann schnell passieren - einfach durch Periodisierungen auf OS / Protokoll / Netzwerk Ebene. Ich spreche da (leider) aus Erfahrung. Der Versuch eine teure Multi-Schnittstellenkarte durch eine via TCP/IP angebundene Serielle Box zu ersetzen hat immer wieder zu Kommunikationsproblemen mit der externen Hardware geführt - selbst als auf der Rechner-Seite eine dedizierte Netzwerkkarte mit aktivem Netzwerkchip eingesetzt wurde (im Gegensatz zu günstigen Netzwerk-Adaptern bei denen der Chip zwar die Hardware ansteuert, das gesamte Protokoll aber in Software vom Prozessor des Rechners gesteuert wird. Die Firma hat dadurch einiges an Zeit und Geld in den Sand gesetzt, und den Versuch letztendlich dann auch begraben und setzt statt dessen wieder auf PCIE-Multiserielle Karten.
Letztendlich hat uns das gezeigt das eine auf TCP-Ebene nachweisbare Erreichbarkeit nicht immer hinreichend ist um sicher zu stellen das RS232 via Ethernet sauber läuft.
A.
-
@asgothian
Zu Netzwerken habe ich absolut kein Hintergrundwissen, schon gar nicht in der Tiefe.Ich werde nun einfach beobachten was passiert, wenn das Skript auslöst. Wenn durch den Reboot ein automatischer Connect erfolgreich ist, wäre ich absolut zufrieden.
-
@andreas-s sagte in Zigbee Instanzen stürzen alle paar Tage ab:
Wenn durch den Reboot ein automatischer Connect erfolgreich ist, wäre ich absolut zufrieden.
Ich hoffe das das klappt.
A.
-
@asgothian
Heute habe ich im Protokoll einen Abbruch gefunden. Das Skript hat ausgelöst und aktuell ist der Adapter grünABER
Eine Unmenge von Fehlern im Protokoll, die ich nicht verstehe bis hin zum Log Eintrag "Fehler beim Reboot-Request" aus meinem Logging im Java Skript.
Das Skript hatte ich aber getestet, um sicherzustellen, dass es den Reboot auslöst, lasse aber natürlich auch im Fehlerfall einen Log-Eintrag wegschreiben.request.on("error", (err) => { console.error("Fehler beim Reboot-Request:", err.message); });So sieht das Protokoll aus.
2025-05-11 00:35:14.481 - error: zigbee.3 (202714) Adapter disconnected, stopping 2025-05-11 00:35:14.597 - info: javascript.0 (886) script.js.Javaskripte.Zigbee_3_Reboot: Zigbee Verbindung verloren – Reboot wird ausgelöst… 2025-05-11 00:35:24.571 - info: zigbee.3 (202714) Try to reconnect. 2025-05-11 00:35:24.574 - info: zigbee.3 (202714) Starting Adapter npm ... 2025-05-11 00:35:24.581 - info: zigbee.3 (202714) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-11 00:35:24.582 - info: zigbee.3 (202714) Starting Zigbee-Herdsman 2025-05-11 00:36:18.827 - warn: zigbee.3 (202714) Network parameters in Config : panID=6752 channel=11 extendedPanID=a3c2a022014c1301 2025-05-11 00:36:18.828 - warn: zigbee.3 (202714) Network parameters on Coordinator: panID=6752 channel=11 extendedPanID=00124b00219fc1a2 2025-05-11 00:36:18.887 - error: zigbee.3 (202714) Starting zigbee-herdsman problem : Cannot read properties of null (reading 'key') 2025-05-11 00:36:18.917 - error: zigbee.3 (202714) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-11 00:36:18.918 - error: zigbee.3 (202714) unhandled promise rejection: undefined 2025-05-11 00:36:18.918 - error: zigbee.3 (202714) undefined 2025-05-11 00:36:18.967 - info: zigbee.3 (202714) cleaned everything up... 2025-05-11 00:36:18.968 - info: zigbee.3 (202714) local config saved 2025-05-11 00:36:18.970 - info: zigbee.3 (202714) Saved local configuration data 2025-05-11 00:36:18.971 - info: zigbee.3 (202714) terminating 2025-05-11 00:36:18.974 - warn: zigbee.3 (202714) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-11 00:36:19.002 - error: zigbee.3 (202714) Failed to open the network: Error: Cannot request when znp has not been initialized yet at Znp.request (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:240:19) at ZStackAdapter.dataRequestExtended (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:1100:24) at /opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:746:24 at Queue.execute (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26) at ZStackAdapter.sendZclFrameToAll (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:744:33) at GreenPower.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/greenPower.ts:591:32) at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) 2025-05-11 00:36:19.009 - info: zigbee.3 (202714) terminating 2025-05-11 00:36:19.476 - info: zigbee.3 (202714) terminating 2025-05-11 00:36:19.656 - error: host.iob2022 Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-11 00:36:19.656 - error: host.iob2022 Caught by controller[2]: Error herdsman start 2025-05-11 00:36:19.657 - error: host.iob2022 instance system.adapter.zigbee.3 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-11 00:36:19.657 - info: host.iob2022 Restart adapter system.adapter.zigbee.3 because enabled 2025-05-11 00:36:28.627 - info: broadlink2.0 (1010) interface to be used: { netmaskBits: 24, address: '192.168.178.74/24', addrs: [ 192, 168, 178, 74 ], cidr: '192.168.178.74/24', bcaddr: '192.168.178.255' }: 2025-05-11 00:36:28.628 - info: broadlink2.0 (1010) discover [ '192.168.178.100' ] from 0.0.0.0:49518 2025-05-11 00:36:50.499 - info: host.iob2022 instance system.adapter.zigbee.3 in version "2.0.5" started with pid 210157 2025-05-11 00:36:53.774 - info: zigbee.3 (210157) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-05-11 00:36:53.802 - info: zigbee.3 (210157) init localConfig 2025-05-11 00:36:53.810 - info: zigbee.3 (210157) --> transmitPower : normal 2025-05-11 00:36:53.823 - info: zigbee.3 (210157) delete old Backup files. keep only last 10 2025-05-11 00:36:53.828 - info: zigbee.3 (210157) --- creating device debug --- 2025-05-11 00:36:53.829 - info: zigbee.3 (210157) Starting Adapter npm ... 2025-05-11 00:36:53.881 - info: zigbee.3 (210157) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-11 00:36:53.883 - info: zigbee.3 (210157) Starting Zigbee-Herdsman 2025-05-11 00:37:27.902 - info: sonoff.0 (1112) Client [Sonoff-1079] reconnected. Old secret 1746916418590_8309 ==> New secret 1746916647902_9901 2025-05-11 00:37:28.633 - info: broadlink2.0 (1010) interface to be used: { netmaskBits: 24, address: '192.168.178.74/24', addrs: [ 192, 168, 178, 74 ], cidr: '192.168.178.74/24', bcaddr: '192.168.178.255' }: 2025-05-11 00:37:41.628 - info: zigbee.3 (210157) Unable to obtain herdsman settings 2025-05-11 00:37:41.860 - error: zigbee.3 (210157) Starting zigbee-herdsman problem : Cannot read properties of null (reading 'length') 2025-05-11 00:37:41.862 - error: zigbee.3 (210157) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-11 00:37:41.862 - error: zigbee.3 (210157) unhandled promise rejection: undefined 2025-05-11 00:37:41.864 - error: zigbee.3 (210157) undefined 2025-05-11 00:37:41.918 - info: zigbee.3 (210157) cleaned everything up... 2025-05-11 00:37:41.921 - info: zigbee.3 (210157) local config saved 2025-05-11 00:37:41.923 - info: zigbee.3 (210157) Saved local configuration data 2025-05-11 00:37:41.925 - info: zigbee.3 (210157) terminating 2025-05-11 00:37:41.927 - warn: zigbee.3 (210157) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-11 00:37:42.238 - error: zigbee.3 (210157) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17) 2025-05-11 00:37:42.250 - info: zigbee.3 (210157) terminating 2025-05-11 00:37:42.253 - warn: zigbee.3 (210157) Device 0x00158d000444ad85 "MCCGQ11LM" not found. 2025-05-11 00:37:42.254 - warn: zigbee.3 (210157) Device 0x0017880102b31fc2 "8718696449691" not found. 2025-05-11 00:37:42.255 - warn: zigbee.3 (210157) Device 0x00178801030dc382 "8718696449691" not found. 2025-05-11 00:37:42.256 - warn: zigbee.3 (210157) Device 0x00158d00028ecca8 "MCCGQ01LM" not found. 2025-05-11 00:37:42.257 - warn: zigbee.3 (210157) Device 0x00158d0003f29d41 "RTCGQ11LM" not found. 2025-05-11 00:37:42.258 - warn: zigbee.3 (210157) Device 0x00158d00040aa64d "MCCGQ11LM" not found. 2025-05-11 00:37:42.258 - warn: zigbee.3 (210157) Device 0x00158d0003d2dfaf "WSDCGQ11LM" not found. 2025-05-11 00:37:42.259 - warn: zigbee.3 (210157) Device 0x00158d0006795c22 "WSDCGQ11LM" not found. 2025-05-11 00:37:42.259 - warn: zigbee.3 (210157) Device 0x00158d000407fd80 "WSDCGQ11LM" not found. 2025-05-11 00:37:42.261 - warn: zigbee.3 (210157) Device 0x00158d0002f7bfb9 "WSDCGQ11LM" not found. 2025-05-11 00:37:42.262 - warn: zigbee.3 (210157) Device 0x7cb03eaa0a002eb9 "AB3257001NJ" not found. 2025-05-11 00:37:42.262 - warn: zigbee.3 (210157) Device 0x00158d0002ca12d8 "MCCGQ11LM" not found. 2025-05-11 00:37:42.263 - warn: zigbee.3 (210157) Device 0x00158d000444ac77 "MCCGQ11LM" not found. 2025-05-11 00:37:42.264 - warn: zigbee.3 (210157) Device 0x7cb03eaa00b22528 "AB3257001NJ" not found. 2025-05-11 00:37:42.264 - warn: zigbee.3 (210157) Device 0x00158d0009d0df86 "WSDCGQ11LM" not found. 2025-05-11 00:37:42.392 - info: zigbee.3 (210157) debug devices set to [] 2025-05-11 00:37:42.680 - info: zigbee.3 (210157) terminating 2025-05-11 00:37:42.938 - error: host.iob2022 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-11 00:37:42.939 - error: host.iob2022 Caught by controller[1]: Error herdsman start 2025-05-11 00:37:42.940 - error: host.iob2022 Caught by controller[2]: [ioredis] Unhandled error event: Error: write EPIPE 2025-05-11 00:37:42.940 - error: host.iob2022 Caught by controller[2]: at afterWriteDispatched (node:internal/stream_base_commons:161:15) 2025-05-11 00:37:42.940 - error: host.iob2022 Caught by controller[2]: at writeGeneric (node:internal/stream_base_commons:152:3) 2025-05-11 00:37:42.940 - error: host.iob2022 Caught by controller[2]: at Socket._writeGeneric (node:net:958:11) 2025-05-11 00:37:42.940 - error: host.iob2022 Caught by controller[2]: at Socket._write (node:net:970:8) 2025-05-11 00:37:42.940 - error: host.iob2022 Caught by controller[2]: at writeOrBuffer (node:internal/streams/writable:572:12) 2025-05-11 00:37:42.940 - error: host.iob2022 Caught by controller[2]: at _write (node:internal/streams/writable:501:10) 2025-05-11 00:37:42.941 - error: host.iob2022 Caught by controller[2]: at Socket.Writable.write (node:internal/streams/writable:510:10) 2025-05-11 00:37:42.943 - error: host.iob2022 Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33) 2025-05-11 00:37:42.944 - error: host.iob2022 Caught by controller[2]: at Redis.set (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2025-05-11 00:37:42.944 - error: host.iob2022 Caught by controller[2]: at StateRedisClient.setState (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:809:35) 2025-05-11 00:37:42.944 - error: host.iob2022 instance system.adapter.zigbee.3 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-11 00:37:42.945 - info: host.iob2022 Restart adapter system.adapter.zigbee.3 because enabled 2025-05-11 00:38:13.848 - info: host.iob2022 instance system.adapter.zigbee.3 in version "2.0.5" started with pid 210174 2025-05-11 00:38:17.189 - info: zigbee.3 (210174) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-05-11 00:38:17.221 - info: zigbee.3 (210174) init localConfig 2025-05-11 00:38:17.230 - info: zigbee.3 (210174) --> transmitPower : normal 2025-05-11 00:38:17.243 - info: zigbee.3 (210174) delete old Backup files. keep only last 10 2025-05-11 00:38:17.248 - info: zigbee.3 (210174) --- creating device debug --- 2025-05-11 00:38:17.249 - info: zigbee.3 (210174) Starting Adapter npm ... 2025-05-11 00:38:17.297 - info: zigbee.3 (210174) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-11 00:38:17.299 - info: zigbee.3 (210174) Starting Zigbee-Herdsman 2025-05-11 00:38:28.825 - info: zigbee.3 (210174) Zigbee-Herdsman started successfully with Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}} 2025-05-11 00:38:28.828 - info: zigbee.3 (210174) Unable to disable LED, unsupported function. 2025-05-11 00:38:28.995 - info: zigbee.3 (210174) 0x00158d000444ad85 (addr 48027): MCCGQ11LM - Aqara Door and window sensor (EndDevice) 2025-05-11 00:38:29.146 - info: zigbee.3 (210174) 0x0017880102b31fc2 (addr 18177): 8718696449691 - Philips Hue White A60 Single bulb E27/B22 (Router) 2025-05-11 00:38:29.151 - info: zigbee.3 (210174) 0x00178801030dc382 (addr 57766): 8718696449691 - Philips Hue White A60 Single bulb E27/B22 (Router) 2025-05-11 00:38:29.154 - info: zigbee.3 (210174) 0x00158d00028ecca8 (addr 19476): MCCGQ01LM - Xiaomi Mi door and window sensor (EndDevice) 2025-05-11 00:38:29.157 - info: zigbee.3 (210174) 0x00158d0003f29d41 (addr 60612): RTCGQ11LM - Aqara Motion sensor (EndDevice) 2025-05-11 00:38:29.162 - info: zigbee.3 (210174) 0x00158d00040aa64d (addr 36751): MCCGQ11LM - Aqara Door and window sensor (EndDevice) 2025-05-11 00:38:29.166 - info: zigbee.3 (210174) 0x00158d0003d2dfaf (addr 17235): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-11 00:38:29.170 - info: zigbee.3 (210174) 0x00158d0006795c22 (addr 17235): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-11 00:38:29.174 - info: zigbee.3 (210174) 0x00158d000407fd80 (addr 21659): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-11 00:38:29.179 - info: zigbee.3 (210174) 0x00158d0002f7bfb9 (addr 62255): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-11 00:38:29.199 - info: zigbee.3 (210174) 0x7cb03eaa0a002eb9 (addr 41085): AB3257001NJ - OSRAM Smart+ plug (Router) 2025-05-11 00:38:29.204 - info: zigbee.3 (210174) 0x00158d0002ca12d8 (addr 52694): MCCGQ11LM - Aqara Door and window sensor (EndDevice) 2025-05-11 00:38:29.208 - info: zigbee.3 (210174) 0x00158d000444ac77 (addr 37405): MCCGQ11LM - Aqara Door and window sensor (EndDevice) 2025-05-11 00:38:29.210 - info: zigbee.3 (210174) 0x7cb03eaa00b22528 (addr 17914): AB3257001NJ - OSRAM Smart+ plug (Router) 2025-05-11 00:38:29.212 - info: zigbee.3 (210174) 0x00158d0009d0df86 (addr 42528): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice) 2025-05-11 00:38:29.212 - info: zigbee.3 (210174) Currently 15 devices are joined: 2025-05-11 00:38:29.215 - info: zigbee.3 (210174) Zigbee started 2025-05-11 00:38:29.253 - info: zigbee.3 (210174) DeviceConfigure 0x7cb03eaa0a002eb9 AB3257001NJ needed - Device added to Configuration Queue 2025-05-11 00:38:29.298 - info: zigbee.3 (210174) debug devices set to [] 2025-05-11 00:38:30.974 - info: zigbee.3 (210174) Failed to ping 0x0017880102b31fc2 LWB010 2025-05-11 00:38:31.094 - info: zigbee.3 (210174) Failed to ping 0x00178801030dc382 LWB010 2025-05-11 00:38:31.473 - info: zigbee.3 (210174) Failed to ping 0x7cb03eaa0a002eb9 Plug 01 2025-05-11 00:38:34.257 - info: zigbee.3 (210174) DeviceConfigureQueue configuring 0x7cb03eaa0a002eb9 Plug 01 2025-05-11 00:38:34.260 - info: zigbee.3 (210174) Configuring 0x7cb03eaa0a002eb9 AB3257001NJ 2025-05-11 00:38:39.257 - info: zigbee.3 (210174) Handled all devices Queued for configuration. 2025-05-11 00:38:44.368 - info: zigbee.3 (210174) Timeout trying to configure 0x7cb03eaa0a002eb9 AB3257001NJ (starting CoM). 2025-05-11 00:52:46.888 - error: javascript.0 (886) script.js.Javaskripte.Zigbee_3_Reboot: Fehler beim Reboot-Request: -
@andreas-s
Da muss ich mir noch was überlegen.
Heute ist der Adapter ausgestiegen, beginnend mit "Unhandled promise rejection"?
Mein Java-Skript zum Reboot hat erst eine halbe Minute später ausgelöst, während IOB versucht hat den Adapter neu zu starten.
Dann ging das in einen Schleife und wurde abgebrochen. (Restart loop detected)
Manueller Stopp und Neustart = Problemlos.2025-05-13 06:19:29.553 - error: zigbee.3 (229055) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-13 06:19:29.557 - error: zigbee.3 (229055) unhandled promise rejection: Cannot read properties of undefined (reading 'payload') 2025-05-13 06:19:29.624 - error: zigbee.3 (229055) TypeError: Cannot read properties of undefined (reading 'payload') at AdapterNvMemory.readExtendedTableEntry (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/adapter-nv-memory.ts:208:39) at AdapterNvMemory.readTable (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/adapter-nv-memory.ts:366:28) at AdapterBackup.getTclkTable (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/adapter-backup.ts:497:20) at AdapterBackup.createBackup (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/adapter-backup.ts:119:27) at ZStackAdapter.backup (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:908:16) at Controller.backup (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:382:28) 2025-05-13 06:19:29.625 - error: zigbee.3 (229055) Cannot read properties of undefined (reading 'payload') 2025-05-13 06:19:29.656 - info: zigbee.3 (229055) cleaned everything up... 2025-05-13 06:19:29.657 - info: zigbee.3 (229055) local config saved 2025-05-13 06:19:29.658 - info: zigbee.3 (229055) Saved local configuration data 2025-05-13 06:19:29.659 - info: zigbee.3 (229055) terminating 2025-05-13 06:19:29.660 - warn: zigbee.3 (229055) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-13 06:19:30.162 - info: zigbee.3 (229055) terminating 2025-05-13 06:19:30.343 - error: host.iob2022 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-13 06:19:30.344 - error: host.iob2022 Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'payload') 2025-05-13 06:19:30.345 - error: host.iob2022 Caught by controller[1]: at AdapterNvMemory.readExtendedTableEntry (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/adapter-nv-memory.ts:208:39) 2025-05-13 06:19:30.345 - error: host.iob2022 Caught by controller[1]: at AdapterNvMemory.readTable (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/adapter-nv-memory.ts:366:28) 2025-05-13 06:19:30.345 - error: host.iob2022 Caught by controller[1]: at AdapterBackup.getTclkTable (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/adapter-backup.ts:497:20) 2025-05-13 06:19:30.345 - error: host.iob2022 Caught by controller[1]: at AdapterBackup.createBackup (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/adapter-backup.ts:119:27) 2025-05-13 06:19:30.345 - error: host.iob2022 Caught by controller[1]: at ZStackAdapter.backup (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:908:16) 2025-05-13 06:19:30.345 - error: host.iob2022 Caught by controller[1]: at Controller.backup (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:382:28) 2025-05-13 06:19:30.346 - error: host.iob2022 instance system.adapter.zigbee.3 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-13 06:19:30.346 - info: host.iob2022 Restart adapter system.adapter.zigbee.3 because enabled 2025-05-13 06:20:01.233 - info: host.iob2022 instance system.adapter.zigbee.3 in version "2.0.5" started with pid 244227 2025-05-13 06:20:04.437 - info: zigbee.3 (244227) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-05-13 06:20:04.464 - info: zigbee.3 (244227) init localConfig 2025-05-13 06:20:04.473 - info: zigbee.3 (244227) --> transmitPower : normal 2025-05-13 06:20:04.486 - info: zigbee.3 (244227) delete old Backup files. keep only last 10 2025-05-13 06:20:04.490 - info: zigbee.3 (244227) --- creating device debug --- 2025-05-13 06:20:04.492 - info: zigbee.3 (244227) Starting Adapter npm ... 2025-05-13 06:20:04.535 - info: zigbee.3 (244227) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-13 06:20:04.537 - info: zigbee.3 (244227) Starting Zigbee-Herdsman 2025-05-13 06:20:04.670 - info: javascript.0 (886) script.js.Javaskripte.Zigbee_3_Reboot: Zigbee Verbindung verloren – Reboot wird ausgelöst… 2025-05-13 06:20:08.747 - info: javascript.0 (886) script.js.Javaskripte.Zigbee_3_Reboot: Reboot-Request Status: 2025-05-13 06:20:30.718 - info: zigbee.3 (244227) Unable to obtain herdsman settings 2025-05-13 06:20:30.928 - error: zigbee.3 (244227) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms) 2025-05-13 06:20:30.929 - error: zigbee.3 (244227) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-13 06:20:30.930 - error: zigbee.3 (244227) unhandled promise rejection: undefined 2025-05-13 06:20:30.931 - error: zigbee.3 (244227) undefined 2025-05-13 06:20:30.981 - info: zigbee.3 (244227) cleaned everything up... 2025-05-13 06:20:30.982 - info: zigbee.3 (244227) local config saved 2025-05-13 06:20:30.984 - info: zigbee.3 (244227) Saved local configuration data 2025-05-13 06:20:30.986 - info: zigbee.3 (244227) terminating 2025-05-13 06:20:30.987 - warn: zigbee.3 (244227) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-13 06:20:31.281 - error: zigbee.3 (244227) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17) 2025-05-13 06:20:31.294 - info: zigbee.3 (244227) terminating 2025-05-13 06:20:31.296 - warn: zigbee.3 (244227) Device 0x00158d000444ad85 "MCCGQ11LM" not found. 2025-05-13 06:20:31.297 - warn: zigbee.3 (244227) Device 0x0017880102b31fc2 "8718696449691" not found. 2025-05-13 06:20:31.298 - warn: zigbee.3 (244227) Device 0x00178801030dc382 "8718696449691" not found. 2025-05-13 06:20:31.299 - warn: zigbee.3 (244227) Device 0x00158d00028ecca8 "MCCGQ01LM" not found. 2025-05-13 06:20:31.300 - warn: zigbee.3 (244227) Device 0x00158d0003f29d41 "RTCGQ11LM" not found. 2025-05-13 06:20:31.300 - warn: zigbee.3 (244227) Device 0x00158d00040aa64d "MCCGQ11LM" not found. 2025-05-13 06:20:31.301 - warn: zigbee.3 (244227) Device 0x00158d0003d2dfaf "WSDCGQ11LM" not found. 2025-05-13 06:20:31.301 - warn: zigbee.3 (244227) Device 0x00158d0006795c22 "WSDCGQ11LM" not found. 2025-05-13 06:20:31.302 - warn: zigbee.3 (244227) Device 0x00158d000407fd80 "WSDCGQ11LM" not found. 2025-05-13 06:20:31.303 - warn: zigbee.3 (244227) Device 0x00158d0002f7bfb9 "WSDCGQ11LM" not found. 2025-05-13 06:20:31.304 - warn: zigbee.3 (244227) Device 0x7cb03eaa0a002eb9 "AB3257001NJ" not found. 2025-05-13 06:20:31.305 - warn: zigbee.3 (244227) Device 0x00158d0002ca12d8 "MCCGQ11LM" not found. 2025-05-13 06:20:31.305 - warn: zigbee.3 (244227) Device 0x00158d000444ac77 "MCCGQ11LM" not found. 2025-05-13 06:20:31.306 - warn: zigbee.3 (244227) Device 0x7cb03eaa00b22528 "AB3257001NJ" not found. 2025-05-13 06:20:31.306 - warn: zigbee.3 (244227) Device 0x00158d0009d0df86 "WSDCGQ11LM" not found. 2025-05-13 06:20:31.391 - info: zigbee.3 (244227) debug devices set to [] 2025-05-13 06:20:31.677 - info: zigbee.3 (244227) terminating 2025-05-13 06:20:31.873 - error: host.iob2022 Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-13 06:20:31.874 - error: host.iob2022 Caught by controller[1]: Error herdsman start 2025-05-13 06:20:31.874 - error: host.iob2022 instance system.adapter.zigbee.3 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-13 06:20:31.874 - info: host.iob2022 Restart adapter system.adapter.zigbee.3 because enabled 2025-05-13 06:21:02.819 - info: host.iob2022 instance system.adapter.zigbee.3 in version "2.0.5" started with pid 244244 2025-05-13 06:21:06.102 - info: zigbee.3 (244244) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-05-13 06:21:06.130 - info: zigbee.3 (244244) init localConfig 2025-05-13 06:21:06.138 - info: zigbee.3 (244244) --> transmitPower : normal 2025-05-13 06:21:06.151 - info: zigbee.3 (244244) delete old Backup files. keep only last 10 2025-05-13 06:21:06.156 - info: zigbee.3 (244244) --- creating device debug --- 2025-05-13 06:21:06.157 - info: zigbee.3 (244244) Starting Adapter npm ... 2025-05-13 06:21:06.207 - info: zigbee.3 (244244) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-05-13 06:21:06.209 - info: zigbee.3 (244244) Starting Zigbee-Herdsman 2025-05-13 06:21:09.418 - info: zigbee.3 (244244) Unable to obtain herdsman settings 2025-05-13 06:21:09.503 - error: zigbee.3 (244244) Starting zigbee-herdsman problem : Error while opening socket 2025-05-13 06:21:09.506 - error: zigbee.3 (244244) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-05-13 06:21:09.506 - error: zigbee.3 (244244) unhandled promise rejection: undefined 2025-05-13 06:21:09.507 - error: zigbee.3 (244244) undefined 2025-05-13 06:21:09.554 - info: zigbee.3 (244244) cleaned everything up... 2025-05-13 06:21:09.555 - info: zigbee.3 (244244) local config saved 2025-05-13 06:21:09.557 - info: zigbee.3 (244244) Saved local configuration data 2025-05-13 06:21:09.559 - info: zigbee.3 (244244) terminating 2025-05-13 06:21:09.561 - warn: zigbee.3 (244244) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-05-13 06:21:09.848 - error: zigbee.3 (244244) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17) 2025-05-13 06:21:09.861 - info: zigbee.3 (244244) terminating 2025-05-13 06:21:09.863 - warn: zigbee.3 (244244) Device 0x00158d000444ad85 "MCCGQ11LM" not found. 2025-05-13 06:21:09.864 - warn: zigbee.3 (244244) Device 0x0017880102b31fc2 "8718696449691" not found. 2025-05-13 06:21:09.865 - warn: zigbee.3 (244244) Device 0x00178801030dc382 "8718696449691" not found. 2025-05-13 06:21:09.866 - warn: zigbee.3 (244244) Device 0x00158d00028ecca8 "MCCGQ01LM" not found. 2025-05-13 06:21:09.866 - warn: zigbee.3 (244244) Device 0x00158d0003f29d41 "RTCGQ11LM" not found. 2025-05-13 06:21:09.867 - warn: zigbee.3 (244244) Device 0x00158d00040aa64d "MCCGQ11LM" not found. 2025-05-13 06:21:09.868 - warn: zigbee.3 (244244) Device 0x00158d0003d2dfaf "WSDCGQ11LM" not found. 2025-05-13 06:21:09.868 - warn: zigbee.3 (244244) Device 0x00158d0006795c22 "WSDCGQ11LM" not found. 2025-05-13 06:21:09.869 - warn: zigbee.3 (244244) Device 0x00158d000407fd80 "WSDCGQ11LM" not found. 2025-05-13 06:21:09.870 - warn: zigbee.3 (244244) Device 0x00158d0002f7bfb9 "WSDCGQ11LM" not found. 2025-05-13 06:21:09.871 - warn: zigbee.3 (244244) Device 0x7cb03eaa0a002eb9 "AB3257001NJ" not found. 2025-05-13 06:21:09.872 - warn: zigbee.3 (244244) Device 0x00158d0002ca12d8 "MCCGQ11LM" not found. 2025-05-13 06:21:09.872 - warn: zigbee.3 (244244) Device 0x00158d000444ac77 "MCCGQ11LM" not found. 2025-05-13 06:21:09.873 - warn: zigbee.3 (244244) Device 0x7cb03eaa00b22528 "AB3257001NJ" not found. 2025-05-13 06:21:09.873 - warn: zigbee.3 (244244) Device 0x00158d0009d0df86 "WSDCGQ11LM" not found. 2025-05-13 06:21:09.922 - info: zigbee.3 (244244) debug devices set to [] 2025-05-13 06:21:10.189 - info: zigbee.3 (244244) terminating 2025-05-13 06:21:10.265 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000444ad85.available: DB closed 2025-05-13 06:21:10.265 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000444ad85.link_quality: DB closed 2025-05-13 06:21:10.266 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000444ad85.link_quality: DB closed 2025-05-13 06:21:10.266 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.0017880102b31fc2.available: DB closed 2025-05-13 06:21:10.267 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.0017880102b31fc2.available: DB closed 2025-05-13 06:21:10.268 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.0017880102b31fc2.link_quality: DB closed 2025-05-13 06:21:10.269 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.0017880102b31fc2.link_quality: DB closed 2025-05-13 06:21:10.269 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00178801030dc382.available: DB closed 2025-05-13 06:21:10.270 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00178801030dc382.available: DB closed 2025-05-13 06:21:10.270 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00178801030dc382.link_quality: DB closed 2025-05-13 06:21:10.271 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00178801030dc382.link_quality: DB closed 2025-05-13 06:21:10.272 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d00028ecca8.available: DB closed 2025-05-13 06:21:10.272 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d00028ecca8.available: DB closed 2025-05-13 06:21:10.273 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d00028ecca8.link_quality: DB closed 2025-05-13 06:21:10.273 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d00028ecca8.link_quality: DB closed 2025-05-13 06:21:10.274 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0003f29d41.available: DB closed 2025-05-13 06:21:10.275 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0003f29d41.available: DB closed 2025-05-13 06:21:10.275 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0003f29d41.link_quality: DB closed 2025-05-13 06:21:10.276 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0003f29d41.link_quality: DB closed 2025-05-13 06:21:10.277 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d00040aa64d.available: DB closed 2025-05-13 06:21:10.277 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d00040aa64d.available: DB closed 2025-05-13 06:21:10.278 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d00040aa64d.link_quality: DB closed 2025-05-13 06:21:10.279 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d00040aa64d.link_quality: DB closed 2025-05-13 06:21:10.280 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0003d2dfaf.available: DB closed 2025-05-13 06:21:10.281 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0003d2dfaf.available: DB closed 2025-05-13 06:21:10.281 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0003d2dfaf.link_quality: DB closed 2025-05-13 06:21:10.282 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0003d2dfaf.link_quality: DB closed 2025-05-13 06:21:10.284 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0006795c22.available: DB closed 2025-05-13 06:21:10.285 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0006795c22.available: DB closed 2025-05-13 06:21:10.286 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0006795c22.link_quality: DB closed 2025-05-13 06:21:10.287 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0006795c22.link_quality: DB closed 2025-05-13 06:21:10.288 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000407fd80.available: DB closed 2025-05-13 06:21:10.288 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000407fd80.available: DB closed 2025-05-13 06:21:10.289 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000407fd80.link_quality: DB closed 2025-05-13 06:21:10.290 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000407fd80.link_quality: DB closed 2025-05-13 06:21:10.290 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0002f7bfb9.available: DB closed 2025-05-13 06:21:10.291 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0002f7bfb9.available: DB closed 2025-05-13 06:21:10.292 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0002f7bfb9.link_quality: DB closed 2025-05-13 06:21:10.293 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0002f7bfb9.link_quality: DB closed 2025-05-13 06:21:10.294 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.7cb03eaa0a002eb9.available: DB closed 2025-05-13 06:21:10.294 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.7cb03eaa0a002eb9.available: DB closed 2025-05-13 06:21:10.295 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.7cb03eaa0a002eb9.link_quality: DB closed 2025-05-13 06:21:10.296 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.7cb03eaa0a002eb9.link_quality: DB closed 2025-05-13 06:21:10.296 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0002ca12d8.available: DB closed 2025-05-13 06:21:10.297 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0002ca12d8.available: DB closed 2025-05-13 06:21:10.298 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0002ca12d8.link_quality: DB closed 2025-05-13 06:21:10.299 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0002ca12d8.link_quality: DB closed 2025-05-13 06:21:10.299 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000444ac77.available: DB closed 2025-05-13 06:21:10.300 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000444ac77.available: DB closed 2025-05-13 06:21:10.300 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000444ac77.link_quality: DB closed 2025-05-13 06:21:10.300 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d000444ac77.link_quality: DB closed 2025-05-13 06:21:10.301 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.7cb03eaa00b22528.available: DB closed 2025-05-13 06:21:10.302 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.7cb03eaa00b22528.available: DB closed 2025-05-13 06:21:10.302 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.7cb03eaa00b22528.link_quality: DB closed 2025-05-13 06:21:10.303 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.7cb03eaa00b22528.link_quality: DB closed 2025-05-13 06:21:10.304 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0009d0df86.available: DB closed 2025-05-13 06:21:10.304 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0009d0df86.available: DB closed 2025-05-13 06:21:10.305 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0009d0df86.link_quality: DB closed 2025-05-13 06:21:10.306 - warn: zigbee.3 (244244) Could not perform strict object check of state zigbee.3.00158d0009d0df86.link_quality: DB closed 2025-05-13 06:21:10.432 - error: host.iob2022 Caught by controller[0]: [2025-05-13T04:21:09.417Z] zh:zstack:znp: Socket error Error: connect EHOSTUNREACH 192.168.178.130:20108 2025-05-13 06:21:10.433 - error: host.iob2022 Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2025-05-13 06:21:10.433 - error: host.iob2022 Caught by controller[2]: Error herdsman start 2025-05-13 06:21:10.433 - error: host.iob2022 Caught by controller[3]: [ioredis] Unhandled error event: Error: write EPIPE 2025-05-13 06:21:10.433 - error: host.iob2022 Caught by controller[3]: at afterWriteDispatched (node:internal/stream_base_commons:161:15) 2025-05-13 06:21:10.433 - error: host.iob2022 Caught by controller[3]: at writeGeneric (node:internal/stream_base_commons:152:3) 2025-05-13 06:21:10.433 - error: host.iob2022 Caught by controller[3]: at Socket._writeGeneric (node:net:958:11) 2025-05-13 06:21:10.434 - error: host.iob2022 Caught by controller[3]: at Socket._write (node:net:970:8) 2025-05-13 06:21:10.434 - error: host.iob2022 Caught by controller[3]: at writeOrBuffer (node:internal/streams/writable:572:12) 2025-05-13 06:21:10.434 - error: host.iob2022 Caught by controller[3]: at _write (node:internal/streams/writable:501:10) 2025-05-13 06:21:10.434 - error: host.iob2022 Caught by controller[3]: at Socket.Writable.write (node:internal/streams/writable:510:10) 2025-05-13 06:21:10.434 - error: host.iob2022 Caught by controller[3]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:679:33) 2025-05-13 06:21:10.434 - error: host.iob2022 Caught by controller[3]: at Redis.publish (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) 2025-05-13 06:21:10.434 - error: host.iob2022 Caught by controller[3]: at StateRedisClient.setState (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:813:35) 2025-05-13 06:21:10.434 - error: host.iob2022 instance system.adapter.zigbee.3 terminated with code 6 (UNCAUGHT_EXCEPTION) 2025-05-13 06:21:10.435 - info: host.iob2022 Restart adapter system.adapter.zigbee.3 because enabled 2025-05-13 06:21:10.435 - warn: host.iob2022 Do not restart adapter system.adapter.zigbee.3 because restart loop detected -
@andreas-s Offensichtlich braucht der Koordinator zeit zum Booten - jedenfalls beschwert sich der Adapter darüber das keine Verbindung zur Firmware auf dem Koordinator aufgebaut werden kann.
Siehe hier:
2025-05-13 06:20:30.928 - error: zigbee.3 (244227) Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)Ich würde empfehlen den folgenden Ablauf zu nutzen wenn ein Disconnect aufgetreten ist:
- Entsprechende Zigbee Instanz (via Skript) Anhalten
- Koordinator neu starten
- 30 Sekunden Warten
- Zigbee Instanz (via Skript) wieder starten.
Wobei ich Dir nicht sagen kann wie das starten / anhalten via Skript geht.
A.
Nachtrag: Versuch bitte ein Update auf die aktuelle 'latest' Version (3.0.1) - da hat sich am Neustart-Verhalten im Adapter einiges getan. Bitte dabei beachten: In der Konfiguration der Instanz muss der Haken im folgenden Screenshot gesetzt werden - diese Einstellung ist neu.
-
@asgothian said in Zigbee Instanzen stürzen alle paar Tage ab:
Wobei ich Dir nicht sagen kann wie das starten / anhalten via Skript geht.
system.adapter.zigbee.X.aliveauf true / false setzen -
@asgothian sagte in Zigbee Instanzen stürzen alle paar Tage ab:
Wobei ich Dir nicht sagen kann wie das starten / anhalten via Skript geht.
Mit Blockly ganz einfach:
await restartInstanceAsync('zigbee.0');
await stopInstanceAsync('zigbee.0');
await startInstanceAsync('zigbee.0');
