Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14

    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

    Gelöst: Zigbee: Cannot lock port nach Update auf 1.10.14

    This topic has been deleted. Only users with topic management privileges can see it.
    • arteck
      arteck Developer Most Active @Squelsh last edited by arteck

      @squelsh sagte in Zigbee: Cannot lock port nach Update auf 1.10.14:

      Ich mach mal einen Issue beim Zigbee Adapter auf.

      uns was soll ich da deiner Meinung tun ??? handauflegen ?? die Software entwickelt sich weiter und bei so alten schinken kann schon mal sein dass da was über die Kante fält.. du fährst ja auch nicht ein 50 Jahren alten Wagen oder..

      ich bin immer wieder erstaunt .. dass ihr der meinung seid dass IMMER und ALLES weiter unterstützt wird...

      warte auf den Sonoff .. lerne die Geräte da neu an und. fettisch

      Squelsh 2 Replies Last reply Reply Quote 0
      • Squelsh
        Squelsh @arteck last edited by

        @arteck Wenn's hilft, sehr gerne :))

        Nein, im Ernst: Vielleicht kannst du mir ja sagen, wie ich weiter debuggen kann. Ich habe einiges an Linux Erfahrung, aber Null Erfahrung mit node Projekten. Die Meldung deute ich so, dass irgend ein anderes Programm das Device nutzt. Aber ich finde nichts...

        1 Reply Last reply Reply Quote 0
        • Squelsh
          Squelsh @arteck last edited by

          @arteck Mal ganz allgemein: Riesen Dank für deine Arbeit an dem Zigbee-Connector!!! Und nein, ich erwarte sicher nicht, dass OpenSource Entwickler ihre Zeit in Hardware stecken, die ur-alt ist. Aber wenn das Ding nicht mehr supported wird, dann könntest du es ja vielleicht auf eine Art Blacklist schreiben, so dass die Fehlermeldung eindeutig ist.

          Asgothian 1 Reply Last reply Reply Quote 0
          • Asgothian
            Asgothian Developer @Squelsh last edited by

            @squelsh Mach mal bitte folgendes:

            • ZIgbee adapter anhalten
            • iobroker log löschen
            • Zigbee adapter starten
            • 60 sekunden warten
            • zigbee adapter anhalten
            • log der letzten 60 sekunden hier posten

            Das was du als "offensichtlichen Fehler" oben gepostet hast ist ein Folgefehler - der echte Fehler ist vorher passiert und versteckt sich im Log.

            A.

            Squelsh 1 Reply Last reply Reply Quote 0
            • Squelsh
              Squelsh @Asgothian last edited by

              Hi @asgothian

              Hier der Log nach 60 Sek:

              2025-01-05 11:29:11.270  - info: admin.0 (1023) ==> Connected system.user.admin from ::ffff:192.168.1.218
2025-01-05 11:29:29.675  - info: admin.0 (1023) <== Disconnect system.user.admin from ::ffff:192.168.1.218
2025-01-05 11:29:36.733  - info: host.smartie "system.adapter.zigbee.1" enabled
2025-01-05 11:29:37.312  - info: host.smartie instance system.adapter.zigbee.1 in version "1.10.14" started with pid 39739
2025-01-05 11:29:41.894  - debug: zigbee.1 (39739) Redis Objects: Use Redis connection: 127.0.0.1:9001
2025-01-05 11:29:41.942  - debug: zigbee.1 (39739) Objects client ready ... initialize now
2025-01-05 11:29:41.945  - debug: zigbee.1 (39739) Objects create System PubSub Client
2025-01-05 11:29:41.946  - debug: zigbee.1 (39739) Objects create User PubSub Client
2025-01-05 11:29:41.979  - debug: zigbee.1 (39739) Objects client initialize lua scripts
2025-01-05 11:29:41.989  - debug: zigbee.1 (39739) Objects connected to redis: 127.0.0.1:9001
2025-01-05 11:29:42.021  - debug: zigbee.1 (39739) Redis States: Use Redis connection: 127.0.0.1:9000
2025-01-05 11:29:42.033  - debug: zigbee.1 (39739) States create System PubSub Client
2025-01-05 11:29:42.034  - debug: zigbee.1 (39739) States create User PubSub Client
2025-01-05 11:29:42.090  - debug: zigbee.1 (39739) States connected to redis: 127.0.0.1:9000
2025-01-05 11:29:42.134  - debug: zigbee.1 (39739) Plugin sentry Initialize Plugin (enabled=true)
2025-01-05 11:29:42.765  - info: zigbee.1 (39739) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.5, js-controller: 7.0.6
2025-01-05 11:29:42.801  - debug: zigbee.1 (39739) Using zigbee-herdsman with settings: {"network":{"panID":4576,"extendedPanID":[38,170,60,17,254,47,117,131],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_1/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_1/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0","adapter":"deconz"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false}
2025-01-05 11:29:42.892  - info: zigbee.1 (39739) delete old Backup files. keep only last 10
2025-01-05 11:29:42.895  - info: zigbee.1 (39739) Starting Zigbee  npm ...
2025-01-05 11:29:42.944  - debug: zigbee.1 (39739) Starting zigbee-herdsman...
2025-01-05 11:29:43.310  - debug: zigbee.1 (39739) Backup /opt/iobroker/iobroker-data/zigbee_1/backup_2025_01_05-11_29_42.tar.gz success
2025-01-05 11:29:43.326  - info: zigbee.1 (39739) Installed Version: iobroker.zigbee@1.10.14
2025-01-05 11:29:54.067  - error: zigbee.1 (39739) Starting zigbee-herdsman problem : "TIMEOUT"
2025-01-05 11:29:54.069  - error: zigbee.1 (39739) Failed to start Zigbee
2025-01-05 11:29:54.069  - error: zigbee.1 (39739) Error herdsman start
2025-01-05 11:30:04.074  - info: zigbee.1 (39739) Try to reconnect. 1 attempts left
2025-01-05 11:30:04.077  - info: zigbee.1 (39739) Starting Zigbee  npm ...
2025-01-05 11:30:04.092  - debug: zigbee.1 (39739) Starting zigbee-herdsman...
2025-01-05 11:30:04.121  - info: zigbee.1 (39739) Installed Version: iobroker.zigbee@1.10.14
2025-01-05 11:30:04.354  - error: zigbee.1 (39739) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
2025-01-05 11:30:04.354  - error: zigbee.1 (39739) Failed to start Zigbee
2025-01-05 11:30:04.355  - error: zigbee.1 (39739) Error herdsman start
2025-01-05 11:32:13.436  - info: host.smartie "system.adapter.zigbee.1" disabled
2025-01-05 11:32:13.438  - info: host.smartie stopInstance system.adapter.zigbee.1 (force=false, process=true)
2025-01-05 11:32:13.451  - info: zigbee.1 (39739) Got terminate signal TERMINATE_YOURSELF
2025-01-05 11:32:13.527  - info: host.smartie stopInstance system.adapter.zigbee.1 send kill signal
2025-01-05 11:32:13.455  - info: zigbee.1 (39739) cleaned everything up...
2025-01-05 11:32:13.470  - info: zigbee.1 (39739) Zigbee: disabling joining new devices.
2025-01-05 11:32:13.471  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d000325fb49 = false
2025-01-05 11:32:13.494  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d000325fb49 = 0
2025-01-05 11:32:13.512  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d0003030406 = false
2025-01-05 11:32:13.516  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d0003030406 = 0
2025-01-05 11:32:13.522  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d0003456504 = false
2025-01-05 11:32:13.526  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d0003456504 = 0
2025-01-05 11:32:13.534  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d000323c835 = false
2025-01-05 11:32:13.538  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d000323c835 = 0
2025-01-05 11:32:13.544  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d000303d8f9 = false
2025-01-05 11:32:13.548  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d000303d8f9 = 0
2025-01-05 11:32:13.553  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00035c1631 = false
2025-01-05 11:32:13.558  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00035c1631 = 0
2025-01-05 11:32:13.564  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00034d4c81 = false
2025-01-05 11:32:13.568  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00034d4c81 = 0
2025-01-05 11:32:13.573  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d000303d7db = false
2025-01-05 11:32:13.577  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d000303d7db = 0
2025-01-05 11:32:13.581  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00034d4981 = false
2025-01-05 11:32:13.586  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00034d4981 = 0
2025-01-05 11:32:13.590  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00035c0114 = false
2025-01-05 11:32:13.594  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00035c0114 = 0
2025-01-05 11:32:13.598  - debug: zigbee.1 (39739) DeviceAvailability:Publish available for 0x00158d00034d4896 = false
2025-01-05 11:32:13.602  - debug: zigbee.1 (39739) DeviceAvailability:Publish LQ for 0x00158d00034d4896 = 0
2025-01-05 11:32:13.626  - info: zigbee.1 (39739) terminating
2025-01-05 11:32:13.627  - debug: zigbee.1 (39739) Plugin sentry destroyed
2025-01-05 11:32:13.627  - info: zigbee.1 (39739) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2025-01-05 11:32:13.716  - info: zigbee.1 (39739) debug devices set to []
2025-01-05 11:32:13.956  - info: zigbee.1 (39739) terminating
2025-01-05 11:32:14.209  - info: host.smartie instance system.adapter.zigbee.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              arteck 1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active @Squelsh last edited by

                @squelsh sagte in Zigbee: Cannot lock port nach Update auf 1.10.14:

                2025-01-05 11:29:54.067 - error: zigbee.1 (39739) Starting zigbee-herdsman problem : "TIMEOUT"

                kannst du da mal ne neue Firmware flashen.. ?? conbee war nie mein Ding.. das Ding läuft auf Timeout.. ergo antwortet nicht
                @Asgothian du hast mal mit experimentiert oder ??

                Asgothian 1 Reply Last reply Reply Quote 0
                • Asgothian
                  Asgothian Developer @arteck last edited by Asgothian

                  @arteck sagte in Zigbee: Cannot lock port nach Update auf 1.10.14:

                  @squelsh sagte in Zigbee: Cannot lock port nach Update auf 1.10.14:

                  2025-01-05 11:29:54.067 - error: zigbee.1 (39739) Starting zigbee-herdsman problem : "TIMEOUT"

                  kannst du da mal ne neue Firmware flashen.. ?? conbee war nie mein Ding.. das Ding läuft auf Timeout.. ergo antwortet nicht
                  @Asgothian du hast mal mit experimentiert oder ??

                  Ganz am Anfang mal. Ich hab vielleicht irgendwo noch einen conbee 1 rumliegen - ich weiss aber das die 1.10.14 mit dem conbee prinzipiell läuft. Es kann aber sein das eine Mindest-Firmwaer notwendig ist.

                  @Squelsh Bitte ein Firmware-Update auf dem Conbee machen.

                  A.
                  Nachtrag: bitte den Adapter nicht im Debug laufen lassen - das bringt für diese Situation nix und flutet Dein Log.

                  1 Reply Last reply Reply Quote 0
                  • Squelsh
                    Squelsh last edited by

                    Danke für eure Zeit. Hab die ConBee Firmware geflashed und noch mal alles neu gestartet. Leider sieht es noch genau so aus:

                    pi@smartie:~ $ iob logs
2025-01-05 12:07:10.650  - error: host.smartie cannot call visUtils: Not exists
2025-01-05 12:07:20.246  - info: host.smartie "system.adapter.zigbee.1" enabled
2025-01-05 12:07:20.668  - info: host.smartie instance system.adapter.zigbee.1 in version "1.10.14" started with pid 41757
2025-01-05 12:07:25.355  - debug: zigbee.1 (41757) Redis Objects: Use Redis connection: 127.0.0.1:9001
2025-01-05 12:07:25.389  - debug: zigbee.1 (41757) Objects client ready ... initialize now
2025-01-05 12:07:25.393  - debug: zigbee.1 (41757) Objects create System PubSub Client
2025-01-05 12:07:25.394  - debug: zigbee.1 (41757) Objects create User PubSub Client
2025-01-05 12:07:25.426  - debug: zigbee.1 (41757) Objects client initialize lua scripts
2025-01-05 12:07:25.435  - debug: zigbee.1 (41757) Objects connected to redis: 127.0.0.1:9001
2025-01-05 12:07:25.467  - debug: zigbee.1 (41757) Redis States: Use Redis connection: 127.0.0.1:9000
2025-01-05 12:07:25.478  - debug: zigbee.1 (41757) States create System PubSub Client
2025-01-05 12:07:25.479  - debug: zigbee.1 (41757) States create User PubSub Client
2025-01-05 12:07:25.534  - debug: zigbee.1 (41757) States connected to redis: 127.0.0.1:9000
2025-01-05 12:07:25.577  - debug: zigbee.1 (41757) Plugin sentry Initialize Plugin (enabled=true)
2025-01-05 12:07:26.134  - info: zigbee.1 (41757) starting. Version 1.10.14 in /opt/iobroker/node_modules/iobroker.zigbee, node: v18.20.5, js-controller: 7.0.6
2025-01-05 12:07:26.168  - debug: zigbee.1 (41757) Using zigbee-herdsman with settings: {"network":{"panID":4576,"extendedPanID":[38,170,60,17,254,47,117,131],"channelList":[11],"networkKey":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]},"databasePath":"/opt/iobroker/iobroker-data/zigbee_1/shepherd.db","backupPath":"/opt/iobroker/iobroker-data/zigbee_1/nvbackup.json","serialPort":{"baudRate":115200,"rtscts":false,"path":"/dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_DO00KJDU-if00-port0","adapter":"deconz"},"adapter":{"forceStartWithInconsistentAdapterConfiguration":false},"legacy":false}
2025-01-05 12:07:26.259  - info: zigbee.1 (41757) delete old Backup files. keep only last 10
2025-01-05 12:07:26.262  - info: zigbee.1 (41757) Starting Zigbee  npm ...
2025-01-05 12:07:26.310  - debug: zigbee.1 (41757) Starting zigbee-herdsman...
2025-01-05 12:07:26.673  - debug: zigbee.1 (41757) Backup /opt/iobroker/iobroker-data/zigbee_1/backup_2025_01_05-12_07_26.tar.gz success
2025-01-05 12:07:26.689  - info: zigbee.1 (41757) Installed Version: iobroker.zigbee@1.10.14
2025-01-05 12:07:37.363  - error: zigbee.1 (41757) Starting zigbee-herdsman problem : "TIMEOUT"
2025-01-05 12:07:37.364  - error: zigbee.1 (41757) Failed to start Zigbee
2025-01-05 12:07:37.365  - error: zigbee.1 (41757) Error herdsman start
2025-01-05 12:07:47.369  - info: zigbee.1 (41757) Try to reconnect. 1 attempts left
2025-01-05 12:07:47.371  - info: zigbee.1 (41757) Starting Zigbee  npm ...
2025-01-05 12:07:47.377  - debug: zigbee.1 (41757) Starting zigbee-herdsman...
2025-01-05 12:07:47.391  - info: zigbee.1 (41757) Installed Version: iobroker.zigbee@1.10.14
2025-01-05 12:07:47.573  - error: zigbee.1 (41757) Starting zigbee-herdsman problem : "Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'"
2025-01-05 12:07:47.574  - error: zigbee.1 (41757) Failed to start Zigbee
2025-01-05 12:07:47.574  - error: zigbee.1 (41757) Error herdsman start
                    arteck 1 Reply Last reply Reply Quote 0
                    • arteck
                      arteck Developer Most Active @Squelsh last edited by arteck

                      @squelsh hängt der direkt am pi ?? usb3 ?? oder per kabel ??

                      kannst du mal die baudrate im adapter runnter setzten ?? mehr fällt mir nicht ein..ausser in die Tonne damit 🙂

                      1 Reply Last reply Reply Quote 0
                      • Squelsh
                        Squelsh last edited by

                        OMG! Es kann so einfach sein. DANKE @arteck !!!! Die Baudrate war das Problem.

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

                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        530
                        Online

                        31.8k
                        Users

                        80.0k
                        Topics

                        1.3m
                        Posts

                        5
                        15
                        1815
                        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