Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Tester für Zigbee Adapter 2.0.x gesucht

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Tester für Zigbee Adapter 2.0.x gesucht

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Schranzer @Asgothian last edited by

      @asgothian
      Zur ersten Frage, das ist die Ausgabe, wenn ich auf Test Port drücke:

      attempting dns lookup for 192.168.188.123
      dns lookup for tcp://192.168.188.123:6638 produced 192.168.188.123
      connected successfully to connect to 192.168.188.123 port 6638
      

      Zur zweiten Frage, das ist die Ausgabe, wenn ich auf Start/Stop drücke:

      overriding zigbee options with:
      extPanID : b574a814e360b356
      panID : 820
      channel : 11
      port : tcp://192.168.188.123:6638
      adapterType : zstack
      baudRate : 115200
      precfgkey : 01030507090B0D0F00020406080A0C0D
      flowCTRL : false
      Starting Adapter npm ...
      Installed Version: ioBroker/ioBroker.zigbee (Converters 23.25.0 Herdsman 3.5.1)
      Starting zigbee-herdsman...
      Unable to obtain herdsman settings
      Starting zigbee-herdsman problem : Error while opening socket
      Error herdsman start
      

      Viele Grüße

      Asgothian 1 Reply Last reply Reply Quote 0
      • Asgothian
        Asgothian Developer @Schranzer last edited by

        @schranzer die zigbee Firmware läuft auf deinem Netzwerk Koordinator nicht. Bitte hart zurücksetzen (Strom ab 30 sek. Warten, Strom an und neu versuchen das zigbee subsystem zu starten.

        A.

        S 1 Reply Last reply Reply Quote 0
        • S
          Schranzer @Asgothian last edited by Schranzer

          @asgothian Ich habe das Problem gelöst.
          Lösungsweg:

          • Ich habe den SMLIGHT SLZB-06p10 komplett neu aufgesetzt, mit der aller neuesten Dev-Version v2.8.2.dev3 (Diese hat deutlich mehr Einstellung Funktionen als die alte)
          • Typ: Für den SMLIGHT SLZB-06p10 "Ti" einstellen bei Hardware
          • PanID: 13410
          • Channel: 11
          • COM Anschluss: tcp://EIGENEIP:6638
          • start Zigbee network automatically Hacken aktiv
          • flow control Hacken aktiv (bin mir nicht sicher was es macht)

          Ich habe zuerst den SMLIGHT SLZB-06p10 aufgesetzt das er bereit ist und DANN den Zigbee Adapter eingeschalten (welcher schon fertig konfiguriert war).

          Und noch mal danke für deine Hilfe :)!

          c91c6f8c-6376-4856-9239-572ce2979cb5-image.png

          Asgothian 1 Reply Last reply Reply Quote 0
          • Asgothian
            Asgothian Developer @Schranzer last edited by

            @schranzer sagte in Tester für Zigbee Adapter 2.0.x gesucht:

            flow control Hacken aktiv (bin mir nicht sicher was es macht)

            In deinem Fall: Nichts. Dieser Haken ist nur bei USB Kommunikation notwendig.

            A.

            1 Reply Last reply Reply Quote 0
            • M
              martinschm last edited by martinschm

              Hi,
              ich hab die Tage auf Zigbee 2 upgedatet.
              Heute kam erst die Meldung das einige Geräte offline sind, komischerweise alles Geräte mit 230V

              Und jetzt bekam ich im Adapter erst eine Fehlermeldung als ich das pairing aktivieren wollte und dann das der Adapter ständig abstürzt.

              Im Log steht das hier

              zigbee.0
              2025-04-14 18:52:47.993	info	terminating
              
              zigbee.0
              2025-04-14 18:52:47.953	error	Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin') at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/dist/controller/controller.js:259:35) at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33) at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
              
              zigbee.0
              2025-04-14 18:52:47.383	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
              
              zigbee.0
              2025-04-14 18:52:47.381	info	terminating
              
              zigbee.0
              2025-04-14 18:52:47.380	info	Saved local configuration data
              
              zigbee.0
              2025-04-14 18:52:47.378	info	local config saved
              
              zigbee.0
              2025-04-14 18:52:47.376	info	cleaned everything up...
              
              zigbee.0
              2025-04-14 18:52:47.373	error	undefined
              
              zigbee.0
              2025-04-14 18:52:47.372	error	unhandled promise rejection: undefined
              
              zigbee.0
              2025-04-14 18:52:47.372	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              
              zigbee.0
              2025-04-14 18:52:47.369	error	Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)
              
              zigbee.0
              2025-04-14 18:52:47.321	info	Unable to obtain herdsman settings
              
              zigbee.0
              2025-04-14 18:52:20.699	info	Starting Zigbee-Herdsman
              
              zigbee.0
              2025-04-14 18:52:20.696	info	Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.1)
              
              zigbee.0
              2025-04-14 18:52:20.642	info	Starting Adapter npm ...
              
              zigbee.0
              2025-04-14 18:52:20.640	info	--- creating device debug ---
              
              zigbee.0
              2025-04-14 18:52:20.635	info	delete old Backup files. keep only last 10
              
              zigbee.0
              2025-04-14 18:52:20.616	info	--> transmitPower : normal
              
              zigbee.0
              2025-04-14 18:52:20.604	info	init localConfig
              
              zigbee.0
              2025-04-14 18:52:20.565	info	starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.1, js-controller: 7.0.6
              
              host.smarthome
              2025-04-14 18:52:15.676	info	instance system.adapter.zigbee.0 in version "2.0.5" started with pid 2760598
              
              device-watcher.0
              2025-04-14 18:52:04.279	info	Instanz-Wachdog:zigbee.0: Instanz deaktiviert
              
              host.smarthome
              2025-04-14 18:51:44.252	info	Restart adapter system.adapter.zigbee.0 because enabled
              
              host.smarthome
              2025-04-14 18:51:44.251	error	instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
              
              zigbee.0
              2025-04-14 18:51:43.649	error	unhandled promise rejection: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:633:26) at Socket.emit (node:events:518:28) at TCP.<anonymous> (node:net:343:12)
              
              zigbee.0
              2025-04-14 18:51:43.649	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
              
              zigbee.0
              2025-04-14 18:51:43.649	error	Error: DB closed
              
              zigbee.0
              2025-04-14 18:51:43.649	error	DB closed
              

              Bei mir läuft
              js-controller 7.0.6
              zigbee 2.0.5
              Node.js: v20.18.1(20.19.0)
              NPM: 10.8.2

              10cc0f6a-6156-4a53-bd8f-b8f408d6f234-image.png

              Asgothian 1 Reply Last reply Reply Quote 0
              • Asgothian
                Asgothian Developer @martinschm last edited by Asgothian

                @martinschm sagte in Tester für Zigbee Adapter 2.0.x gesucht:

                Starting zigbee-herdsman problem : Failed to connect to the adapter (Error: SRSP - SYS - ping after 6000ms)

                Du darfst davon ausgehen das der Adapter insgesamt nicht sauber gestartet wurde. Das sieht man oft erst wenn man versucht aktiv mit dem Adapter zu interagieren.

                Die weiter oben gepostet Meldung zeigt das der Adapter keine Verbindung zur Firmware auf dem Koordinator herstellen kann. Ich würde als erstes folgendes Empfehlen:

                • Adapter anhalten - um sicher zu gehen das er nicht läuft
                • Koordinator stromlos machen. Bei USB Koordinatoren: Abziehen 30 Sekunden warten. Anstecken. Bei Netzwerk Koordinatoren: Stromversorgung kappen, 60 Sekunden warten, Stromversorgung wieder herstellen
                • Adapter starten
                • im Log schauen ob der Adapter erfolgreich gestartet wird.

                A.
                Nachtrag: Da du anscheinend DDDDDDDDDDDDDDDD als deine PanID hast kann es auch sein das der Adapter nicht startet weil die konfigurierte von der vom ZH benutzten Pan ID abweicht - ob das der Fall ist hängt davon ab von welcher Version du das Update gemacht hast.

                M 1 Reply Last reply Reply Quote 0
                • M
                  martinschm @Asgothian last edited by martinschm

                  @asgothian

                  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.6
                  

                  Bezü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

                  M 1 Reply Last reply Reply Quote 0
                  • R
                    Rene 5 @KBH10 last edited by Rene 5

                    @kbh10

                    Ich habe leider auch ein Problem mit der Version.
                    Alle meine Geräte waren nicht mehr erreichbar, dann habe ich den Adapter gelöscht und wollte ihn neu installieren.
                    Jetzt bekomme ich noch nicht mal mehr den Adapter zum laufen.

                    Meine Daten
                    Node.js: v20.19.0
                    NPM: 10.8.2
                    55745abc-91a1-4a98-929c-44e64d91a082-image.png

                    Ich hoffe ihr könnt mir helfen.

                    edit
                    bekomme den Adapter einfach nicht zum laufen
                    Bin nach deiner Anleitung vorgegangen

                    0c4eb5a9-d4a4-4ca7-ba3f-ea664c393fe4-image.png

                    Viele Grüße

                    Asgothian 1 Reply Last reply Reply Quote 0
                    • Asgothian
                      Asgothian Developer @Rene 5 last edited by

                      @rene-5 bitte genau dem folgen was ich oben im thread geschrieben hab,

                      A.

                      1 Reply Last reply Reply Quote 0
                      • F
                        FI_84 last edited by FI_84

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

                        Moin.

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

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

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

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

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

                        Danke für Eure Hilfe

                        Mfg
                        Fi

                        Asgothian 1 Reply Last reply Reply Quote 0
                        • Asgothian
                          Asgothian Developer @FI_84 last edited by

                          @fi_84 Die wichtigste Information im Log hast du zensiert oder vergessen zu kopieren. Da steht

                          zigbee.0 2025-04-15 16:20:28.648	error	Starting zigbee-herdsman problem : Error: Operation not supported, cannot set
                          

                          Nebenbei - ist es wirklich zuviel verlangt das Ihr die Logs so editiert das sie auch vernünftig lesbar sind ? Beispiel wie du open gepostet hast:

                          zigbee.0
                          2025-04-15 16:20:28.648	error	Starting zigbee-herdsman problem : Error: Operation not supported, cannot set
                           
                          zigbee.0
                          2025-04-15 16:20:28.602	info	Unable to obtain herdsman settings
                           
                          zigbee.0
                          2025-04-15 16:20:26.770	info	Starting Zigbee-Herdsman
                          

                          und Beispiel nach trivialem Edit

                          zigbee.0 2025-04-15 16:20:28.648	error	Starting zigbee-herdsman problem : Error: Operation not supported, cannot set 
                          zigbee.0 2025-04-15 16:20:28.602	info	Unable to obtain herdsman settings
                          zigbee.0 2025-04-15 16:20:26.770	info	Starting Zigbee-Herdsman
                          

                          A.

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • F
                            FI_84 last edited by

                            sorry hab es editiert.

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

                            1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Asgothian last edited by Thomas Braun

                              @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.

                              1 Reply Last reply Reply Quote 0
                              • Homoran
                                Homoran Global Moderator Administrators last edited by

                                @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.

                                Duffy F 2 Replies Last reply Reply Quote 0
                                • Duffy
                                  Duffy @Homoran last edited by Duffy

                                  Hüstel, hallo zusammen,

                                  Ich habe im Adapter 2.0.5 folgenden Hinweis gelesen, kann aber auch nach einer Übersetzung nichts damit anfangen.

                                  IMG_2570.jpeg

                                  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?

                                  Asgothian 1 Reply Last reply Reply Quote 0
                                  • Asgothian
                                    Asgothian Developer @Duffy last edited by

                                    @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/24198

                                    Letztendlich ä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.

                                    Duffy 1 Reply Last reply Reply Quote 0
                                    • F
                                      FI_84 @Homoran last edited by

                                      @homoran

                                      Hier noch mal direkt aus der Console
                                      iob logs zigbee

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

                                        @fi_84 die Zeile
                                        zigbee.0 2025-04-15 16:20:28.648 error Starting zigbee-herdsman problem : Error: Operation not supported, cannot set

                                        hast du gerade nicht mehr erwischt

                                        1 Reply Last reply Reply Quote 0
                                        • Homoran
                                          Homoran Global Moderator Administrators @FI_84 last edited by Homoran

                                          @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 set                        
                                          

                                          hier ist sie nochmal!
                                          @Asgothian
                                          wieder unvollständig
                                          ich fürchte das fehlende ist genau das Problem

                                          F 1 Reply Last reply Reply Quote 0
                                          • F
                                            FI_84 @Homoran last edited by

                                            @homoran

                                            449f25b7-3ead-4b2b-b8e4-8d7ea8a6cc8d-image.png

                                            es steht nicht mehr drin

                                            Homoran 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            908
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            zigbee 2.0.1
                                            47
                                            494
                                            55040
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo