Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • 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

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Zigbee Instanz rot nach node.js Update auf v12.18.4 [Gelöst]

NEWS

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

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

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.3k

Zigbee Instanz rot nach node.js Update auf v12.18.4 [Gelöst]

Geplant Angeheftet Gesperrt Verschoben Ungelöst Error/Bug
zigbee
95 Beiträge 5 Kommentatoren 8.3k Aufrufe 3 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • birdyB birdy

    @birdy

    Es würde mir ja schon reichen, wenn ich den Adapter weg bekomme und wieder neu installieren könnte... :cold_sweat:

    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von
    #28

    @birdy
    Dann musst du halt irgendwo anfangen das Gebilde zu sanieren.

    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 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @birdy
      Das du da ggf. irgendeine Leiche im Keller hast. Denn wir haben soweit ich das sehe ganz ähnliche Adapter installiert. Was liefert denn der Befehl auf deinem System?

      birdyB Offline
      birdyB Offline
      birdy
      schrieb am zuletzt editiert von birdy
      #29

      @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

      @birdy
      Das du da ggf. irgendeine Leiche im Keller hast. Denn wir haben soweit ich das sehe ganz ähnliche Adapter installiert. Was liefert denn der Befehl auf deinem System?

      pi@raspberrypi:/opt/iobroker $ npm list dissolve
      iobroker.inst@1.0.8 /opt/iobroker
      └─┬ iobroker.zigbee@0.10.2
        └─┬ zigbee-shepherd@0.3.0
          └─┬ zcl-packet@0.2.4
            └─┬ dissolve-chunks@1.3.0
              └── dissolve@0.3.3
      
      

      Was sagt diese Meldung aus?

      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • birdyB birdy

        @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

        @birdy
        Das du da ggf. irgendeine Leiche im Keller hast. Denn wir haben soweit ich das sehe ganz ähnliche Adapter installiert. Was liefert denn der Befehl auf deinem System?

        pi@raspberrypi:/opt/iobroker $ npm list dissolve
        iobroker.inst@1.0.8 /opt/iobroker
        └─┬ iobroker.zigbee@0.10.2
          └─┬ zigbee-shepherd@0.3.0
            └─┬ zcl-packet@0.2.4
              └─┬ dissolve-chunks@1.3.0
                └── dissolve@0.3.3
        
        

        Was sagt diese Meldung aus?

        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von Thomas Braun
        #30

        @birdy sagte in Zigbee Instanz rot nach node.js Update auf v12.18.4:

        cd /opt/iobroker
        npm i iobroker.zigbee@1.2.1
        

        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

        birdyB 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @birdy sagte in Zigbee Instanz rot nach node.js Update auf v12.18.4:

          cd /opt/iobroker
          npm i iobroker.zigbee@1.2.1
          
          birdyB Offline
          birdyB Offline
          birdy
          schrieb am zuletzt editiert von
          #31

          @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

          @birdy sagte in Zigbee Instanz rot nach node.js Update auf v12.18.4:

          cd /opt/iobroker
          npm i iobroker.zigbee@1.2.1
          

          Hab aber vergessen, iobroker zu stoppen... Schlecht?

          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroker.info/node_modules/osx-temperature-sensor):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: concentrate@^0.2.3 (node_modules/unpi/node_modules/concentrate):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported engine for concentrate@0.2.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Not compatible with your version of node/npm: concentrate@0.2.3
          
          npm ERR! code ENOTSUP
          npm ERR! notsup Unsupported engine for dissolve@0.3.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
          npm ERR! notsup Not compatible with your version of node/npm: dissolve@0.3.3
          npm ERR! notsup Not compatible with your version of node/npm: dissolve@0.3.3
          npm ERR! notsup Required: {"node":"~0.10.0"}
          npm ERR! notsup Actual:   {"npm":"6.14.6","node":"12.18.4"}
          
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /home/iobroker/.npm/_logs/2020-09-20T16_27_48_926Z-debug.log
          
          
          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • birdyB birdy

            @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

            @birdy sagte in Zigbee Instanz rot nach node.js Update auf v12.18.4:

            cd /opt/iobroker
            npm i iobroker.zigbee@1.2.1
            

            Hab aber vergessen, iobroker zu stoppen... Schlecht?

            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroker.info/node_modules/osx-temperature-sensor):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: concentrate@^0.2.3 (node_modules/unpi/node_modules/concentrate):
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported engine for concentrate@0.2.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Not compatible with your version of node/npm: concentrate@0.2.3
            
            npm ERR! code ENOTSUP
            npm ERR! notsup Unsupported engine for dissolve@0.3.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
            npm ERR! notsup Not compatible with your version of node/npm: dissolve@0.3.3
            npm ERR! notsup Not compatible with your version of node/npm: dissolve@0.3.3
            npm ERR! notsup Required: {"node":"~0.10.0"}
            npm ERR! notsup Actual:   {"npm":"6.14.6","node":"12.18.4"}
            
            npm ERR! A complete log of this run can be found in:
            npm ERR!     /home/iobroker/.npm/_logs/2020-09-20T16_27_48_926Z-debug.log
            
            
            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von Thomas Braun
            #32

            @birdy
            Versuch mal dissolve rauszukicken.
            Ein aktuelles zigbee benötigt das nicht mehr.

            npm uninstall dissolve
            

            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

            birdyB 1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @birdy
              Versuch mal dissolve rauszukicken.
              Ein aktuelles zigbee benötigt das nicht mehr.

              npm uninstall dissolve
              
              birdyB Offline
              birdyB Offline
              birdy
              schrieb am zuletzt editiert von
              #33

              @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

              @birdy
              Versuch mal dissolve rauszukicken.
              Ein akutelles zigbee benötigt das nicht mehr.

              npm uninstall dissolve
              

              vorher iobroker stoppen?

              Thomas BraunT 2 Antworten Letzte Antwort
              0
              • birdyB birdy

                @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

                @birdy
                Versuch mal dissolve rauszukicken.
                Ein akutelles zigbee benötigt das nicht mehr.

                npm uninstall dissolve
                

                vorher iobroker stoppen?

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #34

                @birdy
                Kannst du machen.

                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

                birdyB 1 Antwort Letzte Antwort
                0
                • birdyB birdy

                  @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

                  @birdy
                  Versuch mal dissolve rauszukicken.
                  Ein akutelles zigbee benötigt das nicht mehr.

                  npm uninstall dissolve
                  

                  vorher iobroker stoppen?

                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von
                  #35

                  @birdy sagte in Zigbee Instanz rot nach node.js Update auf v12.18.4:

                  npm uninstall dissolve

                  Wenn das nicht klappt versuch mal mit

                  npm uninstall dissolve --save
                  

                  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

                  birdyB 1 Antwort Letzte Antwort
                  0
                  • Thomas BraunT Thomas Braun

                    @birdy
                    Kannst du machen.

                    birdyB Offline
                    birdyB Offline
                    birdy
                    schrieb am zuletzt editiert von
                    #36

                    @Thomas-Braun

                    pi@raspberrypi:/opt/iobroker $ npm uninstall dissolve
                    npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
                    
                    > canvas@2.6.1 install /opt/iobroker/node_modules/canvas
                    > node-pre-gyp install --fallback-to-build
                    
                    node-pre-gyp WARN Using request for node-pre-gyp https download
                    node-pre-gyp WARN Tried to download(404): https://github.com/node-gfx/node-canvas-prebuilt/releases/download/v2.6.1/canvas-v2.6.1-node-v72-linux-glibc-arm.tar.gz
                    node-pre-gyp WARN Pre-built binaries not found for canvas@2.6.1 and node@12.18.4 (node-v72 ABI, glibc) (falling back to source compile with node-gyp)
                    Package cairo was not found in the pkg-config search path.
                    Perhaps you should add the directory containing `cairo.pc'
                    to the PKG_CONFIG_PATH environment variable
                    No package 'cairo' found
                    gyp: Call to 'pkg-config cairo --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
                    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:315:20)
                    gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                    gyp ERR! System Linux 4.19.66-v7+
                    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=6" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72"
                    gyp ERR! cwd /opt/iobroker/node_modules/canvas
                    gyp ERR! node -v v12.18.4
                    gyp ERR! node-gyp -v v5.1.0
                    gyp ERR! not ok
                    node-pre-gyp ERR! build error
                    node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
                    node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/canvas/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
                    node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
                    node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
                    node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
                    node-pre-gyp ERR! System Linux 4.19.66-v7+
                    node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/canvas/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
                    node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas
                    node-pre-gyp ERR! node -v v12.18.4
                    node-pre-gyp ERR! node-pre-gyp -v v0.11.0
                    node-pre-gyp ERR! not ok
                    Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
                    
                    > sharp@0.25.2 install /opt/iobroker/node_modules/sharp
                    > (node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)
                    
                    ERR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.9.1
                    info sharp Attempting to build from source via node-gyp but this may fail due to the above error
                    info sharp Please see https://sharp.pixelplumbing.com/install for required dependencies
                    make: Verzeichnis „/opt/iobroker/node_modules/sharp/build“ wird betreten
                      CC(target) Release/obj.target/nothing/../node-addon-api/src/nothing.o
                      AR(target) Release/obj.target/../node-addon-api/src/nothing.a
                      COPY Release/nothing.a
                      TOUCH Release/obj.target/libvips-cpp.stamp
                      CXX(target) Release/obj.target/sharp/src/common.o
                    ../src/common.cc:23:22: fatal error: vips/vips8: Datei oder Verzeichnis nicht gefunden
                     #include <vips/vips8>
                                          ^
                    compilation terminated.
                    sharp.target.mk:138: die Regel für Ziel „Release/obj.target/sharp/src/common.o“ scheiterte
                    make: *** [Release/obj.target/sharp/src/common.o] Fehler 1
                    make: Verzeichnis „/opt/iobroker/node_modules/sharp/build“ wird verlassen
                    gyp ERR! build error
                    gyp ERR! stack Error: `make` failed with exit code: 2
                    gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                    gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
                    gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                    gyp ERR! System Linux 4.19.66-v7+
                    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/sharp
                    gyp ERR! node -v v12.18.4
                    gyp ERR! node-gyp -v v5.1.0
                    gyp ERR! not ok
                    
                    > iobroker@1.0.8 install /opt/iobroker/node_modules/iobroker
                    > node lib/setup.js
                    
                    NPM version: 6.14.8
                    
                    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                    NPM 5 is currently NOT supported!
                    Please use "npm install -g npm@4" to downgrade npm to 4.x and try again.
                    You need to make sure to downgrade again with the above command after you
                    installed an update to nodejs/npm!
                    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroker.info/node_modules/osx-temperature-sensor):
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: concentrate@^0.2.3 (node_modules/unpi/node_modules/concentrate):
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported engine for concentrate@0.2.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Not compatible with your version of node/npm: concentrate@0.2.3
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.6.1 (node_modules/canvas):
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build`
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sharp@0.25.2 (node_modules/sharp):
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sharp@0.25.2 install: `(node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)`
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                    
                    npm ERR! code ELIFECYCLE
                    npm ERR! errno 1
                    npm ERR! iobroker@1.0.8 install: `node lib/setup.js`
                    npm ERR! Exit status 1
                    npm ERR!
                    npm ERR! Failed at the iobroker@1.0.8 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/2020-09-20T16_36_28_808Z-debug.log
                    
                    Thomas BraunT 1 Antwort Letzte Antwort
                    0
                    • Thomas BraunT Thomas Braun

                      @birdy sagte in Zigbee Instanz rot nach node.js Update auf v12.18.4:

                      npm uninstall dissolve

                      Wenn das nicht klappt versuch mal mit

                      npm uninstall dissolve --save
                      
                      birdyB Offline
                      birdyB Offline
                      birdy
                      schrieb am zuletzt editiert von
                      #37

                      @Thomas-Braun

                      So nebenbei möchte ich mich mal bei dir für die Zeit, die du in den fall investierst, bedanken!

                      1 Antwort Letzte Antwort
                      1
                      • birdyB birdy

                        @Thomas-Braun

                        pi@raspberrypi:/opt/iobroker $ npm uninstall dissolve
                        npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
                        
                        > canvas@2.6.1 install /opt/iobroker/node_modules/canvas
                        > node-pre-gyp install --fallback-to-build
                        
                        node-pre-gyp WARN Using request for node-pre-gyp https download
                        node-pre-gyp WARN Tried to download(404): https://github.com/node-gfx/node-canvas-prebuilt/releases/download/v2.6.1/canvas-v2.6.1-node-v72-linux-glibc-arm.tar.gz
                        node-pre-gyp WARN Pre-built binaries not found for canvas@2.6.1 and node@12.18.4 (node-v72 ABI, glibc) (falling back to source compile with node-gyp)
                        Package cairo was not found in the pkg-config search path.
                        Perhaps you should add the directory containing `cairo.pc'
                        to the PKG_CONFIG_PATH environment variable
                        No package 'cairo' found
                        gyp: Call to 'pkg-config cairo --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
                        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:315:20)
                        gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                        gyp ERR! System Linux 4.19.66-v7+
                        gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=6" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v72"
                        gyp ERR! cwd /opt/iobroker/node_modules/canvas
                        gyp ERR! node -v v12.18.4
                        gyp ERR! node-gyp -v v5.1.0
                        gyp ERR! not ok
                        node-pre-gyp ERR! build error
                        node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
                        node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/canvas/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
                        node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
                        node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
                        node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
                        node-pre-gyp ERR! System Linux 4.19.66-v7+
                        node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/canvas/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
                        node-pre-gyp ERR! cwd /opt/iobroker/node_modules/canvas
                        node-pre-gyp ERR! node -v v12.18.4
                        node-pre-gyp ERR! node-pre-gyp -v v0.11.0
                        node-pre-gyp ERR! not ok
                        Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v72' (1)
                        
                        > sharp@0.25.2 install /opt/iobroker/node_modules/sharp
                        > (node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)
                        
                        ERR! sharp Use with glibc 2.24 requires manual installation of libvips >= 8.9.1
                        info sharp Attempting to build from source via node-gyp but this may fail due to the above error
                        info sharp Please see https://sharp.pixelplumbing.com/install for required dependencies
                        make: Verzeichnis „/opt/iobroker/node_modules/sharp/build“ wird betreten
                          CC(target) Release/obj.target/nothing/../node-addon-api/src/nothing.o
                          AR(target) Release/obj.target/../node-addon-api/src/nothing.a
                          COPY Release/nothing.a
                          TOUCH Release/obj.target/libvips-cpp.stamp
                          CXX(target) Release/obj.target/sharp/src/common.o
                        ../src/common.cc:23:22: fatal error: vips/vips8: Datei oder Verzeichnis nicht gefunden
                         #include <vips/vips8>
                                              ^
                        compilation terminated.
                        sharp.target.mk:138: die Regel für Ziel „Release/obj.target/sharp/src/common.o“ scheiterte
                        make: *** [Release/obj.target/sharp/src/common.o] Fehler 1
                        make: Verzeichnis „/opt/iobroker/node_modules/sharp/build“ wird verlassen
                        gyp ERR! build error
                        gyp ERR! stack Error: `make` failed with exit code: 2
                        gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
                        gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
                        gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                        gyp ERR! System Linux 4.19.66-v7+
                        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/sharp
                        gyp ERR! node -v v12.18.4
                        gyp ERR! node-gyp -v v5.1.0
                        gyp ERR! not ok
                        
                        > iobroker@1.0.8 install /opt/iobroker/node_modules/iobroker
                        > node lib/setup.js
                        
                        NPM version: 6.14.8
                        
                        !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                        NPM 5 is currently NOT supported!
                        Please use "npm install -g npm@4" to downgrade npm to 4.x and try again.
                        You need to make sure to downgrade again with the above command after you
                        installed an update to nodejs/npm!
                        !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroker.info/node_modules/osx-temperature-sensor):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: concentrate@^0.2.3 (node_modules/unpi/node_modules/concentrate):
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported engine for concentrate@0.2.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Not compatible with your version of node/npm: concentrate@0.2.3
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.6.1 (node_modules/canvas):
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build`
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sharp@0.25.2 (node_modules/sharp):
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: sharp@0.25.2 install: `(node install/libvips && node install/dll-copy && prebuild-install --runtime=napi) || (node-gyp rebuild && node install/dll-copy)`
                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                        
                        npm ERR! code ELIFECYCLE
                        npm ERR! errno 1
                        npm ERR! iobroker@1.0.8 install: `node lib/setup.js`
                        npm ERR! Exit status 1
                        npm ERR!
                        npm ERR! Failed at the iobroker@1.0.8 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/2020-09-20T16_36_28_808Z-debug.log
                        
                        Thomas BraunT Online
                        Thomas BraunT Online
                        Thomas Braun
                        Most Active
                        schrieb am zuletzt editiert von
                        #38

                        @birdy
                        Wie gesagt: Viele viele Baustellen.
                        Vermutlich geht das schneller, wenn du das System komplett neuinstallierst (Buster) und dann dein Backup in den ioBroker einspielst.

                        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

                        birdyB 2 Antworten Letzte Antwort
                        1
                        • Thomas BraunT Thomas Braun

                          @birdy
                          Wie gesagt: Viele viele Baustellen.
                          Vermutlich geht das schneller, wenn du das System komplett neuinstallierst (Buster) und dann dein Backup in den ioBroker einspielst.

                          birdyB Offline
                          birdyB Offline
                          birdy
                          schrieb am zuletzt editiert von
                          #39

                          @Thomas-Braun

                          aber jetzt ganz schlimm:

                          pi@raspberrypi:/opt/iobroker $ start iobroker
                          -bash: start: Kommando nicht gefunden.
                          
                          GlasfaserG Thomas BraunT 2 Antworten Letzte Antwort
                          0
                          • birdyB birdy

                            @Thomas-Braun

                            aber jetzt ganz schlimm:

                            pi@raspberrypi:/opt/iobroker $ start iobroker
                            -bash: start: Kommando nicht gefunden.
                            
                            GlasfaserG Offline
                            GlasfaserG Offline
                            Glasfaser
                            schrieb am zuletzt editiert von
                            #40

                            @birdy

                            iobroker start
                            

                            Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..

                            1 Antwort Letzte Antwort
                            0
                            • birdyB birdy

                              @Thomas-Braun

                              aber jetzt ganz schlimm:

                              pi@raspberrypi:/opt/iobroker $ start iobroker
                              -bash: start: Kommando nicht gefunden.
                              
                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #41

                              @birdy
                              Nö. Das heißt ja auch

                              iobroker start
                              

                              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

                              birdyB 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @birdy
                                Nö. Das heißt ja auch

                                iobroker start
                                
                                birdyB Offline
                                birdyB Offline
                                birdy
                                schrieb am zuletzt editiert von
                                #42

                                @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

                                @birdy
                                Nö. Das heißt ja auch

                                iobroker start
                                

                                Sorry, bin schon etwas durch den Wind...

                                Thomas BraunT 1 Antwort Letzte Antwort
                                0
                                • birdyB birdy

                                  @Thomas-Braun said in Zigbee Instanz rot nach node.js Update auf v12.18.4:

                                  @birdy
                                  Nö. Das heißt ja auch

                                  iobroker start
                                  

                                  Sorry, bin schon etwas durch den Wind...

                                  Thomas BraunT Online
                                  Thomas BraunT Online
                                  Thomas Braun
                                  Most Active
                                  schrieb am zuletzt editiert von
                                  #43

                                  @birdy
                                  Die Meldung bzgl. cairo dürfest du mit

                                  sudo apt install libcairo2-dev
                                  

                                  schon mal loswerden. Ändert aber nix am Umfang der Großbaustelle.

                                  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 Antwort Letzte Antwort
                                  0
                                  • Thomas BraunT Thomas Braun

                                    @birdy
                                    Wie gesagt: Viele viele Baustellen.
                                    Vermutlich geht das schneller, wenn du das System komplett neuinstallierst (Buster) und dann dein Backup in den ioBroker einspielst.

                                    birdyB Offline
                                    birdyB Offline
                                    birdy
                                    schrieb am zuletzt editiert von
                                    #44

                                    @Thomas-Braun

                                    Aber was soll ich jetzt mit dem deistallierten dissolve machen?

                                    Nochmal?

                                    npm i iobroker.zigbee@1.2.1
                                    
                                    Thomas BraunT 1 Antwort Letzte Antwort
                                    0
                                    • birdyB birdy

                                      @Thomas-Braun

                                      Aber was soll ich jetzt mit dem deistallierten dissolve machen?

                                      Nochmal?

                                      npm i iobroker.zigbee@1.2.1
                                      
                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      schrieb am zuletzt editiert von
                                      #45

                                      @birdy
                                      Probier mal. Ich bin nicht mal sicher das dissolve sich jetzt aufgelöst hat...

                                      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

                                      birdyB 1 Antwort Letzte Antwort
                                      0
                                      • Thomas BraunT Thomas Braun

                                        @birdy
                                        Probier mal. Ich bin nicht mal sicher das dissolve sich jetzt aufgelöst hat...

                                        birdyB Offline
                                        birdyB Offline
                                        birdy
                                        schrieb am zuletzt editiert von
                                        #46

                                        @Thomas-Braun

                                        Scheint nicht so... :(

                                        pi@raspberrypi:/opt/iobroker $ npm i iobroker.zigbee@1.2.1
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
                                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroker.info/node_modules/osx-temperature-sensor):
                                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: concentrate@^0.2.3 (node_modules/unpi/node_modules/concentrate):
                                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported engine for concentrate@0.2.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
                                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Not compatible with your version of node/npm: concentrate@0.2.3
                                        
                                        npm ERR! code ENOTSUP
                                        npm ERR! notsup Unsupported engine for dissolve@0.3.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
                                        npm ERR! notsup Not compatible with your version of node/npm: dissolve@0.3.3
                                        npm ERR! notsup Not compatible with your version of node/npm: dissolve@0.3.3
                                        npm ERR! notsup Required: {"node":"~0.10.0"}
                                        npm ERR! notsup Actual:   {"npm":"6.14.6","node":"12.18.4"}
                                        
                                        npm ERR! A complete log of this run can be found in:
                                        npm ERR!     /home/iobroker/.npm/_logs/2020-09-20T16_51_25_317Z-debug.log
                                        
                                        Thomas BraunT 1 Antwort Letzte Antwort
                                        0
                                        • birdyB birdy

                                          @Thomas-Braun

                                          Scheint nicht so... :(

                                          pi@raspberrypi:/opt/iobroker $ npm i iobroker.zigbee@1.2.1
                                          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
                                          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.5 (node_modules/iobroker.info/node_modules/osx-temperature-sensor):
                                          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                                          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: concentrate@^0.2.3 (node_modules/unpi/node_modules/concentrate):
                                          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported engine for concentrate@0.2.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
                                          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Not compatible with your version of node/npm: concentrate@0.2.3
                                          
                                          npm ERR! code ENOTSUP
                                          npm ERR! notsup Unsupported engine for dissolve@0.3.3: wanted: {"node":"~0.10.0"} (current: {"node":"12.18.4","npm":"6.14.6"})
                                          npm ERR! notsup Not compatible with your version of node/npm: dissolve@0.3.3
                                          npm ERR! notsup Not compatible with your version of node/npm: dissolve@0.3.3
                                          npm ERR! notsup Required: {"node":"~0.10.0"}
                                          npm ERR! notsup Actual:   {"npm":"6.14.6","node":"12.18.4"}
                                          
                                          npm ERR! A complete log of this run can be found in:
                                          npm ERR!     /home/iobroker/.npm/_logs/2020-09-20T16_51_25_317Z-debug.log
                                          
                                          Thomas BraunT Online
                                          Thomas BraunT Online
                                          Thomas Braun
                                          Most Active
                                          schrieb am zuletzt editiert von Thomas Braun
                                          #47

                                          @birdy sagte in Zigbee Instanz rot nach node.js Update auf v12.18.4:

                                          Unsupported engine for concentrate@0.2.3: wanted: "node":"~0.10.0"}
                                          

                                          Da hast du übrigens den nächsten alten Hund.
                                          Wer weiß was da noch alles nach oben gespült wird.
                                          Ich würde das Ding plattmachen und ein Backup des ioBrokers einspielen. Backitup hast du ja hoffentlich am Start?

                                          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

                                          birdyB 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          689

                                          Online

                                          32.6k

                                          Benutzer

                                          82.3k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden

                                          • Du hast noch kein Konto? Registrieren

                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe