Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Installation
    5. Proxmox Zigbee Conbee Stick einrichten: Cannot lock port

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Proxmox Zigbee Conbee Stick einrichten: Cannot lock port

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

      Hallo,
      ich bin mit meiner ioBroker Installation von einem rp4 auf eine Proxmox Umgebung gewechselt. Ich habe versucht nach dieser Anleitung https://www.iobroker.net/#de/documentation/install/proxmox.md meinen Conbee 2 Stick einzurichten, was leider nicht funktioniert. An meinem rp4 lief er einwandfrei.

      Angezeigt wird er mir:

      root@ioBroker-main:~# lsusb
      Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      Bus 001 Device 020: ID 1cf1:0030 Dresden Elektronik ZigBee gateway [ConBee II]
      Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
      Bus 001 Device 004: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      
      root@ioBroker-main:~# ls -l /dev/tty*
      crw-rw-rw- 1 nobody nogroup   5, 0 30. Jan 02:02 /dev/tty
      crw------- 1 root   tty     136, 1 30. Jan 02:33 /dev/tty1
      crw--w---- 1 root   tty     136, 2 30. Jan 02:00 /dev/tty2
      crw-rw-rw- 1 nobody nogroup 166, 0 30. Jan 02:13 /dev/ttyACM0
      

      Konfigurationsdatei auf dem main:

      arch: amd64
      cores: 4
      features: nesting=1
      hostname: ioBroker-main
      memory: 4096
      net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.188.1,hwaddr=BC:24:11:6A:05:FA,ip=192.168.188.11/24,type=veth
      onboot: 1
      ostype: debian
      rootfs: local-lvm:vm-100-disk-0,size=32G
      swap: 4096
      unprivileged: 1
      lxc.cgroup2.devices.allow: c 189:* rwm
      lxc.mount.entry: usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2400882-if00 dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2400882-if00 none bind,optional,create=file
      lxc.cgroup2.devices.allow: c 166:* rwm
      lxc.mount.entry: /dev/ttyACM0 dev/ttyACM0 none bind,optional,create=file
      

      Im Log habe ich folgende Fehlermeldung beim Starten des Adapters:

      2024-01-30 02:37:24.411 - info: host.ioBroker-main stopInstance system.adapter.zigbee.0 (force=false, process=true)
      2024-01-30 02:37:24.412 - info: zigbee.0 (1525) Got terminate signal TERMINATE_YOURSELF
      2024-01-30 02:37:24.413 - info: zigbee.0 (1525) cleaned everything up...
      2024-01-30 02:37:24.415 - info: zigbee.0 (1525) Zigbee: disabling joining new devices.
      2024-01-30 02:37:24.453 - info: zigbee.0 (1525) debug devices set to []
      2024-01-30 02:37:24.456 - info: host.ioBroker-main stopInstance system.adapter.zigbee.0 send kill signal
      2024-01-30 02:37:24.913 - info: zigbee.0 (1525) terminating
      2024-01-30 02:37:24.914 - info: zigbee.0 (1525) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2024-01-30 02:37:25.476 - info: host.ioBroker-main instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      2024-01-30 02:37:27.505 - info: host.ioBroker-main instance system.adapter.zigbee.0 started with pid 1541
      2024-01-30 02:37:28.658 - info: host.ioBroker-main instance system.adapter.info.0 started with pid 1548
      2024-01-30 02:37:29.172 - info: zigbee.0 (1541) starting. Version 1.10.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.19.0, js-controller: 5.0.17
      2024-01-30 02:37:29.214 - info: zigbee.0 (1541) delete old Backup files. keep only last 10
      2024-01-30 02:37:29.215 - info: zigbee.0 (1541) Starting Zigbee npm ...
      2024-01-30 02:37:29.244 - error: host.ioBroker-main Caught by controller[0]: /bin/sh: 1: npm: not found
      2024-01-30 02:37:29.244 - error: host.ioBroker-main Caught by controller[1]: /opt/iobroker/node_modules/iobroker.info/main.js:89
      2024-01-30 02:37:29.244 - error: host.ioBroker-main Caught by controller[1]: adapter.log.error("Could not check npm version: " + e);
      2024-01-30 02:37:29.244 - error: host.ioBroker-main Caught by controller[1]: ^
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: TypeError: Cannot read properties of undefined (reading 'log')
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: at getSystemVersions (/opt/iobroker/node_modules/iobroker.info/main.js:89:11)
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: at Object. (/opt/iobroker/node_modules/iobroker.info/main.js:58:18)
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: at Module._compile (node:internal/modules/cjs/loader:1356:14)
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: at Module._extensions..js (node:internal/modules/cjs/loader:1414:10)
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: at Module.load (node:internal/modules/cjs/loader:1197:32)
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: at Module._load (node:internal/modules/cjs/loader:1013:12)
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12)
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: at node:internal/main/run_main_module:28:49
      2024-01-30 02:37:29.245 - error: host.ioBroker-main Caught by controller[1]: Node.js v18.19.0
      2024-01-30 02:37:29.245 - error: host.ioBroker-main instance system.adapter.info.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
      2024-01-30 02:37:29.245 - info: host.ioBroker-main Restart adapter system.adapter.info.0 because enabled
      2024-01-30 02:37:29.344 - info: zigbee.0 (1541) Installed Version: iobroker.zigbee@1.10.1
      2024-01-30 02:37:39.572 - error: zigbee.0 (1541) Starting zigbee-herdsman problem : undefined
      2024-01-30 02:37:39.573 - error: zigbee.0 (1541) Failed to start Zigbee
      2024-01-30 02:37:39.573 - error: zigbee.0 (1541) Error herdsman start
      2024-01-30 02:37:49.575 - info: zigbee.0 (1541) Try to reconnect. 1 attempts left
      2024-01-30 02:37:49.575 - info: zigbee.0 (1541) Starting Zigbee npm ...
      2024-01-30 02:37:49.583 - info: zigbee.0 (1541) Installed Version: iobroker.zigbee@1.10.1
      2024-01-30 02:37:49.788 - error: zigbee.0 (1541) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
      2024-01-30 02:37:49.788 - error: zigbee.0 (1541) Failed to start Zigbee
      2024-01-30 02:37:49.788 - error: zigbee.0 (1541) Error herdsman start
      

      Adapter Einstellungen: Screenshot 2024-01-30 023944.png

      MartinP Thomas Braun 2 Replies Last reply Reply Quote 0
      • MartinP
        MartinP @Laire last edited by

        @laire bitte ls -l /dev/serial/by-id

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

          @laire

           /bin/sh: 1: npm: not found
          

          Nodejs offenbar falsch installiert.
          Und kasper nicht als root durch den Container.

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

            Danke Euch beiden, das Nodejs nicht richtig lief, hatte ich gar nicht mitgeschnitten.
            Ist korrigiert. Normalerweise nutze ich auch den User iobroker, hatte nur vergessen zu wechseln, für die Ausgaben.

            ls "ls -l /dev/serial/by-id" hat mich dann drauf gebracht, dass was mit den Rechten nicht stimmt, ist jetzt korrigiert und läuft alles.

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

              @laire sagte in Proxmox Zigbee Conbee Stick einrichten: Cannot lock port:

              Normalerweise nutze ich auch den User iobroker

              Auch der wird nicht verwendet, das ist eigentlich ein systemuser, ohne login...
              Leg dir einen vernünftigen user an und log dich damit ein und nichts anderes.

              iob diag
              

              in der Langfassung sagt nun?

              1 Reply Last reply Reply Quote 0
              • L
                lesiflo Most Active last edited by lesiflo

                gelöscht

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

                Support us

                ioBroker
                Community Adapters
                Donate

                929
                Online

                31.7k
                Users

                79.7k
                Topics

                1.3m
                Posts

                4
                6
                400
                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