Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. ZigBee neue Version 1.4.4

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    17
    1
    3.7k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    1.2k

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.5k

ZigBee neue Version 1.4.4

Scheduled Pinned Locked Moved Tester
neue versionzigbeezigbee neue version 1.4.0
302 Posts 35 Posters 61.1k Views 36 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Jan FiedlerJ Jan Fiedler

    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
    
    AsgothianA Offline
    AsgothianA Offline
    Asgothian
    Developer
    wrote on last edited by
    #173

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

    A.

    ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
    "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

    Jan FiedlerJ 1 Reply Last reply
    0
    • AsgothianA Asgothian

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

      A.

      Jan FiedlerJ Offline
      Jan FiedlerJ Offline
      Jan Fiedler
      wrote on last edited by
      #174

      @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 FiedlerJ 1 Reply Last reply
      0
      • Jan FiedlerJ Jan Fiedler

        @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 FiedlerJ Offline
        Jan FiedlerJ Offline
        Jan Fiedler
        wrote on last edited by
        #175

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

        
        pi@raspberrypi:~ $ npm list serialport
        /home/pi
        └── (empty)
        
        
        
        Thomas BraunT AsgothianA 2 Replies Last reply
        0
        • Jan FiedlerJ Jan Fiedler

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

          
          pi@raspberrypi:~ $ npm list serialport
          /home/pi
          └── (empty)
          
          
          
          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          wrote on last edited by
          #176

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

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          1 Reply Last reply
          0
          • Jan FiedlerJ Jan Fiedler

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

            
            pi@raspberrypi:~ $ npm list serialport
            /home/pi
            └── (empty)
            
            
            
            AsgothianA Offline
            AsgothianA Offline
            Asgothian
            Developer
            wrote on last edited by
            #177

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

            A.

            ioBroker auf RPi4 - Hardware soweit wie möglich via Zigbee.
            "Shit don't work" ist keine Fehlermeldung, sondern ein Fluch.

            Jan FiedlerJ 1 Reply Last reply
            0
            • AsgothianA Asgothian

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

              A.

              Jan FiedlerJ Offline
              Jan FiedlerJ Offline
              Jan Fiedler
              wrote on last edited by
              #178

              @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 BraunT 1 Reply Last reply
              1
              • Jan FiedlerJ Jan Fiedler

                @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 BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                wrote on last edited by
                #179

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

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                Jan FiedlerJ 1 Reply Last reply
                0
                • Thomas BraunT Thomas Braun

                  @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 FiedlerJ Offline
                  Jan FiedlerJ Offline
                  Jan Fiedler
                  wrote on last edited by Jan Fiedler
                  #180

                  @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 BraunT 1 Reply Last reply
                  0
                  • Jan FiedlerJ 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 BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    wrote on last edited by
                    #181

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

                    Linux-Werkzeugkasten:
                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                    NodeJS Fixer Skript:
                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                    Jan FiedlerJ 1 Reply Last reply
                    0
                    • Thomas BraunT Thomas Braun

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

                      Jan FiedlerJ Offline
                      Jan FiedlerJ Offline
                      Jan Fiedler
                      wrote on last edited by
                      #182

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

                      Thomas BraunT 1 Reply Last reply
                      0
                      • Jan FiedlerJ Jan Fiedler

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

                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        wrote on last edited by
                        #183

                        @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
                        

                        Linux-Werkzeugkasten:
                        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                        NodeJS Fixer Skript:
                        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                        Jan FiedlerJ arteckA 2 Replies Last reply
                        0
                        • Thomas BraunT Thomas Braun

                          @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 FiedlerJ Offline
                          Jan FiedlerJ Offline
                          Jan Fiedler
                          wrote on last edited by
                          #184

                          @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 BraunT 1 Reply Last reply
                          0
                          • Jan FiedlerJ Jan Fiedler

                            @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 BraunT Online
                            Thomas BraunT Online
                            Thomas Braun
                            Most Active
                            wrote on last edited by
                            #185

                            @jan-fiedler dann mach es jetzt.

                            Linux-Werkzeugkasten:
                            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                            NodeJS Fixer Skript:
                            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                            Jan FiedlerJ 1 Reply Last reply
                            0
                            • Thomas BraunT Thomas Braun

                              @jan-fiedler dann mach es jetzt.

                              Jan FiedlerJ Offline
                              Jan FiedlerJ Offline
                              Jan Fiedler
                              wrote on last edited by
                              #186

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

                              Thomas BraunT arteckA 2 Replies Last reply
                              0
                              • Jan FiedlerJ Jan Fiedler

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

                                Thomas BraunT Online
                                Thomas BraunT Online
                                Thomas Braun
                                Most Active
                                wrote on last edited by Thomas Braun
                                #187

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

                                Linux-Werkzeugkasten:
                                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                NodeJS Fixer Skript:
                                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                1 Reply Last reply
                                1
                                • K Offline
                                  K Offline
                                  klassisch
                                  Most Active
                                  wrote on last edited by
                                  #188

                                  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
                                  1
                                  • Thomas BraunT Thomas Braun

                                    @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
                                    
                                    arteckA Offline
                                    arteckA Offline
                                    arteck
                                    Developer Most Active
                                    wrote on last edited by
                                    #189

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

                                    zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                    Thomas BraunT 1 Reply Last reply
                                    0
                                    • arteckA arteck

                                      @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 BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      wrote on last edited by
                                      #190

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

                                      Linux-Werkzeugkasten:
                                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                      NodeJS Fixer Skript:
                                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                      Jan FiedlerJ 1 Reply Last reply
                                      0
                                      • Jan FiedlerJ Jan Fiedler

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

                                        arteckA Offline
                                        arteckA Offline
                                        arteck
                                        Developer Most Active
                                        wrote on last edited by
                                        #191

                                        @jan-fiedler ist das ein Multihost??

                                        zigbee hab ich, zwave auch, nuc's genauso und HA auch

                                        Jan FiedlerJ 1 Reply Last reply
                                        0
                                        • Thomas BraunT Thomas Braun

                                          @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 FiedlerJ Offline
                                          Jan FiedlerJ Offline
                                          Jan Fiedler
                                          wrote on last edited by
                                          #192

                                          @thomas-braun @arteck Grundsätzlich habt ihr beide Recht. Das Problem rührte von anderer Seite her, nämlich dem Serialport Treiber. Wenn man diesen richtig installiert, updated und rebuilded, scheint alles zu gehen. Auch wenn der Zigbee Adapter immer noch Cast Fehler schmeißt beim updaten. Der Hinweis auf ein Update ist gut, schließlich beschäftige ich mich damit viel zu wenig. Hätte aber auch per PM gereicht und gehört nicht in den Thread zum Zigbee Adapter ;)

                                          Danke euch für die schnelle Hilfe!

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          673

                                          Online

                                          32.7k

                                          Users

                                          82.4k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe