Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst] Zigbee Adapter nach Update "defekt"

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    [gelöst] Zigbee Adapter nach Update "defekt"

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

      @asgothian

      Hallo!

      Ich habe mir einen Sonoff Zigbee 3.0 USB Dongle Plus besorgt und nun geht alles. War zwar mühselig alles neu zu koppeln, aber so ist es eben 😉

      Vielen Dank für eure Hilfe!

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

        @spectrum1981 sagte in [gelöst] Zigbee Adapter nach Update "defekt":

        i@ioBroker-RasPi4:~ $ npm install iobroker.zigbee@1.5.6 --production

        Du stehst im falschen Verzeichnis.
        Mit npm hantiert man im Installationsverzeichnis, beim ioBroker in /opt/iobroker

        Besser die iobroker-Kommandos verwenden, die laufen im richtigen Verzeichnis ab.

        S 1 Reply Last reply Reply Quote 0
        • S
          SigiMOE @Thomas Braun last edited by SigiMOE

          Brauche mal euren Rat:

          Habe einen neuen Sonoff Zigbee 3.0 USB Dongle Plus in meinen Raspi 4 reingesteckt ( inkl. USB Verlängerung )

          Leider wird die Instanz nur teilweise "grün"

          fce5184e-8543-4011-a1f7-dc831a502cae-2022-02-12_12-46-24.jpg

          Hier noch ein paar Infos zu meinem System :
          b1bea71b-334f-4b51-be85-584f917c1e0b-2022-02-12_12-48-53.jpg

          Kann mir jemand ein paar Tipps geben ( Anfängerfreundlich ) 😉

          Hier mal ein Auszug aus dem LOG :

          2022-02-12 12:42:18.342 - info: host.raspi4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
2022-02-12 12:42:18.348 - info: zigbee.0 (5967) Got terminate signal TERMINATE_YOURSELF
2022-02-12 12:42:18.350 - info: zigbee.0 (5967) cleaned everything up...
2022-02-12 12:42:18.354 - info: zigbee.0 (5967) Zigbee: disabling joining new devices.
2022-02-12 12:42:18.360 - warn: zigbee.0 (5967) Failed to stop zigbee during startup
2022-02-12 12:42:18.361 - info: zigbee.0 (5967) terminating
2022-02-12 12:42:18.362 - info: zigbee.0 (5967) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-02-12 12:42:18.387 - info: host.raspi4 stopInstance system.adapter.zigbee.0 send kill signal
2022-02-12 12:42:19.078 - info: host.raspi4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-02-12 12:42:21.413 - info: host.raspi4 instance system.adapter.zigbee.0 started with pid 7679
2022-02-12 12:42:24.018 - info: plenticore.0 (26886) State value to set for "plenticore.0.scb.export.LastExportOk" has to be type "boolean" but received type "number"
2022-02-12 12:42:25.087 - info: zigbee.0 (7679) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-02-12 12:42:25.324 - info: zigbee.0 (7679) starting. Version 1.6.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.16.3, js-controller: 4.0.8
2022-02-12 12:42:25.428 - info: zigbee.0 (7679) Starting Zigbee npm ...
2022-02-12 12:42:25.965 - info: zigbee.0 (7679) Installed Version: iobroker.zigbee@1.6.14
2022-02-12 12:42:26.184 - error: zigbee.0 (7679) Configuration is not consistent with adapter state/backup!
2022-02-12 12:42:26.185 - error: zigbee.0 (7679) - PAN ID: configured=6552, adapter=6553
2022-02-12 12:42:26.185 - error: zigbee.0 (7679) - Extended PAN ID: configured=00124b0024cae2bc, adapter=00124b0024cae2bc
2022-02-12 12:42:26.186 - error: zigbee.0 (7679) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
2022-02-12 12:42:26.186 - error: zigbee.0 (7679) - Channel List: configured=11, adapter=11
2022-02-12 12:42:26.187 - error: zigbee.0 (7679) Please update configuration to prevent further issues.
2022-02-12 12:42:26.187 - error: zigbee.0 (7679) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
2022-02-12 12:42:26.188 - error: zigbee.0 (7679) Re-commissioning your network will require re-pairing of all devices!
2022-02-12 12:42:26.189 - error: zigbee.0 (7679) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2022-02-12 12:42:26.189 - error: zigbee.0 (7679) Failed to start Zigbee
2022-02-12 12:42:26.190 - error: zigbee.0 (7679) Error herdsman start
2022-02-12 12:42:27.754 - warn: octoprint.1 (27757) You should update your OctoPrint installation - supported version of this adapter is 1.7.2 (or later). Your current version is 1.7.0
2022-02-12 12:42:36.192 - info: zigbee.0 (7679) Try to reconnect. 1 attempts left
2022-02-12 12:42:36.193 - info: zigbee.0 (7679) Starting Zigbee npm ...
2022-02-12 12:42:36.214 - info: zigbee.0 (7679) Installed Version: iobroker.zigbee@1.6.14
2022-02-12 12:42:36.380 - error: zigbee.0 (7679) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
2022-02-12 12:42:36.381 - error: zigbee.0 (7679) Failed to start Zigbee
2022-02-12 12:42:36.381 - error: zigbee.0 (7679) Error herdsman start
          Thomas Braun 1 Reply Last reply Reply Quote 0
          • J
            jaridian last edited by

            PAN ID: configured=6552, adapter=6553

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

              @sigimoe sagte in [gelöst] Zigbee Adapter nach Update "defekt":

              PAN ID: configured=6552, adapter=6553

              Im Adapter übereinstimmend einstellen. Und dein System auf Stand halten. Updates der Adapter und von nodeJS dringend empfohlen.

              S 1 Reply Last reply Reply Quote 0
              • S
                SigiMOE @Thomas Braun last edited by

                @thomas-braun

                gerade alle Adapter, Host auf den neuen Stand gebracht leider kein Erfolg
                immer noch gleiche Fehler

                Hier das LOG. Was kann ich noch prüfen ?

                2022-02-12 18:02:05.973 - info: zigbee.0 (12653) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-02-12 18:02:06.290 - info: zigbee.0 (12653) starting. Version 1.6.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.0, js-controller: 4.0.8
2022-02-12 18:02:06.417 - info: zigbee.0 (12653) Starting Zigbee npm ...
2022-02-12 18:02:06.936 - info: zigbee.0 (12653) Installed Version: iobroker.zigbee@1.6.14
2022-02-12 18:02:07.409 - info: zigbee.0 (12653) Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}}
2022-02-12 18:02:07.420 - info: zigbee.0 (12653) Unable to disable LED, unsupported function.
2022-02-12 18:02:07.421 - info: zigbee.0 (12653) --> transmitPower : normal
2022-02-12 18:02:07.430 - info: zigbee.0 (12653) Currently no devices.
2022-02-12 18:02:07.431 - info: zigbee.0 (12653) Zigbee started
2022-02-12 18:02:07.435 - error: zigbee.0 (12653) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms
2022-02-12 18:02:07.512 - info: host.raspi4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
2022-02-12 18:02:07.517 - warn: zigbee.0 (12653) State "zigbee.0.info.undefinedDevices" has no existing object, this might lead to an error in future versions
2022-02-12 18:02:07.526 - info: zigbee.0 (12653) Got terminate signal TERMINATE_YOURSELF
2022-02-12 18:02:07.529 - info: zigbee.0 (12653) cleaned everything up...
2022-02-12 18:02:07.532 - info: zigbee.0 (12653) Zigbee: disabling joining new devices.
2022-02-12 18:02:07.592 - info: host.raspi4 stopInstance system.adapter.zigbee.0 send kill signal
2022-02-12 18:02:08.030 - info: zigbee.0 (12653) terminating
2022-02-12 18:02:08.033 - info: zigbee.0 (12653) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-02-12 18:02:08.667 - info: host.raspi4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-02-12 18:02:10.635 - info: host.raspi4 instance system.adapter.zigbee.0 started with pid 12829
2022-02-12 18:02:14.620 - info: zigbee.0 (12829) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-02-12 18:02:14.890 - info: zigbee.0 (12829) starting. Version 1.6.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.0, js-controller: 4.0.8
2022-02-12 18:02:14.999 - info: zigbee.0 (12829) Starting Zigbee npm ...
2022-02-12 18:02:15.514 - info: zigbee.0 (12829) Installed Version: iobroker.zigbee@1.6.14
2022-02-12 18:02:15.720 - error: zigbee.0 (12829) Configuration is not consistent with adapter state/backup!
2022-02-12 18:02:15.721 - error: zigbee.0 (12829) - PAN ID: configured=6553, adapter=6553
2022-02-12 18:02:15.722 - error: zigbee.0 (12829) - Extended PAN ID: configured=dd2dc1dddddb4da3, adapter=00124b0024cae2bc
2022-02-12 18:02:15.723 - error: zigbee.0 (12829) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
2022-02-12 18:02:15.723 - error: zigbee.0 (12829) - Channel List: configured=11, adapter=11
2022-02-12 18:02:15.724 - error: zigbee.0 (12829) Please update configuration to prevent further issues.
2022-02-12 18:02:15.724 - error: zigbee.0 (12829) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
2022-02-12 18:02:15.725 - error: zigbee.0 (12829) Re-commissioning your network will require re-pairing of all devices!
2022-02-12 18:02:15.726 - error: zigbee.0 (12829) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2022-02-12 18:02:15.727 - error: zigbee.0 (12829) Failed to start Zigbee
2022-02-12 18:02:15.728 - error: zigbee.0 (12829) Error herdsman start
2022-02-12 18:02:18.105 - warn: octoprint.1 (5345) You should update your OctoPrint installation - supported version of this adapter is 1.7.2 (or later). Your current version is 1.7.0
2022-02-12 18:02:22.791 - error: iot.0 (5453) [GHOME] device hm-rpc.1.NEQ0510324.2.STATE is unknown to google home
2022-02-12 18:02:23.636 - info: plenticore.0 (4434) State value to set for "plenticore.0.scb.export.LastExportOk" has to be type "boolean" but received type "number"
2022-02-12 18:02:25.729 - info: zigbee.0 (12829) Try to reconnect. 1 attempts left
2022-02-12 18:02:25.730 - info: zigbee.0 (12829) Starting Zigbee npm ...
2022-02-12 18:02:25.753 - info: zigbee.0 (12829) Installed Version: iobroker.zigbee@1.6.14
2022-02-12 18:02:25.978 - error: zigbee.0 (12829) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
2022-02-12 18:02:25.979 - error: zigbee.0 (12829) Failed to start Zigbee
2022-02-12 18:02:25.980 - error: zigbee.0 (12829) Error herdsman start
2022-02-12 18:02:44.188 - info: plenticore.0 (4434) State value to set for "plenticore.0.scb.export.LastExportOk" has to be type "boolean" but received type "number"
2022-02-12 18:02:48.063 - warn: octoprint.1 (5345) You should update your OctoPrint installation - supported version of this adapter is 1.7.2 (or later). Your current version is 1.7.0
2022-02-12 18:02:50.040 - info: host.raspi4 stopInstance system.adapter.zigbee.0 (force=false, process=true)
2022-02-12 18:02:50.051 - info: zigbee.0 (12829) Got terminate signal TERMINATE_YOURSELF
2022-02-12 18:02:50.089 - info: host.raspi4 stopInstance system.adapter.zigbee.0 send kill signal
2022-02-12 18:02:50.064 - info: zigbee.0 (12829) cleaned everything up...
2022-02-12 18:02:50.082 - info: zigbee.0 (12829) Zigbee: disabling joining new devices.
2022-02-12 18:02:50.100 - warn: zigbee.0 (12829) Failed to stop zigbee during startup
2022-02-12 18:02:50.102 - info: zigbee.0 (12829) terminating
2022-02-12 18:02:50.105 - info: zigbee.0 (12829) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2022-02-12 18:02:50.757 - info: host.raspi4 instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2022-02-12 18:02:53.129 - info: host.raspi4 instance system.adapter.zigbee.0 started with pid 13616
2022-02-12 18:02:58.159 - info: zigbee.0 (13616) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
2022-02-12 18:02:58.645 - info: zigbee.0 (13616) starting. Version 1.6.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.0, js-controller: 4.0.8
2022-02-12 18:02:58.799 - info: zigbee.0 (13616) Starting Zigbee npm ...
2022-02-12 18:02:59.344 - info: zigbee.0 (13616) Installed Version: iobroker.zigbee@1.6.14
2022-02-12 18:02:59.557 - error: zigbee.0 (13616) Configuration is not consistent with adapter state/backup!
2022-02-12 18:02:59.558 - error: zigbee.0 (13616) - PAN ID: configured=6553, adapter=6553
2022-02-12 18:02:59.559 - error: zigbee.0 (13616) - Extended PAN ID: configured=dd2dc1dddddb4da3, adapter=00124b0024cae2bc
2022-02-12 18:02:59.559 - error: zigbee.0 (13616) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
2022-02-12 18:02:59.560 - error: zigbee.0 (13616) - Channel List: configured=11, adapter=11
2022-02-12 18:02:59.561 - error: zigbee.0 (13616) Please update configuration to prevent further issues.
2022-02-12 18:02:59.561 - error: zigbee.0 (13616) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
2022-02-12 18:02:59.561 - error: zigbee.0 (13616) Re-commissioning your network will require re-pairing of all devices!
2022-02-12 18:02:59.563 - error: zigbee.0 (13616) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2022-02-12 18:02:59.563 - error: zigbee.0 (13616) Failed to start Zigbee
2022-02-12 18:02:59.564 - error: zigbee.0 (13616) Error herdsman start
2022-02-12 18:03:04.758 - info: plenticore.0 (4434) State value to set for "plenticore.0.scb.export.LastExportOk" has to be type "boolean" but received type "number"
2022-02-12 18:03:09.566 - info: zigbee.0 (13616) Try to reconnect. 1 attempts left
2022-02-12 18:03:09.567 - info: zigbee.0 (13616) Starting Zigbee npm ...
2022-02-12 18:03:09.589 - info: zigbee.0 (13616) Installed Version: iobroker.zigbee@1.6.14
2022-02-12 18:03:09.781 - error: zigbee.0 (13616) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
2022-02-12 18:03:09.782 - error: zigbee.0 (13616) Failed to start Zigbee
2022-02-12 18:03:09.783 - error: zigbee.0 (13616) Error herdsman start
                Thomas Braun amg_666 2 Replies Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @SigiMOE last edited by Thomas Braun

                  @sigimoe sagte in [gelöst] Zigbee Adapter nach Update "defekt":

                  Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms

                  Riecht nach Issues mit der Firmware. Flash die vielleicht mal neu.

                  Extended PAN ID: configured=dd2dc1dddddb4da3, adapter=00124b0024cae2bc

                  Muss übereinstimmen.

                  S 1 Reply Last reply Reply Quote 0
                  • amg_666
                    amg_666 @SigiMOE last edited by

                    @sigimoe sagte in [gelöst] Zigbee Adapter nach Update "defekt":

                    2022-02-12 18:02:59.557 - error: zigbee.0 (13616) Configuration is not consistent with adapter state/backup!

                    du hast die pan id geändert und er meckert jetzt rum dass die neue Konfiguration nicht mit seinem backup übereinstimmt und dass du ggf alle Geräte neu pairen musst. und wenn du das willst (bzw wohl machen musst), dann sollst du das backup des zigbee coordinators erst löschen, siehe Zeile 67 in deinem geposteten log.

                    please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.

                    halte den Adapter an, gehe in der Konsole in das Verzeichnis und benenne die nvbackup.json um zum Beispiel nvbackup.json.alt (direkt löschen würd ich sie erstmal nicht) und dann neustart des Adapters

                    1 Reply Last reply Reply Quote 0
                    • S
                      SigiMOE last edited by

                      @amg_666

                      Kannst Du mir die Befehle reinkopieren wie ich das machen muss ?

                      1 Reply Last reply Reply Quote 0
                      • S
                        SigiMOE @Thomas Braun last edited by

                        @thomas-braun sagte in [gelöst] Zigbee Adapter nach Update "defekt":

                        @sigimoe sagte in [gelöst] Zigbee Adapter nach Update "defekt":

                        Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms

                        Riecht nach Issues mit der Firmware. Flash die vielleicht mal neu.

                        Extended PAN ID: configured=dd2dc1dddddb4da3, adapter=00124b0024cae2bc

                        Muss übereinstimmen.

                        Von dem Stick die Firmware neu Flashen ? Habe den Stick heute Original ausgepackt. Wie gehe ich da vor ?

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

                          @sigimoe

                          Bevor du die Firmware flashst, erstmal die Einstellungen übereinander bringen.

                          Die aktuelle Firmware wäre jedenfalls 20211217

                          S 1 Reply Last reply Reply Quote 0
                          • S
                            SigiMOE @Thomas Braun last edited by SigiMOE

                            @thomas-braun sagte in [gelöst] Zigbee Adapter nach Update "defekt":

                            @sigimoe

                            Bevor du die Firmware flashst, erstmal die Einstellungen übereinander

                            Habe nun die PAN ID übereinstimmend in den Einstellungen geändert
                            Jetzt scheint es zu laufen :

                            3815b4a3-c270-4f13-b2ca-563df8e182ea-2022-02-13_08-01-38.jpg

                            Was bedeutet diese WARNUNG ? Bzw. Was muss ich tun ?

                            	2022-02-13 08:04:43.529	warn	Extended PAN ID is reversed (expected=bce2ca24004b1200, actual=00124b0024cae2bc)
                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @SigiMOE last edited by

                              @sigimoe
                              Die ID nochmal eintragen, diesmal in umgekehrter Reihenfolge.

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                SigiMOE @Thomas Braun last edited by

                                @thomas-braun
                                Perfekt , vielen lieben Dank für die Geduld

                                Jetzt sieht es super aus oder ?

                                hier mal der LOG nach Neustart des Adapters :

                                zigbee.0
2022-02-13 11:31:53.814	info	Zigbee started

zigbee.0
2022-02-13 11:31:53.813	info	Currently no devices.

zigbee.0
2022-02-13 11:31:53.804	info	--> transmitPower : normal

zigbee.0
2022-02-13 11:31:53.803	info	Unable to disable LED, unsupported function.

zigbee.0
2022-02-13 11:31:53.792	info	Coordinator firmware version: {"type":"zStack3x0","meta":{"transportrev":2,"product":1,"majorrel":2,"minorrel":7,"maintrel":1,"revision":20210708}}

zigbee.0
2022-02-13 11:31:53.312	info	Installed Version: iobroker.zigbee@1.6.14

zigbee.0
2022-02-13 11:31:52.788	info	Starting Zigbee npm ...

zigbee.0
2022-02-13 11:31:52.679	info	starting. Version 1.6.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.19.0, js-controller: 4.0.8

zigbee.0
2022-02-13 11:31:52.344	info	Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system

zigbee.0
2022-02-13 11:31:44.937	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

zigbee.0
2022-02-13 11:31:44.934	info	terminating

zigbee.0
2022-02-13 11:31:44.437	info	Zigbee: disabling joining new devices.

zigbee.0
2022-02-13 11:31:44.433	info	cleaned everything up...

zigbee.0
2022-02-13 11:31:44.430	info	Got terminate signal TERMINATE_YOURSELF
                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post

                                Support us

                                ioBroker
                                Community Adapters
                                Donate
                                FAQ Cloud / IOT
                                HowTo: Node.js-Update
                                HowTo: Backup/Restore
                                Downloads
                                BLOG

                                560
                                Online

                                32.0k
                                Users

                                80.4k
                                Topics

                                1.3m
                                Posts

                                6
                                28
                                2461
                                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