Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. ZigBee neue Version 1.4.4

    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 neue Version 1.4.4

    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      klassisch Most Active @Asgothian last edited by klassisch

      @asgothian Danke, stopp, gut daß wir drüber gesprochen haben. Als ich Controller las, dachte ich an den Coordinator, habe das Drehgestell aus dem Datenpunkt rausgenommen und dann diese Nummer des Coordinators reingenommen.
      Also ich trage jetzt die Nummer des ikea symfonisk Drehreglers rotary encoders ein. Die ist schnell gefunden und steht ja in der Objektliste.
      Neue Energizer Batterie hatte ich gestern schon reingemacht. 3.13V sollte noch iO sein.
      Und ja, beim Drehen kommen ELEVATED log-Einträge. Sieht in meinem laienhaften Auge ziemlich plausibel aus.

      1 Reply Last reply Reply Quote 0
      • Jan Fiedler
        Jan Fiedler last edited by

        Moin zusammen,

        ich habe heute mit der beschriebenen Methode sowohl den JS-Controller als auch alle Adapter auf die aktuellste Version aktualisiert. Danach ging erstmal der Zigbee Adapter nicht mehr (v1.4.4). Mit einem Fehler bzgl Serialport. Ich habe dann Serialport mit npm aktualisiert; danach kommt jetzt folgender Fehler beim Start des Adapters - jetzt bin ich überfragt.
        Ein npm rebuild hat auch nichts gebracht...

        host.raspberrypi	2021-03-04 22:00:47.143	error	instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
        host.raspberrypi	2021-03-04 22:00:47.142	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/index.js:14:22)
        host.raspberrypi	2021-03-04 22:00:47.142	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:25:18)
        host.raspberrypi	2021-03-04 22:00:47.142	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:692:17)
        host.raspberrypi	2021-03-04 22:00:47.142	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:585:3)
        host.raspberrypi	2021-03-04 22:00:47.141	error	Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
        host.raspberrypi	2021-03-04 22:00:47.141	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:653:32)
        host.raspberrypi	2021-03-04 22:00:47.141	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
        host.raspberrypi	2021-03-04 22:00:47.140	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:778:30)
        host.raspberrypi	2021-03-04 22:00:47.140	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36)
        host.raspberrypi	2021-03-04 22:00:47.140	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:126:9)
        host.raspberrypi	2021-03-04 22:00:47.140	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/binding/node-v64-linux-arm/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.139	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/addon-build/default/install-root/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.139	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/addon-build/debug/install-root/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.139	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/addon-build/release/install-root/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.139	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/compiled/10.22.0/linux/arm/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.138	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/default/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.138	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/Release/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.138	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/out/Release/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.138	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/Debug/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.137	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/out/Debug/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.137	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/Release/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.137	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/Debug/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.137	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/bindings.node
        host.raspberrypi	2021-03-04 22:00:47.136	error	Caught by controller[0]: Error: Could not locate the bindings file. Tried:
        host.raspberrypi	2021-03-04 22:00:47.136	error	Caught by controller[0]: ^
        host.raspberrypi	2021-03-04 22:00:47.136	error	Caught by controller[0]: throw err;
        host.raspberrypi	2021-03-04 22:00:47.135	error	Caught by controller[0]: /opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:135
        
        Asgothian 1 Reply Last reply Reply Quote 0
        • Asgothian
          Asgothian Developer @Jan Fiedler last edited by

          @jan-fiedler Bitte den Adapter noch einmal installieren, und zwar vom Admin aus, nicht aus der Konsole.

          A.

          Jan Fiedler 1 Reply Last reply Reply Quote 0
          • Jan Fiedler
            Jan Fiedler @Asgothian last edited by

            @asgothian Hat leider nicht geholfen...

            host.raspberrypi	2021-03-04 22:54:25.246	error	instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
            host.raspberrypi	2021-03-04 22:54:25.246	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/index.js:14:22)
            host.raspberrypi	2021-03-04 22:54:25.245	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:25:18)
            host.raspberrypi	2021-03-04 22:54:25.245	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:692:17)
            host.raspberrypi	2021-03-04 22:54:25.245	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:585:3)
            host.raspberrypi	2021-03-04 22:54:25.245	error	Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
            host.raspberrypi	2021-03-04 22:54:25.244	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:653:32)
            host.raspberrypi	2021-03-04 22:54:25.244	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
            host.raspberrypi	2021-03-04 22:54:25.244	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:778:30)
            host.raspberrypi	2021-03-04 22:54:25.244	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/linux.js:2:36)
            host.raspberrypi	2021-03-04 22:54:25.244	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:126:9)
            host.raspberrypi	2021-03-04 22:54:25.243	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/lib/binding/node-v64-linux-arm/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.243	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/addon-build/default/install-root/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.243	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/addon-build/debug/install-root/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.243	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/addon-build/release/install-root/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.242	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/compiled/10.22.0/linux/arm/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.242	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/default/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.242	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/Release/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.242	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/out/Release/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.241	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/Debug/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.241	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/out/Debug/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.241	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/Release/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.241	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/Debug/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.240	error	Caught by controller[0]: → /opt/iobroker/node_modules/zigbee-herdsman/node_modules/@serialport/bindings/build/bindings.node
            host.raspberrypi	2021-03-04 22:54:25.240	error	Caught by controller[0]: Error: Could not locate the bindings file. Tried:
            host.raspberrypi	2021-03-04 22:54:25.240	error	Caught by controller[0]: ^
            host.raspberrypi	2021-03-04 22:54:25.240	error	Caught by controller[0]: throw err;
            host.raspberrypi	2021-03-04 22:54:25.239	error	Caught by controller[0]: /opt/iobroker/node_modules/zigbee-herdsman/node_modules/bindings/bindings.js:135
            host.raspberrypi	2021-03-04 22:54:23.987	info	instance system.adapter.zigbee.0 started with pid 8841
            
            Jan Fiedler 1 Reply Last reply Reply Quote 0
            • Jan Fiedler
              Jan Fiedler @Jan Fiedler last edited by

              @jan-fiedler Was mir noch aufgefallen ist... Das sollte so nicht sein oder?

              
              pi@raspberrypi:~ $ npm list serialport
              /home/pi
              └── (empty)
              
              
              
              Thomas Braun Asgothian 2 Replies Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Jan Fiedler last edited by

                @jan-fiedler Doch, das soll so sein in deinem home.
                Stell dich nach /opt/iobroker

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

                  @jan-fiedler Doch.. der Befehl muss im Verzeichnis /opt/iobroker angegeben werden

                  A.

                  Jan Fiedler 1 Reply Last reply Reply Quote 0
                  • Jan Fiedler
                    Jan Fiedler @Asgothian last edited by

                    @asgothian

                    pi@raspberrypi:/opt/iobroker $ npm list serialport
                    iobroker.inst@2.0.3 /opt/iobroker
                    ├─┬ iobroker.discovery@2.5.0
                    │ └── serialport@9.0.7  deduped
                    └── serialport@9.0.7
                    
                    
                    Thomas Braun 1 Reply Last reply Reply Quote 1
                    • Thomas Braun
                      Thomas Braun Most Active @Jan Fiedler last edited by

                      @jan-fiedler
                      Schaut bei mir anders aus:

                      pi@raspberrypi:/opt/iobroker $ npm list serialport
                      iobroker.inst@2.0.3 /opt/iobroker
                      └─┬ iobroker.zigbee@1.4.4
                        ├─┬ zigbee-herdsman@0.13.70
                        │ └── serialport@9.0.6
                        └─┬ zigbee-herdsman-converters@14.0.57
                          └─┬ zigbee-herdsman@0.13.68
                            └── serialport@9.0.6
                      
                      pi@raspberrypi:/opt/iobroker $
                      
                      Jan Fiedler 1 Reply Last reply Reply Quote 0
                      • Jan Fiedler
                        Jan Fiedler @Thomas Braun last edited by Jan Fiedler

                        @thomas-braun Ich hab jetzt nochmal ein npm rebuild in den /opt/iobroker Verzeichnis durchgeführt. Allerdings hat das nur zu einem Haufen folgender Fehler geführt. Hab ich vllt eine inkompatible node Version?

                        warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                        
                        
                        npm ERR! code ELIFECYCLE
                        npm ERR! errno 1
                        npm ERR! node-aead-crypto@2.2.0 preinstall: `node lib/preinstall.js`
                        npm ERR! Exit status 1
                        npm ERR!
                        npm ERR! Failed at the node-aead-crypto@2.2.0 preinstall 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:
                        
                        

                        2021-03-04T22_11_47_952Z-debug.log

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

                          @jan-fiedler Wie schaut die node-Installation denn aus?

                          Jan Fiedler 1 Reply Last reply Reply Quote 0
                          • Jan Fiedler
                            Jan Fiedler @Thomas Braun last edited by

                            @thomas-braun Wie genau meinst du das? Versionsnummern? Logs?
                            Der Adapter ist allerdings aktuell auf Grün gewechselt spannenderweise...

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

                              @jan-fiedler

                              which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                              

                              Dein System scheint aber auch steinalt zu sein.

                              sudo apt update
                              sudo apt dist-upgrade
                              sudo reboot
                              
                              Jan Fiedler arteck 2 Replies Last reply Reply Quote 0
                              • Jan Fiedler
                                Jan Fiedler @Thomas Braun last edited by

                                @thomas-braun sagte in ZigBee neue Version 1.4.4:

                                which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs

                                Das kann schon sein... macht halt nur ioBroker 😉

                                pi@raspberrypi:~ $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                                /usr/bin/nodejs
                                v10.22.0
                                /usr/bin/node
                                v10.22.0
                                /usr/bin/npm
                                6.14.6
                                nodejs:
                                  Installiert:           10.22.0-1nodesource1
                                  Installationskandidat: 10.22.0-1nodesource1
                                  Versionstabelle:
                                 *** 10.22.0-1nodesource1 500
                                        500 https://deb.nodesource.com/node_10.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
                                
                                
                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @Jan Fiedler last edited by

                                  @jan-fiedler dann mach es jetzt.

                                  Jan Fiedler 1 Reply Last reply Reply Quote 0
                                  • Jan Fiedler
                                    Jan Fiedler @Thomas Braun last edited by

                                    @thomas-braun Ziehe mir aber morgen erstmal ein Backup, nicht dass ich damit wieder alles zerschieße

                                    Thomas Braun arteck 2 Replies Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @Jan Fiedler last edited by Thomas Braun

                                      @jan-fiedler
                                      Backup haben ist immer gut. Backup von einem sauberen System ist noch besser.

                                      1 Reply Last reply Reply Quote 1
                                      • K
                                        klassisch Most Active last edited by

                                        Ob eine neueres nodejs hilft?

                                        Mein System ist älter und läuft im Prinzip
                                        Node.js v10.17.0
                                        NPM 6.11.3
                                        js-controller Installiert: 3.2.16

                                        Verbindung über COM-Port wird hergestellt. Adapter grün.

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

                                          @thomas-braun jetzt hör auf wieder irgendwelche UPDATES zu propagieren..

                                          das hat nix mit dem Fehler zu tun..

                                          VOR ALLEM NICHT IN DIESEM THREAD

                                          wie oft noch....

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

                                            @arteck Weil's grundsätzlich eine gute Idee ist sein System auf Stand zu haben.
                                            In jedem Thread.
                                            Hier ist noch ein uralter Kernel am Start, mit uralter Firmware für den Pi.

                                            Wenn das System auf dem aktuellen Stand ist hast du die ganzen Fixes drauf und dann von der Seite her Ruhe. Warum sollte man sein System nicht updaten?

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            979
                                            Online

                                            31.7k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            neue version zigbee zigbee neue version 1.4.0
                                            35
                                            302
                                            38334
                                            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