Skip to content
  • 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
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. Problem beim harmony Installation

NEWS

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

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.9k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.1k

Problem beim harmony Installation

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
26 Beiträge 6 Kommentatoren 2.8k Aufrufe
  • Ä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.
  • wendy2702W Online
    wendy2702W Online
    wendy2702
    schrieb am zuletzt editiert von
    #17

    nicht````
    ping auf 8.8.8.8

    
    nur
    
    

    ping 8.8.8.8

    
    Wird aber gehen und DNS scheint ja auch zu klappen.
    
    Kannst du mal das machen:
    
    

    ping github.com

    
    Und hast du mal versucht das LTX zu installieren?
    
    Wenn ja bitte log posten in Code und Spoiler.

    Bitte keine Fragen per PN, die gehören ins Forum!

    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

    1 Antwort Letzte Antwort
    0
    • B Offline
      B Offline
      Biele
      schrieb am zuletzt editiert von
      #18
      root@ioBroker-Pi:~# ping 8.8.8.8
      PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
      64 bytes from 8.8.8.8: icmp_seq=1 ttl=60 time=13.5 ms
      64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=12.7 ms
      64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=13.1 ms
      ^C
      --- 8.8.8.8 ping statistics ---
      3 packets transmitted, 3 received, 0% packet loss, time 2003ms
      rtt min/avg/max/mdev = 12.781/13.159/13.517/0.300 ms
      
      
      root@ioBroker-Pi:~# ping github.com
      ping: github.com: Temporärer Fehler bei der Namensauflösung
      root@ioBroker-Pi:~#
      
      
      root@ioBroker-Pi:~# sudo npm install ltx
      /root
      └── ltx@2.7.1
      
      npm WARN enoent ENOENT: no such file or directory, open '/root/package.json'
      npm WARN root No description
      npm WARN root No repository field.
      npm WARN root No README data
      npm WARN root No license field.
      
      

      ! root@ioBroker-Pi:~# root@ioBroker-Pi:~# sudo npm install ltx
      ! -bash: root@ioBroker-Pi:~#: Kommando nicht gefunden.
      ! root@ioBroker-Pi:~# /root
      ! -bash: /root: Ist ein Verzeichnis
      ! root@ioBroker-Pi:~# └── ltx@2.7.1
      ! -bash: └──: Kommando nicht gefunden.
      ! root@ioBroker-Pi:~#
      ! root@ioBroker-Pi:~# npm WARN enoent ENOENT: no such file or directory, open '/root/package.json'
      ! Usage: npm<command></command>
      ! where <command></command>is one of:
      ! access, adduser, bin, bugs, c, cache, completion, config,
      ! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
      ! explore, get, help, help-search, i, init, install,
      ! install-test, it, link, list, ln, login, logout, ls,
      ! outdated, owner, pack, ping, prefix, prune, publish, rb,
      ! rebuild, repo, restart, root, run, run-script, s, se,
      ! search, set, shrinkwrap, star, stars, start, stop, t, team,
      ! test, tst, un, uninstall, unpublish, unstar, up, update, v,
      ! version, view, whoami
      ! npm <command></command>-h quick help on<command></command>
      ! npm -l display full usage info
      ! npm help <term>search for help on <term>npm help npm involved overview
      ! Specify configs in the ini-formatted file:
      ! /root/.npmrc
      ! or on the command line via: npm <command></command>–key value
      ! Config info can be viewed via: npm help config
      ! npm@4.6.1 /usr/local/lib/node_modules/npm
      ! root@ioBroker-Pi:~# npm WARN root No description
      ! Usage: npm<command></command>
      ! where <command></command>is one of:
      ! access, adduser, bin, bugs, c, cache, completion, config,
      ! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
      ! explore, get, help, help-search, i, init, install,
      ! install-test, it, link, list, ln, login, logout, ls,
      ! outdated, owner, pack, ping, prefix, prune, publish, rb,
      ! rebuild, repo, restart, root, run, run-script, s, se,
      ! search, set, shrinkwrap, star, stars, start, stop, t, team,
      ! test, tst, un, uninstall, unpublish, unstar, up, update, v,
      ! version, view, whoami
      ! npm <command></command>-h quick help on<command></command>
      ! npm -l display full usage info
      ! npm help <term>search for help on <term>npm help npm involved overview
      ! Specify configs in the ini-formatted file:
      ! /root/.npmrc
      ! or on the command line via: npm <command></command>--key value
      ! Config info can be viewed via: npm help config
      ! npm@4.6.1 /usr/local/lib/node_modules/npm
      ! root@ioBroker-Pi:~# npm WARN root No repository field.
      ! Usage: npm<command></command>
      ! where <command></command>is one of:
      ! access, adduser, bin, bugs, c, cache, completion, config,
      ! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
      ! explore, get, help, help-search, i, init, install,
      ! install-test, it, link, list, ln, login, logout, ls,
      ! outdated, owner, pack, ping, prefix, prune, publish, rb,
      ! rebuild, repo, restart, root, run, run-script, s, se,
      ! search, set, shrinkwrap, star, stars, start, stop, t, team,
      ! test, tst, un, uninstall, unpublish, unstar, up, update, v,
      ! version, view, whoami
      ! npm <command></command>-h quick help on<command></command>
      ! npm -l display full usage info
      ! npm help <term>search for help on <term>npm help npm involved overview
      ! Specify configs in the ini-formatted file:
      ! /root/.npmrc
      ! or on the command line via: npm <command></command>--key value
      ! Config info can be viewed via: npm help config
      ! npm@4.6.1 /usr/local/lib/node_modules/npm
      ! root@ioBroker-Pi:~# npm WARN root No README data
      ! Usage: npm<command></command>
      ! where <command></command>is one of:
      ! access, adduser, bin, bugs, c, cache, completion, config,
      ! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
      ! explore, get, help, help-search, i, init, install,
      ! install-test, it, link, list, ln, login, logout, ls,
      ! outdated, owner, pack, ping, prefix, prune, publish, rb,
      ! rebuild, repo, restart, root, run, run-script, s, se,
      ! search, set, shrinkwrap, star, stars, start, stop, t, team,
      ! test, tst, un, uninstall, unpublish, unstar, up, update, v,
      ! version, view, whoami
      ! npm <command></command>-h quick help on<command></command>
      ! npm -l display full usage info
      ! npm help <term>search for help on <term>npm help npm involved overview
      ! Specify configs in the ini-formatted file:
      ! /root/.npmrc
      ! or on the command line via: npm <command></command>--key value
      ! Config info can be viewed via: npm help config
      ! npm@4.6.1 /usr/local/lib/node_modules/npm
      ! root@ioBroker-Pi:~# npm WARN root No license field.
      ! Usage: npm<command></command>
      ! where <command></command>is one of:
      ! access, adduser, bin, bugs, c, cache, completion, config,
      ! ddp, dedupe, deprecate, dist-tag, docs, doctor, edit,
      ! explore, get, help, help-search, i, init, install,
      ! install-test, it, link, list, ln, login, logout, ls,
      ! outdated, owner, pack, ping, prefix, prune, publish, rb,
      ! rebuild, repo, restart, root, run, run-script, s, se,
      ! search, set, shrinkwrap, star, stars, start, stop, t, team,
      ! test, tst, un, uninstall, unpublish, unstar, up, update, v,
      ! version, view, whoami
      ! npm <command></command>-h quick help on<command></command>
      ! npm -l display full usage info
      ! npm help <term>search for help on <term>npm help npm involved overview
      ! Specify configs in the ini-formatted file:
      ! /root/.npmrc
      ! or on the command line via: npm <command></command>--key value
      ! Config info can be viewed via: npm help config
      ! npm@4.6.1 /usr/local/lib/node_modules/npm
      ! root@ioBroker-Pi:~# root@ioBroker-Pi:~#
      ! -bash: root@ioBroker-Pi:~#: Kommando nicht gefunden.</term></term></term></term></term></term></term></term></term></term>

      Ich hoffe das ist das was Du wolltest:-)

      1 Antwort Letzte Antwort
      0
      • B Offline
        B Offline
        Biele
        schrieb am zuletzt editiert von
        #19

        hier nochmal ping Google.de

        root@ioBroker-Pi:~# ping google.de
        PING google.de(fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003)) 56 data bytes
        64 bytes from fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003): icmp_seq=1 ttl=56 time=14.6 ms
        64 bytes from fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003): icmp_seq=2 ttl=56 time=13.3 ms
        64 bytes from fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003): icmp_seq=3 ttl=56 time=13.6 ms
        64 bytes from fra15s29-in-x03.1e100.net (2a00:1450:4001:806::2003): icmp_seq=4 ttl=56 time=13.4 ms
        ^C
        --- google.de ping statistics ---
        4 packets transmitted, 4 received, 0% packet loss, time 3004ms
        rtt min/avg/max/mdev = 13.398/13.797/14.646/0.500 ms
        
        
        1 Antwort Letzte Antwort
        0
        • B Offline
          B Offline
          Biele
          schrieb am zuletzt editiert von
          #20

          Hallo ,

          ich habe glaub das Problem gefunden .

          Lag an meiner Fritzbox Einstellungen es wurde Toredo blockiert .

          Dadurch hatte ich kein Zugriff auf GitHub.

          Grüße

          1 Antwort Letzte Antwort
          0
          • wendy2702W Online
            wendy2702W Online
            wendy2702
            schrieb am zuletzt editiert von
            #21

            Hm,

            Den Toredo Filter habe ich auch aktiv und Github geht trotzdem bei mir.

            Bitte keine Fragen per PN, die gehören ins Forum!

            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

            1 Antwort Letzte Antwort
            0
            • B Offline
              B Offline
              Biele
              schrieb am zuletzt editiert von
              #22

              Ich komm mit aktivem Filter nicht auf die Seite.

              Gruß

              1 Antwort Letzte Antwort
              0
              • wendy2702W Online
                wendy2702W Online
                wendy2702
                schrieb am zuletzt editiert von
                #23

                Komisch…

                Aber wenn es jetzt funktioniert und die Installation durchläuft ist es ja O.K.

                Bitte keine Fragen per PN, die gehören ins Forum!

                Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                1 Antwort Letzte Antwort
                0
                • D Offline
                  D Offline
                  dpt
                  schrieb am zuletzt editiert von
                  #24

                  ich musste unter dem Raspi immer für die Harmony erst ein

                  sudo apt-get install git

                  machen, dann klappte es

                  1 Antwort Letzte Antwort
                  0
                  • R Offline
                    R Offline
                    ramses
                    schrieb am zuletzt editiert von
                    #25

                    @dpt:

                    ich musste unter dem Raspi immer für die Harmony erst ein

                    sudo apt-get install git

                    machen, dann klappte es `

                    Ja der Tip ist der Regel Gold wert!

                    Das jetzige Problem ist eindeutig ein Resolver-Problem 🙂

                    1 Antwort Letzte Antwort
                    0
                    • A Offline
                      A Offline
                      aleks-83
                      schrieb am zuletzt editiert von
                      #26

                      @dpt:

                      ich musste unter dem Raspi immer für die Harmony erst ein

                      sudo apt-get install git

                      machen, dann klappte es `
                      Du bist ein Schatz! :mrgreen:

                      Ich hatte genau das gleiche Problem wie der TE.

                      ! ````
                      $ ./iobroker add harmony --host ioBroker-RasPi
                      NPM version: 4.6.1
                      npm install iobroker.harmony --production --save --prefix "/opt/iobroker" (System call)
                      npm

                      WARN addRemoteGit Error: not found: gitnpm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
                      npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
                      npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
                      npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21)
                      npm WARN addRemoteGit git+https://github.com/swissmanu/ltx.git#cdata-for-ltx-parser resetting remote /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b because of error: { Error: not found: git
                      npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
                      npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
                      npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16

                      ! npm WARN
                      addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
                      npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21) code: 'ENOGIT' }
                      ! npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefinednpm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefined
                      ! npm WARN deprecated node-xmpp-stanza@1.1.0: use @xmpp/xml package <https: www.npmjs.com/package/@xmpp/xml="">
                      npm
                      ERR! code ENOGIT
                      npm

                      ERR! not found: git
                      npm
                      ERR!
                      npm
                      ERR!
                      Failed using git.npm
                      ERR!
                      This is most likely not a problem with npm itself.npm
                      ERR!
                      Please check if you have git installed and in your PATH.

                      ! npm
                      ERR!
                      A complete log of this run can be found in:npm
                      ERR!
                      /root/.npm/_logs/2018-09-19T08_47_13_892Z-debug.log
                      host.ioBroker-RasPi install adapter harmony
                      NPM version: 4.6.1
                      npm install iobroker.harmony --production --save --prefix "/opt/iobroker" (System call)
                      npm
                      WARN
                      addRemoteGit Error: not found: gitnpm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
                      npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
                      npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
                      npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21)
                      npm WARN addRemoteGit git+https://github.com/swissmanu/ltx.git#cdata-for-ltx-parser resetting remote /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b because of error: { Error: not found: git
                      npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
                      npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
                      npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
                      npm
                      WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
                      npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21) code: 'ENOGIT' }
                      ! npm
                      ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefinednpm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefined
                      ! npm
                      WARN deprecated node-xmpp-stanza@1.1.0: use @xmpp/xml package <https: www.npmjs.com/package/@xmpp/xml="">
                      npm
                      ERR! code ENOGIT
                      npm ERR! not found: gitnpm ERR!
                      npm ERR! Failed using git.
                      npm ERR! This is most likely not a problem with npm itself.
                      npm ERR! Please check if you have git installed and in your PATH.
                      ! npm ERR! A complete log of this run can be found in:npm ERR! /root/.npm/_logs/2018-09-19T08_47_39_138Z-debug.log
                      ! host.ioBroker-RasPi install adapter harmony
                      NPM version: 4.6.1npm install iobroker.harmony --production --save --prefix "/opt/iobroker" (System call)
                      ! npm WARN addRemoteGit Error: not found: gitnpm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
                      npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
                      npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
                      npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21)
                      npm WARN addRemoteGit git+https://github.com/swissmanu/ltx.git#cdata-for-ltx-parser resetting remote /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b because of error: { Error: not found: git
                      npm WARN addRemoteGit at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
                      npm WARN addRemoteGit at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
                      npm WARN addRemoteGit at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/index.js:42:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/which/node_modules/isexe/mode.js:8:5
                      npm WARN addRemoteGit at /usr/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:284:29
                      npm WARN addRemoteGit at FSReqWrap.oncomplete (fs.js:152:21) code: 'ENOGIT' }
                      ! npm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefinednpm ERR! git clone --template=/root/.npm/_git-remotes/_templates --mirror https://github.com/swissmanu/ltx.git /root/.npm/_git-remotes/git-https-github-com-swissmanu-ltx-git-cdata-for-ltx-parser-d923f26b: undefined
                      ! npm WARN deprecated node-xmpp-stanza@1.1.0: use @xmpp/xml package <https: www.npmjs.com/package/@xmpp/xml="">
                      npm ERR! code ENOGIT
                      npm ERR! not found: gitnpm ERR!
                      npm ERR! Failed using git.
                      npm ERR! This is most likely not a problem with npm itself.
                      npm ERR! Please check if you have git installed and in your PATH.
                      ! npm ERR! A complete log of this run can be found in:
                      npm ERR! /root/.npm/_logs/2018-09-19T08_48_03_605Z-debug.log
                      ! host.ioBroker-RasPi install adapter harmony
                      ERROR: host.ioBroker-RasPi Cannot install harmony
                      ERROR: process exited with code 13</https:></https:></https:>

                      
                      Nach deinem ****sudo apt-get install git**** kam bei der Installation dann zwar ne andere Fehlermeldung, aber dann hat er offenbar von einer anderen Alternativquelle installiert und jetzt läufts.

                      = Dell Optiplex Micro - 10GB RAM - 200GB SSD - Debian VM =
                      = Node.js v20.18.3 = NPM 10.2.3 = JS Controller 7.0.6 =

                      Ubiquiti UAP-AC-LR - UAP-AC-Lite - Synology DS716+II - Fritz!Box 7490
                      Glasfaser 400

                      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
                      FAQ Cloud / IOT
                      HowTo: Node.js-Update
                      HowTo: Backup/Restore
                      Downloads
                      BLOG

                      300

                      Online

                      32.4k

                      Benutzer

                      81.4k

                      Themen

                      1.3m

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

                      • Du hast noch kein Konto? Registrieren

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