Tester für Zigbee Adapter 2.0.x gesucht
-
@asgothian sagte in Tester für Zigbee Adapter 2.0.x gesucht:
Nebenbei - ist es wirklich zuviel verlangt das Ihr die Logs so editiert das sie auch vernünftig lesbar sind ?
Oder direkt aus der Kommandozeile nehmen, dann stimmt auch direkt die chronologische Abfolge.
iob logs [INSTANZ]sollte kein Hexenwerk sein. Da wird auch nichts gekürzt, weil es zu lang wäre.
-
@asgothian sagte in Tester für Zigbee Adapter 2.0.x gesucht:
Da steht
Sieht tatsächlich abgeschnitten aus, sollte aber nicht der Fall sein.
andere Zeilen sind viel länger.@fi_84
jetzt würde mich wirklich interessieren was da steht oder eben nicht
Entweder im admin das log herunterladen und duese Zeile dirt herauskopieren, oder so wie@thomas-braun sagte in Tester für Zigbee Adapter 2.0.x gesucht:
@asgothian sagte in Tester für Zigbee Adapter 2.0.x gesucht:
Nebenbei - ist es wirklich zuviel verlangt das Ihr die Logs so editiert das sie auch vernünftig lesbar sind ?
Oder direkt aus der Kommandozeile nehmen, dann stimmt auch direkt die chronologische Abfolge.
iob logs [INSTANZ]sollte kein Hexenwerk sein. Da wird auch nichts gekürzt, weil es zu lang wäre.
-
Hüstel, hallo zusammen,
Ich habe im Adapter 2.0.5 folgenden Hinweis gelesen, kann aber auch nach einer Übersetzung nichts damit anfangen.
Was will mir als Laie der Text sagen? Was ist switch to converter 21 .................
Birnen habe ich keine bei denen ich an rgb rumfummel.
Entschuldigt wenn das mal wieder eine dumme Frage sein sollte habe nur massive Sorgen das bei mir vielleicht nach dem Update nicht mehr läuft; dann bin ich geliefert
Viele Grüße Duffy
Edit: könnte ich nach der Installation von 2.0.5 auch wieder auf die 1.xx Version zurück oder ist das dann rum?
-
@duffy sagte in Tester für Zigbee Adapter 2.0.x gesucht:
Was will mir als Laie der Text sagen? Was ist switch to converter 21 .................
Es geht um den folgenden Umstand (leider nur auf englisch)
https://github.com/Koenkk/zigbee2mqtt/discussions/24198Letztendlich ändern sich dadurch einige Datenpunkte (Erklärung dazu im 1. Post dieses Threads)
Der Weg zurück ist nicht versperrt. Du musst allerdings dann wieder einen 'state cleanup' durchführen.
A.
-
Hier noch mal direkt aus der Console
iob logs zigbeeiob logs zigbee 2025-04-15 16:20:29.605 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4b637.link_quality: DB closed 2025-04-15 16:20:29.606 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.606 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4b637.link_quality: DB closed 2025-04-15 16:20:29.607 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.607 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a34c86.available: DB closed 2025-04-15 16:20:29.607 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.608 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a34c86.available: DB closed 2025-04-15 16:20:29.608 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.608 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a34c86.link_quality: DB closed 2025-04-15 16:20:29.609 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.609 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a34c86.link_quality: DB closed 2025-04-15 16:20:29.609 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.610 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4ae97.available: DB closed 2025-04-15 16:20:29.610 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.611 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4ae97.available: DB closed 2025-04-15 16:20:29.611 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.611 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4ae97.link_quality: DB closed 2025-04-15 16:20:29.612 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.612 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0003a4ae97.link_quality: DB closed 2025-04-15 16:20:29.613 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.613 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe35b.available: DB closed 2025-04-15 16:20:29.613 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.614 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe35b.available: DB closed 2025-04-15 16:20:29.614 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.614 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe35b.link_quality: DB closed 2025-04-15 16:20:29.615 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.615 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe35b.link_quality: DB closed 2025-04-15 16:20:29.616 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.616 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe81deaa.available: DB closed 2025-04-15 16:20:29.616 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.617 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe81deaa.available: DB closed 2025-04-15 16:20:29.617 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.618 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe81deaa.link_quality: DB closed 2025-04-15 16:20:29.618 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.618 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe81deaa.link_quality: DB closed 2025-04-15 16:20:29.619 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.619 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe7a364d.available: DB closed 2025-04-15 16:20:29.619 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.620 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe7a364d.available: DB closed 2025-04-15 16:20:29.620 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.620 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe7a364d.link_quality: DB closed 2025-04-15 16:20:29.621 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.621 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe7a364d.link_quality: DB closed 2025-04-15 16:20:29.622 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.622 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe6b4e2c.available: DB closed 2025-04-15 16:20:29.623 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.623 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe6b4e2c.available: DB closed 2025-04-15 16:20:29.624 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.624 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe6b4e2c.link_quality: DB closed 2025-04-15 16:20:29.625 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.625 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.5c0272fffe6b4e2c.link_quality: DB closed 2025-04-15 16:20:29.626 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.626 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00044a926f.available: DB closed 2025-04-15 16:20:29.627 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.627 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00044a926f.available: DB closed 2025-04-15 16:20:29.628 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.628 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00044a926f.link_quality: DB closed 2025-04-15 16:20:29.629 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.629 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00044a926f.link_quality: DB closed 2025-04-15 16:20:29.629 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.630 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe29a.available: DB closed 2025-04-15 16:20:29.630 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.630 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe29a.available: DB closed 2025-04-15 16:20:29.631 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.631 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe29a.link_quality: DB closed 2025-04-15 16:20:29.631 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.632 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d0004abe29a.link_quality: DB closed 2025-04-15 16:20:29.632 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.644 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00035390ec.available: DB closed 2025-04-15 16:20:29.645 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.645 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00035390ec.available: DB closed 2025-04-15 16:20:29.646 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.646 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00035390ec.link_quality: DB closed 2025-04-15 16:20:29.647 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.647 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d00035390ec.link_quality: DB closed 2025-04-15 16:20:29.647 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.648 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d000679273c.available: DB closed 2025-04-15 16:20:29.648 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.649 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d000679273c.available: DB closed 2025-04-15 16:20:29.649 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 16:20:29.649 - warn: zigbee.0 (3853) Could not perform strict object check of state zigbee.0.00158d000679273c.link_quality: DB closed 2025-04-15 16:20:29.650 - warn: zigbee.0 (3853) get state error: Connection is closed. 2025-04-15 20:48:19.060 - info: zigbee.0 (2000) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-04-15 20:48:19.089 - info: zigbee.0 (2000) init localConfig 2025-04-15 20:48:19.100 - info: zigbee.0 (2000) --> transmitPower : normal 2025-04-15 20:48:19.116 - info: zigbee.0 (2000) delete old Backup files. keep only last 10 2025-04-15 20:48:19.121 - info: zigbee.0 (2000) --- creating device debug --- 2025-04-15 20:48:19.123 - info: zigbee.0 (2000) Starting Adapter npm ... 2025-04-15 20:48:19.192 - info: zigbee.0 (2000) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-04-15 20:48:19.195 - info: zigbee.0 (2000) Starting Zigbee-Herdsman 2025-04-15 20:48:21.264 - info: zigbee.0 (2000) Unable to obtain herdsman settings 2025-04-15 20:48:21.351 - error: zigbee.0 (2000) Starting zigbee-herdsman problem : Error: Operation not supported, cannot set 2025-04-15 20:48:21.356 - error: zigbee.0 (2000) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-04-15 20:48:21.358 - error: zigbee.0 (2000) unhandled promise rejection: undefined 2025-04-15 20:48:21.359 - error: zigbee.0 (2000) undefined 2025-04-15 20:48:21.541 - info: zigbee.0 (2000) cleaned everything up... 2025-04-15 20:48:21.543 - info: zigbee.0 (2000) local config saved 2025-04-15 20:48:21.553 - info: zigbee.0 (2000) Saved local configuration data 2025-04-15 20:48:21.554 - info: zigbee.0 (2000) terminating 2025-04-15 20:48:21.556 - warn: zigbee.0 (2000) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-04-15 20:48:22.308 - error: zigbee.0 (2000) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') 2025-04-15 20:48:22.347 - info: zigbee.0 (2000) terminating 2025-04-15 20:48:22.358 - warn: zigbee.0 (2000) Device 0x5c0272fffe7a194d "LED1537R6/LED1739R5" not found. 2025-04-15 20:48:22.360 - warn: zigbee.0 (2000) Device 0x5c0272fffe6c6dac "LED1537R6/LED1739R5" not found. 2025-04-15 20:48:22.362 - warn: zigbee.0 (2000) Device 0x086bd7fffe202f76 "LED1537R6/LED1739R5" not found. 2025-04-15 20:48:22.364 - warn: zigbee.0 (2000) Device 0xd0cf5efffedccd5c "LED1537R6/LED1739R5" not found. 2025-04-15 20:48:22.366 - warn: zigbee.0 (2000) Device 0x086bd7fffe5a65e9 "LED1537R6/LED1739R5" not found. 2025-04-15 20:48:22.368 - warn: zigbee.0 (2000) Device 0xd0cf5efffedcdea0 "LED1537R6/LED1739R5" not found. 2025-04-15 20:48:22.370 - warn: zigbee.0 (2000) Device 0x680ae2fffe7f2cd1 "E1524/E1810" not found. 2025-04-15 20:48:22.371 - warn: zigbee.0 (2000) Device 0x00158d0003a4b637 "MCCGQ11LM" not found. 2025-04-15 20:48:22.374 - warn: zigbee.0 (2000) Device 0x00158d0003a34c86 "MCCGQ11LM" not found. 2025-04-15 20:48:22.376 - warn: zigbee.0 (2000) Device 0x00158d0003a4ae97 "MCCGQ11LM" not found. 2025-04-15 20:48:22.378 - warn: zigbee.0 (2000) Device 0x00158d0004abe35b "RTCGQ11LM" not found. 2025-04-15 20:48:22.380 - warn: zigbee.0 (2000) Device 0x5c0272fffe81deaa "E1743" not found. 2025-04-15 20:48:22.383 - warn: zigbee.0 (2000) Device 0x5c0272fffe7a364d "LED1537R6/LED1739R5" not found. 2025-04-15 20:48:22.384 - warn: zigbee.0 (2000) Device 0x5c0272fffe6b4e2c "LED1537R6/LED1739R5" not found. 2025-04-15 20:48:22.387 - warn: zigbee.0 (2000) Device 0x00158d00044a926f "WSDCGQ11LM" not found. 2025-04-15 20:48:22.389 - warn: zigbee.0 (2000) Device 0x00158d0004abe29a "RTCGQ11LM" not found. 2025-04-15 20:48:22.390 - warn: zigbee.0 (2000) Device 0x00158d00035390ec "MCCGQ11LM" not found. 2025-04-15 20:48:22.392 - warn: zigbee.0 (2000) Device 0x00158d000679273c "WXKG11LM" not found. 2025-04-15 20:48:22.395 - warn: zigbee.0 (2000) Device 0x00158d00067bd3e6 "WXKG11LM" not found. 2025-04-15 20:48:22.396 - warn: zigbee.0 (2000) Device 0x00124b0024545ee5 "SNZB-03" not found. 2025-04-15 20:48:22.626 - info: zigbee.0 (2000) terminating 2025-04-15 20:48:22.796 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:22.798 - warn: zigbee.0 (2000) redis get zigbee.0.info.debugmessages, error - DB closed 2025-04-15 20:48:22.800 - warn: zigbee.0 (2000) get state error: DB closed 2025-04-15 20:48:23.558 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.available: DB closed 2025-04-15 20:48:23.560 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.561 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.available: DB closed 2025-04-15 20:48:23.562 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.563 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.link_quality: DB closed 2025-04-15 20:48:23.564 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.567 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.link_quality: DB closed 2025-04-15 20:48:23.568 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.569 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.available: DB closed 2025-04-15 20:48:23.570 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.574 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.available: DB closed 2025-04-15 20:48:23.575 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.576 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.link_quality: DB closed 2025-04-15 20:48:23.577 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.578 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.link_quality: DB closed 2025-04-15 20:48:23.580 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.583 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.086bd7fffe202f76.available: DB closed 2025-04-15 20:48:23.584 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.585 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.086bd7fffe202f76.available: DB closed 2025-04-15 20:48:23.588 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.589 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.086bd7fffe202f76.link_quality: DB closed 2025-04-15 20:48:23.591 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.592 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.086bd7fffe202f76.link_quality: DB closed 2025-04-15 20:48:23.593 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.594 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.d0cf5efffedccd5c.available: DB closed 2025-04-15 20:48:23.595 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.596 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.d0cf5efffedccd5c.available: DB closed 2025-04-15 20:48:23.599 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.600 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.d0cf5efffedccd5c.link_quality: DB closed 2025-04-15 20:48:23.601 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.602 - warn: zigbee.0 (2000) Could not perform strict object check of state zigbee.0.d0cf5efffedccd5c.link_quality: DB closed 2025-04-15 20:48:23.603 - warn: zigbee.0 (2000) get state error: Connection is closed. 2025-04-15 20:48:23.627 - info: zigbee.0 (2000) terminating with timeout 2025-04-15 20:48:57.895 - info: zigbee.0 (2347) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.0, js-controller: 7.0.6 2025-04-15 20:48:57.923 - info: zigbee.0 (2347) init localConfig 2025-04-15 20:48:57.932 - info: zigbee.0 (2347) --> transmitPower : normal 2025-04-15 20:48:57.947 - info: zigbee.0 (2347) delete old Backup files. keep only last 10 2025-04-15 20:48:57.952 - info: zigbee.0 (2347) --- creating device debug --- 2025-04-15 20:48:57.953 - info: zigbee.0 (2347) Starting Adapter npm ... 2025-04-15 20:48:58.023 - info: zigbee.0 (2347) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) 2025-04-15 20:48:58.026 - info: zigbee.0 (2347) Starting Zigbee-Herdsman 2025-04-15 20:48:59.913 - info: zigbee.0 (2347) Unable to obtain herdsman settings 2025-04-15 20:48:59.995 - error: zigbee.0 (2347) Starting zigbee-herdsman problem : Error: Operation not supported, cannot set 2025-04-15 20:48:59.998 - error: zigbee.0 (2347) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2025-04-15 20:49:00.000 - error: zigbee.0 (2347) unhandled promise rejection: undefined 2025-04-15 20:49:00.001 - error: zigbee.0 (2347) undefined 2025-04-15 20:49:00.101 - info: zigbee.0 (2347) cleaned everything up... 2025-04-15 20:49:00.104 - info: zigbee.0 (2347) local config saved 2025-04-15 20:49:00.106 - info: zigbee.0 (2347) Saved local configuration data 2025-04-15 20:49:00.107 - info: zigbee.0 (2347) terminating 2025-04-15 20:49:00.110 - warn: zigbee.0 (2347) Terminated (UNCAUGHT_EXCEPTION): Without reason 2025-04-15 20:49:00.520 - error: zigbee.0 (2347) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') 2025-04-15 20:49:00.535 - info: zigbee.0 (2347) terminating 2025-04-15 20:49:00.538 - warn: zigbee.0 (2347) Device 0x5c0272fffe7a194d "LED1537R6/LED1739R5" not found. 2025-04-15 20:49:00.539 - warn: zigbee.0 (2347) Device 0x5c0272fffe6c6dac "LED1537R6/LED1739R5" not found. 2025-04-15 20:49:00.540 - warn: zigbee.0 (2347) Device 0x086bd7fffe202f76 "LED1537R6/LED1739R5" not found. 2025-04-15 20:49:00.541 - warn: zigbee.0 (2347) Device 0xd0cf5efffedccd5c "LED1537R6/LED1739R5" not found. 2025-04-15 20:49:00.542 - warn: zigbee.0 (2347) Device 0x086bd7fffe5a65e9 "LED1537R6/LED1739R5" not found. 2025-04-15 20:49:00.543 - warn: zigbee.0 (2347) Device 0xd0cf5efffedcdea0 "LED1537R6/LED1739R5" not found. 2025-04-15 20:49:00.544 - warn: zigbee.0 (2347) Device 0x680ae2fffe7f2cd1 "E1524/E1810" not found. 2025-04-15 20:49:00.545 - warn: zigbee.0 (2347) Device 0x00158d0003a4b637 "MCCGQ11LM" not found. 2025-04-15 20:49:00.547 - warn: zigbee.0 (2347) Device 0x00158d0003a34c86 "MCCGQ11LM" not found. 2025-04-15 20:49:00.548 - warn: zigbee.0 (2347) Device 0x00158d0003a4ae97 "MCCGQ11LM" not found. 2025-04-15 20:49:00.549 - warn: zigbee.0 (2347) Device 0x00158d0004abe35b "RTCGQ11LM" not found. 2025-04-15 20:49:00.550 - warn: zigbee.0 (2347) Device 0x5c0272fffe81deaa "E1743" not found. 2025-04-15 20:49:00.551 - warn: zigbee.0 (2347) Device 0x5c0272fffe7a364d "LED1537R6/LED1739R5" not found. 2025-04-15 20:49:00.552 - warn: zigbee.0 (2347) Device 0x5c0272fffe6b4e2c "LED1537R6/LED1739R5" not found. 2025-04-15 20:49:00.553 - warn: zigbee.0 (2347) Device 0x00158d00044a926f "WSDCGQ11LM" not found. 2025-04-15 20:49:00.554 - warn: zigbee.0 (2347) Device 0x00158d0004abe29a "RTCGQ11LM" not found. 2025-04-15 20:49:00.554 - warn: zigbee.0 (2347) Device 0x00158d00035390ec "MCCGQ11LM" not found. 2025-04-15 20:49:00.555 - warn: zigbee.0 (2347) Device 0x00158d000679273c "WXKG11LM" not found. 2025-04-15 20:49:00.556 - warn: zigbee.0 (2347) Device 0x00158d00067bd3e6 "WXKG11LM" not found. 2025-04-15 20:49:00.557 - warn: zigbee.0 (2347) Device 0x00124b0024545ee5 "SNZB-03" not found. 2025-04-15 20:49:00.627 - info: zigbee.0 (2347) terminating 2025-04-15 20:49:01.072 - warn: zigbee.0 (2347) redis get zigbee.0.info.debugmessages, error - Connection is closed. 2025-04-15 20:49:01.094 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.096 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.315 - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.available: DB closed 2025-04-15 20:49:01.317 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.320 - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.available: DB closed 2025-04-15 20:49:01.325 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.326 - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.link_quality: DB closed 2025-04-15 20:49:01.327 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.328 - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe7a194d.link_quality: DB closed 2025-04-15 20:49:01.333 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.334 - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.available: DB closed 2025-04-15 20:49:01.335 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.336 - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.available: DB closed 2025-04-15 20:49:01.339 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.340 - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.link_quality: DB closed 2025-04-15 20:49:01.341 - warn: zigbee.0 (2347) get state error: Connection is closed. 2025-04-15 20:49:01.342 - warn: zigbee.0 (2347) Could not perform strict object check of state zigbee.0.5c0272fffe6c6dac.link_quality: DB closed 2025-04-15 20:49:01.344 - warn: zigbee.0 (2347) get state error: Connection is closed. -
@fi_84 die Zeile
zigbee.0 2025-04-15 16:20:28.648 error Starting zigbee-herdsman problem : Error: Operation not supported, cannot sethast du gerade nicht mehr erwischt
-
@fi_84 sagte in Tester für Zigbee Adapter 2.0.x gesucht:
2025-04-15 20:48:21.351 - error: zigbee.0 (2000) Starting zigbee-herdsman problem : Error: Operation not supported, cannot sethier ist sie nochmal!
@Asgothian
wieder unvollständig
ich fürchte das fehlende ist genau das Problem -
-
@fi_84 sagte in Tester für Zigbee Adapter 2.0.x gesucht:
es steht nicht mehr drin
glaub ich dir!
Danke
-
Danke für die Info.
Ein „State cleanup“ erfordert dann ein erneutes anlernen aller Geräte?
Und wie würde man ein „state cleanup“ machen müssen? Den coordinator neu flashen?
Gruss Duffy
-
@duffy sagte in Tester für Zigbee Adapter 2.0.x gesucht:
Danke für die Info.
Ein „State cleanup“ erfordert dann ein erneutes anlernen aller Geräte?
Und wie würde man ein „state cleanup“ machen müssen? Den coordinator neu flashen?
Gruss Duffy
Bevor wir so weit gehen würde ich Dich bitten der Anleitung in diesem Post zu folgen.
Zum Thema state-cleanup empfehle ich die Lektüre des 1. Posts dieses Threads. Da ist beschrieben wie man das macht, was das macht, und was weiter passiert.
Es muss nichts neu angelernt werden.
A.
-
-
@asgothian hast du hier nochmal Feedback für mich ?
Hi,
Koordinator stromlos machen hat erstmal geholfen. Die normalen Geräte scheinen sich wieder zu verbinden nur die 230V Geräte machen wohl noch Probleme.
zigbee.0 2025-04-15 13:05:07.531 info Timeout trying to configure 0x04cf8cdf3c7db935 WXCJKG13LM (starting CoM). zigbee.0 2025-04-15 13:04:42.140 info Timeout trying to configure 0x00158d0004fcf82a HS1SA (starting CoM). zigbee.0 2025-04-15 13:04:42.125 info Handled all devices Queued for configuration. zigbee.0 2025-04-15 13:04:37.618 info Failed to ping 0x385cfbfffe89e560 ZBMINIL2 zigbee.0 2025-04-15 13:04:37.125 info Configuring 0x04cf8cdf3c7db935 WXCJKG13LM zigbee.0 2025-04-15 13:04:37.125 info DeviceConfigureQueue configuring 0x04cf8cdf3c7db935 lumi.remote.b686opcn01 zigbee.0 2025-04-15 13:04:32.333 info Failed to ping 0x04cd15fffe02d085 TS0121 zigbee.0 2025-04-15 13:04:32.244 info Failed to ping 0x04cd15fffe02dd9b TS0121 zigbee.0 2025-04-15 13:04:32.125 info Configuring 0x00158d0004fcf82a HS1SA zigbee.0 2025-04-15 13:04:32.124 info DeviceConfigureQueue configuring 0x00158d0004fcf82a SmokeSensor-N-3.0 zigbee.0 2025-04-15 13:04:31.954 info Failed to ping 0x04cd15fffe067cd7 TS0121 zigbee.0 2025-04-15 13:04:30.962 info Failed to ping 0x842e14fffe35a210 TS0121 zigbee.0 2025-04-15 13:04:30.256 info Failed to ping 0x588e81fffedbcfe2 TS0121 zigbee.0 2025-04-15 13:04:29.853 info Failed to ping 0x842e14fffe1262bf TS0121 zigbee.0 2025-04-15 13:04:29.527 info Failed to ping 0x04cd15fffe02d9f3 TS0121 zigbee.0 2025-04-15 13:04:28.810 info Failed to ping 0x385cfbfffe8eb302 ZBMINIL2 zigbee.0 2025-04-15 13:04:28.549 info Failed to ping 0x14b457fffe2ea155 TRADFRI bulb E27 WW 806lm zigbee.0 2025-04-15 13:04:27.391 info debug devices set to [] zigbee.0 2025-04-15 13:04:27.128 info DeviceConfigure 0x04cf8cdf3c7db935 WXCJKG13LM needed - Device added to Configuration Queue zigbee.0 2025-04-15 13:04:27.122 info DeviceConfigure 0x00158d0004fcf82a HS1SA needed - Device added to Configuration Queue zigbee.0 2025-04-15 13:04:27.027 info Zigbee started zigbee.0 2025-04-15 13:04:27.023 info Currently 70 devices are joined: zigbee.0 2025-04-15 13:04:26.531 info 0x00158d0004b487d4 (addr 62422): HS1SA - HEIMAN Smoke detector (EndDevice) zigbee.0 2025-04-15 13:04:26.498 info 0x00158d00033ad77d (addr 20078): RTCGQ11LM - Aqara Motion sensor (EndDevice) zigbee.0 2025-04-15 13:04:26.348 info Unable to disable LED, unsupported function. zigbee.0 2025-04-15 13:04:26.345 info Zigbee-Herdsman started successfully with Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20200805}} zigbee.0 2025-04-15 13:04:22.855 info Starting Zigbee-Herdsman zigbee.0 2025-04-15 13:04:22.853 info Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1) zigbee.0 2025-04-15 13:04:22.771 info Starting Adapter npm ... zigbee.0 2025-04-15 13:04:22.768 info --- creating device debug --- zigbee.0 2025-04-15 13:04:22.761 info delete old Backup files. keep only last 10 zigbee.0 2025-04-15 13:04:22.741 info --> transmitPower : normal zigbee.0 2025-04-15 13:04:22.728 info init localConfig zigbee.0 2025-04-15 13:04:22.691 info starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.1, js-controller: 7.0.6Bezüglich der PanID, da weiß ich nicht ob ich da mal was geändert habe.
Ich hab von @1.10.14 to @2.0.5 aktualisiert -
@martinschm 'die' ist gut. 6 von 70 geräten. Gib denen Zeit.
A.
-
Gibt es keine Idee was ich tun / ausprobieren soll?
-
Seit dem Update wird die Temperatur, wenn diese direkt am Eurotronic Thermostat verändert wird, in keinem Objekt aktualisiert.
-
@heko bist du sicher das der Datenpunkt für die Temperatur noch aktiv ist (nicht orange im Objektbaum) ?
-
@asgothian ja - es kommen auch keine anderen Zustände zurück (Battery percent, valve_positiom, etc)
Senden ans Gerät funktioniert bei allen Objekten.
Am Geräte sind 20,0 Grad eingestellt.
-
@heko Ich hab 3 von diesen TRVs (mit Zigbee 3.0.0) problemlos am laufen.
Allerdings haben meine Ventile eine neuere Firmware.
-
@heko bitte das Gerät von der Kachel,aus neu konfigurieren.
A.
