Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Hardware
    4. Zigbee Koordinator wechseln

    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

    Zigbee Koordinator wechseln

    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      el-lutschi last edited by

      Hallo zusammen,

      ich habe nun einige Threads zum Thema gefunden, aber leider bekomme ich es nicht hin.

      Ich möchte von einem Sonoff Zigbee Dongle Plus-P auf den SLZB-06 wechseln. Beide haben den gleichen Zigbee-Chip (CC2652P) und die gleiche FW Version. Wenn ich es richtig verstanden habe sollte hier doch ein Wechsel ohne neues anlernen der Zigbee-Endgeräte funktionieren.

      Was ich bisher erfolglos versucht habe:

      • Zigbee Instanz stoppen -> IP des neuen Koordinator im Adapter eingeben -> Adapter wieder starten. / Adapter startet nicht.

      • Zigbee Instanz komplett löschen -> Neu installieren ->Neuen Koordinator eintragen -> Backup einspielen. / Adapter startet aber Geräte nicht erreichbar.

      • IEEE auf dem neuen Koordinator mit der im Adapter eingetragenen ExtendedPanID flashen. / Adapter startet nicht.

      Hat vll schonmal jemand den Wechsel erfolgreich geschafft und kann mir ein paar Tipps geben wie ich es ohne neues Anlernen hinbekomme?

      Viele Grüsse

      Asgothian haus-automatisierung 2 Replies Last reply Reply Quote 0
      • Asgothian
        Asgothian Developer @el-lutschi last edited by Asgothian

        @el-lutschi Mehr details bitte:

        • was kommt an Meldungen beim Start ?
        • was hast du an Parametern im Zigbee Adapter eingetragen ?
        • Welche Adapter-Version nutzt du ?
        • Befinden sich der alte und der neue Koordinator in etwa am gleichen Platz ?

        A.
        Nachtrag: Ich mach diese Art von Wechsel bei der Entwicklung so ca. alle 2 Tage. Das geht wenn man es richtig macht ohne Probleme.

        Nachtrag 2: Log ausgaben bitte als Text in Code Tags (mit diesem button) posten !!! Screenshot 2025-07-18 at 12.08.12.png

        1 Reply Last reply Reply Quote 1
        • haus-automatisierung
          haus-automatisierung Developer Most Active @el-lutschi last edited by

          @el-lutschi sagte in Zigbee Koordinator wechseln:

          IP des neuen Koordinator im Adapter eingeben

          Mit tcp:// und dem richtigen Port? Zeig mal die Konfiguration.

          1 Reply Last reply Reply Quote 0
          • E
            el-lutschi last edited by el-lutschi

            Danke für eure Rückmeldung.

            Hier die Daten aus dem Adapter:

            Version 2.0.5
            ComPort: tcp://<IP>:<port> (stimmt)
            ExtendedPanID: DDDDDDDDDDDDDDDD
            PanID: 6753
            Kanal: 25

            Beide Koordinatoren sind genau am gleichen Platz.

            Und die Log:

            2025-07-16 17:58:15.576 - info: zigbee.0 (894) Got terminate signal TERMINATE_YOURSELF
            2025-07-16 17:58:15.576 - info: zigbee.0 (894) cleaned everything up...
            2025-07-16 17:58:15.576 - info: zigbee.0 (894) local config saved
            2025-07-16 17:58:15.577 - info: zigbee.0 (894) Saved local configuration data
            2025-07-16 17:58:15.577 - info: zigbee.0 (894) terminating
            2025-07-16 17:58:15.577 - info: zigbee.0 (894) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
            2025-07-16 17:58:15.617 - info: host.iobroker stopInstance system.adapter.zigbee.0 send kill signal
            2025-07-16 17:58:15.808 - info: zigbee.0 (894) Closing Zigbee network, 0 seconds remaining
            2025-07-16 17:58:16.107 - info: host.iobroker instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
            2025-07-16 17:58:17.456 - info: admin.0 (591) ==> Connected system.user.admin from ::ffff:10.88.88.1
            2025-07-16 17:58:30.306 - info: host.iobroker "system.adapter.zigbee.0" enabled
            2025-07-16 17:58:30.562 - info: host.iobroker instance system.adapter.zigbee.0 in version "2.0.5" started with pid 2800
            2025-07-16 17:58:31.061 - info: zigbee.0 (2800) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v20.18.0, js-controller: 7.0.6
            2025-07-16 17:58:31.066 - info: zigbee.0 (2800) init localConfig
            2025-07-16 17:58:31.067 - info: zigbee.0 (2800) --> transmitPower : high
            2025-07-16 17:58:31.069 - info: zigbee.0 (2800) delete old Backup files. keep only last 10
            2025-07-16 17:58:31.070 - info: zigbee.0 (2800) --- creating device debug ---
            2025-07-16 17:58:31.070 - info: zigbee.0 (2800) Starting Adapter npm ...
            2025-07-16 17:58:31.077 - info: zigbee.0 (2800) Installed Version: iobroker.zigbee@2.0.5 (Converters 23.6.0 Herdsman 3.5.2)
            2025-07-16 17:58:31.077 - info: zigbee.0 (2800) Starting Zigbee-Herdsman
            2025-07-16 17:58:32.921 - info: admin.0 (591) <== Disconnect system.user.admin from ::ffff:10.88.88.1
            2025-07-16 17:59:38.704 - warn: zigbee.0 (2800) Network parameters in Config : panID=6753 channel=25 extendedPanID=dededededededede
            2025-07-16 17:59:38.704 - warn: zigbee.0 (2800) Network parameters on Coordinator: panID=65534 channel=0 extendedPanID=dddddddddddddddd
            2025-07-16 17:59:38.719 - error: zigbee.0 (2800) Starting zigbee-herdsman problem : network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby (Error: AREQ - ZDO - stateChangeInd after 60000ms
            at Object.start (/opt/iobroker/node_modules/zigbee-herdsman/src/utils/waitress.ts:67:23)
            at ZnpAdapterManager.beginCommissioning (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:372:31)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            at ZnpAdapterManager.start (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:91:21)
            at ZStackAdapter.start (/opt/iobroker/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:158:16)
            at Controller.start (/opt/iobroker/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
            at ZigbeeController.start (/opt/iobroker/node_modules/iobroker.zigbee/lib/zigbeecontroller.js:171:13)
            at Immediate. (/opt/iobroker/node_modules/iobroker.zigbee/main.js:413:17))
            2025-07-16 17:59:38.720 - error: zigbee.0 (2800) 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-07-16 17:59:38.720 - error: zigbee.0 (2800) unhandled promise rejection: undefined
            2025-07-16 17:59:38.720 - error: zigbee.0 (2800) undefined
            2025-07-16 17:59:38.727 - info: zigbee.0 (2800) cleaned everything up...
            2025-07-16 17:59:38.727 - info: zigbee.0 (2800) local config saved
            2025-07-16 17:59:38.728 - info: zigbee.0 (2800) Saved local configuration data
            2025-07-16 17:59:38.728 - info: zigbee.0 (2800) terminating
            2025-07-16 17:59:38.728 - warn: zigbee.0 (2800) Terminated (UNCAUGHT_EXCEPTION): Without reason
            2025-07-16 17:59:38.776 - error: zigbee.0 (2800) 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-07-16 17:59:38.815 - info: zigbee.0 (2800) terminating
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d0008cf0a78 "WSDCGQ11LM" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x001788010b093dd8 "9290012607" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d0007e02164 "MCCGQ11LM" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d0007e09489 "MCCGQ11LM" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d000abd31a2 "MCCGQ11LM" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d0007e0e166 "MCCGQ11LM" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d0006c53dc2 "WXKG06LM" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d0007dcc871 "WXKG11LM" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d0008ce7428 "WSDCGQ11LM" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x001788010b094ff7 "9290012607" not found.
            2025-07-16 17:59:38.816 - warn: zigbee.0 (2800) Device 0x00158d0008ce73f3 "WSDCGQ11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d0008ce73f7 "WSDCGQ11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d0008ce7423 "WSDCGQ11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d0008cec1ce "WSDCGQ11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d0008913b0a "MCCGQ11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d0008913b0f "MCCGQ11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x3425b4fffeb36d65 "E160x/E170x/E190x" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d0007dccbe3 "WXKG11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d0007dccf1f "WXKG11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d0009ef7c52 "WSDCGQ11LM" not found.
            2025-07-16 17:59:38.817 - warn: zigbee.0 (2800) Device 0x00158d000ae166e0 "WSDCGQ11LM" not found.
            2025-07-16 17:59:38.818 - warn: zigbee.0 (2800) Device 0x54ef441000c76c26 "SJCGQ12LM" not found.
            2025-07-16 17:59:38.818 - warn: zigbee.0 (2800) Device 0x38398ffffe91d5e7 "LED2103G5" not found.
            2025-07-16 17:59:38.818 - warn: zigbee.0 (2800) Device 0x001788010bd086b5 "9290030675" not found.
            2025-07-16 17:59:38.818 - warn: zigbee.0 (2800) Device 0x001788010b4266c5 "929002376201" not found.
            2025-07-16 17:59:38.825 - warn: zigbee.0 (2800) Device 0x000000000177db43 "PTM 215Z" not found.
            2025-07-16 17:59:38.826 - warn: zigbee.0 (2800) Device 0x70b3d52b6004ea13 "TS011F_plug_3" not found.
            2025-07-16 17:59:38.836 - info: zigbee.0 (2800) debug devices set to []
            2025-07-16 17:59:39.257 - error: host.iobroker 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-07-16 17:59:39.257 - error: host.iobroker Caught by controller[1]: Error herdsman start
            2025-07-16 17:59:39.257 - error: host.iobroker instance system.adapter.zigbee.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
            2025-07-16 17:59:39.257 - info: host.iobroker Restart adapter system.adapter.zigbee.0 because enabled
            

            Asgothian 1 Reply Last reply Reply Quote 0
            • Asgothian
              Asgothian Developer @el-lutschi last edited by

              @el-lutschi sagte in Zigbee Koordinator wechseln:

              2025-07-16 17:59:38.704 - warn: zigbee.0 (2800) Network parameters in Config : panID=6753 channel=25 extendedPanID=dededededededede                                                                                                                                                                            
              2025-07-16 17:59:38.704 - warn: zigbee.0 (2800) Network parameters on Coordinator: panID=65534 channel=0 extendedPanID=dddddddddddddddd                                                                                                                                                                           
              2025-07-16 17:59:38.719 - error: zigbee.0 (2800) Starting zigbee-herdsman problem : network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby
              

              Da steht warum es nicht geht.

              Du hast das Problem das du mit veralteten Standard-Einstellungen (dddddddddddddd als ExtPanId) arbeitest. Das geht schief.

              Du musst die Konfguration gerade ziehen, und dann schauen ob der 'comissioning timeout' weiter kommt. Wenn ja, dann musst du die Antenne des Koordinators mit Alufolie umwickeln um den Adapter zu starten, und dann - wenn er läuft - dieses entfernen und dem Netz 24 h geben sich zu stabilisieren.

              A.

              E 1 Reply Last reply Reply Quote 0
              • E
                el-lutschi @Asgothian last edited by

                @asgothian sagte in Zigbee Koordinator wechseln:

                Du musst die Konfguration gerade ziehen

                Was genau meinst du damit?

                arteck 1 Reply Last reply Reply Quote 0
                • arteck
                  arteck Developer Most Active @el-lutschi last edited by

                  @el-lutschi flashe den SLZB-06 neu ... und steck den dann um..so dass der sich die jetzige konfig zieht..
                  der darf kein Netzwerk konfiguriert haben..

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

                  Support us

                  ioBroker
                  Community Adapters
                  Donate

                  967
                  Online

                  31.9k
                  Users

                  80.1k
                  Topics

                  1.3m
                  Posts

                  4
                  7
                  83
                  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