Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Harmony hub adapter lässt sich nicht installieren

    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

    Harmony hub adapter lässt sich nicht installieren

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

      Hallo,

      der harmony hub adapter lässt sich nicht installieren, kann jemand mal bitte über die Log Datei schauen und mir sagen was nicht stimmig ist?

      Danke

      goofy
      1594_npm-debug.log

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

         verbose stack Error: not found: git
        

        Git installieren.

        Log nächste mal bitte ins Forum Kopieren zwischen Code Blöcke und nicht als Datei anhängen

        –-----------------------

        Send from mobile device

        Das schöne ios hat Auto Korrektur zum k****

        Wer Schreibfehler findet darf sie behalten oder auf eBay verkaufen, mindest Umsatz 10% für die community

        1 Reply Last reply Reply Quote 0
        • G
          goofy84 last edited by

          …. sorry wie mache ich das? Über iobroker im Terminal? Wenn ja wie lautet der Befehl? Oder muss ich auf den Raspi per Putty und dort die Befehlszeile eingeben.

          Danke

          1 Reply Last reply Reply Quote 0
          • Homoran
            Homoran Global Moderator Administrators last edited by

            @goofy84:

            per Putty und dort die Befehlszeile eingeben `

            sudo apt-get install git
            

            Gruß

            Rainer

            1 Reply Last reply Reply Quote 0
            • T
              Tech-Nerd last edited by

              Update

              Ich musste in den Windows Umgebungsvariablen nochr den Pfad zu meinem installierten Git eintragen und ioBroker restarten.

              Danach lief die Installation ohne Fehler durch.

              *Update*

              Ich habe auch das Problem das er mir den Harmony Adpater nicht installieren will.

              0 info it worked if it ends with ok
              1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
              1 verbose cli   'C:\\Users\\TasKForcE\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
              1 verbose cli   'install',
              1 verbose cli   'iobroker.harmony',
              1 verbose cli   '--production',
              1 verbose cli   '--prefix',
              1 verbose cli   'U:/ioBroker' ]
              2 info using npm@5.6.0
              3 info using node@v8.9.3
              4 verbose npm-session c15e87f660b4f20d
              5 silly install loadCurrentTree
              6 silly install readGlobalPackageData
              7 http fetch GET 304 https://registry.npmjs.org/iobroker.harmony 108ms (from cache)
              8 silly pacote tag manifest for iobroker.harmony@latest fetched in 135ms
              9 silly install loadIdealTree
              10 silly install cloneCurrentTreeToIdealTree
              11 silly install loadShrinkwrap
              12 silly install loadAllDepsIntoIdealTree
              13 silly resolveWithNewModule iobroker.harmony@0.9.0 checking installable status
              14 http fetch GET 304 https://registry.npmjs.org/harmonyhubjs-client 27ms (from cache)
              15 silly pacote range manifest for harmonyhubjs-client@^1.1.10 fetched in 30ms
              16 silly resolveWithNewModule harmonyhubjs-client@1.1.10 checking installable status
              17 http fetch GET 304 https://registry.npmjs.org/harmonyhubjs-discover 76ms (from cache)
              18 silly pacote range manifest for harmonyhubjs-discover@^1.0.2 fetched in 78ms
              19 silly resolveWithNewModule harmonyhubjs-discover@1.1.1 checking installable status
              20 http fetch GET 304 https://registry.npmjs.org/semaphore 80ms (from cache)
              21 silly pacote range manifest for semaphore@~1.0.3 fetched in 81ms
              22 silly resolveWithNewModule semaphore@1.0.5 checking installable status
              23 silly fetchPackageMetaData error for ltx@git+https://github.com/swissmanu/ltx.git#cdata-for-ltx-parser No git binary found in $PATH
              24 http fetch GET 304 https://registry.npmjs.org/node-xmpp-client 47ms (from cache)
              25 silly pacote version manifest for node-xmpp-client@3.0.0 fetched in 51ms
              26 silly resolveWithNewModule node-xmpp-client@3.0.0 checking installable status
              27 http fetch GET 304 https://registry.npmjs.org/node-xmpp-stanza 54ms (from cache)
              28 silly pacote version manifest for node-xmpp-stanza@1.1.0 fetched in 55ms
              29 warn deprecated node-xmpp-stanza@1.1.0: use @xmpp/xml package <https: www.npmjs.com/package/@xmpp/xml="">30 silly resolveWithNewModule node-xmpp-stanza@1.1.0 checking installable status
              31 http fetch GET 304 https://registry.npmjs.org/q 55ms (from cache)
              32 silly pacote range manifest for q@^1.1.2 fetched in 57ms
              33 silly resolveWithNewModule q@1.5.1 checking installable status
              34 http fetch GET 304 https://registry.npmjs.org/debug 93ms (from cache)
              35 silly pacote range manifest for debug@^2.1.0 fetched in 94ms
              36 silly resolveWithNewModule debug@2.6.9 checking installable status
              37 http fetch GET 304 https://registry.npmjs.org/request 99ms (from cache)
              38 silly pacote range manifest for request@^2.48.0 fetched in 102ms
              39 silly resolveWithNewModule request@2.83.0 checking installable status
              40 verbose stack Error: No git binary found in $PATH
              40 verbose stack     at checkGit (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\pacote\lib\util\git.js:203:17)
              40 verbose stack     at spawnGit (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\pacote\lib\util\git.js:182:10)
              40 verbose stack     at pinflight (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\pacote\lib\util\git.js:114:12)
              40 verbose stack     at C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\promise-inflight\inflight.js:29:24
              40 verbose stack     at Promise._execute (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\debuggability.js:303:9)
              40 verbose stack     at Promise._resolveFromExecutor (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:483:18)
              40 verbose stack     at new Promise (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:79:10)
              40 verbose stack     at _inflight (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\promise-inflight\inflight.js:28:25)
              40 verbose stack     at C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\promise-inflight\inflight.js:22:14
              40 verbose stack     at tryCatcher (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\util.js:16:23)
              40 verbose stack     at Promise._settlePromiseFromHandler (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:512:31)
              40 verbose stack     at Promise._settlePromise (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:569:18)
              40 verbose stack     at Promise._settlePromiseCtx (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\promise.js:606:10)
              40 verbose stack     at Async._drainQueue (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:138:12)
              40 verbose stack     at Async._drainQueues (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:143:10)
              40 verbose stack     at Immediate.Async.drainQueues (C:\Users\TasKForcE\AppData\Roaming\npm\node_modules\npm\node_modules\bluebird\js\release\async.js:17:14)
              41 verbose cwd U:\
              42 verbose Windows_NT 10.0.16299
              43 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\TasKForcE\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "iobroker.harmony" "--production" "--prefix" "U:/ioBroker"
              44 verbose node v8.9.3
              45 verbose npm  v5.6.0
              46 error code ENOGIT
              47 error No git binary found in $PATH
              48 error Failed using git.
              48 error Please check if you have git installed and in your PATH.
              49 verbose exit [ 1, true ]</https:> 
              

              NPM, NodeJS und GIT habe ich jetzt mal nach https://blog.risingstack.com/node-js-wi … -tutorial/ geupdatet, aber der Fehler ist immer noch.

              Kann mir jemand weiterhelfen?

              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

              446
              Online

              31.9k
              Users

              80.1k
              Topics

              1.3m
              Posts

              4
              5
              729
              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