Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Tester wanted - Zigbee Adapter 3.1

NEWS

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    18
    1
    582

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.0k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.3k

Tester wanted - Zigbee Adapter 3.1

Geplant Angeheftet Gesperrt Verschoben Tester
testerzhczigbeezigbee 3.1
270 Beiträge 17 Kommentatoren 18.0k Aufrufe 16 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • D dimaiv

    @asgothian
    Adapter 3.1.3 alpha 4 stürzt sofort ab.

    2025-09-24 22:25:18.298 - info: zigbee.0 (296477) 20 devices are part of the network
    2025-09-24 22:25:18.300 - info: zigbee.0 (296477) Zigbee started
    2025-09-24 22:25:18.333 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x60a423fffe61dd4a
    2025-09-24 22:25:18.349 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df66f
    2025-09-24 22:25:18.355 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df516
    2025-09-24 22:25:18.357 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df594
    2025-09-24 22:25:18.359 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x881a14fffeea1db2
    2025-09-24 22:25:18.361 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df5f6
    2025-09-24 22:25:18.362 - warn: zigbee.0 (296477) DeviceEvent:calling onEvent for start on 0xa4c13801838effff
    2025-09-24 22:25:18.365 - error: zigbee.0 (296477) 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-09-24 22:25:18.365 - error: zigbee.0 (296477) unhandled promise rejection: Cannot read properties of undefined (reading 'measurement_poll_interval')
    2025-09-24 22:25:18.537 - error: zigbee.0 (296477) TypeError: Cannot read properties of undefined (reading 'measurement_poll_interval')
    at onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:678:58)
    at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/index.ts:376:27)
    at DeviceEvent.callOnEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:69:26)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:13:13)
    at async Promise.all (index 2)
    2025-09-24 22:25:18.538 - error: zigbee.0 (296477) Cannot read properties of undefined (reading 'measurement_poll_interval')
    2025-09-24 22:25:18.592 - info: zigbee.0 (296477) Halting zigbee adapter. Restart delay is at least 30 seconds.
    2025-09-24 22:25:18.592 - info: zigbee.0 (296477) cleaning everything up
    2025-09-24 22:25:18.596 - info: zigbee.0 (296477) Saved local configuration data
    2025-09-24 22:25:18.598 - info: zigbee.0 (296477) cleanup successful
    2025-09-24 22:25:18.599 - info: zigbee.0 (296477) terminating
    2025-09-24 22:25:18.602 - warn: zigbee.0 (296477) Terminated (UNCAUGHT_EXCEPTION): Without reason
    2025-09-24 22:25:18.610 - info: zigbee.0 (296477) zigbecontroller stopped successfully - ZH was not running
    2025-09-24 22:25:18.797 - info: zigbee.0 (296477) debug devices set to []
    2025-09-24 22:25:19.207 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.208 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.208 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.209 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.210 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.211 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.211 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.212 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.213 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.214 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.214 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.215 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.216 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.216 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.217 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.217 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.218 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.218 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.219 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.219 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.220 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.220 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.220 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.221 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.221 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.222 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.222 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.223 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.223 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.224 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.224 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.225 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.225 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.226 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.227 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.228 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.229 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.230 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.231 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.232 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.232 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.233 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.234 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.234 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.235 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.236 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.237 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.237 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.238 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.239 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.239 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.240 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.241 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.242 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.242 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.243 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.244 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.245 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.245 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.246 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.246 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.247 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.248 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.248 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.249 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.249 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.250 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.251 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.251 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.252 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.252 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.253 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.253 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.254 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.254 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.255 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.255 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.255 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.256 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.256 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.257 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.257 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.258 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.258 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.470 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.471 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.471 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.472 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.472 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.473 - warn: zigbee.0 (296477) get state error: Connection is closed.
    2025-09-24 22:25:19.478 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/RTCGQ11LM.png$%$data": DB closed
    2025-09-24 22:25:19.478 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/WSDCGQ11LM.png$%$data": DB closed
    2025-09-24 22:25:19.479 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/ptvo.switch.png$%$data": DB closed
    2025-09-24 22:25:19.479 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/MCCGQ11LM.png$%$data": DB closed
    2025-09-24 22:25:19.499 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/MCCGQ11LM.png$%$data": Connection is closed.
    2025-09-24 22:25:19.500 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/TS0121_plug.png$%$data": Connection is closed.
    2025-09-24 22:25:19.500 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/DIYRuZ_Flower.png$%$data": Connection is closed.
    2025-09-24 22:25:19.501 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
    2025-09-24 22:25:19.501 - error: zigbee.0 (296477) Cannot check file existence of "cfg.f.zigbee.admin$%$img/HG08010.png$%$data": Connection is closed.
    2025-09-24 22:25:19.542 - error: zigbee.0 (296477) 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-09-24 22:25:19.542 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.544 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.544 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.552 - error: zigbee.0 (296477) 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-09-24 22:25:19.553 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.554 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.554 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.556 - error: zigbee.0 (296477) 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-09-24 22:25:19.557 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.557 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.558 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.560 - error: zigbee.0 (296477) 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-09-24 22:25:19.561 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.561 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.562 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.564 - error: zigbee.0 (296477) 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-09-24 22:25:19.564 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.565 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.565 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.567 - error: zigbee.0 (296477) 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-09-24 22:25:19.568 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.568 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.569 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.571 - error: zigbee.0 (296477) 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-09-24 22:25:19.572 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.572 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.573 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.575 - error: zigbee.0 (296477) 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-09-24 22:25:19.576 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.576 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.576 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.579 - error: zigbee.0 (296477) 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-09-24 22:25:19.580 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.580 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.581 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.582 - error: zigbee.0 (296477) 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-09-24 22:25:19.583 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.583 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.584 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.586 - error: zigbee.0 (296477) 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-09-24 22:25:19.586 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.587 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.587 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.589 - error: zigbee.0 (296477) 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-09-24 22:25:19.590 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.590 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.591 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.592 - error: zigbee.0 (296477) 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-09-24 22:25:19.593 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.594 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.595 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.596 - error: zigbee.0 (296477) 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-09-24 22:25:19.596 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.596 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.597 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.598 - error: zigbee.0 (296477) 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-09-24 22:25:19.599 - error: zigbee.0 (296477) unhandled promise rejection: DB closed
    2025-09-24 22:25:19.599 - error: zigbee.0 (296477) Error: DB closed
    at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    at Object.onceWrapper (node:events:639:26)
    at Socket.emit (node:events:524:28)
    at Socket.emit (node:domain:489:12)
    at TCP. (node:net:343:12)
    2025-09-24 22:25:19.600 - error: zigbee.0 (296477) DB closed
    2025-09-24 22:25:19.602 - info: zigbee.0 (296477) downloading https://www.zigbee2mqtt.io/images/devices/RTCGQ11LM.png to img/RTCGQ11LM.png
    2025-09-24 22:25:19.629 - info: zigbee.0 (296477) downloading https://www.zigbee2mqtt.io/images/devices/WSDCGQ11LM.png to img/WSDCGQ11LM.png
    2025-09-24 22:25:19.639 - info: zigbee.0 (296477) downloading https://www.zigbee2mqtt.io/images/devices/ptvo.switch.png to img/ptvo.switch.png
    2025-09-24 22:25:19.647 - info: zigbee.0 (296477) downloading https://www.zigbee2mqtt.io/images/devices/MCCGQ11LM.png to img/MCCGQ11LM.png
    2025-09-24 22:25:19.878 - error: host.GartenIoB Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'measurement_poll_interval')
    2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:678:58)
    2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/index.ts:376:27)
    2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at DeviceEvent.callOnEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:69:26)
    2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
    2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:13:13)
    2025-09-24 22:25:19.879 - error: host.GartenIoB Caught by controller[1]: at async Promise.all (index 2)
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: Error: DB closed
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[3]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[4]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.880 - error: host.GartenIoB Caught by controller[5]: Error: DB closed
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[5]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[6]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[7]: Error: DB closed
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[7]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.881 - error: host.GartenIoB Caught by controller[7]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[7]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[7]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[7]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[7]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[8]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[9]: Error: DB closed
    2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[9]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.882 - error: host.GartenIoB Caught by controller[9]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[9]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[9]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[9]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[9]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[10]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: Error: DB closed
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.883 - error: host.GartenIoB Caught by controller[11]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[11]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[11]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[12]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: Error: DB closed
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.884 - error: host.GartenIoB Caught by controller[13]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[13]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[14]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: Error: DB closed
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[15]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.885 - error: host.GartenIoB Caught by controller[16]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: Error: DB closed
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[17]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[18]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.886 - error: host.GartenIoB Caught by controller[19]: Error: DB closed
    2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[19]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.887 - error: host.GartenIoB Caught by controller[20]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: Error: DB closed
    2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[21]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.888 - error: host.GartenIoB Caught by controller[22]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: Error: DB closed
    2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.889 - error: host.GartenIoB Caught by controller[23]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[24]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: Error: DB closed
    2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.890 - error: host.GartenIoB Caught by controller[25]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[25]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[26]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: Error: DB closed
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.891 - error: host.GartenIoB Caught by controller[27]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[28]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: Error: DB closed
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[29]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[30]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.892 - error: host.GartenIoB Caught by controller[31]: Error: DB closed
    2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
    2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
    2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at Object.onceWrapper (node:events:639:26)
    2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at Socket.emit (node:events:524:28)
    2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at Socket.emit (node:domain:489:12)
    2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[31]: at TCP. (node:net:343:12)
    2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[32]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.893 - error: host.GartenIoB Caught by controller[33]: Error: DB closed
    2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[33]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[34]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[35]: Error: DB closed
    2025-09-24 22:25:19.894 - error: host.GartenIoB Caught by controller[35]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[35]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[35]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[35]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[35]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[36]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[37]: Error: DB closed
    2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[37]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.895 - error: host.GartenIoB Caught by controller[37]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[37]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[37]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[37]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[38]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: Error: DB closed
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.896 - error: host.GartenIoB Caught by controller[39]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[39]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[40]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: Error: DB closed
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[41]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.897 - error: host.GartenIoB Caught by controller[42]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: Error: DB closed
    2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.898 - error: host.GartenIoB Caught by controller[43]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[43]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[44]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: Error: DB closed
    2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.899 - error: host.GartenIoB Caught by controller[45]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.900 - error: host.GartenIoB Caught by controller[45]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.900 - error: host.GartenIoB Caught by controller[46]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.900 - error: host.GartenIoB Caught by controller[47]: Error: DB closed
    2025-09-24 22:25:19.900 - error: host.GartenIoB Caught by controller[47]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[47]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[47]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[47]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[47]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[48]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.901 - error: host.GartenIoB Caught by controller[49]: Error: DB closed
    2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[49]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[50]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.902 - error: host.GartenIoB Caught by controller[51]: Error: DB closed
    2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[51]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[52]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[53]: Error: DB closed
    2025-09-24 22:25:19.903 - error: host.GartenIoB Caught by controller[53]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[53]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[53]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[53]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[53]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[54]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[55]: Error: DB closed
    2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[55]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.904 - error: host.GartenIoB Caught by controller[55]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[55]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[55]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[55]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[56]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[57]: Error: DB closed
    2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[57]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[57]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.905 - error: host.GartenIoB Caught by controller[57]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[57]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[57]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[58]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: Error: DB closed
    2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.906 - error: host.GartenIoB Caught by controller[59]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[59]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[60]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: Error: DB closed
    2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.907 - error: host.GartenIoB Caught by controller[61]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[62]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: Error: DB closed
    2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[63]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.908 - error: host.GartenIoB Caught by controller[64]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: Error: DB closed
    2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[65]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.909 - error: host.GartenIoB Caught by controller[66]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
    2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: Error: DB closed
    2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
    2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
    2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
    2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
    2025-09-24 22:25:19.910 - error: host.GartenIoB Caught by controller[67]: at processImmediate (node:internal/timers:485:21)
    2025-09-24 22:25:19.910 - error: host.GartenIoB instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
    2025-09-24 22:25:19.911 - info: host.GartenIoB Restart adapter system.adapter.zigbee.0 because enabled
    2025-09-24 22:25:19.911 - warn: host.GartenIoB Do not restart adapter system.adapter.zigbee.0 because restart loop detected
    2025-09-24 22:25:25.285 - info: host.GartenIoB "system.adapter.zigbee.0" disabled
    
    AsgothianA Offline
    AsgothianA Offline
    Asgothian
    Developer
    schrieb am zuletzt editiert von Asgothian
    #162

    @dimaiv Log bitte. Bei mir läuft der (sowohl auf dem Testsystem als auch auf dem Produktivsystem)

    ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
    "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

    D 1 Antwort Letzte Antwort
    0
    • AsgothianA Asgothian

      @dimaiv Log bitte. Bei mir läuft der (sowohl auf dem Testsystem als auch auf dem Produktivsystem)

      D Offline
      D Offline
      dimaiv
      schrieb am zuletzt editiert von
      #163

      @asgothian
      Oben eingefügt.

      ioBroker- NUC8i3 / Proxmox / VM
      Node.js v22.21.0
      NPM v10.9.4
      JS controller 7.0.7
      Admin 7.7.19
      ZigBee Adapter 3.2.5
      Zigbee LAN Gateway CC2652P
      Zigbee Firmware 20250321

      AsgothianA 1 Antwort Letzte Antwort
      0
      • D dimaiv

        @asgothian
        Oben eingefügt.

        AsgothianA Offline
        AsgothianA Offline
        Asgothian
        Developer
        schrieb am zuletzt editiert von Asgothian
        #164

        @dimaiv Patch mal bitte bei Dir die Datei

        /opt/iobroker/node-modules/iobroker.zigbee/lib/zbDeviceEvevnt.js

        von

                if (mappedDevice && mappedDevice.onEvent && eventData.data) {
                    this.warn(`calling onEvent for ${eventData.type} on ${device.ieeeAddr}`);
                    mappedDevice.onEvent({type, data});
                }
            }
        }
        
        module.exports = DeviceEvent;
        

        zu

                if (mappedDevice && mappedDevice.onEvent && eventData.data) {
                    this.warn(`calling onEvent for ${eventData.type} on ${device.ieeeAddr}`);
                    try {
                        mappedDevice.onEvent({type, data});
                    }
                    catch (error)
                   {
                        this.warn(`error in onEvent: ${error && error.message ? error.message : 'no details'}`);
                   }
                }
            }
        }
        
        module.exports = DeviceEvent;
        

        Der eigentliche Fehler kommt aus dem Konverter.

        A.

        ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
        "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

        D 1 Antwort Letzte Antwort
        0
        • AsgothianA Asgothian

          @dimaiv Patch mal bitte bei Dir die Datei

          /opt/iobroker/node-modules/iobroker.zigbee/lib/zbDeviceEvevnt.js

          von

                  if (mappedDevice && mappedDevice.onEvent && eventData.data) {
                      this.warn(`calling onEvent for ${eventData.type} on ${device.ieeeAddr}`);
                      mappedDevice.onEvent({type, data});
                  }
              }
          }
          
          module.exports = DeviceEvent;
          

          zu

                  if (mappedDevice && mappedDevice.onEvent && eventData.data) {
                      this.warn(`calling onEvent for ${eventData.type} on ${device.ieeeAddr}`);
                      try {
                          mappedDevice.onEvent({type, data});
                      }
                      catch (error)
                     {
                          this.warn(`error in onEvent: ${error && error.message ? error.message : 'no details'}`);
                     }
                  }
              }
          }
          
          module.exports = DeviceEvent;
          

          Der eigentliche Fehler kommt aus dem Konverter.

          A.

          D Offline
          D Offline
          dimaiv
          schrieb am zuletzt editiert von
          #165

          @asgothian
          Gleiche Fehler

          2025-09-24 23:03:33.936 - info: zigbee.0 (298385) 20 devices are part of the network
          2025-09-24 23:03:33.938 - info: zigbee.0 (298385) Zigbee started
          2025-09-24 23:03:33.971 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x60a423fffe61dd4a
          2025-09-24 23:03:33.986 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df66f
          2025-09-24 23:03:33.993 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df516
          2025-09-24 23:03:33.995 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df594
          2025-09-24 23:03:33.996 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x881a14fffeea1db2
          2025-09-24 23:03:33.999 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df5f6
          2025-09-24 23:03:34.000 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0xa4c13801838effff
          2025-09-24 23:03:34.022 - error: zigbee.0 (298385) 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-09-24 23:03:34.022 - error: zigbee.0 (298385) unhandled promise rejection: Cannot read properties of undefined (reading 'measurement_poll_interval')
          2025-09-24 23:03:34.169 - error: zigbee.0 (298385) TypeError: Cannot read properties of undefined (reading 'measurement_poll_interval')
          at onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:678:58)
          at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/index.ts:376:27)
          at DeviceEvent.callOnEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:71:30)
          at processTicksAndRejections (node:internal/process/task_queues:95:5)
          at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:13:13)
          at async Promise.all (index 2)
          2025-09-24 23:03:34.169 - error: zigbee.0 (298385) Cannot read properties of undefined (reading 'measurement_poll_interval')
          2025-09-24 23:03:34.285 - info: zigbee.0 (298385) Halting zigbee adapter. Restart delay is at least 30 seconds.
          2025-09-24 23:03:34.286 - info: zigbee.0 (298385) cleaning everything up
          2025-09-24 23:03:34.290 - info: zigbee.0 (298385) Saved local configuration data
          2025-09-24 23:03:34.292 - info: zigbee.0 (298385) cleanup successful
          2025-09-24 23:03:34.293 - info: zigbee.0 (298385) terminating
          2025-09-24 23:03:34.296 - warn: zigbee.0 (298385) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2025-09-24 23:03:34.304 - info: zigbee.0 (298385) zigbecontroller stopped successfully - ZH was not running
          2025-09-24 23:03:34.439 - info: zigbee.0 (298385) debug devices set to []
          2025-09-24 23:03:34.885 - warn: zigbee.0 (298385) get state error: DB closed
          2025-09-24 23:03:34.886 - warn: zigbee.0 (298385) get state error: DB closed
          2025-09-24 23:03:34.886 - warn: zigbee.0 (298385) get state error: DB closed
          

          ioBroker- NUC8i3 / Proxmox / VM
          Node.js v22.21.0
          NPM v10.9.4
          JS controller 7.0.7
          Admin 7.7.19
          ZigBee Adapter 3.2.5
          Zigbee LAN Gateway CC2652P
          Zigbee Firmware 20250321

          AsgothianA 1 Antwort Letzte Antwort
          0
          • D dimaiv

            @asgothian
            Gleiche Fehler

            2025-09-24 23:03:33.936 - info: zigbee.0 (298385) 20 devices are part of the network
            2025-09-24 23:03:33.938 - info: zigbee.0 (298385) Zigbee started
            2025-09-24 23:03:33.971 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x60a423fffe61dd4a
            2025-09-24 23:03:33.986 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df66f
            2025-09-24 23:03:33.993 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df516
            2025-09-24 23:03:33.995 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df594
            2025-09-24 23:03:33.996 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x881a14fffeea1db2
            2025-09-24 23:03:33.999 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df5f6
            2025-09-24 23:03:34.000 - warn: zigbee.0 (298385) DeviceEvent:calling onEvent for start on 0xa4c13801838effff
            2025-09-24 23:03:34.022 - error: zigbee.0 (298385) 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-09-24 23:03:34.022 - error: zigbee.0 (298385) unhandled promise rejection: Cannot read properties of undefined (reading 'measurement_poll_interval')
            2025-09-24 23:03:34.169 - error: zigbee.0 (298385) TypeError: Cannot read properties of undefined (reading 'measurement_poll_interval')
            at onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:678:58)
            at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/index.ts:376:27)
            at DeviceEvent.callOnEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:71:30)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:13:13)
            at async Promise.all (index 2)
            2025-09-24 23:03:34.169 - error: zigbee.0 (298385) Cannot read properties of undefined (reading 'measurement_poll_interval')
            2025-09-24 23:03:34.285 - info: zigbee.0 (298385) Halting zigbee adapter. Restart delay is at least 30 seconds.
            2025-09-24 23:03:34.286 - info: zigbee.0 (298385) cleaning everything up
            2025-09-24 23:03:34.290 - info: zigbee.0 (298385) Saved local configuration data
            2025-09-24 23:03:34.292 - info: zigbee.0 (298385) cleanup successful
            2025-09-24 23:03:34.293 - info: zigbee.0 (298385) terminating
            2025-09-24 23:03:34.296 - warn: zigbee.0 (298385) Terminated (UNCAUGHT_EXCEPTION): Without reason
            2025-09-24 23:03:34.304 - info: zigbee.0 (298385) zigbecontroller stopped successfully - ZH was not running
            2025-09-24 23:03:34.439 - info: zigbee.0 (298385) debug devices set to []
            2025-09-24 23:03:34.885 - warn: zigbee.0 (298385) get state error: DB closed
            2025-09-24 23:03:34.886 - warn: zigbee.0 (298385) get state error: DB closed
            2025-09-24 23:03:34.886 - warn: zigbee.0 (298385) get state error: DB closed
            
            AsgothianA Offline
            AsgothianA Offline
            Asgothian
            Developer
            schrieb am zuletzt editiert von Asgothian
            #166

            @dimaiv Seltsam - der try/catch sollte das eigentlich fangen.

            Das kann ich ohne Gerät effektiv nicht Debuggen.

            A.

            Nachtrag: Eine mögliche Quelle hab ich noch. Bitte den folgenden Aufruf auch noch patchen:

                        try {
                            mappedDevice.onEvent({type, data});
                        }
            

            zu

                        try {
                            mappedDevice.onEvent(eventData);
                        }
            

            ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
            "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

            D 1 Antwort Letzte Antwort
            0
            • AsgothianA Asgothian

              @dimaiv Seltsam - der try/catch sollte das eigentlich fangen.

              Das kann ich ohne Gerät effektiv nicht Debuggen.

              A.

              Nachtrag: Eine mögliche Quelle hab ich noch. Bitte den folgenden Aufruf auch noch patchen:

                          try {
                              mappedDevice.onEvent({type, data});
                          }
              

              zu

                          try {
                              mappedDevice.onEvent(eventData);
                          }
              
              D Offline
              D Offline
              dimaiv
              schrieb am zuletzt editiert von
              #167

              @asgothian
              Aber welchen genau...
              So komme ich such nicht zum deaktivieren...
              Hätte ich eins nach dem anderen probiert...

              ioBroker- NUC8i3 / Proxmox / VM
              Node.js v22.21.0
              NPM v10.9.4
              JS controller 7.0.7
              Admin 7.7.19
              ZigBee Adapter 3.2.5
              Zigbee LAN Gateway CC2652P
              Zigbee Firmware 20250321

              AsgothianA 1 Antwort Letzte Antwort
              0
              • D dimaiv

                @asgothian
                Aber welchen genau...
                So komme ich such nicht zum deaktivieren...
                Hätte ich eins nach dem anderen probiert...

                AsgothianA Offline
                AsgothianA Offline
                Asgothian
                Developer
                schrieb am zuletzt editiert von
                #168

                @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                @asgothian
                Aber welchen genau...
                So komme ich such nicht zum deaktivieren...
                Hätte ich eins nach dem anderen probiert...

                Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                0xa4c13801838effff

                Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                A.

                ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                D 2 Antworten Letzte Antwort
                0
                • AsgothianA Asgothian

                  @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                  @asgothian
                  Aber welchen genau...
                  So komme ich such nicht zum deaktivieren...
                  Hätte ich eins nach dem anderen probiert...

                  Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                  0xa4c13801838effff

                  Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                  A.

                  D Offline
                  D Offline
                  dimaiv
                  schrieb am zuletzt editiert von dimaiv
                  #169

                  @asgothian
                  Jetzt startet gar nicht

                  2025-09-24 23:22:06.365 - info: host.GartenIoB iobroker Updating objects from io-package.json for adapter "zigbee" with version "3.1.3-alpha-4"
                  2025-09-24 23:22:07.449 - info: host.GartenIoB iobroker exit 0
                  2025-09-24 23:22:22.257 - info: host.GartenIoB "system.adapter.zigbee.0" enabled
                  2025-09-24 23:22:23.077 - info: host.GartenIoB instance system.adapter.zigbee.0 in version "3.1.3-alpha-4" (non-npm: ioBroker/ioBroker.zigbee) started with pid 305740
                  2025-09-24 23:22:24.723 - error: host.GartenIoB Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:80
                  2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: SyntaxError: Unexpected end of input
                  2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1472:18)
                  2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1501:20)
                  2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
                  2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1275:32)
                  2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1096:12)
                  2025-09-24 23:22:24.724 - error: host.GartenIoB Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1298:19)
                  2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: at require (node:internal/modules/helpers:182:18)
                  2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:12:24)
                  2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1529:14)
                  2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1613:10)
                  2025-09-24 23:22:24.725 - error: host.GartenIoB Caught by controller[0]: Node.js v20.19.4
                  2025-09-24 23:22:24.725 - error: host.GartenIoB instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                  2025-09-24 23:22:24.726 - info: host.GartenIoB Restart adapter system.adapter.zigbee.0 because enabled
                  2025-09-24 23:22:29.156 - info: host.GartenIoB "system.adapter.zigbee.0" disabled
                  

                  es ist Version frisch vom Git

                  ioBroker- NUC8i3 / Proxmox / VM
                  Node.js v22.21.0
                  NPM v10.9.4
                  JS controller 7.0.7
                  Admin 7.7.19
                  ZigBee Adapter 3.2.5
                  Zigbee LAN Gateway CC2652P
                  Zigbee Firmware 20250321

                  1 Antwort Letzte Antwort
                  0
                  • AsgothianA Asgothian

                    @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                    @asgothian
                    Aber welchen genau...
                    So komme ich such nicht zum deaktivieren...
                    Hätte ich eins nach dem anderen probiert...

                    Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                    0xa4c13801838effff

                    Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                    A.

                    D Offline
                    D Offline
                    dimaiv
                    schrieb am zuletzt editiert von Homoran
                    #170

                    @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                    @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                    @asgothian
                    Aber welchen genau...
                    So komme ich such nicht zum deaktivieren...
                    Hätte ich eins nach dem anderen probiert...

                    Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                    0xa4c13801838effff

                    Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                    A.

                    Es ist ein Temperatur Sensor: (https://www.zigbee2mqtt.io/devices/SNZB-02LD.html)

                    ioBroker- NUC8i3 / Proxmox / VM
                    Node.js v22.21.0
                    NPM v10.9.4
                    JS controller 7.0.7
                    Admin 7.7.19
                    ZigBee Adapter 3.2.5
                    Zigbee LAN Gateway CC2652P
                    Zigbee Firmware 20250321

                    AsgothianA 1 Antwort Letzte Antwort
                    0
                    • D dimaiv

                      @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                      @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                      @asgothian
                      Aber welchen genau...
                      So komme ich such nicht zum deaktivieren...
                      Hätte ich eins nach dem anderen probiert...

                      Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                      0xa4c13801838effff

                      Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                      A.

                      Es ist ein Temperatur Sensor: (https://www.zigbee2mqtt.io/devices/SNZB-02LD.html)

                      AsgothianA Offline
                      AsgothianA Offline
                      Asgothian
                      Developer
                      schrieb am zuletzt editiert von Asgothian
                      #171

                      @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                      @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                      @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                      @asgothian
                      Aber welchen genau...
                      So komme ich such nicht zum deaktivieren...
                      Hätte ich eins nach dem anderen probiert...

                      Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                      0xa4c13801838effff

                      Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                      A.

                      Es ist ein Temperatur Sensor

                      Dumme Tippfehler, jetzt sollte die git Version wieder gehen.
                      Was genau für ein Sensor ?

                      ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                      "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                      D 2 Antworten Letzte Antwort
                      0
                      • AsgothianA Asgothian

                        @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                        @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                        @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                        @asgothian
                        Aber welchen genau...
                        So komme ich such nicht zum deaktivieren...
                        Hätte ich eins nach dem anderen probiert...

                        Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                        0xa4c13801838effff

                        Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                        A.

                        Es ist ein Temperatur Sensor

                        Dumme Tippfehler, jetzt sollte die git Version wieder gehen.
                        Was genau für ein Sensor ?

                        D Offline
                        D Offline
                        dimaiv
                        schrieb am zuletzt editiert von
                        #172

                        @asgothian
                        Immer noch

                        2025-09-24 23:36:41.771 - info: zigbee.0 (310968) 20 devices are part of the network
                        2025-09-24 23:36:41.774 - info: zigbee.0 (310968) Zigbee started
                        2025-09-24 23:36:41.809 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x60a423fffe61dd4a
                        2025-09-24 23:36:41.825 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df66f
                        2025-09-24 23:36:41.832 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df516
                        2025-09-24 23:36:41.834 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df594
                        2025-09-24 23:36:41.835 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x881a14fffeea1db2
                        2025-09-24 23:36:41.838 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0x28dba7fffe6df5f6
                        2025-09-24 23:36:41.839 - warn: zigbee.0 (310968) DeviceEvent:calling onEvent for start on 0xa4c13801838effff
                        2025-09-24 23:36:41.841 - error: zigbee.0 (310968) 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-09-24 23:36:41.842 - error: zigbee.0 (310968) unhandled promise rejection: Cannot read properties of undefined (reading 'measurement_poll_interval')
                        2025-09-24 23:36:42.010 - error: zigbee.0 (310968) TypeError: Cannot read properties of undefined (reading 'measurement_poll_interval')
                        at onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/lib/modernExtend.ts:678:58)
                        at Object.onEvent (/opt/iobroker/node_modules/zigbee-herdsman-converters/src/index.ts:376:27)
                        at DeviceEvent.callOnEvent (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:70:30)
                        at processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at DeviceEvent.onZigbeeStarted (/opt/iobroker/node_modules/iobroker.zigbee/lib/zbDeviceEvent.js:13:13)
                        at async Promise.all (index 2)
                        2025-09-24 23:36:42.011 - error: zigbee.0 (310968) Cannot read properties of undefined (reading 'measurement_poll_interval')
                        2025-09-24 23:36:42.069 - info: zigbee.0 (310968) Halting zigbee adapter. Restart delay is at least 30 seconds.
                        2025-09-24 23:36:42.070 - info: zigbee.0 (310968) cleaning everything up
                        2025-09-24 23:36:42.073 - info: zigbee.0 (310968) Saved local configuration data
                        2025-09-24 23:36:42.076 - info: zigbee.0 (310968) cleanup successful
                        2025-09-24 23:36:42.077 - info: zigbee.0 (310968) terminating
                        2025-09-24 23:36:42.081 - warn: zigbee.0 (310968) Terminated (UNCAUGHT_EXCEPTION): Without reason
                        2025-09-24 23:36:42.089 - info: zigbee.0 (310968) zigbecontroller stopped successfully - ZH was not running
                        2025-09-24 23:36:42.509 - info: zigbee.0 (310968) debug devices set to []
                        2025-09-24 23:36:42.684 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.685 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.686 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.686 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.687 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.688 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.688 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.689 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.690 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.691 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.691 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.693 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.693 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.694 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.694 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.695 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.695 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.696 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.697 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.697 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.698 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.699 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.700 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.700 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.701 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.702 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.703 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.703 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.704 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.705 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.705 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.706 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.707 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.708 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.709 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.709 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.710 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.711 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.712 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.713 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.714 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.715 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.716 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.717 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.718 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.719 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.720 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.721 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.722 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.722 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.723 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.724 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.725 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.726 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.727 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.728 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.729 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.730 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.731 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.732 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.733 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.734 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.735 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.735 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.736 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.737 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.738 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.738 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.739 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.797 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.798 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.799 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.800 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.800 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.801 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.801 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.802 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.803 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.804 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.805 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.805 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.806 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.807 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.808 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.809 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.810 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:42.811 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/RTCGQ11LM.png to img/RTCGQ11LM.png
                        2025-09-24 23:36:42.838 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/WSDCGQ11LM.png to img/WSDCGQ11LM.png
                        2025-09-24 23:36:42.984 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/ptvo.switch.png$%$data": DB closed
                        2025-09-24 23:36:42.985 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/MCCGQ11LM.png$%$data": DB closed
                        2025-09-24 23:36:42.985 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/MCCGQ11LM.png$%$data": DB closed
                        2025-09-24 23:36:42.985 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/TS0121_plug.png$%$data": DB closed
                        2025-09-24 23:36:42.986 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/DIYRuZ_Flower.png$%$data": DB closed
                        2025-09-24 23:36:42.986 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": DB closed
                        2025-09-24 23:36:42.994 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/HG08010.png$%$data": Connection is closed.
                        2025-09-24 23:36:42.995 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/WXCJKG13LM.png$%$data": Connection is closed.
                        2025-09-24 23:36:42.995 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/Egony_Flower.png$%$data": Connection is closed.
                        2025-09-24 23:36:42.996 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/WSDCGQ11LM.png$%$data": Connection is closed.
                        2025-09-24 23:36:42.996 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
                        2025-09-24 23:36:42.997 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
                        2025-09-24 23:36:42.998 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/TS0601_din.png$%$data": Connection is closed.
                        2025-09-24 23:36:42.999 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
                        2025-09-24 23:36:42.999 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/Egony_Flower.png$%$data": Connection is closed.
                        2025-09-24 23:36:43.000 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SWV.png$%$data": Connection is closed.
                        2025-09-24 23:36:43.000 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/SNZB-02LD.png$%$data": Connection is closed.
                        2025-09-24 23:36:43.001 - error: zigbee.0 (310968) Cannot check file existence of "cfg.f.zigbee.admin$%$img/RB-SRAIN01.png$%$data": Connection is closed.
                        2025-09-24 23:36:43.039 - error: zigbee.0 (310968) 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-09-24 23:36:43.040 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.042 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.042 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.050 - error: zigbee.0 (310968) 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-09-24 23:36:43.051 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.052 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.052 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.054 - error: zigbee.0 (310968) 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-09-24 23:36:43.054 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.055 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.055 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.058 - error: zigbee.0 (310968) 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-09-24 23:36:43.059 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.059 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.059 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.061 - error: zigbee.0 (310968) 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-09-24 23:36:43.061 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.062 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.062 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.064 - error: zigbee.0 (310968) 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-09-24 23:36:43.065 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.065 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.065 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.067 - error: zigbee.0 (310968) 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-09-24 23:36:43.068 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.068 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.069 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.070 - error: zigbee.0 (310968) 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-09-24 23:36:43.071 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.071 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.072 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.074 - error: zigbee.0 (310968) 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-09-24 23:36:43.075 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.075 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.076 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.077 - error: zigbee.0 (310968) 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-09-24 23:36:43.078 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.078 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.079 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.081 - error: zigbee.0 (310968) 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-09-24 23:36:43.082 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.082 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.082 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.084 - error: zigbee.0 (310968) 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-09-24 23:36:43.084 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.085 - error: zigbee.0 (310968) Error: DB closed
                        at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                        at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                        at Object.onceWrapper (node:events:639:26)
                        at Socket.emit (node:events:524:28)
                        at Socket.emit (node:domain:489:12)
                        at TCP. (node:net:343:12)
                        2025-09-24 23:36:43.085 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.087 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/ptvo.switch.png to img/ptvo.switch.png
                        2025-09-24 23:36:43.095 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/MCCGQ11LM.png to img/MCCGQ11LM.png
                        2025-09-24 23:36:43.101 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/TS0121_plug.png to img/TS0121_plug.png
                        2025-09-24 23:36:43.107 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/DIYRuZ_Flower.png to img/DIYRuZ_Flower.png
                        2025-09-24 23:36:43.113 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/SWV.png to img/SWV.png
                        2025-09-24 23:36:43.129 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/HG08010.png to img/HG08010.png
                        2025-09-24 23:36:43.137 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/WXCJKG13LM.png to img/WXCJKG13LM.png
                        2025-09-24 23:36:43.146 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/Egony_Flower.png to img/Egony_Flower.png
                        2025-09-24 23:36:43.153 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/TS0601_din.png to img/TS0601_din.png
                        2025-09-24 23:36:43.160 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/SNZB-02LD.png to img/SNZB-02LD.png
                        2025-09-24 23:36:43.166 - info: zigbee.0 (310968) downloading https://www.zigbee2mqtt.io/images/devices/RB-SRAIN01.png to img/RB-SRAIN01.png
                        2025-09-24 23:36:43.172 - warn: zigbee.0 (310968) Could not perform strict object check of state zigbee.0.00124b001ec80d25.link_quality: DB closed
                        2025-09-24 23:36:43.172 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:43.173 - warn: zigbee.0 (310968) Could not perform strict object check of state zigbee.0.00124b001ec80d25.msg_from_zigbee: DB closed
                        2025-09-24 23:36:43.174 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:43.174 - warn: zigbee.0 (310968) Could not perform strict object check of state zigbee.0.00124b001ec80d25.state_l1: DB closed
                        2025-09-24 23:36:43.175 - warn: zigbee.0 (310968) get state error: Connection is closed.
                        2025-09-24 23:36:43.175 - error: zigbee.0 (310968) 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-09-24 23:36:43.176 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.177 - error: zigbee.0 (310968) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                        at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                        at processImmediate (node:internal/timers:485:21)
                        2025-09-24 23:36:43.178 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.183 - error: zigbee.0 (310968) 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-09-24 23:36:43.184 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.185 - error: zigbee.0 (310968) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                        at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                        at processImmediate (node:internal/timers:485:21)
                        2025-09-24 23:36:43.186 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.191 - error: zigbee.0 (310968) 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-09-24 23:36:43.191 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.193 - error: zigbee.0 (310968) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                        at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                        at processImmediate (node:internal/timers:485:21)
                        2025-09-24 23:36:43.194 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.198 - error: zigbee.0 (310968) 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-09-24 23:36:43.198 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.199 - error: zigbee.0 (310968) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                        at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                        at processImmediate (node:internal/timers:485:21)
                        2025-09-24 23:36:43.200 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.203 - error: zigbee.0 (310968) 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-09-24 23:36:43.204 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.205 - error: zigbee.0 (310968) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                        at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                        at processImmediate (node:internal/timers:485:21)
                        2025-09-24 23:36:43.205 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.208 - error: zigbee.0 (310968) 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-09-24 23:36:43.209 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.210 - error: zigbee.0 (310968) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                        at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                        at processImmediate (node:internal/timers:485:21)
                        2025-09-24 23:36:43.211 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.214 - error: zigbee.0 (310968) 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-09-24 23:36:43.214 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.215 - error: zigbee.0 (310968) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                        at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                        at processImmediate (node:internal/timers:485:21)
                        2025-09-24 23:36:43.216 - error: zigbee.0 (310968) DB closed
                        2025-09-24 23:36:43.220 - error: zigbee.0 (310968) 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-09-24 23:36:43.220 - error: zigbee.0 (310968) unhandled promise rejection: DB closed
                        2025-09-24 23:36:43.221 - error: zigbee.0 (310968) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:121:25)
                        at ObjectsInRedisClient._getObject (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3011:37)
                        at Immediate. (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:3070:29)
                        at processImmediate (node:internal/timers:485:21)
                        
                        

                        ich muss Log kürzen, sonnst meckert Forum.

                        ioBroker- NUC8i3 / Proxmox / VM
                        Node.js v22.21.0
                        NPM v10.9.4
                        JS controller 7.0.7
                        Admin 7.7.19
                        ZigBee Adapter 3.2.5
                        Zigbee LAN Gateway CC2652P
                        Zigbee Firmware 20250321

                        1 Antwort Letzte Antwort
                        0
                        • AsgothianA Asgothian

                          @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                          @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                          @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                          @asgothian
                          Aber welchen genau...
                          So komme ich such nicht zum deaktivieren...
                          Hätte ich eins nach dem anderen probiert...

                          Deaktivieren zieht an der Stelle ggf. noch nicht. Ansonsten, der der den Absturz erzeugt ist dieser:
                          0xa4c13801838effff

                          Erstmal geht es darum die Abstürze loszuwerden - der Fehler darf bleiben, der Adapter muss weiter laufen

                          A.

                          Es ist ein Temperatur Sensor

                          Dumme Tippfehler, jetzt sollte die git Version wieder gehen.
                          Was genau für ein Sensor ?

                          D Offline
                          D Offline
                          dimaiv
                          schrieb am zuletzt editiert von
                          #173

                          @asgothian sagte in Tester wanted - Zigbee Adapter 3.1:

                          Was genau für ein Sensor ?

                          es ist verlinkt da.

                          ioBroker- NUC8i3 / Proxmox / VM
                          Node.js v22.21.0
                          NPM v10.9.4
                          JS controller 7.0.7
                          Admin 7.7.19
                          ZigBee Adapter 3.2.5
                          Zigbee LAN Gateway CC2652P
                          Zigbee Firmware 20250321

                          1 Antwort Letzte Antwort
                          0
                          • AsgothianA Offline
                            AsgothianA Offline
                            Asgothian
                            Developer
                            schrieb am zuletzt editiert von Asgothian
                            #174

                            @dimaiv ok, der kann es nicht sein, der hat kein on Event.
                            Dann sollte es der auf den folgende in der Liste der Geräte sein. Die müsste vorher im log stehen.

                            A.

                            P.s. damit ist für heute erst einmal Schluss. Morgen kann ich weiter machen. Zum Thema log kürzen, alles was nach DB closed oder connection closed kommt ist irrelevant.

                            A.

                            ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                            "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                            D 1 Antwort Letzte Antwort
                            1
                            • AsgothianA Asgothian

                              @dimaiv ok, der kann es nicht sein, der hat kein on Event.
                              Dann sollte es der auf den folgende in der Liste der Geräte sein. Die müsste vorher im log stehen.

                              A.

                              P.s. damit ist für heute erst einmal Schluss. Morgen kann ich weiter machen. Zum Thema log kürzen, alles was nach DB closed oder connection closed kommt ist irrelevant.

                              A.

                              D Offline
                              D Offline
                              dimaiv
                              schrieb am zuletzt editiert von Homoran
                              #175

                              @asgothian

                              0x60a423fffe61dd4a - Steckdose: (https://www.zigbee2mqtt.io/devices/TS0121_plug.html)

                              0x28dba7fffe6df66f - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                              0x28dba7fffe6df516 - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                              0x28dba7fffe6df594 - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                              0x881a14fffeea1db2 - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                              0x28dba7fffe6df5f6 - SWV: (https://www.zigbee2mqtt.io/devices/SWV.html)

                              0xa4c13801838effff - Temp Sensor: (https://www.zigbee2mqtt.io/devices/SNZB-02LD.html)

                              ioBroker- NUC8i3 / Proxmox / VM
                              Node.js v22.21.0
                              NPM v10.9.4
                              JS controller 7.0.7
                              Admin 7.7.19
                              ZigBee Adapter 3.2.5
                              Zigbee LAN Gateway CC2652P
                              Zigbee Firmware 20250321

                              AsgothianA 1 Antwort Letzte Antwort
                              0
                              • AsgothianA Asgothian

                                Auf Github ist die version 3.1.0 des Zigbee Adapters vorhanden. Dafür benötige ich freiwillige zum Testen. Da es eine massive Anpassung war gibt es durchaus ein Risiko von Abstürzen. Allerdings sind die Änderungen gegenüber 3.0.5 gering, so das ein zurückspielen der 3.0.5 immer gehen wird.

                                Installation via Github vom ioBroker repository.

                                Folgendes ist neu:
                                Synchronisation für Gruppen / Mitglieder

                                • Änderung eines Gruppen States (ack = false) => der Adapter versucht den Status der Mitglieder zu lesen. (Wichtig: Nur der in der Gruppe angepasste state wird gelesen - wichtig bei Gruppen von Leuchten, wenn via brightness eingeschaltet wird. (Hier kann es ggf. noch Timing-Probleme geben)

                                • Änderung eines Mitglieder States (ack = false) => der Adapter bewertet den Status aller Mitglieder und setzt den Gruppenstatus entsprechend (mit ack=true) Ansteuerung über den State stateupdate. Gültige Werte sind: 'off' - keine Synchronisation (default), 'mat' - match -> der Gruppenstatus ändert sich wenn alle Mitglieder den gleichen Status haben. 'avg' der Gruppenstatus wird auf den durchschnittlichen Status aller Mitglieder gesetzt, wobei bei true/false intern true=1, false=0 gerechnet wird, und beim setzen gilt true = avg>4.9999999, 'min' - Der Gruppenstatus entspricht dem 'geringsten' Mitgliederstatus. 'max' - Der Gruppenstatus entspricht dem 'höchsten' Mitgliederstatus

                                • Optional: automatisch ein device_query wenn ein Gerät sich neu am Netz meldet (und als 'pingable' gilt - Konfigurierbar über die Einstellungen)

                                • Optional: automatisch beim Start für alle 'pingable' Geräte ein Device-query absetzen (incl. Timeout in sekunden, min 0.5 sekunden, max 10 sekunden, default 1 Sekunde. - konfigurierbar über die Einstellungen / an/aus, timeout)

                                Improved device_query - Device_query liest jetzt mehr Werte, und wirft weniger Fehler
                                ZH 5.0.3

                                Admin: Wird das Pairing vom Tab aus gestartet, so kann es angehalten oder verlängert werden.
                                Admin: Die Funktionen 'firmware update', 'touchlink reset', 'pairing with code', 'gruppe erzeugen' sind nur noch im Zigbee-Tab zugänglich
                                Admin: Die Karte des Koordinators wird immer dargestellt wenn der Adapter gestartet wurde - auch wenn das Zigbee-Subsystem nicht läuft (mit begrenzter Info)
                                Admin: Die Koordinator-Karte zeigt die ZH/ZHC und Adapter version

                                ToDo:

                                • (Prio 2) optimierung bei den nicht unterstützten Gruppenstates
                                • (Prio 4) Umgang mit den 'color' states bei memberupdate und stateupdate
                                • 'no converter for' Meldungen beim anpassen von memberuptate und stateupdate Fixed 11.9.
                                • (Prio 3) Deaktivierte Geräte die in Gruppen sind werden aktuell nicht vom Leseversuch der States ausgenommen
                                • Lesen der States asynchron gestalten, sowie mit einer einstellbaren Verzögerung ausstatten Asynchron: done 11.9. Einstellbare Verzögerung - unnötig
                                • Bindings: Bindings aus dem Zigbee-Herdsman holen und damit synchronisieren
                                • (Prio 7) Umstieg zu Z2M: Export für Gruppen und Bindings, damit diese vor einem Umstieg nicht zwangsweise gelöscht werden müssen
                                • (Prio 1) Timing-Auffälligkeiten bei der Konfiguration von neuen Geräten.
                                • (Prio 6) Recall Map data Option
                                • (Prio 7) save map Data as png option

                                Über rege Mithilfe würde ich mich freuen.

                                Version 3.1.3: Es gibt weitere Neuigkeiten:

                                • Deaktivierte Geräte sind jetzt in den Objekten erkennbar:

                                Im Tab:
                                Screenshot 2025-09-19 at 22.17.53.png

                                Im Objektbaum:
                                Screenshot 2025-09-19 at 22.18.18.png

                                Debug Interface verbesserungen:

                                • Mehr Meldungen im Log
                                • Links um sich die Log Meldungen zu bestimmten events gezielt anschauen zu können (die blauen Icons links)
                                  Screenshot 2025-09-19 at 22.20.20.png
                                • Anzeige so das sie direkt kopiert und mit code tags und allem im Forum gepostet werden können
                                  Screenshot 2025-09-19 at 22.21.06.png

                                Da rauskopiert, hier einkopiert sieht das dann so aus:

                                
                                I01: Zigbee Event of Type readResponse from device 0x00be44fffeab0b87, incoming event: {"type":"readResponse","data":{},"linkquality":163,"groupID":0,"cluster":"seMetering","meta":{"rawData":{"type":"Buffer","data":[8,14,1,1,0,134]},"zclTransactionSequenceNumber":14,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
                                I02: 1 converter available for 'E2206' '00be44fffeab0b87' with cluster 'seMetering' and type 'readResponse'
                                I03: message received '{"linkquality":163}' from device 00be44fffeab0b87 type 'E2206'
                                I04: value generated '163' from device 00be44fffeab0b87 for 'Link quality'
                                I02.1a: data: {} options: {} meta:{"deviceIEEE":"0x00be44fffeab0b87","logger":"StatesController","state":{"state":""}} result:{}
                                I02.1b: converter 1 : Cluster seMetering => payload : {}
                                I03-1: message received '{}' from device 00be44fffeab0b87 type 'E2206'
                                NOVAL: No value published for device 00be44fffeab0b87
                                
                                

                                A.

                                @Homoran - machst du den 3.0 Tester thread bitte zu ?

                                Nachtrag: Es gibt inzwischen eine 3.1.1, die die ZHC 25 integriert. Alle die die 3.1 installiert haben bitte ich auf die 3.1.1 zu aktualisieren. ! Es gibt inzwischen eine 3.1.2 - auch die nutzt ZHC25 und ZH 6, besitzt aber auch einen Fix für den Pairing bug.

                                P Offline
                                P Offline
                                pk68
                                schrieb am zuletzt editiert von
                                #176

                                Hallo,

                                ich habe mal eine allgemeine Frage zur Konfig des Adapters.
                                Bin gerade dabei den Koordinator zu ersetzen und alles neu zu machen. Nach Neuinstallation des Adapters wurde Kanal 15 eingestellt. Neben "Channel" ist ein grüner Haken. Laut Channels Energy Scan müsste man eigentlich Kanal 20 nutzen. Wenn ich den einstelle, ist anstelle des grünen Hakens ein rotes Kreuz. Was bedeutet das?
                                Der Adapter wird nach einem Neustart wieder grün. Konnte auch unter Kanal 20 einen IKEA Schalter neu anlernen.
                                Was sollte ich als Kanal einstellen, bevor ich alles neu anlerne?

                                Zigbee Channels Energy Scan 15 aktiv.png

                                D AsgothianA 2 Antworten Letzte Antwort
                                0
                                • P pk68

                                  Hallo,

                                  ich habe mal eine allgemeine Frage zur Konfig des Adapters.
                                  Bin gerade dabei den Koordinator zu ersetzen und alles neu zu machen. Nach Neuinstallation des Adapters wurde Kanal 15 eingestellt. Neben "Channel" ist ein grüner Haken. Laut Channels Energy Scan müsste man eigentlich Kanal 20 nutzen. Wenn ich den einstelle, ist anstelle des grünen Hakens ein rotes Kreuz. Was bedeutet das?
                                  Der Adapter wird nach einem Neustart wieder grün. Konnte auch unter Kanal 20 einen IKEA Schalter neu anlernen.
                                  Was sollte ich als Kanal einstellen, bevor ich alles neu anlerne?

                                  Zigbee Channels Energy Scan 15 aktiv.png

                                  D Offline
                                  D Offline
                                  dimaiv
                                  schrieb am zuletzt editiert von
                                  #177

                                  @pk68
                                  Auf welchem Kanal läuft dein WLAN und meisten von Nachbarn?

                                  ioBroker- NUC8i3 / Proxmox / VM
                                  Node.js v22.21.0
                                  NPM v10.9.4
                                  JS controller 7.0.7
                                  Admin 7.7.19
                                  ZigBee Adapter 3.2.5
                                  Zigbee LAN Gateway CC2652P
                                  Zigbee Firmware 20250321

                                  P 1 Antwort Letzte Antwort
                                  0
                                  • D dimaiv

                                    @pk68
                                    Auf welchem Kanal läuft dein WLAN und meisten von Nachbarn?

                                    P Offline
                                    P Offline
                                    pk68
                                    schrieb am zuletzt editiert von
                                    #178

                                    @dimaiv sagte in Tester wanted - Zigbee Adapter 3.1:

                                    @pk68
                                    Auf welchem Kanal läuft dein WLAN und meisten von Nachbarn?

                                    Bei meiner Fritzbox wird der Kanal automatisch gewählt. Kann also morgen wieder anders sein. Aktuell sieht es so aus:

                                    Kanalbelegung Fritzbox.png
                                    WLAN Kanal 3 am Stärksten belegt. Also gleich neben Zigbee-Kanal 15. Der wäre aktuelle eher ungünstig.
                                    Weißt Du, was der grünen Haken bzw. rotes Kreuz zu bedeuten hat?

                                    D 1 Antwort Letzte Antwort
                                    0
                                    • P pk68

                                      Hallo,

                                      ich habe mal eine allgemeine Frage zur Konfig des Adapters.
                                      Bin gerade dabei den Koordinator zu ersetzen und alles neu zu machen. Nach Neuinstallation des Adapters wurde Kanal 15 eingestellt. Neben "Channel" ist ein grüner Haken. Laut Channels Energy Scan müsste man eigentlich Kanal 20 nutzen. Wenn ich den einstelle, ist anstelle des grünen Hakens ein rotes Kreuz. Was bedeutet das?
                                      Der Adapter wird nach einem Neustart wieder grün. Konnte auch unter Kanal 20 einen IKEA Schalter neu anlernen.
                                      Was sollte ich als Kanal einstellen, bevor ich alles neu anlerne?

                                      Zigbee Channels Energy Scan 15 aktiv.png

                                      AsgothianA Offline
                                      AsgothianA Offline
                                      Asgothian
                                      Developer
                                      schrieb am zuletzt editiert von
                                      #179

                                      @pk68 sagte in Tester wanted - Zigbee Adapter 3.1:

                                      Wenn ich den einstelle, ist anstelle des grünen Hakens ein rotes Kreuz. Was bedeutet das?

                                      Ein rotes X bedeutet das der gewählte Kanal nicht dem entpricht der in der nvbackup.json eingestellt ist.
                                      Ein Gelbes Rufzeichen bedeutet das die Einstellung zum nvbackup.json passt, aber ein Wert ist der nicht empfohlen wird.
                                      Ein grünes Zeichen bedeutet das der Wert ok ist und mit dem nvbackup übereinstimmt.

                                      Keines der Zeichen gibt eine klare Aussage darüber ob das Zigbee-Subsystem starten wird oder nicht.

                                      A.

                                      ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                                      "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                                      P 1 Antwort Letzte Antwort
                                      0
                                      • AsgothianA Asgothian

                                        @pk68 sagte in Tester wanted - Zigbee Adapter 3.1:

                                        Wenn ich den einstelle, ist anstelle des grünen Hakens ein rotes Kreuz. Was bedeutet das?

                                        Ein rotes X bedeutet das der gewählte Kanal nicht dem entpricht der in der nvbackup.json eingestellt ist.
                                        Ein Gelbes Rufzeichen bedeutet das die Einstellung zum nvbackup.json passt, aber ein Wert ist der nicht empfohlen wird.
                                        Ein grünes Zeichen bedeutet das der Wert ok ist und mit dem nvbackup übereinstimmt.

                                        Keines der Zeichen gibt eine klare Aussage darüber ob das Zigbee-Subsystem starten wird oder nicht.

                                        A.

                                        P Offline
                                        P Offline
                                        pk68
                                        schrieb am zuletzt editiert von
                                        #180

                                        @asgothian
                                        Danke für die Infos. Ganz schlau werde ich daraus nicht. Wenn man einen anderen Kanal wählt, muss man dann auch die nvbackup.json bearbeiten oder wird die dann irgendwann automatisch aktualisiert?

                                        AsgothianA 1 Antwort Letzte Antwort
                                        0
                                        • P pk68

                                          @asgothian
                                          Danke für die Infos. Ganz schlau werde ich daraus nicht. Wenn man einen anderen Kanal wählt, muss man dann auch die nvbackup.json bearbeiten oder wird die dann irgendwann automatisch aktualisiert?

                                          AsgothianA Offline
                                          AsgothianA Offline
                                          Asgothian
                                          Developer
                                          schrieb am zuletzt editiert von
                                          #181

                                          @pk68 sagte in Tester wanted - Zigbee Adapter 3.1:

                                          @asgothian
                                          Danke für die Infos. Ganz schlau werde ich daraus nicht. Wenn man einen anderen Kanal wählt, muss man dann auch die nvbackup.json bearbeiten oder wird die dann irgendwann automatisch aktualisiert?

                                          wenn der Adapter das Netzwerk erfolgreich aufbaut, und du dann das Netzwerk wieder anhälst wird die nvbackup.json neu geschrieben - mit den neuen Parametern.

                                          A.

                                          ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
                                          "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

                                          1 Antwort Letzte Antwort
                                          1
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          901

                                          Online

                                          32.5k

                                          Benutzer

                                          81.6k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe