Tester Zigbee Adapter 3.x gesucht

[Asgothian]

Hallo zusammen,

nachdem die 2.0. erfolgreich im Stable gelandet ist (als 2.0.5) hat @arteck für mich die 3.0 zusammengebaut und ins Latest verfrachtet (nochmal Danke dafür). Jetzt brauche ich dafür Tester:

Aktuelle Test Version	3.0.0
Veröffentlichungsdatum	08.04.2025
Github Link	https://github.com/ioBroker/ioBroker.zigbee

Changelog:

• Breaking change: Start of zigbee subsystem requires configuration entry !!!
• Hardware configuration panel
• Update for external converter - detect /dist/ subfolder
• Update device image: use of icons defined in external converter (beta)
• Updated Adapter documentation

Die Version beinhaltet wieder einen breaking change - aber deutlich kleiner als zuvor. Wird die Version installiert und dann neu gestartet wird das Zigbee-Subsystem nicht automatisch gestartet. Der Adapter läuft dann zwar, bleibt aber gelb und es lassen sich keine Zigbee-Geräte ansteuern. Das ist kein bug, sondern by design.

In der Konfiguration des Adapters gibt es ein neues Tab Hardware. Auf diesem sind alle Hardware-Relevanten Einstellungen zu machen - und man kann sie damit auch gleich testen. Genau diese Funktionalität hätte ich gerne getestet. Damit das entsprechend einfach geht habe ich die Doku (Deutsch/ Englisch) angepasst. Da ist dann beschrieben wie eine neue Instanz eingerichtet werden soll.

Für die die nur kurz installieren und später testen wollen - damit der Adapter das Zigbee-Subsystem automatisch startet, muss der Haken bei G in der Konfiguration gesetzt werden.

Diese Änderung war notwendig weil es immer wieder Probleme bei Anfängern gab den Adapter sauber aufzusetzen. Eine automatische Trennung zwischen 'konfiguriert' und 'nicht konfiguriert' ist mir nicht gelungen, deswegen die Notwendigkeit für eine manuelle Einstellung.

Erklärung zum Configure in 3.0:
Bei Adapterstart wird im System geprüft ob das System eine erneute Konfiguration anfragt. Dazu gibt es Daten im ZHC / State. Wenn das System eine Konfiguration für notwendig erachtet wird versucht das Gerät zu konfigurieren. Dabei gibt es 3 mögliche Ergebnisse:

• Erfolg - Die Konfiguration wird eingetragen - solange das Gerät nicht bei jedem Neustart eine Neukonfiguration fordert wird es nicht wieder konfiguriert, egal wie oft der Adapter neu startet
• Zeitüberschreitung: Das Gerät hat nicht geantwortet: Dieses Gerät kommt in die 'configure_on_message' Struktur. (siehe unten)
• Miserfolg - Die Konfiguration konnte nicht durchgeführt werden. Das Gerät wird beim nächsten Start erneut einen Konfigurationsversuch erleben.

configure_on_message:
Diese Methode dient dazu das insbesondere batteriebetriebene Geräte einfacher zu konfigurieren sind. Ein Gerät welches hier eingetragen wird wird in dem Moment konfiguriert wo der Adapter eine Nachricht des Gerätes erhält - ausgehend von der Annahme das das Gerät dann wach ist und die Konfiguration erfolgreich sein wird. Dieses wird

• max 5 mal probiert
• max alle 5 Sekunden probiert, egal wie viele Meldungen in der Zwischenzeit eintreffen.
  Aktuell erzeugt es noch viele Info-Meldungen. Diese werden mit der Zeit auf eine Sinnvolle Anzahl reduziert.

A.

[Asgothian]

@asgothian reserved
Hier werden geplante Neuerungen des Adapters aufgeführt (und ihr Erfolg)
Weitere Vorschläge zu systematischen Änderungen bitte gerne im Thread posten - wenn ich diese angehen will landen sie hier.

Wichtig: Alles was hier steht kann und soll diskutiert werden. Es ist die Liste der Punkte die bei mir anstehen. Wenn da etwas steht was so als schlecht empfunden wird, schreibt das bitte. Ich sehe das nicht als Kritik sondern als Diskussion dazu wie der Adapter besser werden kann.

1. Definition von Device-Bildern über 'externe Konverter'
   Stand: Initial implementiert - muss getestet werden. Bilder als Link sollten gehen, Bilder als base64 String sind ungetestet.
   -- in der JS Datei des externen Konverters kann als icon: '<pfad zum icon> ein Bild vorgegeben werden - als Link oder als base64 kodiertes Bild. Dieses soll im Adapter übernommen werden. Beispiele dafür gibt es unter :https://github.com/inventwo/custom-zigbee (nebenbei - ich kann bestätigen das die meisten Konverter aus diesem Projekt auch im Zigbee-Adapter gehen sollten.

2. KonfigurationsDP für Gruppen
   Stand: in Planung:
   -- Gruppenstatus basierend auf Mitgliederstatus
   -- eingrenzen von Gruppenfunktion (Datenpunkte die die Gruppe liefert)
   -- Option zur erzwungenen Aktualisierung aller Mitglieder basierend auf Gruppenstatus.

3. Änderung bei den Gerätekacheln (Die Kacheln sind generell zu voll, und mit zu vielen Dingen belastet die wenig Sinn machen):
   -- Enum-States mit genau 1 Auswahlmöglichkeit werden von den Gerätekacheln entfernt Done (in Testversion)
   -- Text-States ohne Auswahl / Eingabemöglichkeit werden von den Gerätekacheln entfernt Done (in Testversion)
   -- Numerische States ohne min/max werden von den Device-Kacheln entfernt
   -- Numerische States mit min/max werden als slider mit Nummer auf den Kacheln dargestellt, wobei die Nummer nur Anzeige ist
   -- Slider deren Werte-Bereich um 0 geht bekommen ein 'bias' auf 0, um das Einstellen von genau 0 zu vereinfachen.
   -- Denkbar: UI zur Auswahl der auf der Kachel sichtbaren Elemente, basierend auf Gerätetyp oder Gerät.

A.

[dimaiv]

Folgende Fehler bekomme ich beim starten.
Ich glaube es geht hier um Punkt 1 (Device-Bild über externe Konverter als base64 String)
Wird externe Konverter deaktiviert, startet alles normal durch.
Mit Version 2.0.5 hat es funktioniert.

2025-04-08 12:08:40.009 - info: host.IoBroker "system.adapter.zigbee.0" enabled
2025-04-08 12:08:40.323 - info: host.IoBroker instance system.adapter.zigbee.0 in version "3.0.0" started with pid 5651
2025-04-08 12:08:40.992 - info: sql.0 (607) enabled logging of Zigbee CPU Test, Alias=true, WriteNulls=false
2025-04-08 12:08:41.060 - info: zigbee.0 (5651) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6
2025-04-08 12:08:41.071 - info: zigbee.0 (5651) Adapter ready - starting subsystems. Adapter is running in info mode.
2025-04-08 12:08:41.072 - warn: zigbee.0 (5651) trying to add "calibrateAndPrecisionRoundOptions = require(../zigbee-herdsman-converters/dist/lib/utils)" to sandbox
2025-04-08 12:08:41.073 - warn: zigbee.0 (5651) trying to add "fz = require(../zigbee-herdsman-converters/dist/converters/fromZigbee)" to sandbox
2025-04-08 12:08:41.073 - warn: zigbee.0 (5651) trying to add "tz = require(../zigbee-herdsman-converters/dist/converters/toZigbee)" to sandbox
2025-04-08 12:08:41.073 - warn: zigbee.0 (5651) trying to add "exposes = require(../zigbee-herdsman-converters/dist/lib/exposes)" to sandbox
2025-04-08 12:08:41.074 - warn: zigbee.0 (5651) trying to add "reporting = require(../zigbee-herdsman-converters/dist/lib/reporting)" to sandbox
2025-04-08 12:08:41.074 - warn: zigbee.0 (5651) trying to add "constants = require(../zigbee-herdsman-converters/dist/lib/constants)" to sandbox
2025-04-08 12:08:41.074 - warn: zigbee.0 (5651) Trying to run sandbox for /opt/iobroker/iobroker-data/zigbee_0/IKEA_VINDRIKTNING_EFEKTA_III.js
2025-04-08 12:08:41.075 - info: zigbee.0 (5651) Model IKEA_VINDRIKTNING_EFEKTA III defined in external converter /opt/iobroker/iobroker-data/zigbee_0/IKEA_VINDRIKTNING_EFEKTA_III.js
2025-04-08 12:08:41.076 - info: zigbee.0 (5651) added external converter using addExternalDefinition (0 ms)
2025-04-08 12:08:41.076 - info: zigbee.0 (5651) init localConfig
2025-04-08 12:08:41.077 - info: zigbee.0 (5651) --> transmitPower :
2025-04-08 12:08:41.110 - info: zigbee.0 (5651) delete old Backup files. keep only last 10
2025-04-08 12:08:41.138 - info: zigbee.0 (5651) --- creating device debug ---
2025-04-08 12:08:41.138 - info: zigbee.0 (5651) Starting Adapter npm ...
2025-04-08 12:08:41.161 - info: zigbee.0 (5651) Installed Version: iobroker.zigbee@3.0.0 (Converters 23.23.0 Herdsman 3.5.1)
2025-04-08 12:08:41.162 - info: zigbee.0 (5651) Starting Zigbee-Herdsman
2025-04-08 12:08:42.505 - info: zigbee.0 (5651) Zigbee-Herdsman started successfully with Coordinator firmware version: zStack3x0 : 20240710 (2-1.2.7.1)
2025-04-08 12:08:42.506 - info: zigbee.0 (5651) Unable to disable LED, unsupported function.
2025-04-08 12:08:42.511 - info: zigbee.0 (5651) 0x00124b0022608248 (addr 38446): ptvo.switch - Custom devices (DiY) Multi-functional device (EndDevice)
2025-04-08 12:08:42.525 - info: zigbee.0 (5651) 0x943469fffe70c2c4 (addr 9217): 701721 - Popp Smart thermostat (EndDevice)
2025-04-08 12:08:42.526 - info: zigbee.0 (5651) 0x943469fffe70c2f4 (addr 7279): 701721 - Popp Smart thermostat (EndDevice)
2025-04-08 12:08:42.535 - info: zigbee.0 (5651) 0x385cfbfffe6c6c30 (addr 40250): ICPSHC24-10EU-IL-1/ICPSHC24-10EU-IL-2 - IKEA TRADFRI LED driver, 10 w (Router)
2025-04-08 12:08:42.536 - info: zigbee.0 (5651) 0xf4b3b1fffea967e4 (addr 41303): 701721 - Popp Smart thermostat (EndDevice)
2025-04-08 12:08:42.536 - info: zigbee.0 (5651) 0x943469fffe70c317 (addr 42317): 701721 - Popp Smart thermostat (EndDevice)
2025-04-08 12:08:42.556 - info: zigbee.0 (5651) 0x00158d0001f532c9 (addr 51403): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
2025-04-08 12:08:42.557 - info: zigbee.0 (5651) 0x00158d0001f532ce (addr 22164): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
2025-04-08 12:08:42.557 - info: zigbee.0 (5651) 0x00158d0002018760 (addr 27142): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
2025-04-08 12:08:42.558 - info: zigbee.0 (5651) 0x00158d0001f505b8 (addr 14061): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
2025-04-08 12:08:42.558 - info: zigbee.0 (5651) 0x00158d0001f50e93 (addr 29750): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
2025-04-08 12:08:42.559 - info: zigbee.0 (5651) 0x00158d0001dad5de (addr 60931): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
2025-04-08 12:08:42.559 - info: zigbee.0 (5651) 0x00158d00020196d8 (addr 41400): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
2025-04-08 12:08:42.560 - info: zigbee.0 (5651) 0x00158d00020196e8 (addr 35): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
2025-04-08 12:08:42.560 - info: zigbee.0 (5651) 0x00158d000252943b (addr 42449): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
2025-04-08 12:08:42.560 - info: zigbee.0 (5651) 0x804b50fffe630510 (addr 9790): E1757 - IKEA FYRTUR roller blind, block-out (EndDevice)
2025-04-08 12:08:42.561 - info: zigbee.0 (5651) 0x000d6ffffe8e7e2b (addr 11245): E1757 - IKEA FYRTUR roller blind, block-out (EndDevice)
2025-04-08 12:08:42.561 - info: zigbee.0 (5651) 0x04cf8cdf3c77299e (addr 64627): GZCGQ01LM - Xiaomi Mi light sensor (EndDevice)
2025-04-08 12:08:42.562 - info: zigbee.0 (5651) 0x00158d0001d83bed (addr 53296): JTYJ-GD-01LM/BW - Xiaomi Mijia Honeywell smoke detector (EndDevice)
2025-04-08 12:08:42.570 - info: zigbee.0 (5651) 0x00158d0004fcf9d2 (addr 1792): HS1SA - HEIMAN Smoke detector (EndDevice)
2025-04-08 12:08:42.570 - info: zigbee.0 (5651) 0x00158d0001bb8f04 (addr 9374): SJCGQ11LM - Aqara Water leak sensor (EndDevice)
2025-04-08 12:08:42.571 - info: zigbee.0 (5651) 0x00158d0001ad4ab1 (addr 15395): RTCGQ11LM - Aqara Motion sensor (EndDevice)
2025-04-08 12:08:42.571 - info: zigbee.0 (5651) 0x00158d0001df05e1 (addr 46282): RTCGQ11LM - Aqara Motion sensor (EndDevice)
2025-04-08 12:08:42.602 - info: zigbee.0 (5651) 0x842e14fffedb8ae5 (addr 12629): TS0121_plug - Tuya 10A UK or 16A EU smart plug (Router)
2025-04-08 12:08:42.603 - info: zigbee.0 (5651) 0x842e14fffe51c679 (addr 6497): TS0121_plug - Tuya 10A UK or 16A EU smart plug (Router)
2025-04-08 12:08:42.603 - info: zigbee.0 (5651) 0x842e14fffedb8976 (addr 32550): TS0121_plug - Tuya 10A UK or 16A EU smart plug (Router)
2025-04-08 12:08:42.604 - info: zigbee.0 (5651) 0x842e14fffef5a250 (addr 41712): TS0121_plug - Tuya 10A UK or 16A EU smart plug (Router)
2025-04-08 12:08:42.609 - info: zigbee.0 (5651) 0xcc86ecfffef3c028 (addr 32236): TS0121_plug - Tuya 10A UK or 16A EU smart plug (Router)
2025-04-08 12:08:42.610 - info: zigbee.0 (5651) 0x842e14fffef5a281 (addr 62679): TS0121_plug - Tuya 10A UK or 16A EU smart plug (Router)
2025-04-08 12:08:42.616 - info: zigbee.0 (5651) 0xcc86ecfffe1358a9 (addr 25741): TS011F_plug_1 - Tuya Smart plug (with power monitoring) (Router)
2025-04-08 12:08:42.616 - info: zigbee.0 (5651) 0x90fd9ffffe04db13 (addr 41996): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
2025-04-08 12:08:42.617 - info: zigbee.0 (5651) 0x000b57fffebc3759 (addr 26447): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
2025-04-08 12:08:42.618 - info: zigbee.0 (5651) 0x90fd9ffffed27f57 (addr 2939): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)
2025-04-08 12:08:42.618 - info: zigbee.0 (5651) 0x000d6ffffed09b8d (addr 63637): E1766 - IKEA TRADFRI open/close remote (EndDevice)
2025-04-08 12:08:42.619 - info: zigbee.0 (5651) 0x04cf8cdf3c75b72f (addr 61234): WXCJKG13LM - Aqara Opple wireless switch (triple band) (EndDevice)
2025-04-08 12:08:42.619 - info: zigbee.0 (5651) 0x00158d000255ef1b (addr 31351): WXKG02LM_rev1 - Aqara Wireless remote switch (double rocker), 2016 model (EndDevice)
2025-04-08 12:08:42.620 - info: zigbee.0 (5651) 0x000d6f0014f6c86f (addr 47659): HS2WD-E - HEIMAN Smart siren (Router)
2025-04-08 12:08:42.628 - info: zigbee.0 (5651) 0x7cb03eaa00adea74 (addr 20689): 4052899926110 - OSRAM Flex RGBW (Router)
2025-04-08 12:08:42.628 - info: zigbee.0 (5651) 0x7cb03eaa00adf023 (addr 31545): 4052899926110 - OSRAM Flex RGBW (Router)
2025-04-08 12:08:42.629 - info: zigbee.0 (5651) 0x7cb03eaa00adec1a (addr 2930): 4052899926110 - OSRAM Flex RGBW (Router)
2025-04-08 12:08:42.629 - info: zigbee.0 (5651) 0x90fd9ffffe4c5abf (addr 6388): ICPSHC24-30EU-IL-1/ICPSHC24-10EU-IL-2 - IKEA TRADFRI LED driver, 30 w (Router)
2025-04-08 12:08:42.629 - info: zigbee.0 (5651) 0x000b57fffeecea8a (addr 63018): LED1545G12 - IKEA TRADFRI bulb E26/E27, white spectrum, globe, opal, 980 lm (Router)
2025-04-08 12:08:42.630 - info: zigbee.0 (5651) 0x90fd9ffffe049ad1 (addr 49912): LED1545G12 - IKEA TRADFRI bulb E26/E27, white spectrum, globe, opal, 980 lm (Router)
2025-04-08 12:08:42.630 - info: zigbee.0 (5651) 0x000b57fffedc252b (addr 52249): L1531 - IKEA SURTE door light panel, white spectrum, 38x64 cm (Router)
2025-04-08 12:08:42.631 - info: zigbee.0 (5651) 0x000b57fffeb14c03 (addr 56033): L1531 - IKEA SURTE door light panel, white spectrum, 38x64 cm (Router)
2025-04-08 12:08:42.631 - info: zigbee.0 (5651) 0x7cb03eaa00adef93 (addr 22024): 4052899926110 - OSRAM Flex RGBW (Router)
2025-04-08 12:08:42.631 - info: zigbee.0 (5651) 0x680ae2fffe7896e4 (addr 63576): LED1732G11 - IKEA TRADFRI bulb E26/E27, white spectrum, globe, opal, 1000 lm (Router)
2025-04-08 12:08:42.632 - info: zigbee.0 (5651) 0x90fd9ffffe6e6985 (addr 28720): LED1650R5 - IKEA TRADFRI bulb GU10, white, 400 lm (Router)
2025-04-08 12:08:42.633 - info: zigbee.0 (5651) 0x90fd9ffffe7ff08f (addr 17289): LED1624G9 - IKEA TRADFRI bulb E12/E14/E26/E27, color/white spectum, globe, opal, 600 lm (Router)
2025-04-08 12:08:42.633 - info: zigbee.0 (5651) 0x00124b001c2ab1e7 (addr 11377): CC2530.ROUTER - Custom devices (DiY) CC2530 router (Router)
2025-04-08 12:08:42.634 - info: zigbee.0 (5651) 0x00158d0002a91e86 (addr 27642): DJT11LM - Aqara Vibration sensor (EndDevice)
2025-04-08 12:08:42.639 - info: zigbee.0 (5651) 0x943469fffe711151 (addr 37793): 701721 - Popp Smart thermostat (EndDevice)
2025-04-08 12:08:42.639 - info: zigbee.0 (5651) 0x00158d000223a279 (addr 724): WSDCGQ11LM - Aqara Temperature and humidity sensor (EndDevice)
2025-04-08 12:08:42.639 - info: zigbee.0 (5651) 0x00158d00044dc92b (addr 30843): MCCGQ11LM - Aqara Door and window sensor (EndDevice)
2025-04-08 12:08:42.640 - info: zigbee.0 (5651) 0xa4c138dd663379dc (addr 5121): LYWSD03MMC - Custom devices (DiY) Xiaomi temperature & humidity sensor with custom firmware (EndDevice)
2025-04-08 12:08:42.640 - info: zigbee.0 (5651) 0x00124b002a5ed13a (addr 34196): IKEA_VINDRIKTNING_EFEKTA III - IKEA [IKEA_VINDRIKTNING III - PM2.5, PM10, PM1, VOC Index, CO2, Temperature and Humidity sensor with extended functionality (control of air cleaning)](http://efektalab.com/IKEA_VINDRIKTNING ) (Router)
2025-04-08 12:08:42.651 - info: zigbee.0 (5651) 0x00124b001b80cb27 (addr 17876): Egony_Flower - EFEKTA Soil moisture sensor Egony_Flower, mod DIYRuZ Flower (EndDevice)
2025-04-08 12:08:42.652 - info: zigbee.0 (5651) 0xa4c1387f05f1cc89 (addr 30787): TS0205_smoke_2 - Tuya Optical smoke sensor (model YG500A on the PCB) (EndDevice)
2025-04-08 12:08:42.652 - info: zigbee.0 (5651) 0x84fd27fffed2450f (addr 25967): TS011F_plug_1 - Tuya Smart plug (with power monitoring) (Router)
2025-04-08 12:08:42.652 - info: zigbee.0 (5651) Currently 59 devices are joined:
2025-04-08 12:08:42.653 - info: zigbee.0 (5651) Zigbee started
2025-04-08 12:08:42.978 - info: zigbee.0 (5651) debug devices set to []
2025-04-08 12:08:43.270 - error: zigbee.0 (5651) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2025-04-08 12:08:43.272 - error: zigbee.0 (5651) unhandled promise rejection: Parameter "filename" needs to be of type "string" but type "object" has been passed
2025-04-08 12:08:43.329 - error: zigbee.0 (5651) Error: Parameter "filename" 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:238:19)
at Zigbee.writeFile (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:6982:19)
at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:145:38)
at processImmediate (node:internal/timers:485:21)
2025-04-08 12:08:43.329 - error: zigbee.0 (5651) Parameter "filename" needs to be of type "string" but type "object" has been passed
2025-04-08 12:08:43.336 - warn: zigbee.0 (5651) Unable to copy icon from device definition, looked at img/IKEA_VINDRIKTNING_EFEKTA III.png, /opt/iobroker/iobroker-data/zigbee_0/img/IKEA_VINDRIKTNING_EFEKTA III.png, /opt/iobroker/iobroker-data/zigbee_0/IKEA_VINDRIKTNING_EFEKTA III.png and /opt/iobroker/iobroker-data/zigbee_0/img/IKEA_VINDRIKTNING_EFEKTA III.png
2025-04-08 12:08:43.339 - info: zigbee.0 (5651) cleaned everything up...
2025-04-08 12:08:43.340 - info: zigbee.0 (5651) local config saved
2025-04-08 12:08:43.340 - info: zigbee.0 (5651) Saved local configuration data
2025-04-08 12:08:43.341 - info: zigbee.0 (5651) terminating
2025-04-08 12:08:43.342 - warn: zigbee.0 (5651) Terminated (UNCAUGHT_EXCEPTION): Without reason
2025-04-08 12:08:43.842 - info: zigbee.0 (5651) terminating
2025-04-08 12:08:43.873 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:43.874 - warn: zigbee.0 (5651) get state error: DB closed
2025-04-08 12:08:43.998 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.004 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.004 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.004 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.004 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.004 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.004 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.005 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.006 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.006 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.006 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.021 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d0004fcf9d2.available: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d0004fcf9d2.link_quality: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d0001bb8f04.available: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d0001bb8f04.link_quality: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d0001ad4ab1.available: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d0001ad4ab1.link_quality: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d0001df05e1.available: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d0001df05e1.link_quality: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffedb8ae5.available: DB closed
2025-04-08 12:08:44.022 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffedb8ae5.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffe51c679.available: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffe51c679.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffedb8976.available: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffedb8976.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffef5a250.available: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffef5a250.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.cc86ecfffef3c028.available: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.cc86ecfffef3c028.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffef5a281.available: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.842e14fffef5a281.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.cc86ecfffe1358a9.available: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.cc86ecfffe1358a9.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe04db13.available: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe04db13.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000b57fffebc3759.available: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000b57fffebc3759.link_quality: DB closed
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.023 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffed27f57.available: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffed27f57.link_quality: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000d6ffffed09b8d.available: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000d6ffffed09b8d.link_quality: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.04cf8cdf3c75b72f.available: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.04cf8cdf3c75b72f.link_quality: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d000255ef1b.available: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d000255ef1b.link_quality: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000d6f0014f6c86f.available: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000d6f0014f6c86f.link_quality: DB closed
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.024 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.7cb03eaa00adea74.available: DB closed
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.7cb03eaa00adea74.link_quality: DB closed
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.7cb03eaa00adf023.available: DB closed
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.7cb03eaa00adf023.link_quality: DB closed
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.7cb03eaa00adec1a.available: DB closed
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.7cb03eaa00adec1a.link_quality: DB closed
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe4c5abf.available: DB closed
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe4c5abf.link_quality: DB closed
2025-04-08 12:08:44.025 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000b57fffeecea8a.available: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000b57fffeecea8a.link_quality: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe049ad1.available: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe049ad1.link_quality: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000b57fffedc252b.available: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000b57fffedc252b.link_quality: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000b57fffeb14c03.available: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.000b57fffeb14c03.link_quality: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.7cb03eaa00adef93.available: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.7cb03eaa00adef93.link_quality: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.680ae2fffe7896e4.available: DB closed
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.042 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.680ae2fffe7896e4.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe6e6985.available: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe6e6985.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe7ff08f.available: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.90fd9ffffe7ff08f.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00124b001c2ab1e7.available: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00124b001c2ab1e7.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.943469fffe711151.available: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.943469fffe711151.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d000223a279.available: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d000223a279.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d00044dc92b.available: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00158d00044dc92b.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.a4c138dd663379dc.available: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.a4c138dd663379dc.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00124b002a5ed13a.available: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00124b002a5ed13a.link_quality: DB closed
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.043 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00124b001b80cb27.available: DB closed
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.00124b001b80cb27.link_quality: DB closed
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.a4c1387f05f1cc89.available: DB closed
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.a4c1387f05f1cc89.link_quality: DB closed
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.84fd27fffed2450f.available: DB closed
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) Could not perform strict object check of state zigbee.0.84fd27fffed2450f.link_quality: DB closed
2025-04-08 12:08:44.057 - warn: zigbee.0 (5651) get state error: Connection is closed.
2025-04-08 12:08:44.062 - error: zigbee.0 (5651) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2025-04-08 12:08:44.062 - error: zigbee.0 (5651) unhandled promise rejection: DB closed
2025-04-08 12:08:44.063 - error: zigbee.0 (5651) 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-04-08 12:08:44.063 - error: zigbee.0 (5651) DB closed
2025-04-08 12:08:44.090 - error: zigbee.0 (5651) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2025-04-08 12:08:44.090 - error: zigbee.0 (5651) unhandled promise rejection: DB closed
2025-04-08 12:08:44.090 - error: zigbee.0 (5651) 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-04-08 12:08:44.090 - error: zigbee.0 (5651) DB closed
2025-04-08 12:08:44.090 - error: zigbee.0 (5651) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2025-04-08 12:08:44.097 - error: zigbee.0 (5651) unhandled promise rejection: DB closed
2025-04-08 12:08:44.097 - error: zigbee.0 (5651) 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-04-08 12:08:44.097 - error: zigbee.0 (5651) DB closed
2025-04-08 12:08:44.098 - error: zigbee.0 (5651) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2025-04-08 12:08:44.098 - error: zigbee.0 (5651) unhandled promise rejection: DB closed
2025-04-08 12:08:44.098 - error: zigbee.0 (5651) 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-04-08 12:08:44.098 - error: zigbee.0 (5651) DB closed
2025-04-08 12:08:44.098 - error: zigbee.0 (5651) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
2025-04-08 12:08:44.098 - error: zigbee.0 (5651) unhandled promise rejection: DB closed
2025-04-08 12:08:44.098 - error: zigbee.0 (5651) 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-04-08 12:08:44.098 - error: zigbee.0 (5651) DB closed
2025-04-08 12:08:44.143 - error: host.IoBroker 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-04-08 12:08:44.143 - error: host.IoBroker Caught by controller[1]: Error: Parameter "filename" needs to be of type "string" but type "object" has been passed
2025-04-08 12:08:44.143 - error: host.IoBroker Caught by controller[1]: at Function.assertString (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/validator.ts:238:19)
2025-04-08 12:08:44.143 - error: host.IoBroker Caught by controller[1]: at Zigbee.writeFile (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:6982:19)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[1]: at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/lib/statescontroller.js:145:38)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[1]: at processImmediate (node:internal/timers:485:21)
2025-04-08 12:08:44.144 - error: host.IoBroker 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-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: Error: DB closed
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Object.onceWrapper (node:events:639:26)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:events:524:28)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:domain:489:12)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at TCP. (node:net:343:12)
2025-04-08 12:08:44.144 - error: host.IoBroker 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-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: Error: DB closed
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Object.onceWrapper (node:events:639:26)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:events:524:28)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:domain:489:12)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at TCP. (node:net:343:12)
2025-04-08 12:08:44.144 - error: host.IoBroker 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-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: Error: DB closed
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Object.onceWrapper (node:events:639:26)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:events:524:28)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:domain:489:12)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at TCP. (node:net:343:12)
2025-04-08 12:08:44.144 - error: host.IoBroker 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-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: Error: DB closed
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Object.onceWrapper (node:events:639:26)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:events:524:28)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:domain:489:12)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at TCP. (node:net:343:12)
2025-04-08 12:08:44.144 - error: host.IoBroker 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-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: Error: DB closed
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Object.onceWrapper (node:events:639:26)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:events:524:28)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at Socket.emit (node:domain:489:12)
2025-04-08 12:08:44.144 - error: host.IoBroker Caught by controller[2]: at TCP. (node:net:343:12)
2025-04-08 12:08:44.144 - error: host.IoBroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

Externe Konverter:
IKEA_VINDRIKTNING_EFEKTA_III.js

[Asgothian]

@dimaiv exakt. Nimm bitte das ‚Icon‘ aus dem externen Konverter - dann wird es gehen.

A.

Nachtrag - wird der externe Konverter überhaupt nonchalantly gebraucht ?Der sollte doch eigentlich im ZHC drin sein.

[dimaiv]

@asgothian sagte in Tester Zigbee Adapter 3.x gesucht:

@dimaiv exakt. Nimm bitte das ‚Icon‘ aus dem externen Konverter - dann wird es gehen.

Ich habe die Zeile auskommentiert, Adapter startet durch, aber ohne Bild dazu:

2025-04-08 12:46:32.867 - info: zigbee.0 (19404) downloading https://www.zigbee2mqtt.io/images/devices/IKEA_VINDRIKTNING_EFEKTA-III.png to /tmp/IKEA_VINDRIKTNING_EFEKTA III.png
2025-04-08 12:46:33.088 - warn: zigbee.0 (19404) ERROR : icon path not found /tmp/IKEA_VINDRIKTNING_EFEKTA III.png

A.

Nachtrag - wird der externe Konverter überhaupt nonchalantly gebraucht ?Der sollte doch eigentlich im ZHC drin sein.

Ja, externe Konverter wird noch gebraucht.

[Shadowhunter23]

@asgothian

Ich bin mal auf die neue Version hoch und bekomme beim öffnen der Instanz folgende Warnungen:

zigbee.0
2025-04-08 16:35:00.623	warn	readNvBackup returns {"channel":11,"precfgkey":"01030507090b0d0f00020406080a0c0d","extPanID":"8949b203f0c8df88","panID":6749}

zigbee.0
2025-04-08 16:35:00.623	warn	readNvBackup called

Sehe aber sonst keine Probleme.

[Flugschüler]

@shadowhunter23 Das gleiche auch bei mir.

[Asgothian]

@shadowhunter23 sagte in Tester Zigbee Adapter 3.x gesucht:

@asgothian

Ich bin mal auf die neue Version hoch und bekomme beim öffnen der Instanz folgende Warnungen:

zigbee.0
2025-04-08 16:35:00.623	warn	readNvBackup returns {"channel":11,"precfgkey":"01030507090b0d0f00020406080a0c0d","extPanID":"8949b203f0c8df88","panID":6749}

zigbee.0
2025-04-08 16:35:00.623	warn	readNvBackup called

Sehe aber sonst keine Probleme.

Das ist Teil von internen warn-Meldungen. Es wird ,ist der Zeit verschwinden.

A.

[Asgothian]

@dimaiv sagte in Tester Zigbee Adapter 3.x gesucht:

@asgothian sagte in Tester Zigbee Adapter 3.x gesucht:

@dimaiv exakt. Nimm bitte das ‚Icon‘ aus dem externen Konverter - dann wird es gehen.

Ich habe die Zeile auskommentiert, Adapter startet durch, aber ohne Bild dazu:

2025-04-08 12:46:32.867 - info: zigbee.0 (19404) downloading https://www.zigbee2mqtt.io/images/devices/IKEA_VINDRIKTNING_EFEKTA-III.png to /tmp/IKEA_VINDRIKTNING_EFEKTA III.png
2025-04-08 12:46:33.088 - warn: zigbee.0 (19404) ERROR : icon path not found /tmp/IKEA_VINDRIKTNING_EFEKTA III.png

Ja, das ist auch klar - unter dem Link ist kein Bild zu finden. Was du bitte versuchen kannst:

• im externen Konverter die Einstellung für das Icon umstellen:

   icon: 'IKEA_VINDRIKTNING_EFEKTA_III.png'

• 'neben' dem Koordinator die Datei IKEA_VINDRIKTNING_EFEKTA_III.png mit dem entsprechenden Bild ablegen.
• Adapter neu starten.

Der Adapter sollte starten und auch das Bild darstellen.

A.
Nochmal ein Nachtrag: gibt es bei den ZHC oder Z2M einen Issue zur Integration des Vindriktning ?

[MeisterQ 0]

@Asgothian Bekommt man die Version schon aus dem Latest? Weil da wird sie mir nicht angezeigt, oder muss ich sie über die Github Katze Installieren?

[Asgothian]

@meisterq-0 die version ist im Latest. (sollte sie zumindest sein)

A.

[MeisterQ 0]

@asgothian Komisch. Wird mir nicht Angezeigt.

[Rushmed]

Hallo,

was bedeuten auf dem Hardware Tab die Warnung und der Error?
Muss ich hier aktiv werden?

[Asgothian]

@rushmed sagte in Tester Zigbee Adapter 3.x gesucht:

Hallo,

was bedeuten auf dem Hardware Tab die Warnung und der Error?
Muss ich hier aktiv werden?

Hast du die Doku auf Github dazu gelesen ? Da steht es drin.

Das X bedeutet das der Transport Key nicht mit dem übereinstimmt der im Backup der Einstellungen steht.
Der grüne Haken bedeutet das der Kanal mit dem überein stimmt der im Backup steht
das gelbe Dreieck warnt das es ein ungünstiger Kanal ist (nicht teil der ZLL Kanäle, so das ggf. einzelne Geräte bei Dir nicht gehen

Du kannst durch einlesen des Backup schauen ob das rote X weg geht - da ist noch ein Fehler drin, da aktuell gross/kleinschreibung noch einen Unterschied macht - das kommt noch weg.

A.
TLDR: Nein.

[Rushmed]

@asgothian sagte in Tester Zigbee Adapter 3.x gesucht:

Du kannst durch einlesen des Backup schauen ob das rote X weg geht - da ist noch ein Fehler drin, da aktuell gross/kleinschreibung noch einen Unterschied macht - das kommt noch weg.

Hat geklappt, danke.

[BigMike71]

Habe heute von 1.10.4 direkt auf die 3.0 upgedatet!
Nachdem ich meine ca. 20 Aqara Wandschalter in meinen Skripten an die neuen Datenpunkte angepasst habe und vorher ein readNvBackup durchgeführt habe läuft bisher alles problemlos!

Allerdings bekomme ich wenn ich auf den Zigbee-Tab wechsel jedes Mal eine Warnung:

2025-04-11 15:52:31.145 - warn: zigbee.0 (1118465) readNvBackup called
2025-04-11 15:52:31.149 - warn: zigbee.0 (1118465) readNvBackup returns {"channel":11,"precfgkey":"b2090507090c0d0f00020406080b0c0d","extPanID":"0123456799abcdef","panID":3369}

kann man das noch abschalten?

[Shadowhunter23]

@bigmike71

~8 Beiträge zuvor:
https://forum.iobroker.net/topic/80644/tester-zigbee-adapter-3-x-gesucht/8?_=1744382131667

[Fabio]

@asgothian bin jetzt auch auf die 3.0 hoch bis jetzt keine Probleme

ausser diese Warn Meldungen

zigbee.0
2025-04-15 15:17:06.934	warn	readNvBackup returns {"channel":11,"precfgkey":"01030507090b0d0f00020406080a0c0d","extPanID":"fecad609004b1200","panID":6754}

zigbee.0
2025-04-15 15:17:06.929	warn	readNvBackup called

aber da hast du ja schon zu geantwortet.

Vielen Dank für deine Mühen
Herzliche Grüße aus Köln
Fabio

[ste_glei]

@Asgothian
Bin jetzt seit ein paar Tagen auf 3.0 und es läuft ohne Probleme.

gefühlt stabiler als die Vorgänger.

Vielen Dank für deinen Einsatz

[locito09]

@asgothian
Bei mir läuft die 3.0 auch sehr stabil, hab aber ab und zuGeräte die die Verbindung verlieren 2 x Flower verlieren immer wieder die Verbindung und ich muss sie nochmals anlernen und auch verschiedene Hue Lampe muss ich kurz ausschalten und neu verbinden