Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Zigbee startet nicht mehr

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Zigbee startet nicht mehr

    This topic has been deleted. Only users with topic management privileges can see it.
    • David G.
      David G. @Thomas Braun last edited by

      @thomas-braun

      Hab sie genommen weil einige hier im Forum die Produktiv nutzen und es scheinbar keine Probleme gibt.
      Hoffe mal, mein Problem liegt nicht daran.

      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @David G. last edited by

        @david-g

        git-Versionen sind nie produktiv.

        David G. arteck 2 Replies Last reply Reply Quote 0
        • David G.
          David G. @Thomas Braun last edited by David G.

          @thomas-braun

          Okay, verstanden.
          Jedoch wäre es schön jetzt wieder auf das ursprüngliche Thema zu kommen.

          EDIT: Hab eben deinen Befehl übersehen. Teste ich grad.

          1 Reply Last reply Reply Quote 0
          • David G.
            David G. @Thomas Braun last edited by David G.

            @thomas-braun sagte in Zigbee startet nicht mehr:

            @david-g

            iobroker add zigbee 
            

            liefert?

            pi@iobroker:~ $ iobroker add zigbee
            NPM version: 6.14.15
            npm install iobroker.zigbee@1.5.6 --loglevel error --prefix "/opt/iobroker" (System call)
            Traceback (most recent call last):
              File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 47, in <module>
                import gyp
              File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>
                import gyp.input
              File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>
                import ast
            ImportError: No module named ast
            gyp ERR! configure error
            gyp ERR! stack Error: `gyp` failed with exit code: 1
            gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
            gyp ERR! stack     at ChildProcess.emit (events.js:400:28)
            gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)
            gyp ERR! System Linux 5.10.63-v7l+
            gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
            gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings
            gyp ERR! node -v v14.18.2
            gyp ERR! node-gyp -v v5.1.0
            gyp ERR! not ok
            Traceback (most recent call last):
              File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 47, in <module>
                import gyp
              File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>
                import gyp.input
              File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>
                import ast
            ImportError: No module named ast
            gyp ERR! configure error
            gyp ERR! stack Error: `gyp` failed with exit code: 1
            gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
            gyp ERR! stack     at ChildProcess.emit (events.js:400:28)
            gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)
            gyp ERR! System Linux 5.10.63-v7l+
            gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
            gyp ERR! cwd /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
            gyp ERR! node -v v14.18.2
            gyp ERR! node-gyp -v v5.1.0
            gyp ERR! not ok
            npm ERR! code ELIFECYCLE
            npm ERR! errno 1
            npm ERR! @serialport/bindings@9.0.4 install: `prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild`
            npm ERR! Exit status 1
            npm ERR!
            npm ERR! Failed at the @serialport/bindings@9.0.4 install script.
            npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
            
            npm ERR! A complete log of this run can be found in:
            npm ERR!     /home/iobroker/.npm/_logs/2021-12-01T20_54_28_658Z-debug.log
            host.iobroker Cannot install iobroker.zigbee@1.5.6: 1
            pi@iobroker:~ $
            

            Anbei das erwähnte log aus Zeile 51.
            2021-12-01T20_54_28_658Z-debug.log

            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @David G. last edited by

              @david-g
              Mach den Cache mal leer:

              cd /opt/iobroker
              npm cache clean --force
              
              David G. 1 Reply Last reply Reply Quote 0
              • David G.
                David G. @Thomas Braun last edited by David G.

                @thomas-braun

                Leider nichts

                pi@iobroker:~ $ cd /opt/iobroker
                pi@iobroker:/opt/iobroker $ npm cache clean --force      npm WARN using --force I sure hope you know what you are doing.
                pi@iobroker:/opt/iobroker $ iobroker add zigbee
                NPM version: 6.14.15
                npm install iobroker.zigbee@1.5.6 --loglevel error --prefix "/opt/iobroker" (System call)
                Traceback (most recent call last):
                  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 47, in <module>
                    import gyp
                  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>
                    import gyp.input
                  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>
                    import ast
                ImportError: No module named ast
                gyp ERR! configure error
                gyp ERR! stack Error: `gyp` failed with exit code: 1
                gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
                gyp ERR! stack     at ChildProcess.emit (events.js:400:28)
                gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)
                gyp ERR! System Linux 5.10.63-v7l+
                gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings
                gyp ERR! node -v v14.18.2
                gyp ERR! node-gyp -v v5.1.0
                gyp ERR! not ok
                Traceback (most recent call last):
                  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 47, in <module>
                    import gyp
                  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>
                    import gyp.input
                  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>
                    import ast
                ImportError: No module named ast
                gyp ERR! configure error
                gyp ERR! stack Error: `gyp` failed with exit code: 1
                gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
                gyp ERR! stack     at ChildProcess.emit (events.js:400:28)
                gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)
                gyp ERR! System Linux 5.10.63-v7l+
                gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                gyp ERR! cwd /opt/iobroker/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/@serialport/bindings
                gyp ERR! node -v v14.18.2
                gyp ERR! node-gyp -v v5.1.0
                gyp ERR! not ok
                npm ERR! code ELIFECYCLE
                npm ERR! errno 1
                npm ERR! @serialport/bindings@9.0.4 install: `prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild`
                npm ERR! Exit status 1
                npm ERR!
                npm ERR! Failed at the @serialport/bindings@9.0.4 install script.
                npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                
                npm ERR! A complete log of this run can be found in:
                npm ERR!     /home/iobroker/.npm/_logs/2021-12-01T21_26_11_036Z-debug.log
                host.iobroker Cannot install iobroker.zigbee@1.5.6: 1
                pi@iobroker:/opt/iobroker $
                

                Auch ein

                npm rebuild
                

                hat nichts gebracht.

                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @David G. last edited by

                  @david-g

                  cd /opt/iobroker
                  npm ls
                  
                  David G. 1 Reply Last reply Reply Quote 0
                  • David G.
                    David G. @Thomas Braun last edited by

                    @thomas-braun

                    Sprengt leider, was ich hier posten darf.
                    Hab es als txt angegangen.

                    npm ls.txt

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @David G. last edited by

                      @david-g

                      Da stimmt was mit irgendeinem vis-Zeug nicht.
                      Mir fällt aber nix mehr dazu ein. Außer ZigBee komplett rauswerfen und nach einem Neustart noch mal ins System ziehen.

                      David G. 1 Reply Last reply Reply Quote 0
                      • David G.
                        David G. @Thomas Braun last edited by David G.

                        @thomas-braun

                        Okay,

                        danke für deine Unterstützung.
                        Zigbee hatte ich schonmal komplett runter geworfen (Instanz gelöscht und Adapter über den Papierkorb gelöscht).

                        Ggf werde ich am Wochenende das System neu aufsetzen.
                        Mal sehen, ob ich sql und nut wieder konfiguriert bekomme. Da hatte ich was Probleme mit 😅

                        EDIT:
                        Das System läuft jetzt wieder.
                        Mache ca alle 3 Monate ein Image auf eine SD-Karte.
                        Hab ich zurück auf meine SSD gespielt und das Backup durchlaufen lassen.

                        Hätte den Fehler zwar gerne gefunden, auch um zu sehen woran es nun lag, jedoch war es mir jetzt wichtiger, dass das System wieder läuft.

                        1 Reply Last reply Reply Quote 0
                        • P
                          Philipp.Schlegel @arteck last edited by

                          @arteck

                          Hi, tatsächlich trifft mich dasselbe Problem. Der FI flog raus, sofortiger Shutdown, nach Neustart startet der Adapter nicht mehr vollständig. LOG sieht für mich ebenso nach fehlerhaftem Serialport aus:

                          
                          zigbee.0	2021-12-02 08:04:51.703	error	Error herdsman start
                          
                          zigbee.0	2021-12-02 08:04:51.702	error	Failed to start Zigbee
                          
                          zigbee.0	2021-12-02 08:04:51.702	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
                          
                          zigbee.0	2021-12-02 08:04:51.465	info	Installed Version: ioBroker/ioBroker.zigbee#5149bcb2392471287f6a60f855ffe690d74da714
                          
                          zigbee.0	2021-12-02 08:04:51.419	info	Starting Zigbee npm ...
                          
                          zigbee.0	2021-12-02 08:04:51.417	info	Try to reconnect. 1 attempts left
                          
                          zigbee.0	2021-12-02 08:04:41.415	error	Error herdsman start
                          
                          zigbee.0	2021-12-02 08:04:41.414	error	Failed to start Zigbee
                          
                          zigbee.0	2021-12-02 08:04:41.413	error	Starting zigbee-herdsman problem : "network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby"
                          host.RaspberryPi4IoBroker-Main
                          
                          zigbee.0	2021-12-02 08:04:25.504	info	instance system.adapter.coronavirus-statistics.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                          
                          zigbee.0	2021-12-02 08:03:36.377	info	Installed Version: ioBroker/ioBroker.zigbee#5149bcb2392471287f6a60f855ffe690d74da714
                          
                          zigbee.0	2021-12-02 08:03:35.829	info	Starting Zigbee npm ...
                          
                          zigbee.0	2021-12-02 08:03:35.664	info	starting. Version 1.6.7 in /opt/iobroker/node_modules/iobroker.zigbee, node: v14.18.2, js-controller: 3.3.21
                          
                          zigbee.0	2021-12-02 08:03:35.632	info	Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                          

                          An Deine beschriebenen Schritte des Löschens von iobroker.zigbee/serialport/@serialport/zigbee-herdsman-converters/zigbee-herdsman sowie Neuinstallation von GitHub habe ich schon versucht. Das Ergebnis ist immer analog dem Fehlerbild oben.

                          Hat noch jemand eine Idee?

                          Danke und beste Grüße!
                          Phil

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

                            @philipp-schlegel

                            same panId or extendedPanId

                            Setz die beiden Werte mal neu.

                            P 1 Reply Last reply Reply Quote 0
                            • P
                              Philipp.Schlegel @Thomas Braun last edited by

                              @thomas-braun

                              Damit komme ich zu einer noch ausgiebigeren Fehlermeldung...

                              
                              zigbee.0	2021-12-02 08:35:17.255	error	Error herdsman start
                              zigbee.0	2021-12-02 08:35:17.254	error	Failed to start Zigbee
                              zigbee.0	2021-12-02 08:35:17.253	error	Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
                              zigbee.0	2021-12-02 08:35:17.084	info	Installed Version: ioBroker/ioBroker.zigbee#5149bcb2392471287f6a60f855ffe690d74da714
                              zigbee.0	2021-12-02 08:35:17.063	info	Starting Zigbee npm ...
                              zigbee.0	2021-12-02 08:35:17.062	info	Try to reconnect. 1 attempts left
                              zigbee.0	2021-12-02 08:35:07.060	error	Error herdsman start
                              zigbee.0	2021-12-02 08:35:07.060	error	Failed to start Zigbee
                              zigbee.0	2021-12-02 08:35:07.059	error	Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
                              zigbee.0	2021-12-02 08:35:07.057	error	Re-commissioning your network will require re-pairing of all devices!
                              zigbee.0	2021-12-02 08:35:07.056	error	If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
                              zigbee.0	2021-12-02 08:35:07.056	error	Please update configuration to prevent further issues.
                              zigbee.0	2021-12-02 08:35:07.055	error	- Channel List: configured=11, adapter=11
                              zigbee.0	2021-12-02 08:35:07.054	error	- Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
                              zigbee.0	2021-12-02 08:35:07.053	error	- Extended PAN ID: configured=adcaccbdcdddddda, adapter=00124b00219fb99b
                              zigbee.0	2021-12-02 08:35:07.052	error	- PAN ID: configured=601, adapter=601
                              zigbee.0	2021-12-02 08:35:07.051	error	Configuration is not consistent with adapter state/backup!
                              
                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Philipp.Schlegel last edited by

                                @philipp-schlegel

                                Extended PAN ID: configured=adcaccbdcdddddda, adapter=00124b00219fb99b
                                

                                Das muss übereinstimmen.
                                Und ich würde den Adapter nicht als git-Version betreiben.

                                P 1 Reply Last reply Reply Quote 1
                                • arteck
                                  arteck Developer Most Active @Thomas Braun last edited by arteck

                                  @thomas-braun sagte in Zigbee startet nicht mehr:

                                  git-Versionen sind nie produktiv.

                                  @thomas-braun sagte in Zigbee startet nicht mehr:

                                  Und ich würde den Adapter nicht als git-Version betreiben.

                                  wobei bei Zigbee ist es bissel anders..
                                  da sind die release Zeiten bissel anders

                                  wir sehen zu dass es immer funktioniert..

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    Philipp.Schlegel @Thomas Braun last edited by

                                    @thomas-braun TOP! Tausend Dank. Daran hing es tatsächlich.

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

                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate

                                    953
                                    Online

                                    31.9k
                                    Users

                                    80.1k
                                    Topics

                                    1.3m
                                    Posts

                                    5
                                    32
                                    1254
                                    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