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. Einsteigerfragen
  4. Installation
  5. Update js-controller - "nodejs is NOT correctly installed"

NEWS

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    22
    1
    1.1k

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.1k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    14
    1
    2.4k

Update js-controller - "nodejs is NOT correctly installed"

Scheduled Pinned Locked Moved Installation
40 Posts 3 Posters 4.6k Views 2 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.
  • Thomas BraunT Thomas Braun

    @george_best

    Ja. Backports will man eigentlich nicht verwenden.

    G Offline
    G Offline
    George_Best
    wrote on last edited by
    #31

    @thomas-braun Ich versuch mich mal nun wieder nach oben zu hangeln..

    sudo -H -u iobroker npm install iobroker.js-controller
    
    

    sagt nun:

    npm WARN skipping integrity check for git dependency ssh://git@github.com/DrozmotiX/ioBroker.esphome.git
    npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
    npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
    npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
    npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
    npm WARN deprecated har-validator@5.1.5: this library is no longer supported
    npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
    npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
    npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
    npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
    npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
    npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
    npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
    npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
    npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
    npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
    npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
    npm WARN deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0
    npm ERR! code 6
    npm ERR! path /opt/iobroker/node_modules/iobroker.vis-google-fonts
    npm ERR! command failed
    npm ERR! command sh -c node main.js --install
    
    npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-03T12_24_45_263Z-debug-0.log
    
    G 1 Reply Last reply
    0
    • G George_Best

      @thomas-braun Ich versuch mich mal nun wieder nach oben zu hangeln..

      sudo -H -u iobroker npm install iobroker.js-controller
      
      

      sagt nun:

      npm WARN skipping integrity check for git dependency ssh://git@github.com/DrozmotiX/ioBroker.esphome.git
      npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
      npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
      npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
      npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
      npm WARN deprecated har-validator@5.1.5: this library is no longer supported
      npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
      npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
      npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
      npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
      npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
      npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
      npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
      npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
      npm WARN deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0
      npm ERR! code 6
      npm ERR! path /opt/iobroker/node_modules/iobroker.vis-google-fonts
      npm ERR! command failed
      npm ERR! command sh -c node main.js --install
      
      npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-03T12_24_45_263Z-debug-0.log
      
      G Offline
      G Offline
      George_Best
      wrote on last edited by
      #32

      sehr seltsam... Beim 2.

      sudo -H -u iobroker npm install iobroker.js-controller
      

      wurde der js-controller nun installiert...

      G 1 Reply Last reply
      0
      • G George_Best

        sehr seltsam... Beim 2.

        sudo -H -u iobroker npm install iobroker.js-controller
        

        wurde der js-controller nun installiert...

        G Offline
        G Offline
        George_Best
        wrote on last edited by
        #33

        Was für ein Kampf :anguished:
        Aber letztendlich doch erfolgreich - JS-Controller wurde erfolgreich geupdated.

        @Thomas-Braun Vielen, vielen Dank für deine Hilfe und deine unendliche Geduld :blush:

        Thomas BraunT 1 Reply Last reply
        0
        • G George_Best

          Was für ein Kampf :anguished:
          Aber letztendlich doch erfolgreich - JS-Controller wurde erfolgreich geupdated.

          @Thomas-Braun Vielen, vielen Dank für deine Hilfe und deine unendliche Geduld :blush:

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

          @george_best

          Gut. Dann schau jetzt per

          iob diag
          

          über Ganze nochmal drüber.

          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
          • G Offline
            G Offline
            George_Best
            wrote on last edited by
            #35

            @thomas-braun
            Das sieht es jetzt prinzipiell besser aus...

            Errors in npm tree:
            npm ERR! code ELSPROBLEMS
            npm ERR! invalid: iobroker.vis-materialdesign@0.2.62 /opt/iobroker/node_modules/iobroker.vis-materialdesign
            npm ERR! invalid: socksv5@0.0.6 /opt/iobroker/node_modules/socksv5
            npm ERR! invalid: xmlbuilder@0.4.2 /opt/iobroker/node_modules/xmlbuilder
            npm ERR! missing: cli@0.4.x, required by ipv6@3.1.1
            npm ERR! missing: cliff@0.1.x, required by ipv6@3.1.1
            
            npm ERR! A complete log of this run can be found in: /home/jonny/.npm/_logs/2023-11-03T15_35_17_056Z-debug-0.log
            
            *** ioBroker-Installation ***
            
            ioBroker Status
            iobroker is running on this host.
            
            
            Objects type: jsonl
            States  type: jsonl
            
            Core adapters versions
            js-controller:  5.0.12
            admin:          6.12.0
            javascript:     7.1.4
            
            npm ERR! code ELSPROBLEMS
            npm ERR! invalid: iobroker.vis-materialdesign@0.2.62 /opt/iobroker/node_modules/iobroker.vis-materialdesign
            
            npm ERR! A complete log of this run can be found in: /home/jonny/.npm/_logs/2023-11-03T15_35_25_269Z-debug-0.log
            Adapters from github:   1
            
            

            Aber den iobroker.vis-materialdesign kann ich nicht entfernen, da scheinbar 50% meiner Vis darauf basieren.

            Thomas BraunT 1 Reply Last reply
            0
            • G George_Best

              @thomas-braun
              Das sieht es jetzt prinzipiell besser aus...

              Errors in npm tree:
              npm ERR! code ELSPROBLEMS
              npm ERR! invalid: iobroker.vis-materialdesign@0.2.62 /opt/iobroker/node_modules/iobroker.vis-materialdesign
              npm ERR! invalid: socksv5@0.0.6 /opt/iobroker/node_modules/socksv5
              npm ERR! invalid: xmlbuilder@0.4.2 /opt/iobroker/node_modules/xmlbuilder
              npm ERR! missing: cli@0.4.x, required by ipv6@3.1.1
              npm ERR! missing: cliff@0.1.x, required by ipv6@3.1.1
              
              npm ERR! A complete log of this run can be found in: /home/jonny/.npm/_logs/2023-11-03T15_35_17_056Z-debug-0.log
              
              *** ioBroker-Installation ***
              
              ioBroker Status
              iobroker is running on this host.
              
              
              Objects type: jsonl
              States  type: jsonl
              
              Core adapters versions
              js-controller:  5.0.12
              admin:          6.12.0
              javascript:     7.1.4
              
              npm ERR! code ELSPROBLEMS
              npm ERR! invalid: iobroker.vis-materialdesign@0.2.62 /opt/iobroker/node_modules/iobroker.vis-materialdesign
              
              npm ERR! A complete log of this run can be found in: /home/jonny/.npm/_logs/2023-11-03T15_35_25_269Z-debug-0.log
              Adapters from github:   1
              
              

              Aber den iobroker.vis-materialdesign kann ich nicht entfernen, da scheinbar 50% meiner Vis darauf basieren.

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

              @george_best

              Dann installiere den nochmal.

              iob upgrade vis-materialdesign@0.5.9
              

              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

              G 1 Reply Last reply
              0
              • Thomas BraunT Thomas Braun

                @george_best

                Dann installiere den nochmal.

                iob upgrade vis-materialdesign@0.5.9
                
                G Offline
                G Offline
                George_Best
                wrote on last edited by George_Best
                #37

                @thomas-braun

                jonny@ioBroker-V2:~$ iob upgrade vis-materialdesign@0.5.9
                Adapter "vis-materialdesign" is not in the repository and cannot be updated.
                
                

                Der ist (vermutlich) von hier: https://github.com/Scrounger/ioBroker.vis-materialdesign/blob/master/README.md

                Thomas BraunT 2 Replies Last reply
                0
                • G George_Best

                  @thomas-braun

                  jonny@ioBroker-V2:~$ iob upgrade vis-materialdesign@0.5.9
                  Adapter "vis-materialdesign" is not in the repository and cannot be updated.
                  
                  

                  Der ist (vermutlich) von hier: https://github.com/Scrounger/ioBroker.vis-materialdesign/blob/master/README.md

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

                  @george_best

                  Dann zieh das aus npm / Beta rein. Der hat es nie nach Stable gebracht:

                  vis-materialdesign
                  github:	0.5.94
                  latest:	0.5.9 for 29 months
                  stable:	-.-.-
                  

                  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
                  • G George_Best

                    @thomas-braun

                    jonny@ioBroker-V2:~$ iob upgrade vis-materialdesign@0.5.9
                    Adapter "vis-materialdesign" is not in the repository and cannot be updated.
                    
                    

                    Der ist (vermutlich) von hier: https://github.com/Scrounger/ioBroker.vis-materialdesign/blob/master/README.md

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

                    @george_best

                    socksv5, ipv6 usw wirst du vermultich nicht gefixt bekommen, das ist alles zu alt und ungewartet.

                    cd /opt/iobroker && npm ls xmlbuilder
                    

                    kann man vielleicht noch angehen.

                    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

                    mcm1957M 1 Reply Last reply
                    0
                    • Thomas BraunT Thomas Braun

                      @george_best

                      socksv5, ipv6 usw wirst du vermultich nicht gefixt bekommen, das ist alles zu alt und ungewartet.

                      cd /opt/iobroker && npm ls xmlbuilder
                      

                      kann man vielleicht noch angehen.

                      mcm1957M Online
                      mcm1957M Online
                      mcm1957
                      wrote on last edited by
                      #40

                      @thomas-braun said in Update js-controller - "nodejs is NOT correctly installed":

                      @george_best

                      socksv5, ipv6 usw wirst du vermultich nicht gefixt bekommen, das ist alles zu alt und ungewartet.

                      cd /opt/iobroker && npm ls xmlbuilder
                      

                      kann man vielleicht noch angehen.

                      socksv5 und ipv6 kommen wahrscheinlich via Telegram Adapter rein.

                      Da ist was im Anmarsch. Wir haben heute entschieden den socks Proxy support aus dem Telegram Adapter rauszuschmeißen da die entsprechenden Module total veraltet sind und kein 1:1 Ersatz existiert. Falls ggF ein zu großer Aufschrei kommt müssen wir Aifwand setzen um eine Ersatzlösung zu implementieren - aber derzeit sind Resoiurcen eher knapp ...

                      Entwicklung u Betreuung: envertech-pv, hoymiles-ms, ns-client, pid, snmp Adapter;
                      Support Repositoryverwaltung.

                      Wer Danke sagen will, kann nen Kaffee spendieren: https://paypal.me/mcm1957atiobroker

                      LESEN - gute Forenbeitrage

                      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

                      894

                      Online

                      32.5k

                      Users

                      81.6k

                      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