<![CDATA[Batterielevel bei Zigbeegerät über 110%]]>Ich habe mit zu meinen super funktionierenen Aqara-Temperatursensoren noch 2 SZ-T04 von Tuya zugelegt.
Das einlernen klappte super und die Werte scheinen auch zu stimmen. Leider stimmt wohl die Berechnung der Batteriespannung nicht und ich bekomme immer Warnmeldungen im Log. Gefüttert wird das Gerät mit 3 AAA-Batterien.
Was kann man da tun?
ZigbeeBatterie1.jpg ZigbeeBatterie2.jpg ZigbeeBatterie3.jpg

]]>https://forum.iobroker.net/topic/65146/batterielevel-bei-zigbeegerät-über-110RSS for NodeSat, 09 May 2026 09:52:41 GMTFri, 05 May 2023 11:16:46 GMT60<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Sat, 06 May 2023 07:30:42 GMT]]>@arteck Ein Downgrade des Zigbeeadapters auf 1.8.10 reichte aus um die Geräte wieder drin zu haben.
0307a359-ccc9-4b08-91c5-4c79506fe1c0-image.png
Mit der 1.8.11 erkennt er das Model "ZY-M100-S" welches es scheinbar nicht gibt.
Ich belasse es jetzt erstmal bei der 1.8.10 und teste irgendwann ein neues Release in der Hoffnung, das diese dann wieder wie bisher erkannt werden. Ich denke, da würde beim Update irgend ein Wert im Herdsman (oder sonstwo) geändert.

]]>https://forum.iobroker.net/post/987892https://forum.iobroker.net/post/987892Sat, 06 May 2023 07:30:42 GMT<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Sat, 06 May 2023 07:02:33 GMT]]>@docgame sagte in Batterielevel bei Zigbeegerät über 110%:

iobroker NPM version: 9.5.0

warum ?? geh auf 8 zurück

die Geräte sind kompliziert ... da im converter zur Zeit sehr viel passiert.. an den tuya Geräten

]]>https://forum.iobroker.net/post/987879https://forum.iobroker.net/post/987879Sat, 06 May 2023 07:02:33 GMT<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Fri, 05 May 2023 17:01:48 GMT]]>@arteck Ich hab mal die Git-Version draufgemacht. Wird noch dauern bis der Batteriestatus kommt.
Jetzt ist aber ein viel größeres Problem wieder aufgetreten.
Ich habe seit einigen Monaten mehrere MMWave Präsenzmelder von Tuya (5v und 220v) am laufen. Die sind wirklich super.
Im Zigbeeadapter wurden die als "ZY-M100-S" angezeigt. Vor 2 Tagen habe ich ein GIT-Update gemacht uns seither kommt:


zigbee.1 2023-05-05 18:34:50.904	error	Device 0xdc8e95fffe3abdae "ZY-M100-S" not described in statesMapping.
zigbee.1 2023-05-05 18:34:50.896	error	Device 0x70ac08fffe959bc3 "ZY-M100-S" not described in statesMapping.
zigbee.1 2023-05-05 18:34:50.893	error	Device 0xdc8e95fffe301a24 "ZY-M100-S" not described in statesMapping.
zigbee.1 2023-05-05 18:34:50.880	error	Device 0xdc8e95fffe301cdc "ZY-M100-S" not described in statesMapping.

Wenn ich in der Kachel unter Model auf den "blauen" Link zum Gerät klicke kommt ein 404 (Seite nicht gefunden)- Das ging immer.
Habe dann heute mittag einen alten Stand eingespielt und sie gingen wieder allerdings stand dann unter Model "TS0601_smart_human_presence_sensor"

zigbee.1 2023-05-05 08:46:34.197	info	0x94deb8fffec54abd (addr 47228): TS0601_smart_human_presence_sensor - TuYa Smart Human presence sensor (Router)
zigbee.1 2023-05-05 08:46:34.196	info	0xdc8e95fffe301a24 (addr 9189): TS0601_smart_human_presence_sensor - TuYa Smart Human presence sensor (Router)

Nach dem GIT-Update eben wieder das selbe....
Nach dem Installieren jede Menge Fehler...das ist der Adapter grün und alle Geräte sehen gut aus. Es geht auch alles bis auf die MMWave Geräte.
Erkennst du anhand des Logs an was das liegen könnte? Sonst würde ich nochmals meinen Snapshot einspielen und warten (da ja bestimmt auch andere mit diesen Geräten Probleme haben. Hier der Log nach Installation:

host.iobroker
2023-05-05 18:34:25.883	info	Restart adapter system.adapter.zigbee.1 because enabled
host.iobroker
2023-05-05 18:34:25.883	error	instance system.adapter.zigbee.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.883	error	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:
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.883	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.882	error	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:
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.882	error	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:
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.882	error	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:
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.882	error	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:
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.882	error	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:
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.882	error	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:
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.882	error	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:
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.882	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.881	error	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:
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.881	error	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:
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.881	error	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:
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.881	error	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:
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.881	error	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:
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.881	error	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:
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.881	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.880	error	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:
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.880	error	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:
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.880	error	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:
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.880	error	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:
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.880	error	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:
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.880	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.879	error	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:
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.879	error	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:
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.879	error	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:
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.879	error	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:
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at processImmediate (node:internal/timers:447:9)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at runNextTicks (node:internal/process/task_queues:60:5)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Zigbee._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7526:34)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[2]: Error: DB closed
host.iobroker
2023-05-05 18:34:25.879	error	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:
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at processImmediate (node:internal/timers:478:21)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/main.js:459:36)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at Array.forEach (<anonymous>)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:460:49
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at Zigbee.deleteStateAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2226:16)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at new Promise (<anonymous>)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at /opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2227:16
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at Zigbee.deleteState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5779:19)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: at Function.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:241:19)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: Error: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[1]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[0]: at processImmediate (node:internal/timers:478:21)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/main.js:459:36)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[0]: at Array.forEach (<anonymous>)
host.iobroker
2023-05-05 18:34:25.879	error	Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.zigbee/main.js:460:49
host.iobroker
2023-05-05 18:34:25.878	error	Caught by controller[0]: at Zigbee.deleteStateAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2226:16)
host.iobroker
2023-05-05 18:34:25.878	error	Caught by controller[0]: at new Promise (<anonymous>)
host.iobroker
2023-05-05 18:34:25.878	error	Caught by controller[0]: at /opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2227:16
host.iobroker
2023-05-05 18:34:25.878	error	Caught by controller[0]: at Zigbee.deleteState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5779:19)
host.iobroker
2023-05-05 18:34:25.878	error	Caught by controller[0]: at Function.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:241:19)
host.iobroker
2023-05-05 18:34:25.878	error	Caught by controller[0]: Error: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed
host.iobroker
2023-05-05 18:34:25.878	error	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:

zigbee.1
2023-05-05 18:34:23.107	info	terminating with timeout

zigbee.1
2023-05-05 18:34:22.108	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

zigbee.1
2023-05-05 18:34:22.107	info	terminating

zigbee.1
2023-05-05 18:34:22.081	warn	download icon from https://www.zigbee2mqtt.io/images/devices/SZ-T04.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/SZ-T04.png

zigbee.1
2023-05-05 18:34:21.984	warn	download icon from https://www.zigbee2mqtt.io/images/devices/SZ-T04.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/SZ-T04.png

zigbee.1
2023-05-05 18:34:21.982	warn	download icon from https://www.zigbee2mqtt.io/images/devices/TS0601_smoke_1.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/TS0601_smoke_1.png

zigbee.1
2023-05-05 18:34:21.980	warn	download icon from https://www.zigbee2mqtt.io/images/devices/MS-108ZR.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/MS-108ZR.png

zigbee.1
2023-05-05 18:34:21.974	warn	download icon from https://www.zigbee2mqtt.io/images/devices/JY-GZ-01AQ.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/JY-GZ-01AQ.png

zigbee.1
2023-05-05 18:34:21.970	warn	download icon from https://www.zigbee2mqtt.io/images/devices/TS0601_dimmer_1.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/TS0601_dimmer_1.png

zigbee.1
2023-05-05 18:34:21.968	warn	download icon from https://www.zigbee2mqtt.io/images/devices/ZTH01.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/ZTH01.png

zigbee.1
2023-05-05 18:34:21.965	warn	download icon from https://www.zigbee2mqtt.io/images/devices/4058075047853.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/4058075047853.png

zigbee.1
2023-05-05 18:34:21.961	warn	download icon from https://www.zigbee2mqtt.io/images/devices/WXKG02LM_rev1.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/WXKG02LM_rev1.png

zigbee.1
2023-05-05 18:34:21.960	warn	download icon from https://www.zigbee2mqtt.io/images/devices/ZB-SW01.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/ZB-SW01.png

zigbee.1
2023-05-05 18:34:21.953	warn	download icon from https://www.zigbee2mqtt.io/images/devices/MS-108ZR.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/MS-108ZR.png

zigbee.1
2023-05-05 18:34:21.949	warn	download icon from https://www.zigbee2mqtt.io/images/devices/ZBMINI.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/ZBMINI.png

zigbee.1
2023-05-05 18:34:21.947	warn	download icon from https://www.zigbee2mqtt.io/images/devices/YSR-MINI-01_dimmer.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/YSR-MINI-01_dimmer.png

zigbee.1
2023-05-05 18:34:21.946	warn	download icon from https://www.zigbee2mqtt.io/images/devices/TS0002_switch_module.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/TS0002_switch_module.png

zigbee.1
2023-05-05 18:34:21.944	warn	download icon from https://www.zigbee2mqtt.io/images/devices/YSR-MINI-01_wwcw.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/YSR-MINI-01_wwcw.png

zigbee.1
2023-05-05 18:34:21.935	warn	download icon from https://www.zigbee2mqtt.io/images/devices/404000-404005-404012-404019.jpg saved into /opt/iobroker/node_modules/iobroker.zigbee/admin/img/404000-404005-404012-404019.png

zigbee.1
2023-05-05 18:34:21.930	info	Zigbee started

zigbee.1
2023-05-05 18:34:21.929	info	0xa4c13851c5872f78 (addr 17235): SZ-T04 - Nous Temperature and humidity sensor with clock (EndDevice)

zigbee.1
2023-05-05 18:34:21.929	info	0x00158d000316d3c1 (addr 18674): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.929	info	0xa4c138cf46d9a10e (addr 62523): TS0601_smoke_1 - TuYa Smoke sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.928	info	0x187a3efffe32f308 (addr 12473): ZY-M100-S - TuYa Human presence sensor (Router)

zigbee.1
2023-05-05 18:34:21.928	info	0x70ac08fffe184b3b (addr 893): MS-108ZR - Moes Zigbee + RF curtain switch module (Router)

zigbee.1
2023-05-05 18:34:21.928	info	0xdc8e95fffe3abdae (addr 63189): ZY-M100-S - TuYa Human presence sensor (Router)

zigbee.1
2023-05-05 18:34:21.927	info	0xdc8e95fffe2ba8a8 (addr 42099): ZY-M100-S - TuYa Human presence sensor (Router)

zigbee.1
2023-05-05 18:34:21.927	info	0x94deb8fffec54abd (addr 47228): ZY-M100-S - TuYa Human presence sensor (Router)

zigbee.1
2023-05-05 18:34:21.927	info	0x70ac08fffe84edb7 (addr 42633): ZY-M100-S - TuYa Human presence sensor (Router)

zigbee.1
2023-05-05 18:34:21.926	info	0x54ef4410000a2b12 (addr 33242): GZCGQ01LM - Xiaomi MiJia light intensity sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.926	info	0xa4c138415407bbac (addr 44107): WHD02 - TuYa Wall switch module (Router)

zigbee.1
2023-05-05 18:34:21.926	info	0x00158d00028f7bcd (addr 35527): WXKG03LM_rev2 - Xiaomi Aqara single key wireless wall switch (2018 model) (EndDevice)

zigbee.1
2023-05-05 18:34:21.925	info	0x70ac08fffe959bc3 (addr 60310): ZY-M100-S - TuYa Human presence sensor (Router)

zigbee.1
2023-05-05 18:34:21.925	info	0x54ef4410005a68a2 (addr 2313): JY-GZ-01AQ - Xiaomi Aqara smart smoke detector (EndDevice)

zigbee.1
2023-05-05 18:34:21.925	info	0xdc8e95fffe301a24 (addr 9189): ZY-M100-S - TuYa Human presence sensor (Router)

zigbee.1
2023-05-05 18:34:21.924	info	0x000d6f000e1b9396 (addr 16757): AC0251100NJ/AC0251600NJ/AC0251700NJ - OSRAM Smart+ switch mini (EndDevice)

zigbee.1
2023-05-05 18:34:21.924	info	0x00158d0004102687 (addr 32062): WSDCGQ01LM - Xiaomi MiJia temperature & humidity sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.924	info	0x000b57fffee24142 (addr 8445): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)

zigbee.1
2023-05-05 18:34:21.923	info	0xdc8e95fffeacb9ef (addr 1921): TS0601_dimmer_1 - TuYa 1 gang smart dimmer (Router)

zigbee.1
2023-05-05 18:34:21.923	info	0x00158d0002238339 (addr 52507): SJCGQ11LM - Xiaomi Aqara water leak sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.923	info	0xa4c138a0d24f8da9 (addr 33722): ZTH01 - TuYa Temperature and humidity sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.922	info	0x7cb03eaa0a07b27e (addr 21752): AB3257001NJ - OSRAM Smart+ plug (Router)

zigbee.1
2023-05-05 18:34:21.922	info	0x00158d0002e9e49f (addr 37244): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.922	info	0x04cf8cdf3c77d848 (addr 28368): WXCJKG11LM - Xiaomi Aqara Opple switch 1 band (EndDevice)

zigbee.1
2023-05-05 18:34:21.921	info	0xf0d1b800001968cb (addr 40871): 4058075047853 - OSRAM Smart+ gardenpole 4W RGBW (Router)

zigbee.1
2023-05-05 18:34:21.921	info	0x84fd27fffe7d489d (addr 53145): WHD02 - TuYa Wall switch module (Router)

zigbee.1
2023-05-05 18:34:21.921	info	0x7cb03eaa00adf9eb (addr 7604): AC0363900NJ - OSRAM Smart+ mini gardenpole RGBW (Router)

zigbee.1
2023-05-05 18:34:21.920	info	0x00158d000215a95d (addr 25079): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)

zigbee.1
2023-05-05 18:34:21.920	info	0x00158d0002e9e6e0 (addr 43385): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.920	info	0xdc8e95fffe301cdc (addr 14732): ZY-M100-S - TuYa Human presence sensor (Router)

zigbee.1
2023-05-05 18:34:21.919	info	0x00158d000237b9ba (addr 18464): WXKG02LM_rev1 - Xiaomi Aqara double key wireless wall switch (2016 model) (EndDevice)

zigbee.1
2023-05-05 18:34:21.919	info	0x00124b0023ad489f (addr 18066): ZB-SW01 - eWeLink Smart light switch - 1 gang (Router)

zigbee.1
2023-05-05 18:34:21.919	info	0x00158d0003981d17 (addr 23617): RTCGQ11LM - Xiaomi Aqara human body movement and illuminance sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.918	info	0x00158d0004015f87 (addr 62439): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.918	info	0x04cf8cdf3c797389 (addr 55005): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice)

zigbee.1
2023-05-05 18:34:21.918	info	0x842e14fffe3a3ede (addr 51625): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)

zigbee.1
2023-05-05 18:34:21.917	info	0x588e81fffed981fe (addr 44877): TS011F_socket_module - TuYa Socket module (Router)

zigbee.1
2023-05-05 18:34:21.917	info	0x588e81fffed39fca (addr 19034): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)

zigbee.1
2023-05-05 18:34:21.916	info	0x00158d00035555e0 (addr 33849): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)

zigbee.1
2023-05-05 18:34:21.916	info	0x04cf8cdf3c77d5ba (addr 24871): WXCJKG11LM - Xiaomi Aqara Opple switch 1 band (EndDevice)

zigbee.1
2023-05-05 18:34:21.916	info	0xdc8e95fffef41db1 (addr 4935): MS-108ZR - Moes Zigbee + RF curtain switch module (Router)

zigbee.1
2023-05-05 18:34:21.915	info	0x04cf8cdf3c82d051 (addr 58315): GZCGQ01LM - Xiaomi MiJia light intensity sensor (EndDevice)

zigbee.1
2023-05-05 18:34:21.915	info	0x00158d00028f7b08 (addr 64606): WXKG03LM_rev2 - Xiaomi Aqara single key wireless wall switch (2018 model) (EndDevice)

zigbee.1
2023-05-05 18:34:21.915	info	0x00158d0002130983 (addr 30758): WXKG11LM - Xiaomi Aqara wireless switch (EndDevice)

zigbee.1
2023-05-05 18:34:21.914	info	0x00158d0002c8ca73 (addr 41954): WXKG01LM - Xiaomi MiJia wireless switch (EndDevice)

zigbee.1
2023-05-05 18:34:21.914	info	0x804b50fffea6b2df (addr 7512): ZBMINI - SONOFF Zigbee two way smart switch (Router)

zigbee.1
2023-05-05 18:34:21.913	info	0x04cf8cdf3c77d522 (addr 21668): WXCJKG11LM - Xiaomi Aqara Opple switch 1 band (EndDevice)

zigbee.1
2023-05-05 18:34:21.913	info	0x00124b00226763aa (addr 15776): YSR-MINI-01_dimmer - YSRSAI Zigbee LED controller (Dimmer) (Router)

zigbee.1
2023-05-05 18:34:21.912	info	0x588e81fffed981b6 (addr 61343): TS011F_socket_module - TuYa Socket module (Router)

zigbee.1
2023-05-05 18:34:21.912	info	0x540f57fffef9260a (addr 12929): TS0002_switch_module - TuYa 2 gang switch module (Router)

zigbee.1
2023-05-05 18:34:21.911	info	0xa4c138bd8ee65e4b (addr 30048): YSR-MINI-01_wwcw - YSRSAI Zigbee LED controller (WW/CW) (Router)

zigbee.1
2023-05-05 18:34:21.909	info	0xf0d1b800001280d4 (addr 63253): 4058075181472 - LEDVANCE SMART+ panel 60x60cm/120x30cm tunable white (Router)

zigbee.1
2023-05-05 18:34:21.909	info	0x842e14fffe3a4295 (addr 7230): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)

zigbee.1
2023-05-05 18:34:21.909	info	0xa4c13841db619e62 (addr 3615): WHD02 - TuYa Wall switch module (Router)

zigbee.1
2023-05-05 18:34:21.908	info	0x84182600000e8d75 (addr 9493): AB3257001NJ - OSRAM Smart+ plug (Router)

zigbee.1
2023-05-05 18:34:21.908	info	0x588e81fffed4af03 (addr 28690): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)

zigbee.1
2023-05-05 18:34:21.908	info	0x588e81fffe623be1 (addr 58890): E1746 - IKEA TRADFRI signal repeater (Router)

zigbee.1
2023-05-05 18:34:21.907	info	0x588e81fffed3a1f5 (addr 42134): TS0121_plug - TuYa 10A UK or 16A EU smart plug (Router)

zigbee.1
2023-05-05 18:34:21.907	info	0x00158d0002eeb636 (addr 63897): 404000/404005/404012/404019 - Müller Licht Tint LED bulb GU10/E14/E27 350/470/806 lumen, dimmable, color, opal white (Router)

zigbee.1
2023-05-05 18:34:21.906	info	0x04cf8cdf3c75b269 (addr 29655): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice)

zigbee.1
2023-05-05 18:34:21.906	info	0x04cf8cdf3c797027 (addr 45197): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice)

zigbee.1
2023-05-05 18:34:21.905	info	0x04cf8cdf3c75bc86 (addr 42318): WXCJKG12LM - Xiaomi Aqara Opple switch 2 bands (EndDevice)

zigbee.1
2023-05-05 18:34:21.905	info	0x04cf8cdf3c75c2c5 (addr 29888): WXCJKG12LM - Xiaomi Aqara Opple switch 2 bands (EndDevice)

zigbee.1
2023-05-05 18:34:21.904	info	0x04cf8cdf3c794714 (addr 34980): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice)

zigbee.1
2023-05-05 18:34:21.902	info	0x04cf8cdf3c75b44a (addr 5889): WXCJKG13LM - Xiaomi Aqara Opple switch 3 bands (EndDevice)

zigbee.1
2023-05-05 18:34:21.854	info	Currently 65 devices are joined:

zigbee.1
2023-05-05 18:34:21.846	info	--> transmitPower : normal

zigbee.1
2023-05-05 18:34:21.845	info	Unable to disable LED, unsupported function.

zigbee.1
2023-05-05 18:34:21.838	error	Parameter "parentChannel" needs to be of type "string" but type "object" has been passed

zigbee.1
2023-05-05 18:34:21.838	error	Error: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed at Function.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:241:19) at Zigbee.deleteState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5779:19) at /opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2227:16 at new Promise (<anonymous>) at Zigbee.deleteStateAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2226:16) at /opt/iobroker/node_modules/iobroker.zigbee/main.js:460:49 at Array.forEach (<anonymous>) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/main.js:459:36) at processImmediate (node:internal/timers:478:21)

zigbee.1
2023-05-05 18:34:21.838	error	unhandled promise rejection: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed

zigbee.1
2023-05-05 18:34:21.837	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

zigbee.1
2023-05-05 18:34:21.820	info	Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20220219}}

zigbee.1
2023-05-05 18:34:21.693	info	Zigbee: disabling joining new devices.

zigbee.1
2023-05-05 18:34:21.687	error	Device 0x187a3efffe32f308 "ZY-M100-S" not described in statesMapping.

zigbee.1
2023-05-05 18:34:21.684	error	Device 0xdc8e95fffe3abdae "ZY-M100-S" not described in statesMapping.

zigbee.1
2023-05-05 18:34:21.681	error	Device 0x94deb8fffec54abd "ZY-M100-S" not described in statesMapping.

zigbee.1
2023-05-05 18:34:21.679	error	Device 0x70ac08fffe84edb7 "ZY-M100-S" not described in statesMapping.

zigbee.1
2023-05-05 18:34:21.673	error	Device 0x70ac08fffe959bc3 "ZY-M100-S" not described in statesMapping.

zigbee.1
2023-05-05 18:34:21.670	error	Device 0xdc8e95fffe301a24 "ZY-M100-S" not described in statesMapping.

zigbee.1
2023-05-05 18:34:21.651	error	Device 0xdc8e95fffe301cdc "ZY-M100-S" not described in statesMapping.

zigbee.1
2023-05-05 18:34:21.596	info	cleaned everything up...

zigbee.1
2023-05-05 18:34:21.590	error	Parameter "parentChannel" needs to be of type "string" but type "object" has been passed

zigbee.1
2023-05-05 18:34:21.590	error	Error: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed at Function.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:241:19) at Zigbee.deleteState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:5779:19) at /opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2227:16 at new Promise (<anonymous>) at Zigbee.deleteStateAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2226:16) at /opt/iobroker/node_modules/iobroker.zigbee/main.js:460:49 at Array.forEach (<anonymous>) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/main.js:459:36) at processImmediate (node:internal/timers:478:21)

zigbee.1
2023-05-05 18:34:21.476	error	unhandled promise rejection: Parameter "parentChannel" needs to be of type "string" but type "object" has been passed

zigbee.1
2023-05-05 18:34:21.476	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

zigbee.1
2023-05-05 18:34:21.421	warn	setObject info.debugmessages (type=state) property common.role missing!

zigbee.1
2023-05-05 18:34:21.376	warn	setObject info.undefinedDevices (type=state) property common.role missing!

zigbee.1
2023-05-05 18:34:21.373	error	Device 0xdc8e95fffe2ba8a8 "ZY-M100-S" not described in statesMapping.

zigbee.1
2023-05-05 18:34:20.106	info	Installed Version: ioBroker/ioBroker.zigbee#6d0ed1d8e463b7fd1dd72fb8739709b6d138329b

zigbee.1
2023-05-05 18:34:20.020	info	Starting Zigbee npm ...

zigbee.1
2023-05-05 18:34:20.020	info	delete old Backup files. keep only last 10

zigbee.1
2023-05-05 18:34:19.979	info	starting. Version 1.8.11 (non-npm: ioBroker/ioBroker.zigbee#6d0ed1d8e463b7fd1dd72fb8739709b6d138329b) in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.15.0, js-controller: 5.0.1-alpha.0-20230403-fd495c2e
host.iobroker
2023-05-05 18:34:17.444	info	instance system.adapter.zigbee.1 started with pid 967874
host.iobroker
2023-05-05 18:34:15.995	info	instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
host.iobroker
2023-05-05 18:34:15.194	info	stopInstance system.adapter.zigbee.1 killing pid 210039
host.iobroker
2023-05-05 18:34:15.157	info	iobroker exit 0
host.iobroker
2023-05-05 18:34:14.163	info	stopInstance system.adapter.zigbee.1 send kill signal

zigbee.1
2023-05-05 18:34:14.445	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

zigbee.1
2023-05-05 18:34:14.445	info	terminating

zigbee.1
2023-05-05 18:34:14.021	info	Zigbee: disabling joining new devices.

zigbee.1
2023-05-05 18:34:13.945	info	cleaned everything up...

zigbee.1
2023-05-05 18:34:13.944	info	Got terminate signal TERMINATE_YOURSELF
host.iobroker
2023-05-05 18:34:13.592	info	stopInstance system.adapter.zigbee.1 (force=false, process=true)
host.iobroker
2023-05-05 18:34:13.467	info	iobroker Update "system.adapter.zigbee.1"
host.iobroker
2023-05-05 18:34:13.359	info	iobroker Update "system.adapter.zigbee.0"
host.iobroker
2023-05-05 18:34:13.268	info	iobroker upload [0] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/zigbee.svg zigbee.svg image/svg+xml
host.iobroker
2023-05-05 18:34:13.239	info	iobroker upload [1] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/zigbee.png zigbee.png image/png
host.iobroker
2023-05-05 18:34:13.229	info	iobroker upload [2] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/words.js words.js application/javascript
host.iobroker
2023-05-05 18:34:13.224	info	iobroker upload [3] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/vis-network.min.js vis-network.min.js application/javascript
host.iobroker
2023-05-05 18:34:13.222	info	iobroker upload [4] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/vis-network.min.css vis-network.min.css text/css
host.iobroker
2023-05-05 18:34:13.219	info	iobroker upload [5] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/tab_m.html tab_m.html text/html
host.iobroker
2023-05-05 18:34:13.217	info	iobroker upload [6] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/shuffle.min.js shuffle.min.js application/javascript
host.iobroker
2023-05-05 18:34:13.215	info	iobroker upload [7] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/moment.min.js moment.min.js application/javascript
host.iobroker
2023-05-05 18:34:13.213	info	iobroker upload [8] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/index_m.html index_m.html text/html
host.iobroker
2023-05-05 18:34:13.206	info	iobroker upload [9] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/index.html index.html text/html
host.iobroker
2023-05-05 18:34:13.184	info	iobroker upload [10] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zemismart_sw2.png img/zemismart_sw2.png image/png
host.iobroker
2023-05-05 18:34:13.182	info	iobroker upload [11] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_smart_switch.png img/zbt_smart_switch.png image/png
host.iobroker
2023-05-05 18:34:13.180	info	iobroker upload [12] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_led_panel.png img/zbt_led_panel.png image/png
host.iobroker
2023-05-05 18:34:13.178	info	iobroker upload [13] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_e27_rgbw.png img/zbt_e27_rgbw.png image/png
host.iobroker
2023-05-05 18:34:13.176	info	iobroker upload [14] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/zbt_e27.png img/zbt_e27.png image/png
host.iobroker
2023-05-05 18:34:13.173	info	iobroker upload [15] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/xiaomi_wireless_switch.png img/xiaomi_wireless_switch.png image/png
host.iobroker
2023-05-05 18:34:13.171	info	iobroker upload [16] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/xiaomi_plug_eu.png img/xiaomi_plug_eu.png image/png
host.iobroker
2023-05-05 18:34:13.169	info	iobroker upload [17] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/wemo.png img/wemo.png image/png
host.iobroker
2023-05-05 18:34:13.167	info	iobroker upload [18] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/unknown.png img/unknown.png image/png
host.iobroker
2023-05-05 18:34:13.165	info	iobroker upload [19] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/unavailable.png img/unavailable.png image/png
host.iobroker
2023-05-05 18:34:13.163	info	iobroker upload [20] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/tuya_tyzs1l.png img/tuya_tyzs1l.png image/png
host.iobroker
2023-05-05 18:34:13.149	info	iobroker upload [30] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/ts0203.png img/ts0203.png image/png
host.iobroker
2023-05-05 18:34:13.136	info	iobroker upload [40] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/smartthings_motion.png img/smartthings_motion.png image/png
host.iobroker
2023-05-05 18:34:13.119	info	iobroker upload [50] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/sensor_philipshue.png img/sensor_philipshue.png image/png
host.iobroker
2023-05-05 18:34:13.097	info	iobroker upload [60] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/plug.png img/plug.png image/png
host.iobroker
2023-05-05 18:34:13.084	info	iobroker upload [70] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_ltc021.png img/philips_hue_ltc021.png image/png
host.iobroker
2023-05-05 18:34:13.072	info	iobroker upload [80] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_e27_ambiance.png img/philips_hue_e27_ambiance.png image/png
host.iobroker
2023-05-05 18:34:13.059	info	iobroker upload [90] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_hue_ambiance.png img/philips_hue_ambiance.png image/png
host.iobroker
2023-05-05 18:34:13.045	info	iobroker upload [100] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/philips_amaze.png img/philips_amaze.png image/png
host.iobroker
2023-05-05 18:34:12.965	info	iobroker upload [150] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/lh_32Zb.png img/lh_32Zb.png image/png
host.iobroker
2023-05-05 18:34:12.882	info	iobroker upload [200] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/hive.png img/hive.png image/png
host.iobroker
2023-05-05 18:34:12.802	info	iobroker upload [250] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/bitron_motion.png img/bitron_motion.png image/png
host.iobroker
2023-05-05 18:34:12.756	info	iobroker upload [300] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/img/Bitron_AV201021A.png img/Bitron_AV201021A.png image/png
host.iobroker
2023-05-05 18:34:12.724	info	iobroker upload [322] zigbee.admin /opt/iobroker/node_modules/iobroker.zigbee/admin/adapter-settings.js adapter-settings.js application/javascript
host.iobroker
2023-05-05 18:34:11.846	info	iobroker changed 5 packages in 14s207 packages are looking for funding run `npm fund` for details
host.iobroker
2023-05-05 18:34:09.724	info	iobroker npm WARN skipping integrity check for git dependency ssh://git@github.com/ioBroker/ioBroker.zigbee.git
host.iobroker
2023-05-05 18:33:57.864	info	iobroker Installing ioBroker/ioBroker.zigbee#6d0ed1d8e463b7fd1dd72fb8739709b6d138329b... (System call)
host.iobroker
2023-05-05 18:33:57.864	info	iobroker NPM version: 9.5.0
host.iobroker
2023-05-05 18:33:57.489	info	iobroker install ioBroker/ioBroker.zigbee#6d0ed1d8e463b7fd1dd72fb8739709b6d138329b
host.iobroker
2023-05-05 18:33:56.267	info	iobroker url https://github.com/ioBroker/ioBroker.zigbee.git --host iobroker --debug
]]>https://forum.iobroker.net/post/987693https://forum.iobroker.net/post/987693Fri, 05 May 2023 17:01:48 GMT<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Fri, 05 May 2023 15:07:33 GMT]]>@docgame installier mal den adapter von GIT.. evtl musst du das gerät aus den Objecten löschen.. nicht das Gerät selbst nur aus dem Baum

]]>https://forum.iobroker.net/post/987659https://forum.iobroker.net/post/987659Fri, 05 May 2023 15:07:33 GMT<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Fri, 05 May 2023 12:24:10 GMT]]>@docgame ja ich weiß dass es im Datenpunkt drin steht und hast du den Max wert mal erhöht?

Alternativ das Warnlevel auf error erhöhen bis genügend Batterie verbraucht ist.

Zusätzlich noch ein GitHub Fehler anlegen.

]]>https://forum.iobroker.net/post/987599https://forum.iobroker.net/post/987599Fri, 05 May 2023 12:24:10 GMT<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Fri, 05 May 2023 12:07:33 GMT]]>@mickym hatte ich gestern auch schon probiert. Das steht im Datenpunkt drin:

{
  "type": "state",
  "common": {
    "name": "Battery percent",
    "type": "number",
    "unit": "%",
    "read": true,
    "write": false,
    "role": "value.battery",
    "min": 0,
    "max": 100,
    "icon": "img/battery_p.png"
  },
  "native": {},
  "_id": "zigbee.1.a4c13851c5872f78.battery",
  "acl": {
    "object": 1638,
    "state": 1638,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  },
  "from": "system.adapter.zigbee.1",
  "user": "system.user.admin",
  "ts": 1682983396952
}

Ist ja nicht weiter schlimm, da ja sonst alles geht.

]]>https://forum.iobroker.net/post/987595https://forum.iobroker.net/post/987595Fri, 05 May 2023 12:07:33 GMT<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Fri, 05 May 2023 11:35:25 GMT]]>@docgame du kannst ja mal versuchen das max limit dieses Datenpunktes manuell zu ändern.

]]>https://forum.iobroker.net/post/987583https://forum.iobroker.net/post/987583Fri, 05 May 2023 11:35:25 GMT<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Fri, 05 May 2023 11:26:35 GMT]]>@homoran Ist ja an sich schön wenn die so voll sind. Habe bestimmt über 80 Batteriebetriebene Sensoren (die meisten mit Knopfzellen). Da ist noch keine über 100% rausgekommen.
Mich hat ja nur das ständige warnen im Log gestört. Dachte, das wäre vielleicht was, dass die Anzeige bei 100% begrenzt werden kann. Dann würde es eben viel später unter die 100% fallen.

]]>https://forum.iobroker.net/post/987577https://forum.iobroker.net/post/987577Fri, 05 May 2023 11:26:35 GMT<![CDATA[Reply to Batterielevel bei Zigbeegerät über 110% on Fri, 05 May 2023 11:21:53 GMT]]>@docgame sagte in Batterielevel bei Zigbeegerät über 110%:

Leider stimmt wohl die Berechnung der Batteriespannung nich

ich hab keine Ahnung von den Geräten.
Aber neue Batterien liegen immer über der Nennspannung.
die 112% der Nennspannung sind durchaus realistisch.

]]>https://forum.iobroker.net/post/987575https://forum.iobroker.net/post/987575Fri, 05 May 2023 11:21:53 GMT