Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst] Installation eines Adapters funktioniert nicht

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    [gelöst] Installation eines Adapters funktioniert nicht

    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      bobby1000 last edited by

      Hallo zusammen,

      ich verstehe hier einfach nicht wo er Fehler liegt.

      Das Ergebnis ist auf das ich den Tradfri Adapter nicht installiert bekomme.

      Ich betreibe den Iobroker auf einem PC mit Windows 10. Uch habe bereits beide Wege den Adapter zu installieren versucht, komme aber mit keinem weiter.

      Hier meine bisherige Vorgehensweise:

      Variante 1.

      Ich schalte den Dienst IoBroker über Services aus.

      Danach öffne ich die Eingabeaufforderung im Admin Modus.

      Bei der Eingabeaufforderung gebe ich "iobroker install tradfri" ein

      Als Ausgabe erhalte ich folgende Meldungen incl. Fehlermeldung

      ! c:\ioBroker>iobroker install tradfri
      ! c:\ioBroker>node node_modules/iobroker.js-controller/iobroker.js install tradfri
      ! NPM version: 6.4.1
      ! npm install iobroker.tradfri –production --save --prefix "c:/ioBroker" (System
      ! call)
      ! npm WARN invalid config loglevel="notice"
      ! node-pre-gyp WARN Pre-built binaries not installable for node-aead-crypto@1.1.3
      ! and node@8.11.1 (node-v57 ABI, unknown) (falling back to source compile with nod
      ! e-gyp)
      ! node-pre-gyp WARN Hit error ENOTDIR: Cannot cd into 'c:\ioBroker\node_modules\no
      ! de-aead-crypto\build\Release\node-v57-win32-x64'
      ! gyp ERR! build error
      ! gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe fail
      ! ed with exit code: 1
      ! gyp ERR! stack at ChildProcess.onExit (C:\Users\Ruediger\AppData\Roaming\npm
      ! \node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
      ! gyp ERR! stack at emitTwo (events.js:126:13)
      ! gyp ERR! stack at ChildProcess.emit (events.js:214:7)
      ! gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_proces
      ! s.js:198:12)
      ! gyp ERR! System Windows_NT 6.1.7601
      ! gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Ruediger\App
      ! Data\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js"
      ! "build" "--fallback-to-build" "--module=c:\ioBroker\node_modules\node-aead-c
      ! rypto\build\Release\node-v57-win32-x64\node_aead_crypto.node" "--module_name
      ! =node_aead_crypto" "--module_path=c:\ioBroker\node_modules\node-aead-crypto\
      ! build\Release\node-v57-win32-x64" "--napi_version=1" "--node_abi_napi=napi"
      ! gyp ERR! cwd c:\ioBroker\node_modules\node-aead-crypto
      ! gyp ERR! node -v v8.11.1
      ! gyp ERR! node-gyp -v v3.8.0
      ! gyp ERR! not ok
      ! node-pre-gyp ERR! build error
      ! node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.e
      ! xe C:\Users\Ruediger\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp
      ! bin\node-gyp.js build --fallback-to-build --module=c:\ioBroker\node_modules\node
      ! -aead-crypto\build\Release\node-v57-win32-x64\node_aead_crypto.node --module_nam
      ! e=node_aead_crypto --module_path=c:\ioBroker\node_modules\node-aead-crypto\build
      ! \Release\node-v57-win32-x64 --napi_version=1 --node_abi_napi=napi' (1)
      ! node-pre-gyp ERR! stack at ChildProcess. <anonymous>(c:\ioBroker\node_module
      ! s\node-aead-crypto\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
      ! node-pre-gyp ERR! stack at emitTwo (events.js:126:13)
      ! node-pre-gyp ERR! stack at ChildProcess.emit (events.js:214:7)
      ! node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:925:16)
      ! node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/chi
      ! ld_process.js:209:5)
      ! node-pre-gyp ERR! System Windows_NT 6.1.7601
      ! node-pre-gyp ERR! command "C:\Program Files\nodejs\node.exe" "c:\ioBroker\n
      ! ode_modules\node-aead-crypto\node_modules\node-pre-gyp\bin\node-pre-gyp" "i
      ! nstall" "--fallback-to-build"
      ! node-pre-gyp ERR! cwd c:\ioBroker\node_modules\node-aead-crypto
      ! node-pre-gyp ERR! node -v v8.11.1
      ! node-pre-gyp ERR! node-pre-gyp -v v0.9.1
      ! node-pre-gyp ERR! not ok
      ! npm ERR! Windows_NT 6.1.7601
      ! npm ERR! argv "C:\Program Files\nodejs\node.exe" "c:\ioBroker\node_modules
      ! \npm\bin\npm-cli.js" "run" "install:default"
      ! npm ERR! node v8.11.1
      ! npm ERR! npm v2.15.12
      ! npm ERR! code ELIFECYCLE
      ! npm ERR! node-aead-crypto@1.1.3 install:default: node-pre-gyp install --fallbac ! k-to-build
      ! npm ERR! Exit status 1
      ! npm ERR!
      ! npm ERR! Failed at the node-aead-crypto@1.1.3 install:default script 'node-pre-g
      ! yp install --fallback-to-build'.
      ! npm ERR! This is most likely a problem with the node-aead-crypto package,
      ! npm ERR! not with npm itself.
      ! npm ERR! Tell the author that this fails on your system:
      ! npm ERR! node-pre-gyp install --fallback-to-build
      ! npm ERR! You can get information on how to open an issue for this project with:
      ! npm ERR! npm bugs node-aead-crypto
      ! npm ERR! Or if that isn't available, you can get their info via:
      ! npm ERR!
      ! npm ERR! npm owner ls node-aead-crypto
      ! npm ERR! There is likely additional logging output above.
      ! npm ERR! Please include the following file with any support request:
      ! npm ERR! c:\ioBroker\node_modules\node-aead-crypto\npm-debug.log
      ! child_process.js:644
      ! throw err;
      ! ^
      ! Error: Command failed: npm run install:default
      ! at checkExecSyncError (child_process.js:601:13)
      ! at execSync (child_process.js:641:13)
      ! at Object. <anonymous>(c:\ioBroker\node_modules\node-aead-crypto\lib\install
      ! .js:22:1)
      ! at Module._compile (module.js:652:30)
      ! at Object.Module._extensions..js (module.js:663:10)
      ! at Module.load (module.js:565:32)
      ! at tryModuleLoad (module.js:505:12)
      ! at Function.Module.load (module.js:497:3)
      ! at Function.Module.runMain (module.js:693:10)
      ! at startup (bootstrap_node.js:188:16)
      ! npm ERR! Windows_NT 6.1.7601
      ! npm ERR! argv "C:\Program Files\nodejs\node.exe" "c:\ioBroker\node_modules
      ! \npm\bin\npm-cli.js" "i" "--save" "node-aead-crypto@1.1.3"
      ! npm ERR! node v8.11.1
      ! npm ERR! npm v2.15.12
      ! npm ERR! code ELIFECYCLE
      ! npm ERR! node-aead-crypto@1.1.3 install: node lib/install.js
      ! npm ERR! Exit status 1
      ! npm ERR!
      ! npm ERR! Failed at the node-aead-crypto@1.1.3 install script 'node lib/install.j
      ! s'.
      ! npm ERR! This is most likely a problem with the node-aead-crypto package,
      ! npm ERR! not with npm itself.
      ! npm ERR! Tell the author that this fails on your system:
      ! npm ERR! node lib/install.js
      ! npm ERR! You can get information on how to open an issue for this project with:
      ! npm ERR! npm bugs node-aead-crypto
      ! npm ERR! Or if that isn't available, you can get their info via:
      ! npm ERR!
      ! npm ERR! npm owner ls node-aead-crypto
      ! npm ERR! There is likely additional logging output above.
      ! npm ERR! Please include the following file with any support request:
      ! npm ERR! c:\ioBroker\node_modules\iobroker.tradfri\node_modules\node-dtls-cl
      ! ient\npm-debug.log
      ! npm ERR! code ELIFECYCLE
      ! npm ERR! errno 1
      ! npm ERR! node-dtls-client@0.5.4 install: node install/postinstall.js
      ! npm ERR! Exit status 1
      ! npm ERR!
      ! npm ERR! Failed at the node-dtls-client@0.5.4 install script.
      ! npm ERR! This is probably not a problem with npm. There is likely additional log
      ! ging output above.
      ! npm ERR! A complete log of this run can be found in:
      ! npm ERR! C:\Users\Ruediger\AppData\Roaming\npm-cache_logs\2018-11-03T05_14

      ! 47_427Z-debug.log
      ! host.Ruediger-TestPC Adapter directory "null" does not exists
      ! Cannot parse null/io-package.json:Error: ENOENT: no such file or directory, open
      ! 'c:\ioBroker\null\io-package.json'
      ! c:\ioBroker></anonymous></anonymous>

      Variante 2. ist über die Weboberfläche von IoBroker

      Wenn ich dort versuche eine neue Instanz von Tradfri hinzu zu fügen erhalte ich die folgende Meldung über eine falsche NPM Version

      ! $ ./iobroker add tradfri –host Ruediger-TestPC
      ! NPM version: 5.6.0
      ! ERROR: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!NPM 5 is only supported starting with version 5.7.1!
      ! Please use "npm install -g npm@4" to downgrade npm to 4.x or
      ! use "npm install -g npm@>=5.7.1" to install a supported version of npm 5!
      ! You need to make sure to repeat this step after installing an update to NodeJS and/or npm
      ! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
      ! ERROR: process exited with code 25

      Die aktuell installierte Version ist aber

      c:\ioBroker>npm version

      { 'iobroker.inst': '1.0.4',

      npm: '6.4.1',

      ares: '1.10.1-DEV',

      cldr: '32.0',

      http_parser: '2.8.0',

      icu: '60.1',

      modules: '57',

      nghttp2: '1.25.0',

      node: '8.11.1',

      openssl: '1.0.2o',

      tz: '2017c',

      unicode: '10.0',

      uv: '1.19.1',

      v8: '6.2.414.50',

      zlib: '1.2.11' }

      Hat hier jemand eine Idee wie ich doch noch zu meinem Tradfri Adapter kommen kann?

      Vielen Dank im voraus

      1 Reply Last reply Reply Quote 0
      • arteck
        arteck Developer Most Active last edited by

        installier mal neu

        npm install -g npm@4
        

        danach probier nochmal

        1 Reply Last reply Reply Quote 0
        • AlCalzone
          AlCalzone Developer last edited by

          Es kann sein dass du zuerst die Windows build tools installieren musst.

          npm install --add-python-to-path --global windows-build-tools
          

          Gesendet von unterwegs

          1 Reply Last reply Reply Quote 0
          • Stabilostick
            Stabilostick last edited by

            Du hast zwei Probleme:

            1. Das was AlCalzone schreibt in einer administrativen Kommandozeile !! ausführen, behebt hoffentlich den gyp-Fehler.

            2. Du hast zwei npm-Versionen installiert, einmal npm 5.6.0 zusammen mit Node.js 8.11.1 im Node.js-Programmordner - und einmal npm 6.4.1 wohl mit npm install -g npm in Deinem Benutzerprofil.

            Deinstalliere zum Beheben deshalb Node.js 8.11.1 und installiere das neueste 8.er LTS. Da ist ein neueres npm enthalten.

            PS: Für die Installation von Adaptern musst/darfst Du ioBroker nicht stoppen.

            Viel Erfolg.

            1 Reply Last reply Reply Quote 0
            • B
              bobby1000 last edited by

              Vielen Dank.

              Dank der Hinweise von Stabilostick und AlCalzone läßt sich der Adapter wieder installieren.

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

              Support us

              ioBroker
              Community Adapters
              Donate
              FAQ Cloud / IOT
              HowTo: Node.js-Update
              HowTo: Backup/Restore
              Downloads
              BLOG

              886
              Online

              31.9k
              Users

              80.1k
              Topics

              1.3m
              Posts

              4
              5
              1488
              Loading More Posts
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes
              Reply
              • Reply as topic
              Log in to reply
              Community
              Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
              The ioBroker Community 2014-2023
              logo