Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Probleme mit Zigbee / Generator.next / ZStackAdapter / 2252

    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

    UNSOLVED Probleme mit Zigbee / Generator.next / ZStackAdapter / 2252

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

      @Thomas-Braun Nun ist das zwar so, wie Du es in deinem Blog-Post beschrieben hast, jetzt sind aber mein Zigbee und BLE Adapter dauerhaft auf rot. 😕

      /usr/bin/nodejs
      v12.18.4
      /usr/bin/node
      v12.18.4
      /usr/bin/npm
      6.14.6
      nodejs:
        Installed: 12.18.4-1nodesource1
        Candidate: 12.18.4-1nodesource1
        Version table:
       *** 12.18.4-1nodesource1 500
              500 https://deb.nodesource.com/node_12.x buster/main armhf Packages
              100 /var/lib/dpkg/status
           10.21.0~dfsg-1~deb10u1+rpi1 500
              500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
      
      
      2020-09-28 12:46:37.967 - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled
      2020-09-28 12:47:07.996 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 4776
      2020-09-28 12:47:08.554 - error: host.raspberrypi Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:121
      2020-09-28 12:47:08.554 - error: host.raspberrypi Caught by controller[0]: throw e;
      2020-09-28 12:47:08.554 - error: host.raspberrypi Caught by controller[0]: ^
      2020-09-28 12:47:08.554 - error: host.raspberrypi Caught by controller[0]: Error: libnode.so.64: cannot open shared object file: No such file or directory
      2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1187:18)
      2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:985:32)
      2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:878:14)
      2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:1025:19)
      2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at require (internal/modules/cjs/helpers.js:72:18)
      2020-09-28 12:47:08.555 - error: host.raspberrypi Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:112:48)
      2020-09-28 12:47:08.556 - error: host.raspberrypi Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36)
      2020-09-28 12:47:08.556 - error: host.raspberrypi Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1137:30)
      2020-09-28 12:47:08.556 - error: host.raspberrypi Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
      2020-09-28 12:47:08.556 - error: host.raspberrypi Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:985:32)
      2020-09-28 12:47:08.556 - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
      
      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @Jona last edited by

        @Jona

        iobroker stop
        iobroker fix
        iobroker start
        
        J 1 Reply Last reply Reply Quote 0
        • J
          Jona @Thomas Braun last edited by

          @Thomas-Braun Schon gemacht, keine Besserung.

          Thomas Braun 1 Reply Last reply Reply Quote 0
          • J
            Jona @Asgothian last edited by

            @Asgothian

            • Genau, ich nutze weiterhin den cc2531.

            • Ich nutze derzeit 24 Geräte über Zigbee. Auch OSRAM Steckdosen sind betroffen!

            • Wenn etwas nicht geht, sind alle betroffen (Lichtschalter, Lampen, Steckdosen, etc.)

            • Die Geräte reagieren nicht. Ich kann nachvollziehen, dass der Befehl im Objekt geändert wird.

            • Dazu (OSRAM Firmware) höre ich gerne deine Erfahrung!

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

              @Jona

              Error: libnode.so.64: cannot open shared object file: No such file or directory
              

              Das ist eine 64bit-Library. Da ist bei dir noch irgendwas anderes krumm. Denn Raspbian OS ist eigentlich 32bit.

              sudo apt remove node-*
              
              apt policy libnode64
              
              J 1 Reply Last reply Reply Quote 0
              • J
                Jona @Thomas Braun last edited by

                @Thomas-Braun Hierdurch ist leider mein gesamtes Smarthome lahm gelegt, weil Bluetooth Low Energy und Zigbee meine einzigen beiden Bindestellen nach außen sind. Hast Du eine Idee, wie ich das reparieren kann?

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

                  @Jona
                  Da scheint mir noch unnötiger Kram drauf zu sein.

                  sudo apt remove node-*
                  sudo apt remove libnode*
                  
                  J 1 Reply Last reply Reply Quote 0
                  • J
                    Jona @Thomas Braun last edited by

                    @Thomas-Braun Komischer Weise sucht er beim ersten noch nach Version 10.

                    ~ $ sudo apt remove node-*
                    Reading package lists... Done
                    Building dependency tree       
                    Reading state information... Done
                    E: Unable to locate package node-v10.16.0-linux-armv7l
                    E: Couldn't find any package by glob 'node-v10.16.0-linux-armv7l'
                    E: Couldn't find any package by regex 'node-v10.16.0-linux-armv7l'
                    
                    ~ $ sudo apt remove libnode*
                    Reading package lists... Done
                    Building dependency tree       
                    Reading state information... Done
                    Note, selecting 'libnodeletlib-dev' for glob 'libnode*'
                    Note, selecting 'libnodeletlib1d' for glob 'libnode*'
                    Note, selecting 'libnodelet-topic-tools-dev' for glob 'libnode*'
                    Note, selecting 'libnodeletlib-tools' for glob 'libnode*'
                    Note, selecting 'libnode64-dev' for glob 'libnode*'
                    Note, selecting 'libnode-dev' for glob 'libnode*'
                    Note, selecting 'libnode64' for glob 'libnode*'
                    Note, selecting 'libnodelet-dev' for glob 'libnode*'
                    Package 'libnode64-dev' is not installed, so not removed
                    Package 'libnode-dev' is not installed, so not removed
                    Package 'libnode64' is not installed, so not removed
                    Package 'libnodelet-dev' is not installed, so not removed
                    Package 'libnodelet-topic-tools-dev' is not installed, so not removed
                    Package 'libnodeletlib-dev' is not installed, so not removed
                    Package 'libnodeletlib-tools' is not installed, so not removed
                    Package 'libnodeletlib1d' is not installed, so not removed
                    The following packages were automatically installed and are no longer required:
                      gyp libc-ares2 libgfortran3 libgmime-2.6-0 libjs-inherits
                      libjs-is-typedarray libllvm8 libmicrodns0 libncurses5 libuv1 libuv1-dev
                      libva-wayland2 node-abbrev node-ajv node-ansi node-ansi-align
                      node-ansi-regex node-ansi-styles node-ansistyles node-aproba node-archy
                      node-are-we-there-yet node-asn1 node-assert-plus node-asynckit
                      node-aws-sign2 node-aws4 node-balanced-match node-bcrypt-pbkdf node-bluebird
                      node-boxen node-brace-expansion node-builtin-modules node-builtins
                      node-cacache node-call-limit node-camelcase node-caseless node-chalk
                      node-chownr node-cli-boxes node-cliui node-clone node-co node-color-convert
                      node-color-name node-combined-stream node-concat-map node-concat-stream
                      node-config-chain node-console-control-strings node-copy-concurrently
                      node-core-util-is node-cross-spawn node-cyclist node-dashdash
                      node-decamelize node-decompress-response node-deep-extend node-defaults
                      node-delayed-stream node-delegates node-detect-indent node-detect-newline
                      node-duplexer3 node-duplexify node-ecc-jsbn node-editor node-encoding
                      node-end-of-stream node-errno node-escape-string-regexp node-execa
                      node-extend node-extsprintf node-find-up node-flush-write-stream
                      node-forever-agent node-form-data node-from2 node-fs-vacuum
                      node-fs-write-stream-atomic node-fs.realpath node-gauge node-get-caller-file
                      node-get-stream node-getpass node-glob node-got node-graceful-fs
                      node-har-schema node-har-validator node-has-flag node-has-symbol-support-x
                      node-has-to-string-tag-x node-has-unicode node-hosted-git-info
                      node-http-signature node-iconv-lite node-iferr node-import-lazy
                      node-imurmurhash node-inflight node-inherits node-ini node-invert-kv
                      node-is-builtin-module node-is-npm node-is-object node-is-plain-obj
                      node-is-retry-allowed node-is-stream node-is-typedarray node-isarray
                      node-isexe node-isstream node-isurl node-jsbn node-json-parse-better-errors
                      node-json-schema node-json-stable-stringify node-json-stringify-safe
                      node-jsonify node-jsonparse node-jsonstream node-jsprim node-latest-version
                      node-lazy-property node-lcid node-libnpx node-locate-path node-lockfile
                      node-lowercase-keys node-lru-cache node-mem node-mime-types node-mimic-fn
                      node-mimic-response node-minimatch node-minimist node-mississippi
                      node-mkdirp node-move-concurrently node-mute-stream node-node-uuid node-nopt
                      node-normalize-package-data node-npm-package-arg node-npm-run-path
                      node-npmlog node-oauth-sign node-object-assign node-once node-opener
                      node-os-locale node-osenv node-p-cancelable node-p-finally node-p-limit
                      node-p-locate node-p-timeout node-package-json node-parallel-transform
                      node-path-exists node-path-is-absolute node-path-is-inside
                      node-performance-now node-prepend-http node-process-nextick-args
                      node-promise-inflight node-promzard node-proto-list node-prr node-pump
                      node-pumpify node-punycode node-qs node-qw node-rc node-read
                      node-read-package-json node-readable-stream node-registry-auth-token
                      node-registry-url node-request node-require-directory
                      node-require-main-filename node-resolve-from node-retry node-rimraf
                      node-run-queue node-safe-buffer node-semver node-semver-diff
                      node-set-blocking node-sha node-shebang-command node-shebang-regex
                      node-signal-exit node-slash node-slide node-sorted-object node-spdx-correct
                      node-spdx-expression-parse node-spdx-license-ids node-sshpk node-ssri
                      node-stream-each node-stream-iterate node-stream-shift node-string-decoder
                      node-string-width node-strip-ansi node-strip-eof node-strip-json-comments
                      node-supports-color node-tar node-term-size node-text-table node-through
                      node-through2 node-timed-out node-tough-cookie node-tunnel-agent
                      node-tweetnacl node-typedarray node-uid-number node-unique-filename
                      node-unpipe node-url-parse-lax node-url-to-options node-util-deprecate
                      node-uuid node-validate-npm-package-license node-validate-npm-package-name
                      node-verror node-wcwidth.js node-which node-which-module node-wide-align
                      node-widest-line node-wrap-ansi node-wrappy node-write-file-atomic
                      node-xdg-basedir node-xtend node-y18n node-yallist node-yargs
                      node-yargs-parser nodejs-doc rpi-eeprom-images
                    Use 'sudo apt autoremove' to remove them.
                    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                    
                    
                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Jona last edited by Thomas Braun

                      @Jona
                      Das ist alles alter Kram.

                      sudo apt autoremove
                      sudo reboot
                      

                      Dann würde ich nodejs noch mal drüber bügeln:

                      iobroker stop
                      sudo apt install nodejs --reinstall
                      iobroker start
                      
                      J 1 Reply Last reply Reply Quote 0
                      • J
                        Jona @Thomas Braun last edited by

                        @Thomas-Braun Zwischendurch erst einmal danke für deine Mühe und Hilfe.
                        Leider sind die beiden Adapter noch immer auf rot.
                        Der Fehler-Log sieht so aus:

                        2020-09-28 13:21:00.300 - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled
                        2020-09-28 13:21:30.328 - info: host.raspberrypi instance system.adapter.zigbee.0 started with pid 2930
                        2020-09-28 13:21:30.954 - error: host.raspberrypi Caught by controller[0]: /opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:121
                        2020-09-28 13:21:30.954 - error: host.raspberrypi Caught by controller[0]: throw e;
                        2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: ^
                        2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: Error: libnode.so.64: cannot open shared object file: No such file or directory
                        2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1187:18)
                        2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:985:32)
                        2020-09-28 13:21:30.955 - error: host.raspberrypi Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:878:14)
                        2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:1025:19)
                        2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at require (internal/modules/cjs/helpers.js:72:18)
                        2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at bindings (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:112:48)
                        2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36)
                        2020-09-28 13:21:30.956 - error: host.raspberrypi Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1137:30)
                        2020-09-28 13:21:30.957 - error: host.raspberrypi Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
                        2020-09-28 13:21:30.957 - error: host.raspberrypi Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:985:32)
                        2020-09-28 13:21:30.957 - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                        
                        Thomas Braun F 2 Replies Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Jona last edited by

                          @Jona

                          sudo apt update
                          sudo apt upgrade
                          
                          apt policy node-*
                          

                          Gut möglich, dass man dann noch einen npm rebuild hinterherwerfen muss, wenn die Pakete sauber sind.

                          J Thomas Braun 2 Replies Last reply Reply Quote 0
                          • J
                            Jona @Thomas Braun last edited by

                            @Thomas-Braun Keine Updates verfügbar und:

                            ~ $ apt policy node-*
                            N: Unable to locate package node-v10.16.0-linux-armv7l
                            N: Couldn't find any package by glob 'node-v10.16.0-linux-armv7l'
                            N: Couldn't find any package by regex 'node-v10.16.0-linux-armv7l'
                            
                            
                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Jona last edited by

                              @Jona sagte in Probleme mit Zigbee / Generator.next / ZStackAdapter / 2252:

                              Unable to locate package

                              Bitte die komplete Ein- und Ausgabe inkl. Login Prompt von

                              sudo apt update
                              

                              Nix kürzen, nix weglöschen.

                              J 1 Reply Last reply Reply Quote 0
                              • J
                                Jona @Thomas Braun last edited by

                                @Thomas-Braun

                                pi@raspberrypi:~ $ sudo apt update && sudo apt upgrade
                                Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
                                Hit:2 http://archive.raspberrypi.org/debian buster InRelease                   
                                Get:3 https://download.docker.com/linux/raspbian buster InRelease [29.7 kB]    
                                Hit:4 https://deb.nodesource.com/node_12.x buster InRelease                    
                                Hit:6 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease   
                                Hit:5 https://dl.ubnt.com/unifi/debian stable InRelease                        
                                Fetched 29.7 kB in 2s (13.7 kB/s)
                                Reading package lists... Done
                                Building dependency tree       
                                Reading state information... Done
                                All packages are up to date.
                                Reading package lists... Done
                                Building dependency tree       
                                Reading state information... Done
                                Calculating upgrade... Done
                                0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                                pi@raspberrypi:~ $ apt policy node-*
                                N: Unable to locate package node-v10.16.0-linux-armv7l
                                N: Couldn't find any package by glob 'node-v10.16.0-linux-armv7l'
                                N: Couldn't find any package by regex 'node-v10.16.0-linux-armv7l'
                                pi@raspberrypi:~ $ sudo apt policy node-*
                                N: Unable to locate package node-v10.16.0-linux-armv7l
                                N: Couldn't find any package by glob 'node-v10.16.0-linux-armv7l'
                                N: Couldn't find any package by regex 'node-v10.16.0-linux-armv7l'
                                
                                
                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @Jona last edited by Thomas Braun

                                  @Jona sagte in Probleme mit Zigbee / Generator.next / ZStackAdapter / 2252:

                                  Get:3 https://download.docker.com/linux/raspbian buster InRelease [29.7 kB]             
                                  Hit:6 https://packagecloud.io/headmelted/codebuilds/debian stretch InRelease
                                  Hit:5 https://dl.ubnt.com/unifi/debian stable InRelease
                                  

                                  Was sind das für Quellen? Brauchst du die? Und warum steht die von packagecloud auf stretch?

                                  J 1 Reply Last reply Reply Quote 0
                                  • J
                                    Jona @Thomas Braun last edited by Jona

                                    @Thomas-Braun Mit Docker habe ich mal herumgespielt, kann aber gelöscht werden. Letzteres ist für meinen Unifi Controller - ich glaube nicht, dass das etwas hiermit zu tun hat.

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

                                      @Jona
                                      Und packagecloud?
                                      Deaktivier die mal alle drei.

                                      1 Reply Last reply Reply Quote 0
                                      • F
                                        fabwal @Jona last edited by

                                        @Jona
                                        Hast du deine Adapter nach dem Update auf node 12 neu installiert?

                                        iobroker rebuild apdatername --install
                                        

                                        Siehe auch hier:
                                        https://forum.iobroker.net/topic/22867/how-to-node-js-für-iobroker-richtig-updaten

                                        (Ich hatte übrigens auch immer diverse Probleme mit dem CC2531 und habe ihn dann auf Anraten des Forums in die Tonne gekloppt. Das Teil ist für größere Mesh Netze nur bedingt geeignet. Mal klappt es, mal nicht...)

                                        J 2 Replies Last reply Reply Quote 0
                                        • J
                                          Jona @fabwal last edited by

                                          @fabwal Super Tipp - das war es! Nun kann ich Zigbee und BLE wieder nutzen. Mal schauen, ob die Fehler nach dem Richten meiner Nodejs Installation weiterhin auftauchen.

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

                                            @Thomas-Braun sagte in Probleme mit Zigbee / Generator.next / ZStackAdapter / 2252:

                                            Ich zitier mich mal selber...:

                                            Gut möglich, dass man dann noch einen npm rebuild hinterherwerfen muss, wenn die Pakete sauber sind.

                                            Wobei deine Paketdatenbank wohl noch nicht konsistent ist, denke ich.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            576
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            cc2531 homekit neustart pi 4 raspberry pi 4 yahka zigbee
                                            5
                                            59
                                            2892
                                            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