(FAQ) Zigbee LAN-USB-WLAN Gateway CC2652P
-
@pedder007
Trotzdem interessant was vor dem Absturz im Log stand... -
@dimaiv ich versuche das heute Abend mal rauszufinden, allerdings war der Ausfall schon irgendwann heute Nacht, da die Jalousien heute Morgen alle nicht hochgefahren sind
Bin jetzt die nächsten Stunden erst mal wieder OFF … -
@dimaiv so de‘le, habe jetzt mal die Logs vom Master und vom entsprechenden Slave, auf dem der Adapter läuft, durchsucht (Zigbee Log steht auf Info).
Um ~22:30 wurden noch ein paar Steckdosen per Script abgeschaltet, was per Verbrauchsdaten in Influx/Historie so auch wirklich stimmt. Ab 23:01 laufen dann plötzlich alle Device-Pings, teils mehr als 25tsd, ins Leere.
Dazwischen findet sich leider überhaupt keinerlei Hinweis in Richtung Zigbee oder Gateway.Die zunächst erfolglosen Startversuche (vor dem HW-Reset) sahen dann so aus, evtl. hilft das ja:
2023-07-24 13:40:49.841 - info: host.proxodataslave instance "system.adapter.zigbee.0" disabled via .alive 2023-07-24 13:40:49.850 - info: host.proxodataslave "system.adapter.zigbee.0" disabled 2023-07-24 13:40:49.852 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 (force=false, process=true) 2023-07-24 13:40:49.889 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 (force=false, process=true) 2023-07-24 13:40:49.922 - info: zigbee.0 (17027) Got terminate signal TERMINATE_YOURSELF 2023-07-24 13:40:49.934 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 (force=false, process=true) 2023-07-24 13:40:49.959 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 (force=false, process=true) 2023-07-24 13:40:49.978 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 send kill signal 2023-07-24 13:40:49.924 - info: zigbee.0 (17027) cleaned everything up... 2023-07-24 13:40:50.013 - info: zigbee.0 (17027) Zigbee: disabling joining new devices. 2023-07-24 13:40:50.024 - info: zigbee.0 (17027) Got terminate signal TERMINATE_YOURSELF 2023-07-24 13:40:50.184 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 send kill signal 2023-07-24 13:40:50.199 - info: zigbee.0 (17027) Got terminate signal TERMINATE_YOURSELF 2023-07-24 13:40:50.213 - info: zigbee.0 (17027) Got terminate signal TERMINATE_YOURSELF 2023-07-24 13:40:50.286 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 send kill signal 2023-07-24 13:40:50.287 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 send kill signal 2023-07-24 13:40:50.424 - info: zigbee.0 (17027) terminating 2023-07-24 13:40:50.426 - info: zigbee.0 (17027) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-07-24 13:40:50.981 - info: host.proxodataslave stopInstance system.adapter.zigbee.0 killing pid 17027 2023-07-24 13:40:51.425 - info: zigbee.0 (17027) terminating with timeout 2023-07-24 13:40:55.008 - info: host.proxodataslave instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-07-24 13:41:04.822 - info: host.proxodataslave instance "system.adapter.zigbee.0" enabled via .alive 2023-07-24 13:41:04.840 - info: host.proxodataslave "system.adapter.zigbee.0" enabled 2023-07-24 13:41:05.655 - info: host.proxodataslave instance system.adapter.zigbee.0 started with pid 31882 2023-07-24 13:41:05.656 - info: host.proxodataslave instance system.adapter.zigbee.0 started with pid 31882 2023-07-24 13:41:05.656 - info: host.proxodataslave instance system.adapter.zigbee.0 started with pid 31882 2023-07-24 13:41:05.656 - info: host.proxodataslave instance system.adapter.zigbee.0 started with pid 31882 2023-07-24 13:41:09.359 - info: zigbee.0 (31882) starting. Version 1.8.12 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.16.1, js-controller: 4.0.24 2023-07-24 13:41:09.381 - info: zigbee.0 (31882) Apply converter from module: /opt/iobroker/iobroker-data/zigbee_0/water.js 2023-07-24 13:41:09.417 - info: zigbee.0 (31882) delete old Backup files. keep only last 10 2023-07-24 13:41:09.417 - info: zigbee.0 (31882) Starting Zigbee npm ... 2023-07-24 13:41:09.699 - info: zigbee.0 (31882) Installed Version: iobroker.zigbee@1.8.12 2023-07-24 13:41:28.753 - error: zigbee.0 (31882) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)" 2023-07-24 13:41:28.753 - error: zigbee.0 (31882) Failed to start Zigbee 2023-07-24 13:41:28.753 - error: zigbee.0 (31882) Error herdsman start 2023-07-24 13:41:38.756 - info: zigbee.0 (31882) Try to reconnect. 2023-07-24 13:41:38.756 - info: zigbee.0 (31882) Starting Zigbee npm ... 2023-07-24 13:41:38.860 - info: zigbee.0 (31882) Installed Version: iobroker.zigbee@1.8.12 2023-07-24 13:41:57.765 - error: zigbee.0 (31882) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)" 2023-07-24 13:41:57.767 - error: zigbee.0 (31882) Failed to start Zigbee 2023-07-24 13:41:57.767 - error: zigbee.0 (31882) Error herdsman start 2023-07-24 13:42:07.768 - info: zigbee.0 (31882) Try to reconnect. ``` -
@pedder007 ist bei mir ab und an auch so, würde sagen so alle 2/3 monate geht auf einmal nichts mehr bei zigbee2mqtt, obwohl der adapter im LAN vorhanden ist und ich auf dessen Oberfläche komme. Dann hilft nur ein hardreset.
Ich habe zwei dieser adapter und beide haben das „Problem“. Ich wollte mir mal via blockly ein skript schreiben, das den PoE Port am unifi switch jede woche mal neu startet. Aber da ich aus der ferne auch auf mein unifi system zugreifen kann, habe ich das immer direkt per hand gemacht, wenn ich bemerkt hatte, dass es nicht ging.
An was das liegt, weiß ich nicht, die coordinator firmwares ändern nichts daran. Und da ich den Fehler nicht selbst reproduzieren kann (das kommt immer dann, wenn ich keinen Nerv dafür habe) habe ich keine weiteren „Untersuchungen“ gemacht. -
@toralt danke für Deine Rückmeldung. Wenn ich hier im Post nach oben scrolle, kommt das mit den 2 Monaten bei mir ja ganz gut hin. Der Hinweis bzgl PoE (nutze auch Unifi und komme per VPN an alles ran) ist gut! Ich hatte schon über eine WLAN Steckdose nachgedacht, da ich an eine Zigbee ja nicht mehr rankommen würde
Ich hatte auch nicht auf dem Schirm, dass der Koordinator PoE fähig ist, oder gibts da verschiedene?
Grundsätzlich lief mein Zigbee Adapter auch noch, nur aber ohne Connect zum GW.@dimaiv, wenn ich ja nicht der einzige zu sein scheine:
Schreibt sich der Koordinator da evtl irgendwas über die Zeit voll, was dann zu dem Problem führt?
Nach dem HW reset ist das Symbol am Socket auch sofort wieder grün geworden, was ja vorher beim SW Reboot nicht geklappt hatte.
Ich hatte vorher einen Conbee II genutzt, der wurde über die Zeit gefühlt langsamer, hatte aber keinen Totalausfall. Vor dem Hintergrund habe ich dann aber gewechselt. -
@pedder007 ich habe einen poe auf lan/usb adapter dran, daher kann ich den coordinator über port stromlos schalten und rebooten. Der lan coordinator an sich kann das glaub ich nicht direkt. Der braucht ne usb stromversorgung.
-
@toralt ich gucke dann mal was günstiger ist
, bzw. werde künftig vor längeren Abwesenheiten grundsätzlich einen HW Reset machen.
@dimaiv, Du hattest geschrieben, dass da evtl. schlimmeres passieren kann. Was wäre das denn? Also z. B. kann ein Stromausfall ja auch jederzeit passieren. Wäre natürlich schlecht, wenn dann z. B. plötzlich die Hälfte, oder gar alle, der angelernten Devices fort wären
-
@pedder007
Vor dem Reboot oder Strom ziehen Zigbee Adapter stoppen. Dann kann, eigentlich, nix mehr schief gehen.Wie ist euer Zigbee Firmware Stand?
-
@dimaiv die aktuellste, keine Beta (20230507_other_coordinator). Das war aber mit den beiden anderen Firmwares ähnlich.
Zigbee2Mqttt kommt meistens auch ohne Neustart mit dem Coordinatorneustart klar.
Wie gesagt, was dafür der Grund ist, kann ich nicht genauer erörtern. Bei mir hängen über 120 Geräte dran, da fällt es zumindest recht schnell auf, wenn er hängt.
U.u. hängt das auch mit Unifi zusammen, keine Ahnung. -
@dimaiv bei mir die 0.6.10.
Die Betas nehme ich nur wenn es nicht anders geht. Habe da auch deutlich über 100 Devices dranhängen und lege in einem 4 Personen Haushalt Wert auf einen möglichst ausfallsicheren Betrieb, da es sonst immer direkt Kritik der Nutzer hagelt, bzw. das Haus auch möglichst autark funktionieren soll, um unabhängiger von den Nachbarn zu sein.
@toralt warum soll das an Unifi liegen? Also seit ich von Fritz weg bin funktioniert das alles erst wirklich gut
-
@pedder007 ja, unifi ist schon top, aber ab und an machen die jungs halt auch murks
Vllt liegt es auch an der menge der geräte oder an bestimmten geräten. Aber generell fühlt es sich so an als würde ein speicher volllaufen und dann ist schicht im schacht. Ein hardreset setzt diesen wieder zurück und weiter gehts.
-
@toralt bin in der Pandemie umgestiegen, da bei einem Home’offic’ler plus, zu dem Zeitpunkt noch drei, Home-Schülern, mit dem Fritz-Zeugs um spätestens 11:00/11:30 Vormittags immer das Geschrei aus der oberen Etage anfing 🤪
Alles was am WLAN hing flog dann nach und nach ‚weg‘.
Seit dem Umstieg habe ich nie wieder Probleme gehabt.Bzgl des Koordinators hatte ich ja auch schon den gleichen Verdacht geäußert, aber da muss @dimaiv uns erleuchten
Ich werd mir, ab morgen wieder Zuhause, dann derweil auch eine Übergangslösung schaffen. @dimaiv danke auch noch für den Hinweis bzgl des Adapters. Das lässt sich per Blockly ja einfach umsetzen
-
@toralt
bist du schon erfolgreich auf die aktuelle fw 20230507_other coordinator gewechselt? -
@efxz
Bei mir läuft es gut. -
@efxz läuft ohne probleme
-
@ dimaiv @toralt
Bei mir steigt der Coordinator nach Update auf 20230507 nach rund 7h aus. Bin wieder auf 20221226 zurück. -
sorry, war ein Versehen und lässt sich wohl nicht löschen
-
Darf ich fragen, was bei mir das Problem ist? Ich muss regelmässig die Instanz neustarten.
Kann man hier ras rauslesen?2023-09-11 05:46:10.955 - [32minfo[39m: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin 2023-09-11 05:46:12.545 - [32minfo[39m: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1 2023-09-11 05:46:14.559 - [32minfo[39m: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1 2023-09-11 05:46:29.561 - [32minfo[39m: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 2023-09-11 05:46:32.548 - [32minfo[39m: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin 2023-09-11 06:00:21.395 - [31merror[39m: zigbee.0 (31916) Adapter disconnected, stopping 2023-09-11 06:00:30.966 - [32minfo[39m: homeconnect.0 (5873) Keep Alive failed Reconnect EventStream 2023-09-11 06:00:31.548 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:00:31.549 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:00:31.554 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:00:34.564 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:00:34.564 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:00:34.564 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:00:44.566 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:00:44.566 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:00:44.570 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:00:45.287 - [33mwarn[39m: zigbee.0 (31916) DeviceAvailability:Failed to ping 0xc498860000075005 RS 227 T 2023-09-11 06:01:02.611 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:01:02.612 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:02.612 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:01:12.612 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:12.612 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:12.616 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:15.624 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:01:15.624 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:15.624 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:01:18.531 - [33mwarn[39m: zigbee.0 (31916) DeviceAvailability:Failed to ping 0xc498860000064ac9 RS 227 T 2023-09-11 06:01:19.053 - [33mwarn[39m: zigbee.0 (31916) DeviceAvailability:Failed to ping 0x00124b0024c18e48 01MINIZB 2023-09-11 06:01:25.625 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:25.626 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:25.629 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:28.635 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:01:28.636 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:28.636 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:01:30.091 - [33mwarn[39m: zigbee.0 (31916) DeviceAvailability:Failed to ping 0x9c6937000070f61a RS 227 T 2023-09-11 06:01:38.636 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:38.637 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:38.640 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:40.046 - [32minfo[39m: zigbee.0 (31916) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20230507}} 2023-09-11 06:01:40.046 - [32minfo[39m: zigbee.0 (31916) Unable to disable LED, unsupported function. 2023-09-11 06:01:40.047 - [32minfo[39m: zigbee.0 (31916) --> transmitPower : normal 2023-09-11 06:01:40.056 - [32minfo[39m: zigbee.0 (31916) Currently 21 devices are joined: 2023-09-11 06:01:40.059 - [32minfo[39m: zigbee.0 (31916) 0x00158d0005074e4e (addr 27528): RB 285 C - Innr E27 bulb RGBW (Router) 2023-09-11 06:01:40.060 - [32minfo[39m: zigbee.0 (31916) 0x00124b0024c18e48 (addr 44659): ZBMINI - SONOFF Zigbee two way smart switch (Router) 2023-09-11 06:01:40.060 - [32minfo[39m: zigbee.0 (31916) 0x00158d00075f7ac6 (addr 58538): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-09-11 06:01:40.060 - [32minfo[39m: zigbee.0 (31916) 0x00158d0006f6b4a7 (addr 18958): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) 2023-09-11 06:01:40.061 - [32minfo[39m: zigbee.0 (31916) 0x00158d0005080c62 (addr 41498): RB 285 C - Innr E27 bulb RGBW (Router) 2023-09-11 06:01:40.061 - [32minfo[39m: zigbee.0 (31916) 0x00158d0006c3cbb2 (addr 57839): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-09-11 06:01:40.062 - [32minfo[39m: zigbee.0 (31916) 0x00158d0006f86b58 (addr 61065): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) 2023-09-11 06:01:40.062 - [32minfo[39m: zigbee.0 (31916) 0x00158d0006f25bad (addr 46082): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) 2023-09-11 06:01:40.063 - [32minfo[39m: zigbee.0 (31916) 0x00158d000507dbd0 (addr 21791): RB 285 C - Innr E27 bulb RGBW (Router) 2023-09-11 06:01:40.063 - [32minfo[39m: zigbee.0 (31916) 0x00158d00020e79f5 (addr 21687): FL 140 C - Innr Color Flex LED strip 4m 1200lm (Router) 2023-09-11 06:01:40.065 - [32minfo[39m: zigbee.0 (31916) 0x00158d00075f59eb (addr 48604): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) 2023-09-11 06:01:40.065 - [32minfo[39m: zigbee.0 (31916) 0x00158d00075f862b (addr 1486): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) 2023-09-11 06:01:40.066 - [32minfo[39m: zigbee.0 (31916) 0x00158d0006ba677b (addr 21063): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-09-11 06:01:40.066 - [32minfo[39m: zigbee.0 (31916) 0xc49886000006993c (addr 57860): RS 227 T - Innr GU10 spot 420 lm, dimmable, white spectrum (Router) 2023-09-11 06:01:40.067 - [32minfo[39m: zigbee.0 (31916) 0xc498860000075005 (addr 21427): RS 227 T - Innr GU10 spot 420 lm, dimmable, white spectrum (Router) 2023-09-11 06:01:40.067 - [32minfo[39m: zigbee.0 (31916) 0x00158d0004452056 (addr 55775): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2023-09-11 06:01:40.068 - [32minfo[39m: zigbee.0 (31916) 0x84fd27fffed11f0e (addr 28462): E1757 - IKEA FYRTUR roller blind (EndDevice) 2023-09-11 06:01:40.068 - [32minfo[39m: zigbee.0 (31916) 0xc498860000064ac9 (addr 16431): RS 227 T - Innr GU10 spot 420 lm, dimmable, white spectrum (Router) 2023-09-11 06:01:40.069 - [32minfo[39m: zigbee.0 (31916) 0x9c6937000070f61a (addr 8956): RS 227 T - Innr GU10 spot 420 lm, dimmable, white spectrum (Router) 2023-09-11 06:01:40.070 - [32minfo[39m: zigbee.0 (31916) 0x804b50fffec129ac (addr 36918): E1757 - IKEA FYRTUR roller blind (EndDevice) 2023-09-11 06:01:40.070 - [32minfo[39m: zigbee.0 (31916) 0x00158d00075f688a (addr 10074): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice) 2023-09-11 06:01:40.070 - [32minfo[39m: zigbee.0 (31916) Zigbee started 2023-09-11 06:01:41.028 - [32minfo[39m: homeconnect.0 (5873) Keep Alive failed Reconnect EventStream 2023-09-11 06:01:47.109 - [31merror[39m: zigbee.0 (31916) Adapter disconnected, stopping 2023-09-11 06:01:47.110 - [31merror[39m: zigbee.0 (31916) Adapter disconnected, stopping 2023-09-11 06:01:47.111 - [31merror[39m: zigbee.0 (31916) Adapter disconnected, stopping 2023-09-11 06:01:47.112 - [31merror[39m: zigbee.0 (31916) Adapter disconnected, stopping 2023-09-11 06:01:47.113 - [31merror[39m: zigbee.0 (31916) Adapter disconnected, stopping 2023-09-11 06:01:47.114 - [31merror[39m: zigbee.0 (31916) Adapter disconnected, stopping 2023-09-11 06:01:50.819 - [33mwarn[39m: zigbee.0 (31916) DeviceAvailability:Stopping to ping 0x00158d0005080c62 RB 285 C after 744 ping attempts 2023-09-11 06:01:57.118 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:57.119 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:57.121 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:57.122 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:57.123 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:57.123 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:57.124 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:57.124 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:57.126 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:57.126 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:57.127 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:01:57.127 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:01:57.135 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:57.135 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:57.136 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:57.136 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:57.136 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:57.136 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:01:57.138 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:01:57.138 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:57.138 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:01:58.668 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')" 2023-09-11 06:01:58.668 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:58.668 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:01:58.675 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')" 2023-09-11 06:01:58.675 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:58.675 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:01:58.681 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')" 2023-09-11 06:01:58.681 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:58.681 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:01:58.687 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')" 2023-09-11 06:01:58.687 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:58.687 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:01:58.692 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')" 2023-09-11 06:01:58.692 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:01:58.692 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:07.140 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:07.140 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:07.145 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:07.149 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:07.150 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:07.150 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:08.670 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:08.671 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:08.676 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:08.676 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:08.680 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:08.680 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:08.680 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:08.685 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:08.685 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:08.687 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:08.688 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:08.688 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:08.696 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:08.697 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:08.697 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:08.704 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:08.704 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:08.707 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:08.708 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:08.708 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:08.712 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:08.712 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:08.712 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:08.717 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:11.114 - [33mwarn[39m: zigbee.0 (31916) DeviceAvailability:Stopping to ping 0x00158d00020e79f5 FL 140 C after 6667 ping attempts 2023-09-11 06:02:17.114 - [33mwarn[39m: zigbee.0 (31916) DeviceAvailability:Failed to ping 0xc49886000006993c RS 227 T 2023-09-11 06:02:17.151 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:17.151 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:17.158 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:17.159 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:17.159 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:17.163 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:18.104 - [32minfo[39m: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1 2023-09-11 06:02:18.681 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:18.682 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:18.686 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:18.690 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:18.690 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:18.690 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:18.700 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:18.700 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:18.707 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:18.708 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:18.708 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:18.712 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:18.713 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:18.713 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:18.726 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:18.726 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:18.726 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:18.730 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:20.079 - [32minfo[39m: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1 2023-09-11 06:02:27.160 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:27.160 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:27.163 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:27.167 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:27.168 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:27.168 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:27.693 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)" 2023-09-11 06:02:27.693 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:27.693 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:27.699 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)" 2023-09-11 06:02:27.699 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:27.699 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:28.693 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:28.693 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:28.697 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:28.702 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:28.702 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:28.702 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:28.709 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:28.709 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:28.716 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:28.717 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:28.717 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:28.720 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:28.727 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:28.727 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:28.736 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:28.736 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:28.737 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:28.740 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:37.168 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:37.169 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:37.172 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:37.176 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:37.177 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:37.177 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:37.694 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:37.694 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:37.699 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:37.702 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:37.702 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:37.702 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:37.705 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:37.705 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:37.712 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:37.712 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:37.713 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:37.716 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:38.703 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:38.703 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:38.707 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:38.711 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:38.712 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:38.712 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:38.717 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:38.718 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:38.725 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:38.725 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:38.725 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:38.730 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:38.738 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:38.738 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:38.746 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:38.746 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:38.746 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:38.751 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:47.178 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:47.179 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:47.182 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:47.188 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:47.189 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:47.189 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:47.703 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:47.704 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:47.707 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:47.714 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:47.714 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:47.714 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:47.717 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:47.717 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:47.723 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:47.723 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:47.723 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:47.728 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:48.106 - [32minfo[39m: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin 2023-09-11 06:02:48.712 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:48.713 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:48.716 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:48.719 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:48.720 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:48.720 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:48.726 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:48.727 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:48.733 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:48.734 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:48.734 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:48.737 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:48.747 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:48.748 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:48.754 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:48.755 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:48.755 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:48.758 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:50.079 - [32minfo[39m: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 2023-09-11 06:02:51.033 - [32minfo[39m: homeconnect.0 (5873) Keep Alive failed Reconnect EventStream 2023-09-11 06:02:57.189 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:57.190 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:57.193 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:57.198 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:57.198 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:57.199 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:57.715 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:57.716 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:57.719 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:57.725 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:57.726 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:57.726 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:57.729 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:57.729 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:57.736 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:57.737 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:57.737 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:57.742 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:58.720 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:58.721 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:58.724 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:58.729 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:58.730 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:58.730 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:58.735 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:58.735 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:58.742 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:58.742 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:58.743 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:58.747 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:02:58.755 - [32minfo[39m: zigbee.0 (31916) Try to reconnect. 2023-09-11 06:02:58.756 - [32minfo[39m: zigbee.0 (31916) Starting Zigbee npm ... 2023-09-11 06:02:58.765 - [31merror[39m: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket" 2023-09-11 06:02:58.765 - [31merror[39m: zigbee.0 (31916) Failed to start Zigbee 2023-09-11 06:02:58.765 - [31merror[39m: zigbee.0 (31916) Error herdsman start 2023-09-11 06:02:58.768 - [32minfo[39m: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23 2023-09-11 06:03:03.500 - [32minfo[39m: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1 2023-09-11 06:03:05.684 - [32minfo[39m: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1 -
Hallo @dimaiv Ich hatte heute Mittag wieder so einen Ausstieg, bei welchem am Koordinator Socket (im WEB Frontend) auf rot gegangen war. So wie im Sommer auch schonmal (also für ioBroker/ZigBee Adapter nicht mehr erreichbar) und am Ende nur ein HW-Reset half.
Dieses Mal habe ich aber zumindest etwas aus dem Log fischen können, was evtl. bei der Problemsuch hilft. Der Fachmann bist da sicherlich Du
Damit das Ganze übersichtlich bleibt, habe ich aufeinander folgende gleiche Zeilen und auch gleichartige Zeilen (für die einzelnen Devices) heraus genommen und jeweils durch 3 Hashtags ersetz:zigbee.0 2023-10-22 15:19:56.643 warn DeviceAvailability:Failed to ping 0xf0d1b80000156c63 CLA60 RGBW Z3 ### zigbee.0 2023-10-22 15:19:28.383 warn DeviceAvailability:Failed to ping 0x60a423fffe065b3d TS130F zigbee.0 2023-10-22 15:19:21.093 info debug devices set to [] zigbee.0 2023-10-22 15:19:21.084 info deregister device Ping for deactivated device "0x9035eafffeeb87d6" zigbee.0 2023-10-22 15:19:21.083 info deregister device Ping for deactivated device "0x60a423fffe5e2a9f" zigbee.0 2023-10-22 15:19:21.083 info deregister device Ping for deactivated device "0x60a423fffeff8af1" zigbee.0 2023-10-22 15:19:21.083 info deregister device Ping for deactivated device "0x60a423fffe651e43" zigbee.0 2023-10-22 15:19:21.072 info deregister device Ping for deactivated device "0x000d6f000fbf98a6" zigbee.0 2023-10-22 15:19:21.071 info deregister device Ping for deactivated device "0x842e14fffe9be0ab" zigbee.0 2023-10-22 15:19:21.070 info deregister device Ping for deactivated device "0x00158d00067c165e" zigbee.0 2023-10-22 15:19:20.902 info Zigbee started zigbee.0 2023-10-22 15:19:20.902 info 0xa4c13838ddafadcd (addr 39052): A1Z - Nous Smart plug (with power monitoring) (Router) ### zigbee.0 2023-10-22 15:19:20.830 info 0x847127fffefe7ea7 (addr 3838): LCZ030 - TuYa Temperature & humidity & illuminance sensor with display (EndDevice) zigbee.0 2023-10-22 15:19:20.732 info Currently 112 devices are joined: zigbee.0 2023-10-22 15:19:20.608 info --> transmitPower : low zigbee.0 2023-10-22 15:19:20.602 info Unable to disable LED, unsupported function. zigbee.0 2023-10-22 15:19:20.592 info Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20221102}} zigbee.0 2023-10-22 15:19:13.528 info Installed Version: iobroker.zigbee@1.8.23 zigbee.0 2023-10-22 15:19:13.415 info Starting Zigbee npm ... zigbee.0 2023-10-22 15:19:13.414 info delete old Backup files. keep only last 10 zigbee.0 2023-10-22 15:19:13.388 info Apply converter from module: /opt/iobroker/iobroker-data/zigbee_0/water.js zigbee.0 2023-10-22 15:19:13.373 info starting. Version 1.8.23 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.18.1, js-controller: 5.0.12 zigbee.0 2023-10-22 15:18:53.218 warn Could not perform strict object check of state zigbee.0.00158d0004051854.link_quality: DB closed zigbee.0 2023-10-22 15:18:53.218 warn Could not perform strict object check of state zigbee.0.00158d0004051854.available: DB closed zigbee.0 2023-10-22 15:18:53.218 warn Could not perform strict object check of state zigbee.0.00158d0004506dbe.link_quality: DB closed zigbee.0 2023-10-22 15:18:53.218 warn get state error: Connection is closed. ### zigbee.0 2023-10-22 15:18:53.218 warn get state error: Connection is closed. zigbee.0 2023-10-22 15:18:53.217 warn Could not perform strict object check of state zigbee.0.a4c138fb292efdb0.available: DB closed ### zigbee.0 2023-10-22 15:18:53.217 warn Could not perform strict object check of state zigbee.0.00158d0004506dbe.available: DB closed zigbee.0 2023-10-22 15:18:53.215 warn get state error: Connection is closed. ### zigbee.0 2023-10-22 15:18:53.216 warn get state error: Connection is closed. zigbee.0 2023-10-22 15:18:53.214 warn Could not perform strict object check of state zigbee.0.ec1bbdfffe7dafd2.available: DB closed ### zigbee.0 2023-10-22 15:18:53.215 warn Could not perform strict object check of state zigbee.0.a4c1382b9ea73c50.available: DB closed zigbee.0 2023-10-22 15:18:53.214 warn get state error: Connection is closed. zigbee.0 2023-10-22 15:18:53.214 warn get state error: Connection is closed. zigbee.0 2023-10-22 15:18:53.214 warn get state error: Connection is closed. zigbee.0 2023-10-22 15:18:53.214 warn Could not perform strict object check of state zigbee.0.f0d1b80000157674.link_quality: DB closed zigbee.0 2023-10-22 15:18:53.211 warn get state error: Connection is closed. ### zigbee.0 2023-10-22 15:18:53.211 warn get state error: Connection is closed. zigbee.0 2023-10-22 15:18:53.210 warn Could not perform strict object check of state zigbee.0.f0d1b8000015785b.available: DB closed zigbee.0 2023-10-22 15:18:53.210 warn Could not perform strict object check of state zigbee.0.f0d1b80000157624.link_quality: DB closed ### zigbee.0 2023-10-22 15:18:53.211 warn Could not perform strict object check of state zigbee.0.f0d1b80000157674.available: DB closed zigbee.0 2023-10-22 15:18:53.210 warn get state error: Connection is closed. zigbee.0 2023-10-22 15:18:53.210 warn get state error: Connection is closed. -
Darf ich fragen, was man versuchen soll, wenn die Reaktionszeit verzögert ist?
Bei mir reagieren einige Geräte sehr langsam. Batterien sind voll oder wurden ausgetauscht. Keine Verbesserung. Neustart sowohl von der Antenne als auch vom Adapter, habe ich bereits versucht.
