Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. RFXCOM 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

    RFXCOM Adapter lässt sich nicht installieren

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @Forum-merlin last edited by Thomas Braun

      @forum-merlin sagte in RFXCOM Adapter lässt sich nicht installieren:

      root@vm-iobroker

      Als root führst du da gar nichts aus.

      Installier das Paket 'nodejs' nochmal neu drüber.

      F 1 Reply Last reply Reply Quote 0
      • F
        Forum-merlin @Thomas Braun last edited by

        @thomas-braun
        Naja, wer so verzweifelt über stunden rumfuchtelt macht viele komische Dinge! 🙂
        Und noch viel krasser, ich hab sogar was machen müssen was ich garnicht kapiere...

        root@vm-iobroker:/opt/iobroker# npm install -g node-gyp
npm notice
npm notice New minor version of npm available! 9.5.1 -> 9.8.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.8.0
npm notice Run npm install -g npm@9.8.0 to update!
npm notice
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /usr/lib/node_modules/node-gyp
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/node-gyp'
npm ERR!  [Error: EACCES: permission denied, mkdir '/usr/lib/node_modules/node-gyp'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'mkdir',
npm ERR!   path: '/usr/lib/node_modules/node-gyp'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2023-07-19T14_57_49_852Z-debug-0.log
root@vm-iobroker:/opt/iobroker# npm install -g node-gyp^C
root@vm-iobroker:/opt/iobroker# npm install -g npm@9.8.0
npm ERR! code EACCES
npm ERR! syscall rename
npm ERR! path /usr/lib/node_modules/npm
npm ERR! dest /usr/lib/node_modules/.npm-qUIFSsiV
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm-qUIFSsiV'
npm ERR!  [Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm-qUIFSsiV'] {
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'rename',
npm ERR!   path: '/usr/lib/node_modules/npm',
npm ERR!   dest: '/usr/lib/node_modules/.npm-qUIFSsiV'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2023-07-19T14_58_31_016Z-debug-0.log
root@vm-iobroker:

        das ging dann nur mit sudo unter root ???

        root@vm-iobroker:/opt/iobroker# sudo npm install -g npm@9.8.0

removed 17 packages, and changed 67 packages in 3s

28 packages are looking for funding
  run `npm fund` for details
root@vm-iobroker:

        Ich bin ja nicht sooo der Linux Guru, aber wie kann der super-user root noch mehr als super-user werden?

        Egaaal....

        Hier eben nochmal die drüber-installation von "nodejs"

        iobroker@vm-iobroker:/opt/iobroker$ sudo apt install nodejs
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
nodejs ist schon die neueste Version (18.16.1-deb-1nodesource1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
iobroker@vm-iobroker:/opt/iobroker$ sudo apt install nodejs

        dann

        iob stop
iob fix
iob start

        und natürlich nochmal

        iobroker@vm-iobroker:/opt/iobroker$ iobroker add rfxcom auto --debug
NPM version: 9.8.0
Installing iobroker.rfxcom@2.0.2... (System call)
npm ERR! code 1
npm ERR! path /opt/iobroker/node_modules/@serialport/bindings
npm ERR! command failed
npm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
npm ERR! prebuild-install warn install No prebuilt binaries found (target=18.16.1 runtime=node arch=x64 libc= platform=linux)
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@7.1.2
npm ERR! gyp info using node@18.16.1 | linux | x64
npm ERR! gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"
npm ERR! (node:5888) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
npm ERR! (Use `node --trace-deprecation ...` to show where the warning was created)
npm ERR! gyp info spawn /usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/@serialport/bindings/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.16.1/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.16.1',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.16.1/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/@serialport/bindings',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! Traceback (most recent call last):
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 51, in <module>
npm ERR!     sys.exit(gyp.script_main())
npm ERR!              ^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 670, in script_main
npm ERR!     return main(sys.argv[1:])
npm ERR!            ^^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 662, in main
npm ERR!     return gyp_main(args)
npm ERR!            ^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 629, in gyp_main
npm ERR!     [generator, flat_list, targets, data] = Load(
npm ERR!                                             ^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 150, in Load
npm ERR!     result = gyp.input.Load(
npm ERR!              ^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 3021, in Load
npm ERR!     LoadTargetBuildFile(
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 411, in LoadTargetBuildFile
npm ERR!     build_file_data = LoadOneBuildFile(
npm ERR!                       ^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 239, in LoadOneBuildFile
npm ERR!     build_file_contents = open(build_file_path, "rU").read()
npm ERR!                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
npm ERR! ValueError: invalid mode: 'rU' while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:351:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Linux 6.1.0-10-amd64
npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"
npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings
npm ERR! gyp ERR! node -v v18.16.1
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-19T16_14_11_491Z-debug-0.log
npm ERR! code 1
npm ERR! path /opt/iobroker/node_modules/@serialport/bindings
npm ERR! command failed
npm ERR! command sh -c prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild
npm ERR! prebuild-install warn install No prebuilt binaries found (target=18.16.1 runtime=node arch=x64 libc= platform=linux)
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@7.1.2
npm ERR! gyp info using node@18.16.1 | linux | x64
npm ERR! gyp info find Python using Python version 3.11.2 found at "/usr/bin/python3"
npm ERR! (node:5888) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
npm ERR! (Use `node --trace-deprecation ...` to show where the warning was created)
npm ERR! gyp info spawn /usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/@serialport/bindings/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.16.1/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.16.1',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/opt/iobroker/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.16.1/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/@serialport/bindings',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! Traceback (most recent call last):
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/gyp_main.py", line 51, in <module>
npm ERR!     sys.exit(gyp.script_main())
npm ERR!              ^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 670, in script_main
npm ERR!     return main(sys.argv[1:])
npm ERR!            ^^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 662, in main
npm ERR!     return gyp_main(args)
npm ERR!            ^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 629, in gyp_main
npm ERR!     [generator, flat_list, targets, data] = Load(
npm ERR!                                             ^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 150, in Load
npm ERR!     result = gyp.input.Load(
npm ERR!              ^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 3021, in Load
npm ERR!     LoadTargetBuildFile(
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 411, in LoadTargetBuildFile
npm ERR!     build_file_data = LoadOneBuildFile(
npm ERR!                       ^^^^^^^^^^^^^^^^^
npm ERR!   File "/opt/iobroker/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 239, in LoadOneBuildFile
npm ERR!     build_file_contents = open(build_file_path, "rU").read()
npm ERR!                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
npm ERR! ValueError: invalid mode: 'rU' while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/opt/iobroker/node_modules/node-gyp/lib/configure.js:351:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Linux 6.1.0-10-amd64
npm ERR! gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-gyp" "rebuild"
npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/@serialport/bindings
npm ERR! gyp ERR! node -v v18.16.1
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-07-19T16_14_11_491Z-debug-0.log
host.vm-iobroker Cannot install iobroker.rfxcom@2.0.2: 1
iobroker@vm-iobroker:/opt/iobroker$
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @Forum-merlin last edited by

          @forum-merlin sagte in RFXCOM Adapter lässt sich nicht installieren:

          Ich bin ja nicht sooo der Linux Guru, aber wie kann der super-user root noch mehr als super-user werden?
          Egaaal....

          Mannnnn.... LASST DIE SCHEISSE MIT DEM ROOT!!!!!!!!!11111

          root shell ist verboten!!!

          F 1 Reply Last reply Reply Quote 0
          • F
            Forum-merlin @Thomas Braun last edited by

            @thomas-braun
            is ja guuuut... Beruhig dich.

            Thomas Braun 2 Replies Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Forum-merlin last edited by

              @forum-merlin

              sudo apt update
sudo apt install --reinstall nodejs
iob diag

              Als USER, NICHT! als root!

              1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Forum-merlin last edited by Thomas Braun

                @forum-merlin

                nodejs repariert?
                Gibt es die Datei
                /usr/lib/python3.11/EXTERNALLY-MANAGED
                auf dem System?

                Grundsätzlich baut der adapter nämlich:

                echad@chet:/opt/iobroker $ iob add rfxcom
NPM version: 9.6.7
Installing iobroker.rfxcom@2.0.2... (System call)

added 53 packages in 41s

118 packages are looking for funding
  run `npm fund` for details
host.chet install adapter rfxcom
upload [2] rfxcom.admin /opt/iobroker/node_modules/iobroker.rfxcom/admin/index.html index.html text/html
upload [1] rfxcom.admin /opt/iobroker/node_modules/iobroker.rfxcom/admin/rfxcom.png rfxcom.png image/png
upload [0] rfxcom.admin /opt/iobroker/node_modules/iobroker.rfxcom/admin/words.js words.js application/javascript
host.chet object system.adapter.rfxcom created/updated
host.chet create instance rfxcom
host.chet object system.adapter.rfxcom.0.alive created
host.chet object system.adapter.rfxcom.0.connected created
host.chet object system.adapter.rfxcom.0.compactMode created
host.chet object system.adapter.rfxcom.0.cpu created
host.chet object system.adapter.rfxcom.0.cputime created
host.chet object system.adapter.rfxcom.0.memHeapUsed created
host.chet object system.adapter.rfxcom.0.memHeapTotal created
host.chet object system.adapter.rfxcom.0.memRss created
host.chet object system.adapter.rfxcom.0.uptime created
host.chet object system.adapter.rfxcom.0.inputCount created
host.chet object system.adapter.rfxcom.0.outputCount created
host.chet object system.adapter.rfxcom.0.eventLoopLag created
host.chet object system.adapter.rfxcom.0.sigKill created
host.chet object system.adapter.rfxcom.0.logLevel created
host.chet object rfxcom.0.info created
host.chet object rfxcom.0.info.connection created
host.chet object rfxcom.0.inclusionOn created
host.chet object rfxcom.0.rawData created
host.chet object rfxcom.0.firmwareVersion created
host.chet object rfxcom.0.availableVersion created
host.chet Set default value of rfxcom.0.info.connection: false
host.chet object system.adapter.rfxcom.0 created
echad@chet:/opt/iobroker $
                F 1 Reply Last reply Reply Quote 0
                • F
                  Forum-merlin @Thomas Braun last edited by

                  @thomas-braun
                  Nachdem jetzt dann alles irgendwie komisch wurde hab ich die VM komplett gelöscht und neu aufgesetzt.

                  ioBroker auch nach Anleitung from scratch installiert.
                  Und alles unter iobroker user mit sudo wenn es in der Anleitung erwähnt wurde.

                  Dann erstmal alles in ioBroker aktualisiert was ein update haben wollte.

                  Adapter rfxcom als erstes installiert und der geht nun.
                  Aber dafür der ZigBee nicht mehr.

                  Thomas Braun 2 Replies Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Forum-merlin last edited by

                    @forum-merlin sagte in RFXCOM Adapter lässt sich nicht installieren:

                    Und alles unter iobroker user

                    iobroker ist auch keine clevere Wahl. Es gibt schon einen system user mit dem Namen.
                    Zeig mal die

                    cat /etc/passwd | sort
                    F 1 Reply Last reply Reply Quote 0
                    • F
                      Forum-merlin @Thomas Braun last edited by

                      @thomas-braun

                      iobroker@vm-iobroker:~$ cat /etc/passwd | sort
_apt:x:42:65534::/nonexistent:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
games:x:5:60:games:/usr/games:/usr/sbin/nologin
iobroker:x:1000:1000:iobroker,,,:/home/iobroker:/bin/bash
irc:x:39:39:ircd:/run/ircd:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
messagebus:x:100:107::/nonexistent:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
root:x:0:0:root:/root:/bin/bash
_rpc:x:102:65534::/run/rpcbind:/usr/sbin/nologin
sshd:x:101:65534::/run/sshd:/usr/sbin/nologin
statd:x:103:65534::/var/lib/nfs:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
systemd-network:x:998:998:systemd Network Management:/:/usr/sbin/nologin
systemd-timesync:x:997:997:systemd Time Synchronization:/:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
iobroker@vm-iobroker:~$
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Forum-merlin last edited by Thomas Braun

                        @forum-merlin
                        Ja, ungünstig. 'Richtig' sähe der user so aus:

                        iobroker:x:1001:1001::/home/iobroker:/usr/sbin/nologin

                        Leg dir einen user an, der anders heißt. Hast du keinen schönen Vornamen von deinen Eltern bekommen? Oder haben die dich iobroker genannt? Oder nenn dich 'merlin'. Egal, alles gescheiter als den user 'iobroker' zu nennen.

                        1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Forum-merlin last edited by

                          @forum-merlin sagte in RFXCOM Adapter lässt sich nicht installieren:

                          Aber dafür der ZigBee nicht mehr.

                          Meldungen im LogFile?
                          'Geht nicht mehr' ist keine Fehlermeldung mit der irgendjemand was anfangen könnte.

                          F 1 Reply Last reply Reply Quote 0
                          • F
                            Forum-merlin @Thomas Braun last edited by

                            @thomas-braun

                            Ich wollte jetzt nicht den Thread vermischen. Deswegen hab ich jetzt hier nix geschrieben und suche grad alles möglich im Forum dazu.
                            Aber vielleicht hast du ja gleich den treffenden Blick:

                            2023-07-19 19:47:12.196  - info: host.vm-iobroker instance system.adapter.zigbee.0 started with pid 1144
2023-07-19 19:47:13.525  - info: zigbee.0 (1144) starting. Version 1.8.18 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8
2023-07-19 19:47:13.579  - info: zigbee.0 (1144) delete old Backup files. keep only last 10
2023-07-19 19:47:13.580  - info: zigbee.0 (1144) Starting Zigbee  npm ...
2023-07-19 19:47:13.697  - info: zigbee.0 (1144) Installed Version: iobroker.zigbee@1.8.18
2023-07-19 19:47:13.999  - error: zigbee.0 (1144) Configuration is not consistent with adapter state/backup!
2023-07-19 19:47:13.999  - error: zigbee.0 (1144) - PAN ID: configured=6754, adapter=510
2023-07-19 19:47:13.999  - error: zigbee.0 (1144) - Extended PAN ID: configured=00124b0018ed2fd7, adapter=00124b0018ed2fd7
2023-07-19 19:47:13.999  - error: zigbee.0 (1144) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
2023-07-19 19:47:14.000  - error: zigbee.0 (1144) - Channel List: configured=11, adapter=11
2023-07-19 19:47:14.000  - error: zigbee.0 (1144) Please update configuration to prevent further issues.
2023-07-19 19:47:14.000  - error: zigbee.0 (1144) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
2023-07-19 19:47:14.000  - error: zigbee.0 (1144) Re-commissioning your network will require re-pairing of all devices!
2023-07-19 19:47:14.001  - error: zigbee.0 (1144) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2023-07-19 19:47:14.001  - error: zigbee.0 (1144) Failed to start Zigbee
2023-07-19 19:47:14.001  - error: zigbee.0 (1144) Error herdsman start
2023-07-19 19:47:24.001  - info: zigbee.0 (1144) Try to reconnect. 1 attempts left
2023-07-19 19:47:24.002  - info: zigbee.0 (1144) Starting Zigbee  npm ...
2023-07-19 19:47:24.012  - info: zigbee.0 (1144) Installed Version: iobroker.zigbee@1.8.18
2023-07-19 19:47:24.113  - error: zigbee.0 (1144) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
2023-07-19 19:47:24.113  - error: zigbee.0 (1144) Failed to start Zigbee
2023-07-19 19:47:24.114  - error: zigbee.0 (1144) Error herdsman start
2023-07-19 19:48:45.342  - error: zigbee.0 (1144) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
2023-07-19 19:48:45.442  - info: zigbee.0 (1144) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"RFXCOM","serialNumber":"A1WJDDBR","pnpId":"usb-RFXCOM_RFXtrx433_A1WJDDBR-if00-port0","vendorId":"0403","productId":"6001"},{"path":"/dev/ttyACM0","manufacturer":"Texas Instruments","serialNumber":"__0X00124B0018ED2FD7","pnpId":"usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ED2FD7-if00","vendorId":"0451","productId":"16a8"},{"path":"/dev/ttyS0"},{"path":"/dev/ttyS1"},{"path":"/dev/ttyS2"},{"path":"/dev/ttyS3"}]
2023-07-19 19:50:58.641  - info: zigbee.0 (1144) cleaned everything up...
2023-07-19 19:50:58.643  - info: host.vm-iobroker stopInstance system.adapter.zigbee.0 (force=false, process=true)
2023-07-19 19:50:58.651  - info: host.vm-iobroker stopInstance system.adapter.zigbee.0 send kill signal
2023-07-19 19:50:58.645  - info: zigbee.0 (1144) Zigbee: disabling joining new devices.
2023-07-19 19:50:58.655  - warn: zigbee.0 (1144) Failed to stop zigbee during startup
2023-07-19 19:50:58.656  - info: zigbee.0 (1144) Got terminate signal TERMINATE_YOURSELF
2023-07-19 19:50:58.701  - info: zigbee.0 (1144) terminating
2023-07-19 19:50:58.702  - info: zigbee.0 (1144) Terminated (NO_ERROR): Without reason
2023-07-19 19:50:59.144  - info: zigbee.0 (1144) terminating
2023-07-19 19:50:59.230  - info: host.vm-iobroker instance system.adapter.zigbee.0 terminated with code 0 (NO_ERROR)
2023-07-19 19:51:22.922  - info: host.vm-iobroker instance system.adapter.zigbee.0 started with pid 1797
2023-07-19 19:51:24.257  - info: zigbee.0 (1797) starting. Version 1.8.18 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.17.0, js-controller: 5.0.8
2023-07-19 19:51:24.308  - info: zigbee.0 (1797) delete old Backup files. keep only last 10
2023-07-19 19:51:24.309  - info: zigbee.0 (1797) Starting Zigbee  npm ...
2023-07-19 19:51:24.422  - info: zigbee.0 (1797) Installed Version: iobroker.zigbee@1.8.18
2023-07-19 19:51:24.715  - error: zigbee.0 (1797) Configuration is not consistent with adapter state/backup!
2023-07-19 19:51:24.715  - error: zigbee.0 (1797) - PAN ID: configured=6754, adapter=510
2023-07-19 19:51:24.715  - error: zigbee.0 (1797) - Extended PAN ID: configured=00124b0018ed2fd7, adapter=00124b0018ed2fd7
2023-07-19 19:51:24.715  - error: zigbee.0 (1797) - Network Key: configured=01030507090b0d0f00020406080a0c0d, adapter=01030507090b0d0f00020406080a0c0d
2023-07-19 19:51:24.716  - error: zigbee.0 (1797) - Channel List: configured=11, adapter=11
2023-07-19 19:51:24.716  - error: zigbee.0 (1797) Please update configuration to prevent further issues.
2023-07-19 19:51:24.716  - error: zigbee.0 (1797) If you wish to re-commission your network, please remove coordinator backup at /opt/iobroker/iobroker-data/zigbee_0/nvbackup.json.
2023-07-19 19:51:24.716  - error: zigbee.0 (1797) Re-commissioning your network will require re-pairing of all devices!
2023-07-19 19:51:24.717  - error: zigbee.0 (1797) Starting zigbee-herdsman problem : "startup failed - configuration-adapter mismatch - see logs above for more information"
2023-07-19 19:51:24.717  - error: zigbee.0 (1797) Failed to start Zigbee
2023-07-19 19:51:24.717  - error: zigbee.0 (1797) Error herdsman start
2023-07-19 19:51:34.718  - info: zigbee.0 (1797) Try to reconnect. 1 attempts left
2023-07-19 19:51:34.719  - info: zigbee.0 (1797) Starting Zigbee  npm ...
2023-07-19 19:51:34.729  - info: zigbee.0 (1797) Installed Version: iobroker.zigbee@1.8.18
2023-07-19 19:51:34.834  - error: zigbee.0 (1797) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
2023-07-19 19:51:34.834  - error: zigbee.0 (1797) Failed to start Zigbee
2023-07-19 19:51:34.834  - error: zigbee.0 (1797) Error herdsman start
                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @Forum-merlin last edited by

                              @forum-merlin sagte in RFXCOM Adapter lässt sich nicht installieren:

                              Steht doch da:

                              2023-07-19 19:47:13.999 - error: zigbee.0 (1144) Configuration is not consistent with adapter state/backup!
                              2023-07-19 19:47:13.999 - error: zigbee.0 (1144) - PAN ID: configured=6754, adapter=510

                              Die IDs müsssen übereinstimmen.

                              F 1 Reply Last reply Reply Quote 0
                              • F
                                Forum-merlin @Thomas Braun last edited by

                                @thomas-braun
                                Danke Dir für Deine Hilfe.

                                Hab nun alles am Laufen.
                                (Allerdings hab ich einfach nochmal von vorne angefangen und dann auch nen anderen usernamen als initialen user verwendet. Ich hab im installer Script dann auch gesehen, dass da der user iobroker mitkommt. wer weiss wie sich das auswirkt)

                                Naja, wie auch immer, geht jetzt.

                                CLOSED!

                                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

                                449
                                Online

                                31.9k
                                Users

                                80.2k
                                Topics

                                1.3m
                                Posts

                                2
                                15
                                379
                                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