Gibt es keine Idee was ich tun / ausprobieren soll?

@homoran

es steht nicht mehr drin

@homoran

Hier noch mal direkt aus der Console
iob logs zigbee

iob logs zigbee
2025-04-15 16:20:29.605  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4b637.link_quality: DB closed
2025-04-15 16:20:29.606  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.606  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4b637.link_quality: DB closed
2025-04-15 16:20:29.607  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.607  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a34c86.available: DB closed
2025-04-15 16:20:29.607  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.608  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a34c86.available: DB closed
2025-04-15 16:20:29.608  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.608  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a34c86.link_quality: DB closed
2025-04-15 16:20:29.609  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.609  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a34c86.link_quality: DB closed
2025-04-15 16:20:29.609  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.610  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4ae97.available: DB closed
2025-04-15 16:20:29.610  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.611  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4ae97.available: DB closed
2025-04-15 16:20:29.611  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.611  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4ae97.link_quality: DB closed
2025-04-15 16:20:29.612  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.612  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4ae97.link_quality: DB closed
2025-04-15 16:20:29.613  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.613  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe35b.available: DB closed
2025-04-15 16:20:29.613  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.614  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe35b.available: DB closed
2025-04-15 16:20:29.614  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.614  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe35b.link_quality: DB closed
2025-04-15 16:20:29.615  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.615  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe35b.link_quality: DB closed
2025-04-15 16:20:29.616  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.616  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe81deaa.available: DB closed
2025-04-15 16:20:29.616  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.617  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe81deaa.available: DB closed
2025-04-15 16:20:29.617  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.618  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe81deaa.link_quality: DB closed
2025-04-15 16:20:29.618  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.618  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe81deaa.link_quality: DB closed
2025-04-15 16:20:29.619  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.619  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe7a364d.available: DB closed
2025-04-15 16:20:29.619  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.620  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe7a364d.available: DB closed
2025-04-15 16:20:29.620  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.620  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe7a364d.link_quality: DB closed
2025-04-15 16:20:29.621  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.621  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe7a364d.link_quality: DB closed
2025-04-15 16:20:29.622  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.622  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe6b4e2c.available: DB closed
2025-04-15 16:20:29.623  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.623  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe6b4e2c.available: DB closed
2025-04-15 16:20:29.624  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.624  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe6b4e2c.link_quality: DB closed
2025-04-15 16:20:29.625  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.625  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe6b4e2c.link_quality: DB closed
2025-04-15 16:20:29.626  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.626  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00044a926f.available: DB closed
2025-04-15 16:20:29.627  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.627  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00044a926f.available: DB closed
2025-04-15 16:20:29.628  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.628  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00044a926f.link_quality: DB closed
2025-04-15 16:20:29.629  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.629  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00044a926f.link_quality: DB closed
2025-04-15 16:20:29.629  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.630  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe29a.available: DB closed
2025-04-15 16:20:29.630  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.630  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe29a.available: DB closed
2025-04-15 16:20:29.631  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.631  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe29a.link_quality: DB closed
2025-04-15 16:20:29.631  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.632  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe29a.link_quality: DB closed
2025-04-15 16:20:29.632  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.644  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00035390ec.available: DB closed
2025-04-15 16:20:29.645  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.645  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00035390ec.available: DB closed
2025-04-15 16:20:29.646  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.646  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00035390ec.link_quality: DB closed
2025-04-15 16:20:29.647  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.647  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00035390ec.link_quality: DB closed
2025-04-15 16:20:29.647  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.648  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d000679273c.available: DB closed
2025-04-15 16:20:29.648  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.649  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d000679273c.available: DB closed
2025-04-15 16:20:29.649  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 16:20:29.649  - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d000679273c.link_quality: DB closed
2025-04-15 16:20:29.650  - warn: zigbee.0 (3853) get state error: Connection is closed.
2025-04-15 20:48:19.060  - info: zigbee.0 (2000) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6
2025-04-15 20:48:19.089  - info: zigbee.0 (2000) init localConfig
2025-04-15 20:48:19.100  - info: zigbee.0 (2000)   --> transmitPower : normal
2025-04-15 20:48:19.116  - info: zigbee.0 (2000) delete old Backup files. keep only last 10
2025-04-15 20:48:19.121  - info: zigbee.0 (2000) --- creating device debug ---
2025-04-15 20:48:19.123  - info: zigbee.0 (2000) Starting Adapter npm ...
2025-04-15 20:48:19.192  - info: zigbee.0 (2000) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1)
2025-04-15 20:48:19.195  - info: zigbee.0 (2000) Starting Zigbee-Herdsman
2025-04-15 20:48:21.264  - info: zigbee.0 (2000) Unable to obtain herdsman settings
2025-04-15 20:48:21.351  - error: zigbee.0 (2000) Starting zigbee-herdsman problem : Error: Operation not supported, cannot set
2025-04-15 20:48:21.356  - error: zigbee.0 (2000) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2025-04-15 20:48:21.358  - error: zigbee.0 (2000) unhandled promise rejection: undefined
2025-04-15 20:48:21.359  - error: zigbee.0 (2000) undefined
2025-04-15 20:48:21.541  - info: zigbee.0 (2000) cleaned everything up...
2025-04-15 20:48:21.543  - info: zigbee.0 (2000) local config saved
2025-04-15 20:48:21.553  - info: zigbee.0 (2000) Saved local configuration data
2025-04-15 20:48:21.554  - info: zigbee.0 (2000) terminating
2025-04-15 20:48:21.556  - warn: zigbee.0 (2000) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-04-15 20:48:22.308  - error: zigbee.0 (2000) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
2025-04-15 20:48:22.347  - info: zigbee.0 (2000) terminating
2025-04-15 20:48:22.358  - warn: zigbee.0 (2000) Device 0x5c0272fffe7a194d "LED1537R6/LED1739R5" not found.
2025-04-15 20:48:22.360  - warn: zigbee.0 (2000) Device 0x5c0272fffe6c6dac "LED1537R6/LED1739R5" not found.
2025-04-15 20:48:22.362  - warn: zigbee.0 (2000) Device 0x086bd7fffe202f76 "LED1537R6/LED1739R5" not found.
2025-04-15 20:48:22.364  - warn: zigbee.0 (2000) Device 0xd0cf5efffedccd5c "LED1537R6/LED1739R5" not found.
2025-04-15 20:48:22.366  - warn: zigbee.0 (2000) Device 0x086bd7fffe5a65e9 "LED1537R6/LED1739R5" not found.
2025-04-15 20:48:22.368  - warn: zigbee.0 (2000) Device 0xd0cf5efffedcdea0 "LED1537R6/LED1739R5" not found.
2025-04-15 20:48:22.370  - warn: zigbee.0 (2000) Device 0x680ae2fffe7f2cd1 "E1524/E1810" not found.
2025-04-15 20:48:22.371  - warn: zigbee.0 (2000) Device 0x00158d0003a4b637 "MCCGQ11LM" not found.
2025-04-15 20:48:22.374  - warn: zigbee.0 (2000) Device 0x00158d0003a34c86 "MCCGQ11LM" not found.
2025-04-15 20:48:22.376  - warn: zigbee.0 (2000) Device 0x00158d0003a4ae97 "MCCGQ11LM" not found.
2025-04-15 20:48:22.378  - warn: zigbee.0 (2000) Device 0x00158d0004abe35b "RTCGQ11LM" not found.
2025-04-15 20:48:22.380  - warn: zigbee.0 (2000) Device 0x5c0272fffe81deaa "E1743" not found.
2025-04-15 20:48:22.383  - warn: zigbee.0 (2000) Device 0x5c0272fffe7a364d "LED1537R6/LED1739R5" not found.
2025-04-15 20:48:22.384  - warn: zigbee.0 (2000) Device 0x5c0272fffe6b4e2c "LED1537R6/LED1739R5" not found.
2025-04-15 20:48:22.387  - warn: zigbee.0 (2000) Device 0x00158d00044a926f "WSDCGQ11LM" not found.
2025-04-15 20:48:22.389  - warn: zigbee.0 (2000) Device 0x00158d0004abe29a "RTCGQ11LM" not found.
2025-04-15 20:48:22.390  - warn: zigbee.0 (2000) Device 0x00158d00035390ec "MCCGQ11LM" not found.
2025-04-15 20:48:22.392  - warn: zigbee.0 (2000) Device 0x00158d000679273c "WXKG11LM" not found.
2025-04-15 20:48:22.395  - warn: zigbee.0 (2000) Device 0x00158d00067bd3e6 "WXKG11LM" not found.
2025-04-15 20:48:22.396  - warn: zigbee.0 (2000) Device 0x00124b0024545ee5 "SNZB-03" not found.
2025-04-15 20:48:22.626  - info: zigbee.0 (2000) terminating
2025-04-15 20:48:22.796  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:22.798  - warn: zigbee.0 (2000) redis get zigbee.0.info.debugmessages, error - DB closed
2025-04-15 20:48:22.800  - warn: zigbee.0 (2000) get state error: DB closed
2025-04-15 20:48:23.558  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.available: DB closed
2025-04-15 20:48:23.560  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.561  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.available: DB closed
2025-04-15 20:48:23.562  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.563  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.link_quality: DB closed
2025-04-15 20:48:23.564  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.567  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.link_quality: DB closed
2025-04-15 20:48:23.568  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.569  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.available: DB closed
2025-04-15 20:48:23.570  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.574  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.available: DB closed
2025-04-15 20:48:23.575  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.576  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.link_quality: DB closed
2025-04-15 20:48:23.577  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.578  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.link_quality: DB closed
2025-04-15 20:48:23.580  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.583  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.086bd7fffe202f76.available: DB closed
2025-04-15 20:48:23.584  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.585  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.086bd7fffe202f76.available: DB closed
2025-04-15 20:48:23.588  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.589  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.086bd7fffe202f76.link_quality: DB closed
2025-04-15 20:48:23.591  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.592  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.086bd7fffe202f76.link_quality: DB closed
2025-04-15 20:48:23.593  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.594  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.d0cf5efffedccd5c.available: DB closed
2025-04-15 20:48:23.595  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.596  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.d0cf5efffedccd5c.available: DB closed
2025-04-15 20:48:23.599  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.600  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.d0cf5efffedccd5c.link_quality: DB closed
2025-04-15 20:48:23.601  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.602  - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.d0cf5efffedccd5c.link_quality: DB closed
2025-04-15 20:48:23.603  - warn: zigbee.0 (2000) get state error: Connection is closed.
2025-04-15 20:48:23.627  - info: zigbee.0 (2000) terminating with timeout
2025-04-15 20:48:57.895  - info: zigbee.0 (2347) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6
2025-04-15 20:48:57.923  - info: zigbee.0 (2347) init localConfig
2025-04-15 20:48:57.932  - info: zigbee.0 (2347)   --> transmitPower : normal
2025-04-15 20:48:57.947  - info: zigbee.0 (2347) delete old Backup files. keep only last 10
2025-04-15 20:48:57.952  - info: zigbee.0 (2347) --- creating device debug ---
2025-04-15 20:48:57.953  - info: zigbee.0 (2347) Starting Adapter npm ...
2025-04-15 20:48:58.023  - info: zigbee.0 (2347) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1)
2025-04-15 20:48:58.026  - info: zigbee.0 (2347) Starting Zigbee-Herdsman
2025-04-15 20:48:59.913  - info: zigbee.0 (2347) Unable to obtain herdsman settings
2025-04-15 20:48:59.995  - error: zigbee.0 (2347) Starting zigbee-herdsman problem : Error: Operation not supported, cannot set
2025-04-15 20:48:59.998  - error: zigbee.0 (2347) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2025-04-15 20:49:00.000  - error: zigbee.0 (2347) unhandled promise rejection: undefined
2025-04-15 20:49:00.001  - error: zigbee.0 (2347) undefined
2025-04-15 20:49:00.101  - info: zigbee.0 (2347) cleaned everything up...
2025-04-15 20:49:00.104  - info: zigbee.0 (2347) local config saved
2025-04-15 20:49:00.106  - info: zigbee.0 (2347) Saved local configuration data
2025-04-15 20:49:00.107  - info: zigbee.0 (2347) terminating
2025-04-15 20:49:00.110  - warn: zigbee.0 (2347) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-04-15 20:49:00.520  - error: zigbee.0 (2347) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
2025-04-15 20:49:00.535  - info: zigbee.0 (2347) terminating
2025-04-15 20:49:00.538  - warn: zigbee.0 (2347) Device 0x5c0272fffe7a194d "LED1537R6/LED1739R5" not found.
2025-04-15 20:49:00.539  - warn: zigbee.0 (2347) Device 0x5c0272fffe6c6dac "LED1537R6/LED1739R5" not found.
2025-04-15 20:49:00.540  - warn: zigbee.0 (2347) Device 0x086bd7fffe202f76 "LED1537R6/LED1739R5" not found.
2025-04-15 20:49:00.541  - warn: zigbee.0 (2347) Device 0xd0cf5efffedccd5c "LED1537R6/LED1739R5" not found.
2025-04-15 20:49:00.542  - warn: zigbee.0 (2347) Device 0x086bd7fffe5a65e9 "LED1537R6/LED1739R5" not found.
2025-04-15 20:49:00.543  - warn: zigbee.0 (2347) Device 0xd0cf5efffedcdea0 "LED1537R6/LED1739R5" not found.
2025-04-15 20:49:00.544  - warn: zigbee.0 (2347) Device 0x680ae2fffe7f2cd1 "E1524/E1810" not found.
2025-04-15 20:49:00.545  - warn: zigbee.0 (2347) Device 0x00158d0003a4b637 "MCCGQ11LM" not found.
2025-04-15 20:49:00.547  - warn: zigbee.0 (2347) Device 0x00158d0003a34c86 "MCCGQ11LM" not found.
2025-04-15 20:49:00.548  - warn: zigbee.0 (2347) Device 0x00158d0003a4ae97 "MCCGQ11LM" not found.
2025-04-15 20:49:00.549  - warn: zigbee.0 (2347) Device 0x00158d0004abe35b "RTCGQ11LM" not found.
2025-04-15 20:49:00.550  - warn: zigbee.0 (2347) Device 0x5c0272fffe81deaa "E1743" not found.
2025-04-15 20:49:00.551  - warn: zigbee.0 (2347) Device 0x5c0272fffe7a364d "LED1537R6/LED1739R5" not found.
2025-04-15 20:49:00.552  - warn: zigbee.0 (2347) Device 0x5c0272fffe6b4e2c "LED1537R6/LED1739R5" not found.
2025-04-15 20:49:00.553  - warn: zigbee.0 (2347) Device 0x00158d00044a926f "WSDCGQ11LM" not found.
2025-04-15 20:49:00.554  - warn: zigbee.0 (2347) Device 0x00158d0004abe29a "RTCGQ11LM" not found.
2025-04-15 20:49:00.554  - warn: zigbee.0 (2347) Device 0x00158d00035390ec "MCCGQ11LM" not found.
2025-04-15 20:49:00.555  - warn: zigbee.0 (2347) Device 0x00158d000679273c "WXKG11LM" not found.
2025-04-15 20:49:00.556  - warn: zigbee.0 (2347) Device 0x00158d00067bd3e6 "WXKG11LM" not found.
2025-04-15 20:49:00.557  - warn: zigbee.0 (2347) Device 0x00124b0024545ee5 "SNZB-03" not found.
2025-04-15 20:49:00.627  - info: zigbee.0 (2347) terminating
2025-04-15 20:49:01.072  - warn: zigbee.0 (2347) redis get zigbee.0.info.debugmessages, error - Connection is closed.
2025-04-15 20:49:01.094  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.096  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.315  - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.available: DB closed
2025-04-15 20:49:01.317  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.320  - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.available: DB closed
2025-04-15 20:49:01.325  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.326  - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.link_quality: DB closed
2025-04-15 20:49:01.327  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.328  - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.link_quality: DB closed
2025-04-15 20:49:01.333  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.334  - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.available: DB closed
2025-04-15 20:49:01.335  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.336  - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.available: DB closed
2025-04-15 20:49:01.339  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.340  - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.link_quality: DB closed
2025-04-15 20:49:01.341  - warn: zigbee.0 (2347) get state error: Connection is closed.
2025-04-15 20:49:01.342  - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.link_quality: DB closed
2025-04-15 20:49:01.344  - warn: zigbee.0 (2347) get state error: Connection is closed.

sorry hab es editiert.

aber ich habe nichts zensiert oder vergessen zu kopieren mehr steht da nicht drin

• Adaptername: zigbee
• Adapterversion: 2.0.5
• js-controller Version: 7.0.6
• Admin Version: ...
• Hardwaresystem: Pi4
• Arbeitsspeicher: 4GB
• Festplattenart: SSD
• Betriebssystem: Pi OS Lite
• Nodejs-Version: 20.19.0
• NPM-Version: 10.8.2

Moin.

ich wollte endlich mal mein System aktualisieren. Hatte immer noch Buster im Einsatz auf einer SD Karte und wollte auch auf eine SSD wechseln.

Also Bookworm auf die SSD geflash, Iob instaliert und alles per Backitup wiederhergestellt....

Funktioniert auch alles bis auf den Zigbee adapter.
Bereits auch wieder gelöscht und manuell installiert. Keine Funktion

zigbee.0 2025-04-15 16:20:29.000	info	terminating
zigbee.0 2025-04-15 16:20:28.986	error	Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
zigbee.0 2025-04-15 16:20:28.730	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
zigbee.0 2025-04-15 16:20:28.728	info	terminating
zigbee.0 2025-04-15 16:20:28.726	info	Saved local configuration data
zigbee.0 2025-04-15 16:20:28.725	info	local config saved
zigbee.0 2025-04-15 16:20:28.723	info	cleaned everything up...
zigbee.0 2025-04-15 16:20:28.653	error	undefined
zigbee.0 2025-04-15 16:20:28.652	error	unhandled promise rejection: undefined
zigbee.0 2025-04-15 16:20:28.651	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 2025-04-15 16:20:28.648	error	Starting zigbee-herdsman problem : Error: Operation not supported, cannot set
zigbee.0 2025-04-15 16:20:28.602	info	Unable to obtain herdsman settings
zigbee.0 2025-04-15 16:20:26.770	info	Starting Zigbee-Herdsman
zigbee.0 2025-04-15 16:20:26.768	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1)
zigbee.0 2025-04-15 16:20:26.692	info	Starting Adapter npm ...
zigbee.0 2025-04-15 16:20:26.690	info	--- creating device debug ---
zigbee.0 2025-04-15 16:20:26.686	info	delete old Backup files. keep only last 10
zigbee.0 2025-04-15 16:20:26.668	info	--> transmitPower : normal
zigbee.0 2025-04-15 16:20:26.656	info	init localConfig
zigbee.0 2025-04-15 16:20:26.617	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6

Als Stick hab ich den 12/2020 von @arteck gekaufte "CC2538+CC2592 PA Zigbee Stick/Platine" im Einsatz. Auch nie neu geflash lief immer ohne Probleme.

Danke für Eure Hilfe

Mfg
Fi

@glasfaser sagte in Keine Instanz 0:

@fi_84

jetzt funktioniert es wieder Instanz 0 ist da

dann setze den Thread auf [gelöst]

geht nicht

@glasfaser sagte in Keine Instanz 0:

@fi_84

Mach mal ein

iobroker upload all

hab ich gemacht und auch gleich mal zum testen einen Adapter installiert. jetzt funktioniert es wieder Instanz 0 ist da

@glasfaser sagte in Keine Instanz 0:

@fi_84 sagte in Keine Instanz 0:

Used repository: Stable (default)

Adapter "simple-api" : 2.6.1 , installed 2.6.2
Adapter "socketio" : 3.1.4 , installed 3.1.5

wie kommt denn da BETA rein !?

das kann ich dir auch nicht sagen.... sollte ist das ändere und wenn ja wie??

@glasfaser

pi@raspberrypi:~ $ sudo ln -s /usr/bin/node /usr/bin/nodejs
pi@raspberrypi:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && sudo apt update && sudo apt update && apt policy nodejs
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v14.18.2
v14.18.2
6.14.15
Holen:1 http://archive.raspberrypi.org/debian buster InRelease [32,6 kB]
Holen:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15,0 kB]
OK:3 https://repos.influxdata.com/debian buster InRelease
OK:4 https://deb.nodesource.com/node_14.x buster InRelease
OK:5 https://www.pivccu.de/piVCCU stable InRelease
Holen:6 http://archive.raspberrypi.org/debian buster/main armhf Packages [393 kB]
Es wurden 441 kB in 2 s geholt (281 kB/s).
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Aktualisierung für 8 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
OK:1 http://archive.raspberrypi.org/debian buster InRelease
OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
OK:3 https://repos.influxdata.com/debian buster InRelease
OK:4 https://www.pivccu.de/piVCCU stable InRelease
OK:5 https://deb.nodesource.com/node_14.x buster InRelease
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Aktualisierung für 8 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
nodejs:
  Installiert:           14.18.2-deb-1nodesource1
  Installationskandidat: 14.18.2-deb-1nodesource1
  Versionstabelle:
 *** 14.18.2-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_14.x buster/main armhf Packages
        100 /var/lib/dpkg/status
     10.24.0~dfsg-1~deb10u1 500
        500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
pi@raspberrypi:~ $ iobroker update -i
Used repository: Stable (default)
hash unchanged, use cached sources
update done
Adapter    "admin"         : 5.1.25   , installed 5.1.25
Adapter    "backitup"      : 2.2.2    , installed 2.2.2
Adapter    "ble"           : 0.12.0   , installed 0.12.0
Adapter    "device-reminder": 1.2.9   , installed 1.2.9
Adapter    "discovery"     : 2.7.3    , installed 2.7.3
Adapter    "dwd"           : 2.7.7    , installed 2.7.7
Adapter    "fullybrowser"  : 2.0.10   , installed 2.0.9 [Updateable]
Adapter    "heatingcontrol": 2.7.2    , installed 2.7.2
Adapter    "hm-rega"       : 3.0.33   , installed 3.0.33
Adapter    "hm-rpc"        : 1.14.50  , installed 1.14.50
Adapter    "ical"          : 1.11.4   , installed 1.11.4
Adapter    "icons-mfd-png" : 1.0.2    , installed 1.0.2
Adapter    "icons-mfd-svg" : 1.0.2    , installed 1.0.2
Adapter    "influxdb"      : 1.9.5    , installed 1.9.5
Adapter    "info"          : 1.9.8    , installed 1.9.8
Adapter    "jarvis"        : 2.2.1    , installed 2.2.1
Adapter    "javascript"    : 5.2.13   , installed 5.2.13
Controller "js-controller" : 3.3.21   , installed 3.3.21
Adapter    "rpi2"          : 1.3.1    , installed 1.3.1
Adapter    "simple-api"    : 2.6.1    , installed 2.6.2
Adapter    "socketio"      : 3.1.4    , installed 3.1.5
Adapter    "sonoff"        : 2.4.5    , installed 2.4.5
Adapter    "telegram"      : 1.10.0   , installed 1.10.0
Adapter    "text2command"  : 2.1.1    , installed 2.1.1
Adapter    "tr-064"        : 4.2.14   , installed 4.2.14
Adapter    "trashschedule" : 1.2.0    , installed 1.2.0
Adapter    "velux"         : 0.0.7    , installed 0.0.7
Adapter    "vis"           : 1.4.5    , installed 1.4.5
Adapter    "vis-bars"      : 0.1.4    , installed 0.1.4
Adapter    "vis-colorpicker": 1.2.0   , installed 1.2.0
Adapter    "vis-history"   : 1.0.0    , installed 1.0.0
Adapter    "vis-hqwidgets" : 1.1.7    , installed 1.1.7
Adapter    "vis-jqui-mfd"  : 1.0.12   , installed 1.0.12
Adapter    "vis-justgage"  : 1.0.2    , installed 1.0.2
Adapter    "vis-metro"     : 1.1.2    , installed 1.1.2
Adapter    "vis-players"   : 0.1.6    , installed 0.1.6
Adapter    "vis-timeandweather": 1.1.7   , installed 1.1.7
Adapter    "web"           : 3.4.9    , installed 3.4.9
Adapter    "zigbee"        : 1.6.6    , installed 1.6.6
pi@raspberrypi:~ $ iobroker status
iobroker is running on this host.


Objects type: file
States  type: file
pi@raspberrypi:~ $ iobroker version
3.3.21

Ja hab ich keine Veränderung....
Zwei Laptop und Handy selbes phänomen

das hast du natürlich vollkommen recht
admin ist version 5.1.25

GCC version
8.3.0
Git-version
2.20.1
Kernel-release
5.10.63-v7l+
Node.js version
14.18.2
NPM version
6.14.15
Knoten openssl-version
1.1.1l
Perl-version
5.28.1
Python version
2.7.16
Python 3 version
3.7.3
OS openssl-version
1.1.1d
OpenSSL-Bibliothek
OpenSSL
v8-version
8.4.371.23-node.85