NEWS
Conbee III mit zigbee-Adapter nutzen
-
Hi zusammen,
ich habe jetzt den zigbee-Adapter auf Version 3.4.5 aktualisiert.
root wird nicht mehr genutzt. iob fix wurde durchgeführt.Log mit Typ "Deconz/Conbee":
iobroker@IO-BROKER:~$ tail -n 25 /opt/iobroker/log/iobroker.current.log 2026-06-05 10:54:56.253 - info: host.IO-BROKER "system.adapter.zigbee.0" disabled 2026-06-05 10:54:56.254 - info: host.IO-BROKER stopInstance system.adapter.zigbee.0 (force=false, process=true) 2026-06-05 10:54:56.256 - info: zigbee.0 (2603) Got terminate signal TERMINATE_YOURSELF 2026-06-05 10:54:56.258 - info: zigbee.0 (2603) Halting zigbee adapter. Restart delay is at least 30 seconds. 2026-06-05 10:54:56.258 - info: zigbee.0 (2603) cleaning everything up 2026-06-05 10:54:56.258 - info: zigbee.0 (2603) zigbecontroller stopped successfully - ZH was not running 2026-06-05 10:54:56.258 - info: zigbee.0 (2603) cleanup successful 2026-06-05 10:54:56.258 - info: zigbee.0 (2603) terminating 2026-06-05 10:54:56.259 - info: zigbee.0 (2603) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2026-06-05 10:54:56.296 - info: host.IO-BROKER stopInstance system.adapter.zigbee.0 send kill signal 2026-06-05 10:54:56.758 - info: zigbee.0 (2603) Saved local configuration data 2026-06-05 10:54:56.795 - info: host.IO-BROKER instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-06-05 10:55:02.422 - info: host.IO-BROKER "system.adapter.zigbee.0" enabled 2026-06-05 10:55:02.628 - info: host.IO-BROKER instance system.adapter.zigbee.0 in version "3.4.5" started with pid 2648 2026-06-05 10:55:03.515 - info: zigbee.0 (2648) starting. Version 3.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.22.2, js-controller: 7.0.7 2026-06-05 10:55:03.524 - info: zigbee.0 (2648) init localConfig 2026-06-05 10:55:03.539 - info: zigbee.0 (2648) Adapter ready - starting subsystems. Adapter is running in info mode. 2026-06-05 10:55:03.561 - info: zigbee.0 (2648) delete old Backup files. keep only last 10 2026-06-05 10:55:03.562 - info: zigbee.0 (2648) Autostart Zigbee subsystem 2026-06-05 10:55:03.563 - info: zigbee.0 (2648) Starting Adapter npm ... 2026-06-05 10:55:03.572 - info: zigbee.0 (2648) Installed Version: iobroker.zigbee@3.4.5 (Converters 26.62.0 Herdsman 10.3.0) 2026-06-05 10:55:03.573 - info: zigbee.0 (2648) configured transmit power : normal 2026-06-05 10:55:03.573 - info: zigbee.0 (2648) Starting Zigbee-Herdsman iobroker@IO-BROKER:~$ tail -n 20 /opt/iobroker/log/iobroker.current.log 2026-06-05 10:55:03.563 - info: zigbee.0 (2648) Starting Adapter npm ... 2026-06-05 10:55:03.572 - info: zigbee.0 (2648) Installed Version: iobroker.zigbee@3.4.5 (Converters 26.62.0 Herdsman 10.3.0) 2026-06-05 10:55:03.573 - info: zigbee.0 (2648) configured transmit power : normal 2026-06-05 10:55:03.573 - info: zigbee.0 (2648) Starting Zigbee-Herdsman 2026-06-05 10:55:09.801 - info: shelly.0 (2291) [authEnabled] 192.168.126.63 (shellypill / shellypill-pool / shellypill#pool#1): This device is not protected via restricted login (see adapter documentation for details) 2026-06-05 10:55:23.840 - info: zigbee.0 (2648) Unable to obtain herdsman settings 2026-06-05 10:55:23.866 - error: zigbee.0 (2648) Starting zigbee-herdsman problem : failed to start adapter connection to firmware 2026-06-05 10:55:23.866 - error: zigbee.0 (2648) Failed to start Zigbee: no message givenLog mit "Ember":
iobroker@IO-BROKER:~$ tail -n 15 /opt/iobroker/log/iobroker.current.log 2026-06-05 10:58:09.566 - info: host.IO-BROKER instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-06-05 10:58:42.202 - info: host.IO-BROKER instance system.adapter.zigbee.0 in version "3.4.5" started with pid 2669 2026-06-05 10:58:43.077 - info: zigbee.0 (2669) starting. Version 3.4.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.22.2, js-controller: 7.0.7 2026-06-05 10:58:43.084 - info: zigbee.0 (2669) init localConfig 2026-06-05 10:58:43.092 - info: zigbee.0 (2669) Adapter ready - starting subsystems. Adapter is running in info mode. 2026-06-05 10:58:43.109 - info: zigbee.0 (2669) delete old Backup files. keep only last 10 2026-06-05 10:58:43.110 - info: zigbee.0 (2669) Autostart Zigbee subsystem 2026-06-05 10:58:43.110 - info: zigbee.0 (2669) Starting Adapter npm ... 2026-06-05 10:58:43.119 - info: zigbee.0 (2669) Installed Version: iobroker.zigbee@3.4.5 (Converters 26.62.0 Herdsman 10.3.0) 2026-06-05 10:58:43.119 - info: zigbee.0 (2669) configured transmit power : normal 2026-06-05 10:58:43.120 - info: zigbee.0 (2669) Starting Zigbee-Herdsman 2026-06-05 10:58:43.396 - info: zigbee.0 (2669) Unable to obtain herdsman settings 2026-06-05 10:58:43.447 - error: zigbee.0 (2669) Starting zigbee-herdsman problem : Failed to start EZSP layer with status=HOST_FATAL_ERROR. 2026-06-05 10:58:43.448 - error: zigbee.0 (2669) Failed to start Zigbee: no message givenSteht aktuell auf 115200
/dev/ttyUSB0
SL EFR32 (EMBER) FW 7.4.x.x
Was kann ich noch machen?

Mod-Edit
Bitte Code-Tags</>benutzen.@Awacs2000 sagte:
Was kann ich noch machen?Auf jeden Fall sollte nach 10 Jahren Mitgliedschaft in diesem Forum das Benutzen von Code-Tags
</>grundsätzlich bekannt sein (siehe auch Mod-Edit im Beitrag). Bitte zukünftig beachten. -
Ah, die Version hatte ich übersehen. Ist jetzt geflashed.
Aber, es mag immer noch nicht.


@Awacs2000 Zeigt /dev/ttyUSB0 auch auf den Stick?
Wenn vorhanden, besser den Link 'by-id' verwenden. -
root@LINUX-VMs:~# ls -l /dev/serial/by-id/
total 0
lrwxrwxrwx 1 root root 13 Jun 5 12:16 usb-dresden_elektronik_ConBee_III_DE03480916-if00-port0 -> ../../ttyUSB0
root@LINUX-VMs:~#Ist das so korrekt, wenn ich das in die .conf-Datei meines iobroker-LXC packe?

Oder macht man das besser per Device-Passtrough?
In der VM selbst sieht das aktuell so aus:
root@IO-BROKER:~# ls -l /dev/serial/by-id/
ls: cannot access '/dev/serial/by-id/': No such file or directory
root@IO-BROKER:~# -
Ah, so, oder:
root@IO-BROKER:~# ls -l /dev/ttyUSB0
crw-rw-rw- 1 root dialout 188, 0 Jun 5 12:40 /dev/ttyUSB0
root@IO-BROKER:~#Und was haben wir zum root gesagt?
Ich bin dann an der Stelle raus. -
Ah, sorry. Falsch angemeldet
mike@IO-BROKER:~$ ls -l /dev/ttyUSB0
crw-rw-rw- 1 root dialout 188, 0 Jun 5 13:01 /dev/ttyUSB0
mike@IO-BROKER:~$mike@LINUX-VMs:~# ls -l /dev/serial/by-id/
total 0
lrwxrwxrwx 1 root root 13 Jun 5 12:16 usb-dresden_elektronik_ConBee_III_DE03480916-if00-port0 -> ../../ttyUSB0
mike@LINUX-VMs:~# -
Starting zigbee-herdsman...
Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee3 : 0x26550900 (X-X.2.6.85)
Network parameters: panID=50500 channel=11 extendedPanID=dddddddddddddddd
Unable to disable LED, unsupported function.
No devices
Closing network.mike@IO-BROKER:~$ tail -n 20 /opt/iobroker/log/iobroker.current.log
2026-06-05 13:05:08.388 - info: zigbee.0 (994) delete old Backup files. keep only last 10
2026-06-05 13:05:08.389 - info: zigbee.0 (994) Autostart Zigbee subsystem
2026-06-05 13:05:08.389 - info: zigbee.0 (994) Starting Adapter npm ...
2026-06-05 13:05:08.395 - info: zigbee.0 (994) Installed Version: iobroker.zigbee@3.4.5 (Converters 26.62.0 Herdsman 10.3.0)
2026-06-05 13:05:08.395 - info: zigbee.0 (994) configured transmit power : normal
2026-06-05 13:05:08.395 - info: zigbee.0 (994) Starting Zigbee-Herdsman
2026-06-05 13:05:13.532 - info: zigbee.0 (994) Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee3 : 0x26550900 (X-X.2.6.85)
2026-06-05 13:05:13.532 - info: zigbee.0 (994) No devices
2026-06-05 13:05:13.533 - info: zigbee.0 (994) Zigbee started
2026-06-05 13:05:13.533 - info: zigbee.0 (994) Config value 0xdddddddddddddddd : Network value 0xdddddddddddddddd
2026-06-05 13:05:13.580 - info: host.IO-BROKER stopInstance system.adapter.zigbee.0 (force=false, process=true)
2026-06-05 13:05:13.583 - info: zigbee.0 (994) Got terminate signal TERMINATE_YOURSELF
2026-06-05 13:05:13.583 - info: zigbee.0 (994) Halting zigbee adapter. Restart delay is at least 30 seconds.
2026-06-05 13:05:13.583 - info: zigbee.0 (994) cleaning everything up
2026-06-05 13:05:13.621 - info: host.IO-BROKER stopInstance system.adapter.zigbee.0 send kill signal
2026-06-05 13:05:14.083 - info: zigbee.0 (994) Saved local configuration data
2026-06-05 13:05:15.815 - info: zigbee.0 (994) Closing network.
2026-06-05 13:05:17.584 - info: zigbee.0 (994) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-06-05 13:05:18.119 - info: host.IO-BROKER instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) -
-
Starting zigbee-herdsman...
Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee3 : 0x26550900 (X-X.2.6.85)
Network parameters: panID=50500 channel=11 extendedPanID=dddddddddddddddd
Unable to disable LED, unsupported function.
No devices
Closing network.mike@IO-BROKER:~$ tail -n 20 /opt/iobroker/log/iobroker.current.log
2026-06-05 13:05:08.388 - info: zigbee.0 (994) delete old Backup files. keep only last 10
2026-06-05 13:05:08.389 - info: zigbee.0 (994) Autostart Zigbee subsystem
2026-06-05 13:05:08.389 - info: zigbee.0 (994) Starting Adapter npm ...
2026-06-05 13:05:08.395 - info: zigbee.0 (994) Installed Version: iobroker.zigbee@3.4.5 (Converters 26.62.0 Herdsman 10.3.0)
2026-06-05 13:05:08.395 - info: zigbee.0 (994) configured transmit power : normal
2026-06-05 13:05:08.395 - info: zigbee.0 (994) Starting Zigbee-Herdsman
2026-06-05 13:05:13.532 - info: zigbee.0 (994) Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee3 : 0x26550900 (X-X.2.6.85)
2026-06-05 13:05:13.532 - info: zigbee.0 (994) No devices
2026-06-05 13:05:13.533 - info: zigbee.0 (994) Zigbee started
2026-06-05 13:05:13.533 - info: zigbee.0 (994) Config value 0xdddddddddddddddd : Network value 0xdddddddddddddddd
2026-06-05 13:05:13.580 - info: host.IO-BROKER stopInstance system.adapter.zigbee.0 (force=false, process=true)
2026-06-05 13:05:13.583 - info: zigbee.0 (994) Got terminate signal TERMINATE_YOURSELF
2026-06-05 13:05:13.583 - info: zigbee.0 (994) Halting zigbee adapter. Restart delay is at least 30 seconds.
2026-06-05 13:05:13.583 - info: zigbee.0 (994) cleaning everything up
2026-06-05 13:05:13.621 - info: host.IO-BROKER stopInstance system.adapter.zigbee.0 send kill signal
2026-06-05 13:05:14.083 - info: zigbee.0 (994) Saved local configuration data
2026-06-05 13:05:15.815 - info: zigbee.0 (994) Closing network.
2026-06-05 13:05:17.584 - info: zigbee.0 (994) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-06-05 13:05:18.119 - info: host.IO-BROKER instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee3 : 0x26550900 (X-X.2.6.85)
Network parameters: panID=50500 channel=11 extendedPanID=dddddddddddddddd
Unable to disable LED, unsupported function.
No devices
Closing network.Bevor du Geräte anmeldest solltest du:
- Die ExtPan ID anpassen
- den Transport Key anpassen
Mit der ExtPanID bekommst du in der Zukunft Probleme, und der Standard Network Key ist ungünstig, weil darüber die Transportverschlüsselung läuft - sprich dein Nachbar und du können marodierende Geräte bekommen.
A,.
Nachtrag: die Fensterkontakte sind immer kritisch anzulernen. Da brauche ich auch oft mehrere Versuche.
-
Starting zigbee-herdsman...
Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee3 : 0x26550900 (X-X.2.6.85)
Network parameters: panID=50500 channel=11 extendedPanID=dddddddddddddddd
Unable to disable LED, unsupported function.
No devices
Closing network.mike@IO-BROKER:~$ tail -n 20 /opt/iobroker/log/iobroker.current.log
2026-06-05 13:05:08.388 - info: zigbee.0 (994) delete old Backup files. keep only last 10
2026-06-05 13:05:08.389 - info: zigbee.0 (994) Autostart Zigbee subsystem
2026-06-05 13:05:08.389 - info: zigbee.0 (994) Starting Adapter npm ...
2026-06-05 13:05:08.395 - info: zigbee.0 (994) Installed Version: iobroker.zigbee@3.4.5 (Converters 26.62.0 Herdsman 10.3.0)
2026-06-05 13:05:08.395 - info: zigbee.0 (994) configured transmit power : normal
2026-06-05 13:05:08.395 - info: zigbee.0 (994) Starting Zigbee-Herdsman
2026-06-05 13:05:13.532 - info: zigbee.0 (994) Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee3 : 0x26550900 (X-X.2.6.85)
2026-06-05 13:05:13.532 - info: zigbee.0 (994) No devices
2026-06-05 13:05:13.533 - info: zigbee.0 (994) Zigbee started
2026-06-05 13:05:13.533 - info: zigbee.0 (994) Config value 0xdddddddddddddddd : Network value 0xdddddddddddddddd
2026-06-05 13:05:13.580 - info: host.IO-BROKER stopInstance system.adapter.zigbee.0 (force=false, process=true)
2026-06-05 13:05:13.583 - info: zigbee.0 (994) Got terminate signal TERMINATE_YOURSELF
2026-06-05 13:05:13.583 - info: zigbee.0 (994) Halting zigbee adapter. Restart delay is at least 30 seconds.
2026-06-05 13:05:13.583 - info: zigbee.0 (994) cleaning everything up
2026-06-05 13:05:13.621 - info: host.IO-BROKER stopInstance system.adapter.zigbee.0 send kill signal
2026-06-05 13:05:14.083 - info: zigbee.0 (994) Saved local configuration data
2026-06-05 13:05:15.815 - info: zigbee.0 (994) Closing network.
2026-06-05 13:05:17.584 - info: zigbee.0 (994) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-06-05 13:05:18.119 - info: host.IO-BROKER instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)@Awacs2000
Willst oder kannst Du nicht Lesen, ist das bewusste Ignoranz oder wie muss ich mir das Ignorieren der Bitte um Nutzung von Code-Tags</>erklären? -
2026-06-05 13:10:07.266 - info: zigbee.0 (1035) init localConfig 2026-06-05 13:10:07.277 - info: zigbee.0 (1035) Adapter ready - starting subsystems. Adapter is running in info mode. 2026-06-05 13:10:07.277 - warn: zigbee.0 (1035) Activating zigbee-herdsman debug connection - successfulMeinst Du das so? Ist das so korrekt mal als Beispiel.
-
Also, jetzt mal ganz langsam. Ich war glaube vor vielen Jahren das letzte mal hier im Forum.
Was meinst Du genau? Was mache ich falsch?
Davon mal abgeshen, hatte ich es tatsächlich obern überlesen.@Awacs2000
Poste bitte Logs nicht stumpf als Text mit Copy and Paste oder als Screenshot. Ist beides schlecht zu lesen und aus Bildern kann man auch nicht zitieren. Für Logs gibt es die Code-Tag-Funktion
-
2026-06-05 13:10:07.266 - info: zigbee.0 (1035) init localConfig 2026-06-05 13:10:07.277 - info: zigbee.0 (1035) Adapter ready - starting subsystems. Adapter is running in info mode. 2026-06-05 13:10:07.277 - warn: zigbee.0 (1035) Activating zigbee-herdsman debug connection - successfulMeinst Du das so? Ist das so korrekt mal als Beispiel.
@Awacs2000 sagte:
Meinst Du das so? Ist das so korrekt mal als Beispiel.Jepp. Genau.
-
@Awacs2000
Ich bleibe da hartnäckig
-
Die ExtPan ID rauslöschen
den Transport Key rauslöschen
Reboot?Oder wie macht man das?
Es gibt eine Anleitung hier: https://github.com/ioBroker/ioBroker.zigbee/wiki/Step‐by‐Step-guide-for-the-Zigbee-network-configuration
Ansonsten:
- Konfigurationsseite öffnen
- Hardware Tab
- via 'start stop' button in der Seite nur das Zigbee Netz anhalten
- Werte in der Konfiguration anpassen
- via 'start stop' button in der Seite nur das Zigbee Netz starten
- Schauen was das Ergebnis ist - wenn es läuft: Konfiguration speichern, dann startet der Adapter Neu
A.
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden
