Thread mit Sonoff Dongle E funktioniert nicht

Allgemein
1

Hallo,

ich habe den Dongle mit der OpenThread Firmware über Silabs Firmware Flasher | Web based flasher for ZB-GW04 and ZBDongle-E. MultiPAN RCP firmware enables these devices to be used with Silabs Multiprotocol Addon in Home Assistant. Allow Zigbee and Thread to co-exist on the same dongle. Get ahead of the tech an experiment with Matter! geflasht. Dann habe ich den Dongle an meinen HA-Server angeschlossen. Dann dachte ich, HA wird den Thread-Dongle sehen und mir den Thread-Dienst vorschlagen. Ist aber nicht passiert. Dann habe ich das Addon „OpenThread Border Router“ installiert und meinen Dongle in den Einstellungen ausgewählt. Aber dann bekomme ich immer eine Fehlermeldung und das Addon wird neu gestartet.

Angeschlossen ist der Dongle an meinem Mini PC mit Truenas Scale. Habe das Gerät dann zur der HA VM durchgereicht.

Ich hoffe jemand nutzt auch ein Sonoff Dongle für Thread und weiß Bescheid was hier falsch läuft :frowning: Danke!

[15:50:20] INFO: The otbr-web is disabled.
s6-rc: info: service mdns: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service mdns successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
[15:50:20] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:04:03) starting
-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.13.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.1  (amd64 / qemux86-64)
 Home Assistant Core: 2025.1.2
 Home Assistant Supervisor: 2024.12.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[15:50:20] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[15:50:21] INFO: Setup OTBR firewall...
[15:50:21] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB1?uart-baudrate=460800&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://enp0s3
[NOTE]-ILS-----: Infra link selected: enp0s3
49d.17:08:40.888 [W] P-SpinelDrive-: Wait for response timeout
49d.17:08:42.890 [W] P-SpinelDrive-: Wait for response timeout
49d.17:08:44.893 [W] P-SpinelDrive-: Wait for response timeout
49d.17:08:44.893 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
49d.17:08:46.895 [W] P-SpinelDrive-: Wait for response timeout
[15:50:59] WARNING: otbr-agent exited with code 1 (by signal 0).
Chain OTBR_FORWARD_INGRESS (0 references)
target     prot opt source               destination         
DROP       all  --  anywhere             anywhere             PKTTYPE = unicast
DROP       all  --  anywhere             anywhere             match-set otbr-ingress-deny-src src
ACCEPT     all  --  anywhere             anywhere             match-set otbr-ingress-allow-dst dst
DROP       all  --  anywhere             anywhere             PKTTYPE = unicast
ACCEPT     all  --  anywhere             anywhere            
otbr-ingress-deny-src
otbr-ingress-deny-src-swap
otbr-ingress-allow-dst
otbr-ingress-allow-dst-swap
Chain OTBR_FORWARD_EGRESS (0 references)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere            
[15:50:59] INFO: OTBR firewall teardown completed.
s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died
s6-rc: warning: unable to start service otbr-agent: command exited 1
s6-rc: info: service legacy-cont-init: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service mdns: stopping
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:04:03) stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[15:50:59] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped

grafik
grafik1100×1015 41.6 KB

2

Hallo, was für ein Zufall! Ich sitze auch gerade daran un dhabe das selbe Problem!

3

Habe bisher nichts über das Problem im Internet gefunden und auf einmal hat auch jemand anderes das gleiche Problem? Verrückt. :sweat_smile:

Ich hoffe hier gibt es jemanden der einen Sonoff Dongle mit OpenThreads Firmware im Einsatz hat und uns helfen kann…

4

Habe die Baurate nun auf 460800 gesetzt und Hardware Flow Control und automatisch Updates deaktiviert. Jetzt geht irgendwie alles und HA erkennt auch den Thread Router… ich verstehe es nicht. Das habe ich doch gestern auch ausprobiert.

Bekomme aber trotzdem noch andere Fehler. Vielleicht kann mir die jemand einordnen und sagen, ob diese schlimm sind?

So sieht mein Log nun aus:

s6-rc: info: service mdns: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service mdns successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
[19:16:23] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:04:03) starting
-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.13.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.1  (amd64 / qemux86-64)
 Home Assistant Core: 2025.1.2
 Home Assistant Supervisor: 2024.12.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[19:16:23] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[19:16:24] INFO: Setup OTBR firewall...
[19:16:24] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://enp0s3
[NOTE]-ILS-----: Infra link selected: enp0s3
49d.17:03:00.590 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.035 [N] RoutingManager: BR ULA prefix: fd28:11d5:5185::/48 (loaded)
00:00:00.035 [N] RoutingManager: Local on-link prefix: fdde:ad00:beef:cafe::/64
00:00:00.040 [W] P-Netif-------: Failed to process request#2: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
00:00:00.322 [W] P-Daemon------: Failed to write CLI output: Broken pipe
[19:16:24] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
00:00:15.728 [N] RoutingManager: Local on-link prefix: fd4b:6ae1:e53:83c5::/64
00:00:15.735 [N] Mle-----------: Role disabled -> detached
00:00:15.736 [N] P-Netif-------: Changing interface state to up.
00:00:15.741 [W] P-Netif-------: Failed to process request#5: No such process
00:00:16.463 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7a:ddff:feb0:c74c/veth1ca552c/21
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7a:ddff:feb0:c74c/veth1ca552c/21
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7a:ddff:feb0:c74c/veth1ca552c/21
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7a:ddff:feb0:c74c/veth1ca552c/21
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7a:ddff:feb0:c74c/veth1ca552c/21
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7a:ddff:feb0:c74c/veth1ca552c/21
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7a:ddff:feb0:c74c/veth1ca552c/21
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7a:ddff:feb0:c74c/veth1ca552c/21
00:00:22.963 [N] RouterTable---: Allocate router id 52
00:00:22.963 [N] Mle-----------: RLOC16 fffe -> d000
00:00:22.967 [N] Mle-----------: Role detached -> leader
00:00:22.967 [N] Mle-----------: Partition ID 0x7474e188
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:25.581 [W] DuaManager----: Failed to perform next registration: NotFound
5

Ich hatte die gleichen Probleme, dass ich Thread nicht zum laufen bekommen habe. Der Dongle liegt jetzt als Backup bei mir im Schrank. Habe da auch tagelang alles mögliche probiert.

Jetzt hab ich ne neue Alexa und share es über sie.

6

Aber will man nicht Produkte wie Alexa mit HA meiden? Mein Plan war es, dass ich HA laufen lasse und dann keine weiteren Geräte mehr brauchen. Schon gar nicht sowas wie Alexa.

Ich denke, dass ich aber aufgebe. HA ist einfach zu übertrieben. Das muss man dann schon leben und als Hobby haben, als das man das als Normalo einfach einsetzt.

Dass ich mich überhaupt mit solchen Fehler rumschlage ist so eine Zeitverschwendung. Und dann ist Matter nur im Beta Status, man muss genau auf die Geräte schauen die man einsetzen will, dann sich irgendwo um ein Firmwareupdate kümmern, …

Ich liebe Technik, aber hier ist für mich weniger mehr. Wenn ich irgendwann mal ein Haus haben sollte, dann würde ich wohl jemanden bezahlen alles zu verkabeln und einzurichten. Aber solange das nicht mein Beruf ist oder ich keine anderen Hobbys habe, dann bleibt HA erstmal vergessen. Sehr schade, weil es schon echt cool ist z.B. seinen Roborock und Sonos Lautsprecher in einer App zu haben.

Viel Spaß weiterhin mit eurem Hobby. HA ist ja bereits schon ziemlich gut und ich hoffe das entwickelt sich noch weiter. An sich ein wirklich tolles Projekt.

7

Mit folgende Konfig habe ich meinen geflashten Sonoff E-Dongle seit einigen Monaten laufen:

image
image857×1221 44.3 KB

Hier noch das Protokoll nach dem Start:

-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.13.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.1  (amd64 / qemux86-64)
 Home Assistant Core: 2025.1.2
 Home Assistant Supervisor: 2024.12.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[13:01:45] INFO: Checking /dev/ttyACM0 identifying SONOFF Zigbee 3.0 USB Dongle Plus V2 from ITEAD.
[13:01:45] INFO: Starting universal-silabs-flasher with /dev/ttyACM0
2025-01-17 13:01:45.816 ha universal_silabs_flasher.flash WARNING The 'sonoff' reset target is deprecated. Use '--bootloader-reset rts_dtr' instead.
2025-01-17 13:01:45.817 ha universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.2', ezsp_version=None, ot_rcp_version='SL-OPENTHREAD/2.4.2.0_GitHub-7074a43e4' (2.4.2.0), cpc_version=None, fw_type=<FirmwareImageType.OPENTHREAD_RCP: 'openthread_rcp'>, fw_variant=None, baudrate=460800)
2025-01-17 13:01:45.817 ha universal_silabs_flasher.flasher INFO Triggering rts_dtr bootloader
2025-01-17 13:01:46.457 ha universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2025-01-17 13:01:46.574 ha universal_silabs_flasher.flasher INFO Launched application from bootloader
2025-01-17 13:01:46.595 ha universal_silabs_flasher.flasher INFO Detected bootloader version '1.12.0'
2025-01-17 13:01:46.595 ha universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2025-01-17 13:01:46.626 ha universal_silabs_flasher.flasher INFO Detected ApplicationType.SPINEL, version 'SL-OPENTHREAD/2.4.2.0_GitHub-7074a43e4' (2.4.2.0) at 460800 baudrate (bootloader baudrate 115200)
2025-01-17 13:01:46.626 ha universal_silabs_flasher.flash INFO Firmware version 'SL-OPENTHREAD/2.4.2.0_GitHub-7074a43e4' (2.4.2.0) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[13:01:46] INFO: Setup OTBR firewall...
[13:01:47] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-b067e5ac-dirty
[NOTE]-AGENT---: Thread version: 1.3.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM0?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://enp1s0
[NOTE]-ILS-----: Infra link selected: enp1s0
56d.13:33:36.876 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.052 [N] RoutingManager: BR ULA prefix: fd2b:940a:e98b::/48 (loaded)
00:00:00.052 [N] RoutingManager: Local on-link prefix: fd8d:4002:48da:8594::/64
00:00:00.080 [N] Mle-----------: Role disabled -> detached
00:00:00.093 [N] P-Netif-------: Changing interface state to up.
00:00:00.106 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.106 [W] P-Netif-------: Failed to process request#6: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[13:01:47] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

Gruß, Lars

1 „Gefällt mir“
8

@anon16070298 @anon16070298 @assistent eure Konfiguration ist / sieht richtig aus!
Ihr müsst einmal in der Home Assistant Android / IOS App auf Einstellungen → Companion App → Troubleshooting (fast ganz unten) → Sync Thread credentials. Danach ging es bei mir :slight_smile: