Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. iobroker Zigbee Adapter startet nicht

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    iobroker Zigbee Adapter startet nicht

    This topic has been deleted. Only users with topic management privileges can see it.
    • Asgothian
      Asgothian Developer @Rene 5 last edited by

      @rene-5 sagte in iobroker Zigbee Adapter startet nicht:

      PanID must have a value of 0x0001 (1) - 0xFFFE (65534), got 121012

      Das ist dein Fehler. Die Konfiguration hat eine falsche PanID

      A.

      R 1 Reply Last reply Reply Quote 0
      • R
        Rene 5 @Asgothian last edited by

        @asgothian
        habe ich geändert, leider nichts gebracht

        2025-08-06 14:38:25.844  - warn: zigbee.0 (19271) Failed to stop zigbee during startup
        2025-08-06 14:38:25.860  - info: zigbee.0 (19271) terminating
        2025-08-06 14:38:25.865  - warn: zigbee.0 (19271) Device 0x00158d00049ddc62 "RTCGQ01LM" not found.
        2025-08-06 14:38:25.866  - warn: zigbee.0 (19271) Device 0x00158d0006fe3c6b "MCCGQ11LM" not found.
        2025-08-06 14:38:25.867  - warn: zigbee.0 (19271) Device 0x00158d00079b4ae2 "RTCGQ01LM" not found.
        2025-08-06 14:38:25.868  - warn: zigbee.0 (19271) Device 0x00158d0007e62e89 "MCCGQ11LM" not found.
        2025-08-06 14:38:25.869  - warn: zigbee.0 (19271) Device 0x00158d000705d22a "MCCGQ11LM" not found.
        2025-08-06 14:38:25.871  - warn: zigbee.0 (19271) Device 0x00158d0007105f70 "MCCGQ11LM" not found.
        2025-08-06 14:38:25.872  - warn: zigbee.0 (19271) Device 0x00158d0008647c37 "MCCGQ11LM" not found.
        2025-08-06 14:38:25.874  - warn: zigbee.0 (19271) Device 0x00158d000839178d "MCCGQ11LM" not found.
        2025-08-06 14:38:25.875  - warn: zigbee.0 (19271) Device 0x00158d0008391686 "MCCGQ11LM" not found.
        2025-08-06 14:38:25.876  - warn: zigbee.0 (19271) Device 0x00158d00083911cb "MCCGQ11LM" not found.
        2025-08-06 14:38:25.878  - warn: zigbee.0 (19271) Device 0x00158d0008647d3a "MCCGQ11LM" not found.
        2025-08-06 14:38:25.879  - warn: zigbee.0 (19271) Device 0x00158d0008647cc2 "MCCGQ11LM" not found.
        2025-08-06 14:38:25.880  - warn: zigbee.0 (19271) Device 0x00158d00079b4b30 "RTCGQ01LM" not found.
        2025-08-06 14:38:25.881  - warn: zigbee.0 (19271) Device 0x00158d000445eef5 "RTCGQ01LM" not found.
        2025-08-06 14:38:25.882  - warn: zigbee.0 (19271) Device 0x00158d0002249bc9 "RTCGQ01LM" not found.
        2025-08-06 14:38:25.883  - warn: zigbee.0 (19271) Device 0x00158d0007ec8e79 "MCCGQ11LM" not found.
        2025-08-06 14:38:25.917  - warn: zigbee.0 (19271) Device 0x00158d0002f046e0 "RTCGQ01LM" not found.
        2025-08-06 14:38:25.918  - warn: zigbee.0 (19271) Device 0xf4b3b1fffe51b415 "SWV" not found.
        2025-08-06 14:38:25.956  - warn: zigbee.0 (19271) Device 0xa4c138055725ef44 "ZWV-YC" not found.
        2025-08-06 14:38:25.973  - warn: zigbee.0 (19271) Device 0xa4c138af3c4215ae "809WZT" not found.
        2025-08-06 14:38:25.984  - warn: zigbee.0 (19271) Device 0xa4c138f559c67459 "A1Z" not found.
        2025-08-06 14:38:25.985  - warn: zigbee.0 (19271) Device 0xa4c13840ac5ea693 "A1Z" not found.
        2025-08-06 14:38:25.986  - warn: zigbee.0 (19271) Device 0xa4c138a48fbe67af "A1Z" not found.
        2025-08-06 14:38:25.987  - warn: zigbee.0 (19271) Device 0xa4c138f4953fb3f8 "A1Z" not found.
        2025-08-06 14:38:26.023  - info: zigbee.0 (19271) terminating
        2025-08-06 14:38:26.140  - warn: zigbee.0 (19271) redis get zigbee.0.info.debugmessages, error - DB closed
        2025-08-06 14:38:26.187  - warn: zigbee.0 (19271) get state error: Connection is closed.
        2025-08-06 14:38:26.202  - warn: zigbee.0 (19271) get state error: Connection is closed.
        2025-08-06 14:38:26.309  - error: host.raspberrypi Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
        2025-08-06 14:38:26.309  - error: host.raspberrypi Caught by controller[1]: Error herdsman start
        2025-08-06 14:38:26.310  - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2025-08-06 14:38:26.310  - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled
        2025-08-06 14:38:56.878  - info: host.raspberrypi instance system.adapter.zigbee.0 in version "2.0.5" started with pid 19584
        2025-08-06 14:39:00.774  - info: zigbee.0 (19584) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.1, js-controller: 7.0.6
        2025-08-06 14:39:00.806  - info: zigbee.0 (19584) init localConfig
        2025-08-06 14:39:00.814  - error: zigbee.0 (19584) Serial port not selected! Go to settings page.
        2025-08-06 14:39:00.992  - info: zigbee.0 (19584)   --> transmitPower : normal
        2025-08-06 14:39:01.012  - info: zigbee.0 (19584) --- creating device debug ---
        2025-08-06 14:39:01.014  - info: zigbee.0 (19584) Starting Adapter npm ...
        2025-08-06 14:39:01.078  - info: zigbee.0 (19584) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
        2025-08-06 14:39:01.080  - info: zigbee.0 (19584) Starting Zigbee-Herdsman
        2025-08-06 14:39:01.527  - info: zigbee.0 (19584) Unable to obtain herdsman settings
        2025-08-06 14:39:01.529  - warn: zigbee.0 (19584) unable to stop zigbee-herdsman after failed startup
        2025-08-06 14:39:01.588  - error: zigbee.0 (19584) Starting zigbee-herdsman problem : USB adapter discovery error (No valid USB adapter found). Specify valid 'adapter' and 'port' in your configuration.
        2025-08-06 14:39:01.590  - error: zigbee.0 (19584) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
        2025-08-06 14:39:01.591  - error: zigbee.0 (19584) unhandled promise rejection: undefined
        2025-08-06 14:39:01.592  - error: zigbee.0 (19584) undefined
        2025-08-06 14:39:01.614  - info: zigbee.0 (19584) cleaned everything up...
        2025-08-06 14:39:01.615  - info: zigbee.0 (19584) local config saved
        2025-08-06 14:39:01.617  - info: zigbee.0 (19584) Saved local configuration data
        2025-08-06 14:39:01.618  - info: zigbee.0 (19584) terminating
        2025-08-06 14:39:01.619  - warn: zigbee.0 (19584) Terminated (UNCAUGHT_EXCEPTION): Without reason
        2025-08-06 14:39:01.979  - error: zigbee.0 (19584) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
            at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
            at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
            at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
        2025-08-06 14:39:01.991  - warn: zigbee.0 (19584) Failed to stop zigbee during startup
        2025-08-06 14:39:02.004  - info: zigbee.0 (19584) terminating
        2025-08-06 14:39:02.008  - warn: zigbee.0 (19584) Device 0x00158d00049ddc62 "RTCGQ01LM" not found.
        2025-08-06 14:39:02.009  - warn: zigbee.0 (19584) Device 0x00158d0006fe3c6b "MCCGQ11LM" not found.
        2025-08-06 14:39:02.009  - warn: zigbee.0 (19584) Device 0x00158d00079b4ae2 "RTCGQ01LM" not found.
        2025-08-06 14:39:02.010  - warn: zigbee.0 (19584) Device 0x00158d0007e62e89 "MCCGQ11LM" not found.
        2025-08-06 14:39:02.011  - warn: zigbee.0 (19584) Device 0x00158d000705d22a "MCCGQ11LM" not found.
        2025-08-06 14:39:02.011  - warn: zigbee.0 (19584) Device 0x00158d0007105f70 "MCCGQ11LM" not found.
        2025-08-06 14:39:02.012  - warn: zigbee.0 (19584) Device 0x00158d0008647c37 "MCCGQ11LM" not found.
        2025-08-06 14:39:02.013  - warn: zigbee.0 (19584) Device 0x00158d000839178d "MCCGQ11LM" not found.
        2025-08-06 14:39:02.014  - warn: zigbee.0 (19584) Device 0x00158d0008391686 "MCCGQ11LM" not found.
        2025-08-06 14:39:02.014  - warn: zigbee.0 (19584) Device 0x00158d00083911cb "MCCGQ11LM" not found.
        2025-08-06 14:39:02.015  - warn: zigbee.0 (19584) Device 0x00158d0008647d3a "MCCGQ11LM" not found.
        2025-08-06 14:39:02.016  - warn: zigbee.0 (19584) Device 0x00158d0008647cc2 "MCCGQ11LM" not found.
        2025-08-06 14:39:02.017  - warn: zigbee.0 (19584) Device 0x00158d00079b4b30 "RTCGQ01LM" not found.
        2025-08-06 14:39:02.017  - warn: zigbee.0 (19584) Device 0x00158d000445eef5 "RTCGQ01LM" not found.
        2025-08-06 14:39:02.018  - warn: zigbee.0 (19584) Device 0x00158d0002249bc9 "RTCGQ01LM" not found.
        2025-08-06 14:39:02.018  - warn: zigbee.0 (19584) Device 0x00158d0007ec8e79 "MCCGQ11LM" not found.
        2025-08-06 14:39:02.031  - warn: zigbee.0 (19584) Device 0x00158d0002f046e0 "RTCGQ01LM" not found.
        2025-08-06 14:39:02.032  - warn: zigbee.0 (19584) Device 0xf4b3b1fffe51b415 "SWV" not found.
        2025-08-06 14:39:02.083  - warn: zigbee.0 (19584) Device 0xa4c138055725ef44 "ZWV-YC" not found.
        2025-08-06 14:39:02.097  - warn: zigbee.0 (19584) Device 0xa4c138af3c4215ae "809WZT" not found.
        2025-08-06 14:39:02.106  - warn: zigbee.0 (19584) Device 0xa4c138f559c67459 "A1Z" not found.
        2025-08-06 14:39:02.107  - warn: zigbee.0 (19584) Device 0xa4c13840ac5ea693 "A1Z" not found.
        2025-08-06 14:39:02.107  - warn: zigbee.0 (19584) Device 0xa4c138a48fbe67af "A1Z" not found.
        2025-08-06 14:39:02.108  - warn: zigbee.0 (19584) Device 0xa4c138f4953fb3f8 "A1Z" not found.
        2025-08-06 14:39:02.135  - info: zigbee.0 (19584) terminating
        2025-08-06 14:39:02.157  - warn: zigbee.0 (19584) redis get zigbee.0.info.debugmessages, error - DB closed
        2025-08-06 14:39:02.242  - warn: zigbee.0 (19584) get state error: Connection is closed.
        2025-08-06 14:39:02.243  - warn: zigbee.0 (19584) get state error: Connection is closed.
        2025-08-06 14:39:02.360  - error: host.raspberrypi Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
        2025-08-06 14:39:02.360  - error: host.raspberrypi Caught by controller[1]: Error herdsman start
        2025-08-06 14:39:02.361  - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
        2025-08-06 14:39:02.361  - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled
        
        Asgothian 1 Reply Last reply Reply Quote 0
        • Asgothian
          Asgothian Developer @Rene 5 last edited by Asgothian

          @rene-5 Sag mal liest du was du da postest (bevor du es postest)?

          Hat nichts gebracht ist unsinn. Hat nicht gereicht stimmt. Aber "das ist kaputt" ist auch keine Fehlermeldung.

          Starting zigbee-herdsman problem : USB adapter discovery error (No valid USB adapter found). Specify valid 'adapter' and 'port' in your configuration.
          

          Deine gesamte Adapter-Konfiguration scheint nicht sauber zu sein.

          Hast du den Adapter überhaupt sauber konfiguriert ?

          A.

          R 1 Reply Last reply Reply Quote 0
          • R
            Rene 5 @Asgothian last edited by

            @asgothian

            Folgendes habe ich gemacht.
            Habe erstmal alles geupdatet, dann habe ich ihn gelöscht und neu installiert. Dies hat auch nicht geholfen, danach habe ich das Backup eingespielt, hilft aber auch nicht.

            Was soll ich machen?

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

              @rene-5 sagte in iobroker Zigbee Adapter startet nicht:

              @asgothian

              Folgendes habe ich gemacht.
              Habe erstmal alles geupdatet, dann habe ich ihn gelöscht und neu installiert. Dies hat auch nicht geholfen, danach habe ich das Backup eingespielt, hilft aber auch nicht.

              Was soll ich machen?

              Systematisch vorgehen an Statt einfach blind irgendwelche Aktionen durchführen.

              Dein Log sagt das die Konfiguration des Adapters nicht sauber ist, also:

              • Adapter anhalten
              • Konfiguration öffnen
              • verifizieren das die korrekten Daten eingetragen sind (Port, Typ, PanID, ExtPanID, Kanal). Wenn nicht - die korrekten Werte eintragen.
              • Konfiguration speichern
              • Adapter Starten
              • Log anschauen, hier posten.

              Alternativ:

              • Adapter 3.0.3 aus dem Latest repository installieren
              • nach [dieser Anleitung](dieser Anleitung) konfigurieren (Dabei die Teile die sich mit der Installation beschäftigen ignorieren - der Adapter ist bereits installiert). Ggf. versuchen die Konfiguration aus dem NVBackup widerherzustellen, wenn die Werte nicht bekannt sind.

              A.

              R 1 Reply Last reply Reply Quote 1
              • R
                Rene 5 @Asgothian last edited by

                @asgothian
                danke dir!

                habe ich gemacht, leider noch kein Erfolg

                code_text
                ```2025-08-06 19:08:14.184  - info: zigbee.0 (5419) init localConfig
                2025-08-06 19:08:14.193  - info: zigbee.0 (5419)   --> transmitPower : normal
                2025-08-06 19:08:14.207  - info: zigbee.0 (5419) delete old Backup files. keep only last 10
                2025-08-06 19:08:14.212  - info: zigbee.0 (5419) --- creating device debug ---
                2025-08-06 19:08:14.213  - info: zigbee.0 (5419) Starting Adapter npm ...
                2025-08-06 19:08:14.266  - info: zigbee.0 (5419) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
                2025-08-06 19:08:14.268  - info: zigbee.0 (5419) Starting Zigbee-Herdsman
                2025-08-06 19:08:24.556  - info: zigbee.0 (5419) Unable to obtain herdsman settings
                2025-08-06 19:08:24.685  - error: zigbee.0 (5419) Starting zigbee-herdsman problem : Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/serial/by-id/ usb-dresden_elektronik_ingenieurtechn_GmbH_ConBee_II_DE2448975-if00'
                2025-08-06 19:08:24.687  - error: zigbee.0 (5419) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                2025-08-06 19:08:24.687  - error: zigbee.0 (5419) unhandled promise rejection: undefined
                2025-08-06 19:08:24.688  - error: zigbee.0 (5419) undefined
                2025-08-06 19:08:24.731  - info: zigbee.0 (5419) cleaned everything up...
                2025-08-06 19:08:24.732  - info: zigbee.0 (5419) local config saved
                2025-08-06 19:08:24.733  - info: zigbee.0 (5419) Saved local configuration data
                2025-08-06 19:08:24.734  - info: zigbee.0 (5419) terminating
                2025-08-06 19:08:24.736  - warn: zigbee.0 (5419) Terminated (UNCAUGHT_EXCEPTION): Without reason
                2025-08-06 19:08:25.103  - error: zigbee.0 (5419) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
                    at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
                    at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
                    at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
                    at processTicksAndRejections (node:internal/process/task_queues:95:5)
                    at runNextTicks (node:internal/process/task_queues:64:3)
                    at listOnTimeout (node:internal/timers:545:9)
                    at processTimers (node:internal/timers:519:7)
                    at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
                2025-08-06 19:08:25.152  - info: zigbee.0 (5419) terminating
                2025-08-06 19:08:25.156  - warn: zigbee.0 (5419) Device 0x00158d00049ddc62 "RTCGQ01LM" not found.
                2025-08-06 19:08:25.157  - warn: zigbee.0 (5419) Device 0x00158d0006fe3c6b "MCCGQ11LM" not found.
                2025-08-06 19:08:25.158  - warn: zigbee.0 (5419) Device 0x00158d00079b4ae2 "RTCGQ01LM" not found.
                2025-08-06 19:08:25.158  - warn: zigbee.0 (5419) Device 0x00158d0007e62e89 "MCCGQ11LM" not found.
                2025-08-06 19:08:25.159  - warn: zigbee.0 (5419) Device 0x00158d000705d22a "MCCGQ11LM" not found.
                2025-08-06 19:08:25.159  - warn: zigbee.0 (5419) Device 0x00158d0007105f70 "MCCGQ11LM" not found.
                2025-08-06 19:08:25.160  - warn: zigbee.0 (5419) Device 0x00158d0008647c37 "MCCGQ11LM" not found.
                2025-08-06 19:08:25.161  - warn: zigbee.0 (5419) Device 0x00158d000839178d "MCCGQ11LM" not found.
                2025-08-06 19:08:25.162  - warn: zigbee.0 (5419) Device 0x00158d0008391686 "MCCGQ11LM" not found.
                2025-08-06 19:08:25.162  - warn: zigbee.0 (5419) Device 0x00158d00083911cb "MCCGQ11LM" not found.
                2025-08-06 19:08:25.163  - warn: zigbee.0 (5419) Device 0x00158d0008647d3a "MCCGQ11LM" not found.
                2025-08-06 19:08:25.164  - warn: zigbee.0 (5419) Device 0x00158d0008647cc2 "MCCGQ11LM" not found.
                2025-08-06 19:08:25.164  - warn: zigbee.0 (5419) Device 0x00158d00079b4b30 "RTCGQ01LM" not found.
                2025-08-06 19:08:25.165  - warn: zigbee.0 (5419) Device 0x00158d000445eef5 "RTCGQ01LM" not found.
                2025-08-06 19:08:25.166  - warn: zigbee.0 (5419) Device 0x00158d0002249bc9 "RTCGQ01LM" not found.
                2025-08-06 19:08:25.166  - warn: zigbee.0 (5419) Device 0x00158d0007ec8e79 "MCCGQ11LM" not found.
                2025-08-06 19:08:25.182  - warn: zigbee.0 (5419) Device 0x00158d0002f046e0 "RTCGQ01LM" not found.
                2025-08-06 19:08:25.182  - warn: zigbee.0 (5419) Device 0xf4b3b1fffe51b415 "SWV" not found.
                2025-08-06 19:08:25.242  - warn: zigbee.0 (5419) Device 0xa4c138055725ef44 "ZWV-YC" not found.
                2025-08-06 19:08:25.256  - warn: zigbee.0 (5419) Device 0xa4c138af3c4215ae "809WZT" not found.
                2025-08-06 19:08:25.264  - warn: zigbee.0 (5419) Device 0xa4c138f559c67459 "A1Z" not found.
                2025-08-06 19:08:25.265  - warn: zigbee.0 (5419) Device 0xa4c13840ac5ea693 "A1Z" not found.
                2025-08-06 19:08:25.265  - warn: zigbee.0 (5419) Device 0xa4c138a48fbe67af "A1Z" not found.
                2025-08-06 19:08:25.266  - warn: zigbee.0 (5419) Device 0xa4c138f4953fb3f8 "A1Z" not found.
                2025-08-06 19:08:25.297  - info: zigbee.0 (5419) terminating
                2025-08-06 19:08:25.327  - warn: zigbee.0 (5419) redis get zigbee.0.info.debugmessages, error - DB closed
                2025-08-06 19:08:25.359  - warn: zigbee.0 (5419) get state error: Connection is closed.
                2025-08-06 19:08:25.363  - warn: zigbee.0 (5419) get state error: Connection is closed.
                2025-08-06 19:08:25.762  - error: host.raspberrypi Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                2025-08-06 19:08:25.762  - error: host.raspberrypi Caught by controller[1]: Error herdsman start
                2025-08-06 19:08:25.763  - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                2025-08-06 19:08:25.763  - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled
                Thomas Braun 1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Rene 5 last edited by

                  @rene-5 sagte in iobroker Zigbee Adapter startet nicht:

                  /dev/serial/by-id/ usb-dresden_elektronik_ingenieurtechn_GmbH_ConBee_II_DE2448975-if00

                  Da dürfte ein Leerzeichen zu viel sein.

                  R 1 Reply Last reply Reply Quote 0
                  • R
                    Rene 5 @Thomas Braun last edited by

                    @thomas-braun
                    gut gesehen und sofort korrigiert

                    leider immer noch rot

                    2025-08-06 19:13:52.328  - info: zigbee.0 (7972) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.19.1, js-controller: 7.0.6
                    2025-08-06 19:13:52.356  - info: zigbee.0 (7972) init localConfig
                    2025-08-06 19:13:52.365  - info: zigbee.0 (7972)   --> transmitPower : normal
                    2025-08-06 19:13:52.379  - info: zigbee.0 (7972) delete old Backup files. keep only last 10
                    2025-08-06 19:13:52.383  - info: zigbee.0 (7972) --- creating device debug ---
                    2025-08-06 19:13:52.384  - info: zigbee.0 (7972) Starting Adapter npm ...
                    2025-08-06 19:13:52.438  - info: zigbee.0 (7972) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
                    2025-08-06 19:13:52.439  - info: zigbee.0 (7972) Starting Zigbee-Herdsman
                    2025-08-06 19:14:02.711  - info: zigbee.0 (7972) Unable to obtain herdsman settings
                    2025-08-06 19:14:02.822  - error: zigbee.0 (7972) Starting zigbee-herdsman problem : Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2448975-if00'
                    2025-08-06 19:14:02.824  - error: zigbee.0 (7972) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
                    2025-08-06 19:14:02.825  - error: zigbee.0 (7972) unhandled promise rejection: undefined
                    2025-08-06 19:14:02.825  - error: zigbee.0 (7972) undefined
                    2025-08-06 19:14:02.872  - info: zigbee.0 (7972) cleaned everything up...
                    2025-08-06 19:14:02.873  - info: zigbee.0 (7972) local config saved
                    2025-08-06 19:14:02.874  - info: zigbee.0 (7972) Saved local configuration data
                    2025-08-06 19:14:02.875  - info: zigbee.0 (7972) terminating
                    2025-08-06 19:14:02.877  - warn: zigbee.0 (7972) Terminated (UNCAUGHT_EXCEPTION): Without reason
                    2025-08-06 19:14:03.282  - error: zigbee.0 (7972) Failed to open the network: TypeError: Cannot read properties of undefined (reading 'permitJoin')
                        at Controller.permitJoin (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:315:35)
                        at ZigbeeController.permitJoin (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:659:33)
                        at ZigbeeController.stop (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:634:24)
                        at processTicksAndRejections (node:internal/process/task_queues:95:5)
                        at Zigbee.onUnload (/opt/iobroker/node_modules/iobroker.zigbee/main.js:1037:17)
                    2025-08-06 19:14:03.326  - info: zigbee.0 (7972) terminating
                    2025-08-06 19:14:03.330  - warn: zigbee.0 (7972) Device 0x00158d00049ddc62 "RTCGQ01LM" not found.
                    2025-08-06 19:14:03.331  - warn: zigbee.0 (7972) Device 0x00158d0006fe3c6b "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.332  - warn: zigbee.0 (7972) Device 0x00158d00079b4ae2 "RTCGQ01LM" not found.
                    2025-08-06 19:14:03.333  - warn: zigbee.0 (7972) Device 0x00158d0007e62e89 "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.334  - warn: zigbee.0 (7972) Device 0x00158d000705d22a "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.334  - warn: zigbee.0 (7972) Device 0x00158d0007105f70 "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.335  - warn: zigbee.0 (7972) Device 0x00158d0008647c37 "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.336  - warn: zigbee.0 (7972) Device 0x00158d000839178d "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.337  - warn: zigbee.0 (7972) Device 0x00158d0008391686 "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.337  - warn: zigbee.0 (7972) Device 0x00158d00083911cb "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.338  - warn: zigbee.0 (7972) Device 0x00158d0008647d3a "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.339  - warn: zigbee.0 (7972) Device 0x00158d0008647cc2 "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.340  - warn: zigbee.0 (7972) Device 0x00158d00079b4b30 "RTCGQ01LM" not found.
                    2025-08-06 19:14:03.340  - warn: zigbee.0 (7972) Device 0x00158d000445eef5 "RTCGQ01LM" not found.
                    2025-08-06 19:14:03.341  - warn: zigbee.0 (7972) Device 0x00158d0002249bc9 "RTCGQ01LM" not found.
                    2025-08-06 19:14:03.341  - warn: zigbee.0 (7972) Device 0x00158d0007ec8e79 "MCCGQ11LM" not found.
                    2025-08-06 19:14:03.354  - warn: zigbee.0 (7972) Device 0x00158d0002f046e0 "RTCGQ01LM" not found.
                    2025-08-06 19:14:03.355  - warn: zigbee.0 (7972) Device 0xf4b3b1fffe51b415 "SWV" not found.
                    2025-08-06 19:14:03.391  - warn: zigbee.0 (7972) Device 0xa4c138055725ef44 "ZWV-YC" not found.
                    2025-08-06 19:14:03.409  - warn: zigbee.0 (7972) Device 0xa4c138af3c4215ae "809WZT" not found.
                    2025-08-06 19:14:03.418  - warn: zigbee.0 (7972) Device 0xa4c138f559c67459 "A1Z" not found.
                    2025-08-06 19:14:03.419  - warn: zigbee.0 (7972) Device 0xa4c13840ac5ea693 "A1Z" not found.
                    2025-08-06 19:14:03.419  - warn: zigbee.0 (7972) Device 0xa4c138a48fbe67af "A1Z" not found.
                    2025-08-06 19:14:03.420  - warn: zigbee.0 (7972) Device 0xa4c138f4953fb3f8 "A1Z" not found.
                    2025-08-06 19:14:03.427  - info: zigbee.0 (7972) terminating
                    2025-08-06 19:14:03.450  - warn: zigbee.0 (7972) redis get zigbee.0.info.debugmessages, error - Connection is closed.
                    2025-08-06 19:14:03.479  - warn: zigbee.0 (7972) get state error: Connection is closed.
                    2025-08-06 19:14:03.483  - warn: zigbee.0 (7972) get state error: Connection is closed.
                    2025-08-06 19:14:03.843  - error: host.raspberrypi Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
                    2025-08-06 19:14:03.844  - error: host.raspberrypi Caught by controller[1]: Error herdsman start
                    2025-08-06 19:14:03.844  - error: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                    2025-08-06 19:14:03.844  - info: host.raspberrypi Restart adapter system.adapter.zigbee.0 because enabled
                    2025-08-06 19:14:03.844  - warn: host.raspberrypi Do not restart adapter system.adapter.zigbee.0 because restart loop detected
                    
                    Thomas Braun Asgothian 2 Replies Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @Rene 5 last edited by

                      @rene-5 sagte in iobroker Zigbee Adapter startet nicht:

                      Error: Device or resource busy

                      Starte die Kiste mal neu. Läuft da vielleicht noch der deconz-Kram prallel?

                      R 1 Reply Last reply Reply Quote 0
                      • R
                        Rene 5 @Thomas Braun last edited by

                        @thomas-braun

                        habe den deconz deinstalliert und jetzt läuft es, danke!

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

                          @rene-5

                          Auf serielle Geräte kann immer nur einer zugreifen.

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

                            @rene-5 sagte in iobroker Zigbee Adapter startet nicht:

                            Starting zigbee-herdsman problem : Error while opening serialport 'Error: Error: Device or resource busy, cannot open /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2448975-if00'
                            

                            Lesen scheint immer noch nicht Deins zu sein. Das Log sagt ganz deutlich warum es nicht geht.

                            A.

                            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

                            730
                            Online

                            32.0k
                            Users

                            80.5k
                            Topics

                            1.3m
                            Posts

                            4
                            16
                            185
                            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