(FAQ) Zigbee LAN-USB-WLAN Gateway CC2652P

[Pedder007]

@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

[efxz]

@toralt
bist du schon erfolgreich auf die aktuelle fw 20230507_other coordinator gewechselt?

[dimaiv]

@efxz
Bei mir läuft es gut.

[toralt]

@efxz läuft ohne probleme

[efxz]

@ dimaiv @toralt
Bei mir steigt der Coordinator nach Update auf 20230507 nach rund 7h aus. Bin wieder auf 20221226 zurück.

[Pedder007]

sorry, war ein Versehen und lässt sich wohl nicht löschen

[Dave83]

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  - info: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin
2023-09-11 05:46:12.545  - info: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1
2023-09-11 05:46:14.559  - info: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1
2023-09-11 05:46:29.561  - info: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 
2023-09-11 05:46:32.548  - info: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin
2023-09-11 06:00:21.395  - error: zigbee.0 (31916) Adapter disconnected, stopping
2023-09-11 06:00:30.966  - info: homeconnect.0 (5873) Keep Alive failed Reconnect EventStream
2023-09-11 06:00:31.548  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:00:31.549  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:00:31.554  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:00:34.564  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:00:34.564  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:00:34.564  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:00:44.566  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:00:44.566  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:00:44.570  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:00:45.287  - warn: zigbee.0 (31916) DeviceAvailability:Failed to ping 0xc498860000075005 RS 227 T
2023-09-11 06:01:02.611  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:01:02.612  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:02.612  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:01:12.612  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:12.612  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:12.616  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:15.624  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:01:15.624  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:15.624  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:01:18.531  - warn: zigbee.0 (31916) DeviceAvailability:Failed to ping 0xc498860000064ac9 RS 227 T
2023-09-11 06:01:19.053  - warn: zigbee.0 (31916) DeviceAvailability:Failed to ping 0x00124b0024c18e48 01MINIZB
2023-09-11 06:01:25.625  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:25.626  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:25.629  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:28.635  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:01:28.636  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:28.636  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:01:30.091  - warn: zigbee.0 (31916) DeviceAvailability:Failed to ping 0x9c6937000070f61a RS 227 T
2023-09-11 06:01:38.636  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:38.637  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:38.640  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:40.046  - info: 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  - info: zigbee.0 (31916) Unable to disable LED, unsupported function.
2023-09-11 06:01:40.047  - info: zigbee.0 (31916)   --> transmitPower : normal
2023-09-11 06:01:40.056  - info: zigbee.0 (31916) Currently 21 devices are joined:
2023-09-11 06:01:40.059  - info: zigbee.0 (31916) 0x00158d0005074e4e (addr 27528): RB 285 C - Innr E27 bulb RGBW (Router)
2023-09-11 06:01:40.060  - info: zigbee.0 (31916) 0x00124b0024c18e48 (addr 44659): ZBMINI - SONOFF Zigbee two way smart switch (Router)
2023-09-11 06:01:40.060  - info: zigbee.0 (31916) 0x00158d00075f7ac6 (addr 58538): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2023-09-11 06:01:40.060  - info: zigbee.0 (31916) 0x00158d0006f6b4a7 (addr 18958): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2023-09-11 06:01:40.061  - info: zigbee.0 (31916) 0x00158d0005080c62 (addr 41498): RB 285 C - Innr E27 bulb RGBW (Router)
2023-09-11 06:01:40.061  - info: zigbee.0 (31916) 0x00158d0006c3cbb2 (addr 57839): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2023-09-11 06:01:40.062  - info: zigbee.0 (31916) 0x00158d0006f86b58 (addr 61065): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2023-09-11 06:01:40.062  - info: zigbee.0 (31916) 0x00158d0006f25bad (addr 46082): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2023-09-11 06:01:40.063  - info: zigbee.0 (31916) 0x00158d000507dbd0 (addr 21791): RB 285 C - Innr E27 bulb RGBW (Router)
2023-09-11 06:01:40.063  - info: zigbee.0 (31916) 0x00158d00020e79f5 (addr 21687): FL 140 C - Innr Color Flex LED strip 4m 1200lm (Router)
2023-09-11 06:01:40.065  - info: zigbee.0 (31916) 0x00158d00075f59eb (addr 48604): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2023-09-11 06:01:40.065  - info: zigbee.0 (31916) 0x00158d00075f862b (addr 1486): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2023-09-11 06:01:40.066  - info: zigbee.0 (31916) 0x00158d0006ba677b (addr 21063): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2023-09-11 06:01:40.066  - info: 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  - info: 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  - info: zigbee.0 (31916) 0x00158d0004452056 (addr 55775): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)
2023-09-11 06:01:40.068  - info: zigbee.0 (31916) 0x84fd27fffed11f0e (addr 28462): E1757 - IKEA FYRTUR roller blind (EndDevice)
2023-09-11 06:01:40.068  - info: 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  - info: 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  - info: zigbee.0 (31916) 0x804b50fffec129ac (addr 36918): E1757 - IKEA FYRTUR roller blind (EndDevice)
2023-09-11 06:01:40.070  - info: zigbee.0 (31916) 0x00158d00075f688a (addr 10074): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)
2023-09-11 06:01:40.070  - info: zigbee.0 (31916) Zigbee started
2023-09-11 06:01:41.028  - info: homeconnect.0 (5873) Keep Alive failed Reconnect EventStream
2023-09-11 06:01:47.109  - error: zigbee.0 (31916) Adapter disconnected, stopping
2023-09-11 06:01:47.110  - error: zigbee.0 (31916) Adapter disconnected, stopping
2023-09-11 06:01:47.111  - error: zigbee.0 (31916) Adapter disconnected, stopping
2023-09-11 06:01:47.112  - error: zigbee.0 (31916) Adapter disconnected, stopping
2023-09-11 06:01:47.113  - error: zigbee.0 (31916) Adapter disconnected, stopping
2023-09-11 06:01:47.114  - error: zigbee.0 (31916) Adapter disconnected, stopping
2023-09-11 06:01:50.819  - warn: zigbee.0 (31916) DeviceAvailability:Stopping to ping 0x00158d0005080c62 RB 285 C after 744 ping attempts
2023-09-11 06:01:57.118  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:57.119  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:57.121  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:57.122  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:57.123  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:57.123  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:57.124  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:57.124  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:57.126  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:57.126  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:57.127  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:01:57.127  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:01:57.135  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:57.135  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:57.136  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:57.136  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:57.136  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:57.136  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:01:57.138  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:01:57.138  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:57.138  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:01:58.668  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')"
2023-09-11 06:01:58.668  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:58.668  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:01:58.675  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')"
2023-09-11 06:01:58.675  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:58.675  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:01:58.681  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')"
2023-09-11 06:01:58.681  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:58.681  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:01:58.687  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')"
2023-09-11 06:01:58.687  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:58.687  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:01:58.692  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Cannot read properties of undefined (reading 'execute')"
2023-09-11 06:01:58.692  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:01:58.692  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:07.140  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:07.140  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:07.145  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:07.149  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:07.150  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:07.150  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:08.670  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:08.671  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:08.676  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:08.676  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:08.680  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:08.680  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:08.680  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:08.685  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:08.685  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:08.687  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:08.688  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:08.688  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:08.696  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:08.697  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:08.697  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:08.704  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:08.704  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:08.707  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:08.708  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:08.708  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:08.712  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:08.712  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:08.712  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:08.717  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:11.114  - warn: zigbee.0 (31916) DeviceAvailability:Stopping to ping 0x00158d00020e79f5 FL 140 C after 6667 ping attempts
2023-09-11 06:02:17.114  - warn: zigbee.0 (31916) DeviceAvailability:Failed to ping 0xc49886000006993c RS 227 T
2023-09-11 06:02:17.151  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:17.151  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:17.158  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:17.159  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:17.159  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:17.163  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:18.104  - info: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1
2023-09-11 06:02:18.681  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:18.682  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:18.686  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:18.690  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:18.690  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:18.690  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:18.700  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:18.700  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:18.707  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:18.708  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:18.708  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:18.712  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:18.713  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:18.713  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:18.726  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:18.726  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:18.726  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:18.730  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:20.079  - info: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1
2023-09-11 06:02:27.160  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:27.160  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:27.163  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:27.167  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:27.168  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:27.168  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:27.693  - error: 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  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:27.693  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:27.699  - error: 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  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:27.699  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:28.693  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:28.693  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:28.697  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:28.702  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:28.702  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:28.702  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:28.709  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:28.709  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:28.716  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:28.717  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:28.717  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:28.720  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:28.727  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:28.727  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:28.736  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:28.736  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:28.737  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:28.740  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:37.168  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:37.169  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:37.172  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:37.176  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:37.177  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:37.177  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:37.694  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:37.694  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:37.699  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:37.702  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:37.702  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:37.702  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:37.705  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:37.705  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:37.712  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:37.712  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:37.713  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:37.716  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:38.703  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:38.703  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:38.707  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:38.711  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:38.712  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:38.712  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:38.717  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:38.718  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:38.725  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:38.725  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:38.725  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:38.730  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:38.738  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:38.738  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:38.746  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:38.746  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:38.746  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:38.751  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:47.178  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:47.179  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:47.182  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:47.188  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:47.189  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:47.189  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:47.703  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:47.704  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:47.707  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:47.714  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:47.714  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:47.714  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:47.717  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:47.717  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:47.723  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:47.723  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:47.723  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:47.728  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:48.106  - info: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 admin
2023-09-11 06:02:48.712  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:48.713  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:48.716  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:48.719  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:48.720  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:48.720  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:48.726  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:48.727  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:48.733  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:48.734  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:48.734  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:48.737  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:48.747  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:48.748  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:48.754  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:48.755  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:48.755  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:48.758  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:50.079  - info: admin.0 (26739) <== Disconnect system.user.admin from ::ffff:172.17.0.1 
2023-09-11 06:02:51.033  - info: homeconnect.0 (5873) Keep Alive failed Reconnect EventStream
2023-09-11 06:02:57.189  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:57.190  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:57.193  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:57.198  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:57.198  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:57.199  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:57.715  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:57.716  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:57.719  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:57.725  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:57.726  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:57.726  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:57.729  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:57.729  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:57.736  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:57.737  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:57.737  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:57.742  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:58.720  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:58.721  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:58.724  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:58.729  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:58.730  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:58.730  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:58.735  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:58.735  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:58.742  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:58.742  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:58.743  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:58.747  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:02:58.755  - info: zigbee.0 (31916) Try to reconnect.
2023-09-11 06:02:58.756  - info: zigbee.0 (31916) Starting Zigbee  npm ...
2023-09-11 06:02:58.765  - error: zigbee.0 (31916) Starting zigbee-herdsman problem : "Error while opening socket"
2023-09-11 06:02:58.765  - error: zigbee.0 (31916) Failed to start Zigbee
2023-09-11 06:02:58.765  - error: zigbee.0 (31916) Error herdsman start
2023-09-11 06:02:58.768  - info: zigbee.0 (31916) Installed Version: iobroker.zigbee@1.8.23
2023-09-11 06:03:03.500  - info: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1
2023-09-11 06:03:05.684  - info: admin.0 (26739) ==> Connected system.user.admin from ::ffff:172.17.0.1

[Pedder007]

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.

[Dave83]

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.

[Dave83]

Was bedeutest das?

Error 225 on send command to 3. Error: Error: Command 3 genOnOff.on({}) failed (Data request failed with error: 'MAC channel access failure' (225)) at ZStackAdapter.dataRequestExtended (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:1023:27) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Object.func (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:540:13) at Queue.executeNext (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)

[Dave83]

und das hier?

Send command to 0x00124b0024c0f51a failed with no error code (Timeout - 1970 - 1 - 79 - 6 - 11 after 10000ms)

[BananaJoe]

Versuchst du etwas an batteriebetriebene Geräte zu schicken?

[Dave83]

@bananajoe said in (FAQ) Zigbee LAN/USB/WLAN Gateway CC2652P:

Versuchst du etwas an batteriebetriebene Geräte zu schicken?

Ich weiß nicht genau worauf du dich beziehst. Ich habe auch kleine Aqara Sensoren. Aber wüsste nicht, ob ich an die etwas sende. Eigentlich nicht.

Bei dem hier:

Send command to 0x00124b0024c0f51a failed with no error code (Timeout - 1970 - 1 - 79 - 6 - 11 after 10000ms)

handelt es sich um diesen Schalter.

Außerdem sehe ich, dass der Luftreiniger von Ikea folgendes Problem meldet. Dabei stelle ich das gar nicht ein. Und ich kann das gar nicht ändern.

State value to set for "zigbee.0.cc86ecfffe543275.pm25" has value "-1" less than min "0"

[Dave83]

@arteck said in [Verkaufe] Zigbee LAN/USB/WLAN Gateway CC2652P:

@dave83 sagte in [Verkaufe] Zigbee LAN/USB/WLAN Gateway CC2652P:

Lohnt es sich eine weitere Antenne zu kaufen?

nein... das bringt nix

hast du Osram oder Ledvance verbaut ? wie siehts mit dem WLAN Kanal aus..

Hallo @arteck Nein, beides nicht im Einsatz. Innr, und Sonos. mit Aqara.

@dimaiv said in [Verkaufe] Zigbee LAN/USB/WLAN Gateway CC2652P:

@dave83
So wie @arteck sagt, nur kaufen bringt nix. Erstmal versuchen es zu optimieren.

Bitte hier weiter machen:

https://forum.iobroker.net/post/992879

Hallo @dimaiv was genau kann ich optimieren? Wifi habe ich in dr gesamten Wohnung sehr gut und sehr stark. Gibt es eine Anleitung oder ein Paper, was man wie durchgehen muss oder vergleichen kann oder welche Werte willst du wissen?

[A Former User]

@dave83 sagte in (FAQ) Zigbee LAN/USB/WLAN Gateway CC2652P:

Gibt es eine Anleitung oder ein Paper

Moin,

schau mal hier-> https://www.zigbee2mqtt.io/advanced/zigbee/02_improve_network_range_and_stability.html

Ist vielleicht was dabei.

VG
Bernd

[kiste01]

Hallo @dimaiv,

ich habe leider nicht deinen Rat befolgt und bei laufender Instanz den Stick vom Strom getrennt. Und das auch nur, weil ich nach dem DSL Anbieter Wechsel ein Problem mit der Fritzbox hatte und diese dann blöderweise kurz vom Strom genommen habe und an der Box hängt der Stick. Sch...

Das Log sagt:

zigbee.0
2023-11-28 16:24:38.564	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
zigbee.0
2023-11-28 16:24:38.562	info	terminating
zigbee.0
2023-11-28 16:24:38.170	info	Zigbee: disabling joining new devices.
zigbee.0
2023-11-28 16:24:38.061	info	cleaned everything up...
zigbee.0
2023-11-28 16:24:38.040	error	undefined
zigbee.0
2023-11-28 16:24:38.040	error	unhandled promise rejection: undefined
zigbee.0
2023-11-28 16:24:38.039	error	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().

zigbee.0
2023-11-28 16:24:18.481	info	debug devices set to []

zigbee.0
2023-11-28 16:24:18.309	warn	download icon from https://www.zigbee2mqtt.io/images/devices/P3Z.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/P3Z.png

zigbee.0
2023-11-28 16:24:18.230	info	Zigbee started

Das letzte was ich davor noch erfolgreich machen konnte, was das Anlernen der Lampe P3Z. Also entweder ist beim Anlernen was passiert oder eben beim Stromlos machen.

Der Stick zeigt:

Socket :  0 d 00:04:01
Uptime : 1 d 04:52:06
ESP temperature : 39.78 °C
FW version : 0.6.10
Hardware : WT32-ETH01
ESP32 model : ESP32-D0WDQ5
CPU : 2 cores @ 240 MHz
Flash : 4 Mb, external
Free heap : 226 / 303 KiB

Wie kann ich den Stick wieder erwecken?

Torsten

[dimaiv]

@kiste01

1. Zigbee Instanz stoppen!
2. Stick für 30 sek vom Strom nehmen.
3. Zigbee Instanz Log-Stufe auf Debug setzen.
4. Zigbee Instanz starten.
5. Logausgabe posten.

[kiste01]

@dimaiv

Ich befürchte, ich hab neue Probleme bekommen. Nach dem Debug setzen der Zigbee Instanz wollte ich das Logfile runterladen. Die Meldungen wurden blockweise angezeigt, weil es so viele waren. Das Logfile zeigte irgendwann 35 MB.

Ob es daran lag oder an etwas anderem ... keine Ahnung. Auf jeden Fall bekomme ich den iobroker nicht mehr zum Laufen.

iob status zeigt

pi@iobroker:~$ pi@iobroker:~$ iob status
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iob                                                           roker/iobroker-data/objects.jsonl"!

Mein System läuft unter proxmox

Der iob fix zeigt

pi@iobroker:~$ iob fix
library: loaded
Library version=2023-10-13

==========================================================================

    Welcome to the ioBroker installation fixer!
    Script version: 2023-10-13

    You might need to enter your password a couple of times.

==========================================================================


==========================================================================
    Installing prerequisites (1/5)
==========================================================================

[sudo] Passwort für pi:
Holen:1 http://security.debian.org/debian-security bullseye-security InRelease [                                                           48,4 kB]
Fehl:1 http://security.debian.org/debian-security bullseye-security InRelease
  Fehler beim Schreiben in Datei - write (28: Auf dem Gerät ist kein Speicherpla                                                           tz mehr verfügbar) [IP: 2a04:4e42:8d::644 80]
OK:2 http://deb.debian.org/debian bullseye InRelease
Holen:3 http://deb.debian.org/debian bullseye-updates InRelease [44,1 kB]
Fehl:3 http://deb.debian.org/debian bullseye-updates InRelease
  Fehler beim Schreiben in Datei - write (28: Auf dem Gerät ist kein Speicherpla                                                           tz mehr verfügbar) [IP: 2a04:4e42:8d::644 80]
Fehl:2 http://deb.debian.org/debian bullseye InRelease
  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease                                                            into data and signature failed
Holen:4 https://dl.yarnpkg.com/debian stable InRelease [17,1 kB]
Fehl:4 https://dl.yarnpkg.com/debian stable InRelease
  Fehler beim Schreiben in Datei - write (28: Auf dem Gerät ist kein Speicherpla                                                           tz mehr verfügbar) [IP: 2606:4700::6812:7e64 443]
OK:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Fehl:5 https://deb.nodesource.com/node_18.x nodistro InRelease
  Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f18.x_dists_nodistro_                                                           InRelease into data and signature failed
Paketlisten werden gelesen… Fertig
W: Während der Überprüfung der Signatur trat ein Fehler auf. Das Depot wurde nic                                                           ht aktualisiert und die vorherigen Indexdateien werden verwendet. GPG-Fehler: ht                                                           tp://deb.debian.org/debian bullseye InRelease: Splitting up /var/lib/apt/lists/d                                                           eb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: Während der Überprüfung der Signatur trat ein Fehler auf. Das Depot wurde nic                                                           ht aktualisiert und die vorherigen Indexdateien werden verwendet. GPG-Fehler: ht                                                           tps://deb.nodesource.com/node_18.x nodistro InRelease: Splitting up /var/lib/apt                                                           /lists/deb.nodesource.com_node%5f18.x_dists_nodistro_InRelease into data and sig                                                           nature failed
W: Fehlschlag beim Holen von http://deb.debian.org/debian/dists/bullseye/InRelea                                                           se Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InReleas                                                           e into data and signature failed
W: Fehlschlag beim Holen von http://security.debian.org/debian-security/dists/bu                                                           llseye-security/InRelease Fehler beim Schreiben in Datei - write (28: Auf dem Ge                                                           rät ist kein Speicherplatz mehr verfügbar) [IP: 2a04:4e42:8d::644 80]
W: Fehlschlag beim Holen von http://deb.debian.org/debian/dists/bullseye-updates                                                           /InRelease Fehler beim Schreiben in Datei - write (28: Auf dem Gerät ist kein Sp                                                           eicherplatz mehr verfügbar) [IP: 2a04:4e42:8d::644 80]
W: Fehlschlag beim Holen von https://deb.nodesource.com/node_18.x/dists/nodistro                                                           /InRelease Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f18.x_dists_                                                           nodistro_InRelease into data and signature failed
W: Fehlschlag beim Holen von https://dl.yarnpkg.com/debian/dists/stable/InReleas                                                           e Fehler beim Schreiben in Datei - write (28: Auf dem Gerät ist kein Speicherpla                                                           tz mehr verfügbar) [IP: 2606:4700::6812:7e64 443]
W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignorier                                                           t oder alte an ihrer Stelle benutzt.

==========================================================================
    Checking ioBroker user and directory permissions (2/5)
==========================================================================

main: Zeile 700: echo: Schreibfehler: Auf dem Gerät ist kein Speicherplatz mehr                                                            verfügbar.
Created /etc/sudoers.d/iobroker
Fixing directory permissions...

==========================================================================
    Check and cleanup npm temporary directories (3/5)
==========================================================================

Done.

==========================================================================
    Database maintenance (4/5)
==========================================================================

Checking for uncompressed JSONL databases... This might take a while!

npm ERR! code ENOSPC
npm ERR! syscall write
npm ERR! errno -28
npm ERR! nospc ENOSPC: no space left on device, write
npm ERR! nospc There appears to be insufficient space on your system to finish.
npm ERR! nospc Clear up some disk space and try again.

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-28T20_56_09_663Z-debug-0.log
main: Zeile 12: [: -lt: Einstelliger (unärer) Operator erwartet.
npm ERR! code ENOSPC
npm ERR! syscall write
npm ERR! errno -28
npm ERR! nospc ENOSPC: no space left on device, write
npm ERR! nospc There appears to be insufficient space on your system to finish.
npm ERR! nospc Clear up some disk space and try again.

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-28T20_56_10_005Z-debug-0.log

==========================================================================
    Checking autostart (5/5)
==========================================================================

Enabling autostart...
Autostart enabled!

==========================================================================

    Your installation was fixed successfully
    Run iobroker start to start ioBroker again!

==========================================================================

pi@iobroker:~$ iob start

[Thomas Braun]

@kiste01

Der Datenträger ist rappelvoll. Oder 'read-only' gemountet.

[kiste01]

@thomas-braun

der proxmox Knoten zeigt 86% von 29 GB und der iobroker hat 10 GB. Gibt es Verzeichniss im iobroker, wo ich was löschen könnte zb alte backups o.ä.?

'read-only' gemountet verstehe ich nicht