Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Fehler bei Installation i2c Adapter

    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

    Fehler bei Installation i2c Adapter

    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Chris_B @Thomas Braun last edited by

      @thomas-braun Und jetzt noch einmal über die Kommandozeile den i2c Adapter installieren versuchen?

      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @Chris_B last edited by

        @chris_b

        Versuch nochmal

        iobroker add i2c --debug
        
        C 1 Reply Last reply Reply Quote 0
        • C
          Chris_B @Thomas Braun last edited by

          @thomas-braun Irgend etwas ist mit dem Adapter nicht OK. Ich glaube nicht, dass es an meinem System liegt.

          pi@raspberrypi4-iob:~ $ iobroker add i2c --debug
          NPM version: 8.19.3
          Installing iobroker.i2c@1.2.1... (System call)
          npm ERR! code 1
          npm ERR! path /opt/iobroker/node_modules/i2c-bus
          npm ERR! command failed
          npm ERR! command sh -c -- node-gyp rebuild
          npm ERR! node:internal/modules/cjs/loader:1024
          npm ERR!   throw err;
          npm ERR!   ^
          npm ERR!
          npm ERR! Error: Cannot find module 'object-assign'
          npm ERR! Require stack:
          npm ERR! - /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/render-template.js
          npm ERR! - /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/plumbing.js
          npm ERR! - /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/index.js
          npm ERR! - /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/npmlog/log.js
          npm ERR! - /usr/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js
          npm ERR! - /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js
          npm ERR!     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1021:15)
          npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:866:27)
          npm ERR!     at Module.require (node:internal/modules/cjs/loader:1093:19)
          npm ERR!     at require (node:internal/modules/cjs/helpers:108:18)
          npm ERR!     at Object.<anonymous> (/usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/render-template.js:4:20)
          npm ERR!     at Module._compile (node:internal/modules/cjs/loader:1191:14)
          npm ERR!     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10)
          npm ERR!     at Module.load (node:internal/modules/cjs/loader:1069:32)
          npm ERR!     at Function.Module._load (node:internal/modules/cjs/loader:904:12)
          npm ERR!     at Module.require (node:internal/modules/cjs/loader:1093:19) {
          npm ERR!   code: 'MODULE_NOT_FOUND',
          npm ERR!   requireStack: [
          npm ERR!     '/usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/render-template.js',
          npm ERR!     '/usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/plumbing.js',
          npm ERR!     '/usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/gauge/index.js',
          npm ERR!     '/usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/npmlog/log.js',
          npm ERR!     '/usr/lib/node_modules/npm/node_modules/node-gyp/lib/node-gyp.js',
          npm ERR!     '/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js'
          npm ERR!   ]
          npm ERR! }
          
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /home/iobroker/.npm/_logs/2023-02-18T16_18_11_324Z-debug-0.log
          host.raspberrypi4-iob Cannot install iobroker.i2c@1.2.1: 1
          pi@raspberrypi4-iob:~ $
          
          Thomas Braun 2 Replies Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @Chris_B last edited by

            @chris_b sagte in Fehler bei Installation i2c Adapter:

            Irgend etwas ist mit dem Adapter nicht OK.

            Nö, der ist prima. Hab ich eben hier ganz sauber installiert:

            echad@chet:~ $ iobroker add i2c --debug
            NPM version: 9.4.0
            Installing iobroker.i2c@1.2.1... (System call)
            
            added 2 packages in 19s
            
            99 packages are looking for funding
              run `npm fund` for details
            host.chet install adapter i2c
            upload [4] i2c.admin /opt/iobroker/node_modules/iobroker.i2c/admin/build/index.css build/index.css text/css
            upload [3] i2c.admin /opt/iobroker/node_modules/iobroker.i2c/admin/build/index.js build/index.js application/javascript
            upload [2] i2c.admin /opt/iobroker/node_modules/iobroker.i2c/admin/i2c.png i2c.png image/png
            upload [1] i2c.admin /opt/iobroker/node_modules/iobroker.i2c/admin/index_m.html index_m.html text/html
            upload [0] i2c.admin /opt/iobroker/node_modules/iobroker.i2c/admin/style.css style.css text/css
            host.chet object system.adapter.i2c created/updated
            host.chet create instance i2c
            host.chet object system.adapter.i2c.0.alive created
            host.chet object system.adapter.i2c.0.connected created
            host.chet object system.adapter.i2c.0.compactMode created
            host.chet object system.adapter.i2c.0.cpu created
            host.chet object system.adapter.i2c.0.cputime created
            host.chet object system.adapter.i2c.0.memHeapUsed created
            host.chet object system.adapter.i2c.0.memHeapTotal created
            host.chet object system.adapter.i2c.0.memRss created
            host.chet object system.adapter.i2c.0.uptime created
            host.chet object system.adapter.i2c.0.inputCount created
            host.chet object system.adapter.i2c.0.outputCount created
            host.chet object system.adapter.i2c.0.eventLoopLag created
            host.chet object system.adapter.i2c.0.sigKill created
            host.chet object system.adapter.i2c.0.logLevel created
            host.chet object system.adapter.i2c.0 created
            echad@chet:~ $
            
            C 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Chris_B last edited by

              @chris_b sagte in Fehler bei Installation i2c Adapter:

              /home/iobroker/.npm/_logs/2023-02-18T16_18_11_324Z-debug-0.log

              Was steht denn da so drin?

              1 Reply Last reply Reply Quote 0
              • C
                Chris_B @Thomas Braun last edited by

                @thomas-braun Das steht drin:

                pi@raspberrypi4-iob:/home/iobroker/.npm/_logs $ nano 2023-02-18T16_18_11_324Z-debug-0.log
                  GNU nano 5.4                      2023-02-18T16_18_11_324Z-debug-0.log
                0 verbose cli /usr/bin/node /usr/bin/npm
                1 info using npm@8.19.3
                2 info using node@v16.19.1
                3 timing npm:load:whichnode Completed in 0ms
                4 timing config:load:defaults Completed in 5ms
                5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 4ms
                6 timing config:load:builtin Completed in 4ms
                7 timing config:load:cli Completed in 6ms
                8 timing config:load:env Completed in 1ms
                9 timing config:load:file:/opt/iobroker/.npmrc Completed in 2ms
                10 timing config:load:project Completed in 5ms
                11 timing config:load:file:/home/iobroker/.npmrc Completed in 1ms
                12 timing config:load:user Completed in 1ms
                13 timing config:load:file:/usr/etc/npmrc Completed in 0ms
                14 timing config:load:global Completed in 0ms
                15 timing config:load:validate Completed in 1ms
                16 timing config:load:credentials Completed in 3ms
                17 timing config:load:setEnvs Completed in 3ms
                18 timing config:load Completed in 31ms
                19 timing npm:load:configload Completed in 32ms
                20 timing npm:load:mkdirpcache Completed in 3ms
                21 timing npm:load:mkdirplogs Completed in 0ms
                22 verbose title npm install iobroker.i2c@1.2.1
                23 verbose argv "install" "--save-exact" "iobroker.i2c@1.2.1"
                24 timing npm:load:setTitle Completed in 3ms
                25 timing config:load:flatten Completed in 9ms
                26 timing npm:load:display Completed in 11ms
                27 verbose logfile logs-max:10 dir:/home/iobroker/.npm/_logs
                28 verbose logfile /home/iobroker/.npm/_logs/2023-02-18T16_18_11_324Z-debug-0.log
                
                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Chris_B last edited by

                  @chris_b

                  Fällt mir nix gescheites zu ein.

                  C 2 Replies Last reply Reply Quote 0
                  • C
                    Chris_B @Thomas Braun last edited by

                    @thomas-braun Trotzdem vielen Dank für Deine Unterstützung. Den Zugriff auf ein Gerät via i2c Bus kann ich vermutlich auf eine andere Weise lösen.
                    Eine komplette Neuinstallation, dann 64-bit, und iobroker Backup würde die Sache vermutlich auch lösen. Doch dazu habe ich gerade keine Lust; oder einfach jetzt gerade nicht.
                    Gruss

                    1 Reply Last reply Reply Quote 0
                    • C
                      Chris_B @Thomas Braun last edited by

                      @thomas-braun
                      Ich habe nochmals etwas zu dieser Sache:
                      Der i2c Adapter benötigt vorgängig die Installation des i2c Buses. Es wird dazu auf diesen Link verwiesen:
                      https://www.npmjs.com/package/i2c-bus#installation
                      Ich dachte ich hätte das durchgeführt, habe es aber nach all dem noch einmal versucht, mit
                      npm install i2c-bus
                      Und das, siehe da, führt nun zu folgender Fehlermeldung:

                      pi@raspberrypi4-iob:~ $ npm install i2c-bus
                      npm notice
                      npm notice New major version of npm available! 8.19.3 -> 9.6.1
                      npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.1
                      npm notice Run npm install -g npm@9.6.1 to update!
                      npm notice
                      npm ERR! code 1
                      npm ERR! path /home/pi/node_modules/i2c-bus
                      npm ERR! command failed
                      

                      Wieso wird hier npm 9.6.1 empfohlen? Laut iobroker bin ich auf der aktuellen npm Version.

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Chris_B last edited by

                        @chris_b sagte in Fehler bei Installation i2c Adapter:

                        pi@raspberrypi4-iob:~ $ npm install i2c-bus

                        Du stehst im falschen Pfad...
                        Und die Meldungen zu npm kommen immer, wenn man von Hand mit npm herumfummelt. Ignorieren.

                        1 Reply Last reply Reply Quote 0
                        • C
                          Chris_B last edited by

                          Ich habe mich nochmals dieses Themas angenommen.
                          Habe eine komplett neue Installation gestartet (Bullseye Lite, diesmal 64-bit) und danach das Backit-up Backup eingespielt. Ein paar Details gelöst, und jetzt kann ich den I2C Adapter ohne Probleme installieren.
                          Keine Ahnung, was der Grund war, aber jetzt geht es.

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

                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          529
                          Online

                          31.8k
                          Users

                          80.0k
                          Topics

                          1.3m
                          Posts

                          4
                          58
                          1912
                          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