Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst] Zigbeestick nach Neuinstallation nicht ansprechbar

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    [gelöst] Zigbeestick nach Neuinstallation nicht ansprechbar

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

      Ich habe seit geraumer Zeit probleme mit dem Zigbee Stick. Mein neustes:

      Komplette Neuinstallation iob und backup eingepflegt. Der Stick wird nicht mehr im Adapter erkannt.

      
      ls -l /dev/serial/by-id/
      total 0
      lrwxrwxrwx 1 root root 13 Sep 20 14:14 usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_f211ce48ec1bef11a50ba3d94909ffd0-if00-port0 -> ../../ttyUSB0
      
      

      iob diag zeigt mir den Stick an:

      
      USB-Devices by-id:
      USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':
      
      /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_f211ce48ec1bef11a50ba3d94909ffd0-if00-port0
      
      *** ZigBee Settings ***
      
      Your zigbee.0 COM-Port is matching 'by-id'. Very good!
      Zigbee Network Settings on your coordinator/in nvbackup are:
      
      zigbee.X
      Extended Pan ID:
      *** MASKED ***
      Pan ID:
      *** MASKED ***
      Channel:
      *** MASKED ***
      Network Key:
      *** MASKED ***
      
      

      Die logs beim start/wählen des Sticks in den Einstellungen sagen:

      
      2025-09-22 11:55:13.171 - info: zigbee.0 (463319) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.19.0, js-controller: 7.0.7
      2025-09-22 11:55:13.222 - info: zigbee.0 (463319) Adapter ready - starting subsystems. Adapter is running in info mode.
      2025-09-22 11:55:13.225 - info: zigbee.0 (463319) init localConfig
      2025-09-22 11:55:13.241 - info: zigbee.0 (463319) --- creating device debug ---
      2025-09-22 11:55:13.242 - warn: zigbee.0 (463319) Zigbee autostart option not set - omitting start of zigbee substystem!
      2025-09-22 11:55:52.300 - info: admin.0 (457008) ==> Connected system.user.admin from ::ffff:192.168.178.35
      2025-09-22 11:55:52.712 - info: zigbee.0 (463319) List of port: [{"path":"/dev/ttyUSB0","manufacturer":"ITead","serialNumber":"f211ce48ec1bef11a50ba3d94909ffd0","pnpId":"usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_f211ce48ec1bef11a50ba3d94909ffd0-if00-port0","vendorId":"10c4","productId":"ea60"}]
      2025-09-22 11:55:58.949 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 (force=false, process=true)
      2025-09-22 11:55:58.956 - info: zigbee.0 (463319) Got terminate signal TERMINATE_YOURSELF
      2025-09-22 11:55:58.996 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 send kill signal
      2025-09-22 11:55:59.049 - info: admin.0 (457008) <== Disconnect system.user.admin from ::ffff:192.168.178.35
      2025-09-22 11:55:58.959 - info: zigbee.0 (463319) Halting zigbee adapter. Restart delay is at least 30 seconds.
      2025-09-22 11:55:58.963 - info: zigbee.0 (463319) cleaning everything up...
      2025-09-22 11:55:58.971 - info: zigbee.0 (463319) Saved local configuration data
      2025-09-22 11:55:59.103 - warn: zigbee.0 (463319) Failed to stop zigbee during startup
      2025-09-22 11:55:59.103 - info: zigbee.0 (463319) cleanup successful
      2025-09-22 11:55:59.104 - info: zigbee.0 (463319) terminating
      2025-09-22 11:55:59.105 - info: zigbee.0 (463319) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
      2025-09-22 11:55:59.687 - info: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
      
      

      könnte mein stick auch hinüber sein?

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

        @ianig-iro sagte in Zigbeestick nach Neuinstallation nicht ansprechbar:

        Zigbee autostart option not set - omitting start of zigbee substystem!

        Du musst die 'Startoption' im Adapter setzen.

        I 1 Reply Last reply Reply Quote 0
        • I
          Ianig Iro @Thomas Braun last edited by

          @thomas-braun wo finde ich die? in den adaptereinstellungen habe ich nichts gesehen.

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

            @ianig-iro

            Hab gerade keinen graphischen Zugriff auf den Admin, kann es nicht nachschauen.
            Auf der rechten Seite findet sich da was, wenn ich mich recht entsinne.

            I 1 Reply Last reply Reply Quote 0
            • I
              Ianig Iro @Thomas Braun last edited by

              @thomas-braun danke, ich habe es wirklich 10 mal übersehen.

              jetzt:

              
              2025-09-22 12:14:59.738 - info: zigbee.0 (466687) starting. Version 3.0.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.19.0, js-controller: 7.0.7
              2025-09-22 12:14:59.789 - info: zigbee.0 (466687) Adapter ready - starting subsystems. Adapter is running in info mode.
              2025-09-22 12:14:59.791 - info: zigbee.0 (466687) init localConfig
              2025-09-22 12:14:59.806 - info: zigbee.0 (466687) --- creating device debug ---
              2025-09-22 12:14:59.807 - info: zigbee.0 (466687) Autostart Zigbee subsystem
              2025-09-22 12:14:59.808 - info: zigbee.0 (466687) Starting Adapter npm ...
              2025-09-22 12:14:59.823 - info: zigbee.0 (466687) Installed Version: iobroker.zigbee@3.0.5 (Converters 24.8.0 Herdsman 4.4.1)
              2025-09-22 12:14:59.825 - info: zigbee.0 (466687) configured transmit power : normal
              2025-09-22 12:14:59.827 - info: zigbee.0 (466687) Starting Zigbee-Herdsman
              2025-09-22 12:15:19.653 - info: zigbee.0 (466687) Zigbee-Herdsman started successfully with Coordinator firmware version: ZStack3x0 : 20210708 (2-1.2.7.1)
              2025-09-22 12:15:19.665 - info: zigbee.0 (466687) Unable to disable LED, unsupported function.
              2025-09-22 12:15:19.666 - info: zigbee.0 (466687) No devices are currently joined.
              2025-09-22 12:15:19.670 - info: zigbee.0 (466687) Zigbee started
              2025-09-22 12:15:19.671 - info: zigbee.0 (466687) Config value 0x585c41c0b20ee24b : Network value 0x00124b002f89898f
              2025-09-22 12:15:19.675 - error: zigbee.0 (466687) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms
              2025-09-22 12:15:19.747 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 (force=false, process=true)
              2025-09-22 12:15:19.757 - info: zigbee.0 (466687) Got terminate signal TERMINATE_YOURSELF
              2025-09-22 12:15:19.759 - info: zigbee.0 (466687) Halting zigbee adapter. Restart delay is at least 30 seconds.
              2025-09-22 12:15:19.759 - info: zigbee.0 (466687) cleaning everything up...
              2025-09-22 12:15:19.761 - info: zigbee.0 (466687) Saved local configuration data
              2025-09-22 12:15:19.798 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 send kill signal
              2025-09-22 12:15:19.832 - error: zigbee.0 (466687) getGroups: caught error: TypeError: Cannot read properties of undefined (reading 'getGroups')
              2025-09-22 12:15:20.001 - info: zigbee.0 (466687) Closing Zigbee network, 0 seconds remaining
              2025-09-22 12:15:23.762 - info: zigbee.0 (466687) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
              2025-09-22 12:15:24.387 - info: host.raspberrypi instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
              
              
              arteck 1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active @Ianig Iro last edited by

                @ianig-iro Doku lesen soll da helfen ...

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

                  @arteck sagte in Zigbeestick nach Neuinstallation nicht ansprechbar:

                  @ianig-iro Doku lesen soll da helfen ...

                  Wie kommst du denn auf das dünne Brett ? Da müsste ja jemand Doku geschrieben haben. 😏

                  Scherz beiseite - Du hast ein Problem mit deiner Netzwerk Konfiguration. Steht da auch. Lesen bildet ungemein:

                  2025-09-22 12:15:19.671 - info: zigbee.0 (466687) Config value 0x585c41c0b20ee24b : Network value 0x00124b002f89898f
                  2025-09-22 12:15:19.675 - error: zigbee.0 (466687) Unable to apply ExtPanID changes: Error: SRSP - SYS - osalNvRead after 0,2ms
                  2025-09-22 12:15:19.747 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 (force=false, process=true)
                  2025-09-22 12:15:19.757 - info: zigbee.0 (466687) Got terminate signal TERMINATE_YOURSELF
                  2025-09-22 12:15:19.759 - info: zigbee.0 (466687) Halting zigbee adapter. Restart delay is at least 30 seconds.
                  

                  @Ianig-Iro
                  Du hast jetzt 2 Optionen:

                  Option A) wenn du sowieso alles neu anlernen musst: die ExtPanID aus dem Netzwerk in die Konfiguration übernehmen
                  Option B) wenn du das bestehende übernehmen willst: Alle Router im Netz vom Strom nehmen, eine ggf. vorhandene nvbackup.json löschen, den Adapter starten.

                  A.

                  I 1 Reply Last reply Reply Quote 3
                  • I
                    Ianig Iro @Asgothian last edited by

                    @asgothian danke option a hat es gelöst. den error habe ich gesehen, aber ich habe nicht verstanden, was genau das problem ist. ich wusste noch nichtmal, dass es mehrere IDs gibt.

                    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

                    671
                    Online

                    32.1k
                    Users

                    80.7k
                    Topics

                    1.3m
                    Posts

                    4
                    8
                    112
                    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