IKEA Matter-Geräte hängen bei der Thread-Netzwerk-Prüfung

Moin zusammen,

ich habe seit einigen Tagen das Problem, dass alle meine IKEA Matter-Geräte als „offline“ angezeigt werden. Ein Neuverbinden scheitert leider jedes Mal an derselben Stelle:

Der Anmeldeprozess läuft normal durch, bis die Meldung „Verbindung zum Thread-Netzwerk ‘ha-thread-12ba’ wird geprüft“ erscheint. Ab diesem Punkt geht es nicht mehr weiter und die Einrichtung bricht ab bzw. bleibt hängen.

Hat jemand eine Idee, wie ich diesen Thread-Fehler beheben kann?

Protokoll vom OpenThread Border Router

0:58:28.656 [N] Mle-----------: Delay processing Announce - channel 21, panid 0x12ba
00:58:28.906 [N] Mle-----------: Processing Announce - channel 21, panid 0x12ba
00:58:28.907 [N] Mle-----------: Role leader -> detached
00:58:28.908 [N] Mle-----------: Role detached -> disabled
00:58:28.912 [N] Mle-----------: Role disabled -> detached
[NOTE]-BBA-----: BackboneAgent: Backbone Router resigns Primary to Secondary!
00:58:29.227 [N] Mle-----------: Attach attempt 1, AnyPartition 
00:58:35.731 [N] Mle-----------: RLOC16 1c00 -> fffe
00:58:35.736 [N] Mle-----------: Attach attempt 1 unsuccessful, will try again in 0.276 seconds
00:58:36.012 [N] Mle-----------: Attach attempt 2, AnyPartition 
00:58:38.012 [N] RouterTable---: Allocate router id 7
00:58:38.012 [N] Mle-----------: RLOC16 fffe -> 1c00
00:58:38.016 [N] Mle-----------: Role detached -> leader
00:58:38.016 [N] Mle-----------: Partition ID 0x68bb1671
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:58:38.297 [W] P-McastRtMgr--: RemoveMulticastForwardingCache: Backbone fde1:f087:9d9b:0:47a:a4ff:fe6a:efcf => ff05:0:0:0:0:0:0:c None: Failed
00:58:40.288 [W] DuaManager----: Failed to perform next registration: NotFound
00:58:52.905 [N] Mle-----------: Delay processing Announce - channel 21, panid 0x12ba
00:58:53.155 [N] Mle-----------: Processing Announce - channel 21, panid 0x12ba
00:58:53.156 [N] Mle-----------: Role leader -> detached
00:58:53.156 [N] Mle-----------: Role detached -> disabled
00:58:53.161 [N] Mle-----------: Role disabled -> detached
[NOTE]-BBA-----: BackboneAgent: Backbone Router resigns Primary to Secondary!
00:58:53.591 [N] Mle-----------: Attach attempt 1, AnyPartition 
00:59:00.095 [N] Mle-----------: RLOC16 1c00 -> fffe
00:59:00.101 [N] Mle-----------: Attach attempt 1 unsuccessful, will try again in 0.262 seconds
00:59:00.363 [N] Mle-----------: Attach attempt 2, AnyPartition 
00:59:02.363 [N] RouterTable---: Allocate router id 7
00:59:02.363 [N] Mle-----------: RLOC16 fffe -> 1c00
00:59:02.367 [N] Mle-----------: Role detached -> leader
00:59:02.367 [N] Mle-----------: Partition ID 0x6a3801cd
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:59:04.300 [W] DuaManager----: Failed to perform next registration: NotFound
00:00:34.678 [W] DuaManager----: Failed to perform next registration: NotFound
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cfe:69ff:fe9b:13d3/veth8f14e63/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cfe:69ff:fe9b:13d3/veth8f14e63/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cfe:69ff:fe9b:13d3/veth8f14e63/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cfe:69ff:fe9b:13d3/veth8f14e63/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cfe:69ff:fe9b:13d3/veth8f14e63/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::eca7:8ff:fe5d:c5ca/veth7571270/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::eca7:8ff:fe5d:c5ca/veth7571270/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::eca7:8ff:fe5d:c5ca/veth7571270/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::eca7:8ff:fe5d:c5ca/veth7571270/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::eca7:8ff:fe5d:c5ca/veth7571270/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::eca7:8ff:fe5d:c5ca/veth7571270/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::eca7:8ff:fe5d:c5ca/veth7571270/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2
00:00:37.254 [W] P-InfraNetif--: failed to send ICMPv6 message: Cannot assign requested address
00:00:37.254 [C] RoutingManager: RsSender: Failed to send RS 1/3: Failed
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::eca7:8ff:fe5d:c5ca/veth7571270/31
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::d09c:8725:e670:a3d2/enp0s18/2

Matter Protokoll:

2026-04-13 16:26:04.479 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000007]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:26:04.479 (Dummy-2) CHIP_ERROR [chip.native.CTL] Remove Current Fabric Failed : src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:26:04.479 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to unpair device: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:26:04.480 (MainThread) ERROR [matter_server.server.client_handler] [140178745972432] Error while handling: interview_node (node 7): Failed to interview node 7
2026-04-13 16:26:04.480 (MainThread) WARNING [matter_server.server.device_controller] Removing current fabric from device failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:26:35.493 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-04-13 16:26:49.483 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:0000000000000008]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:26:49.483 (Dummy-2) CHIP_ERROR [chip.native.CTL] Remove Current Fabric Failed : src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:26:49.483 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to unpair device: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:26:49.484 (MainThread) WARNING [matter_server.server.device_controller] Removing current fabric from device failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:27:20.499 (Dummy-2) CHIP_ERROR [chip.native.DIS] Timeout waiting for mDNS resolution.
2026-04-13 16:27:34.494 (Dummy-2) CHIP_ERROR [chip.native.DIS] OperationalSessionSetup[1:000000000000000D]: operational discovery failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:27:34.495 (Dummy-2) CHIP_ERROR [chip.native.CTL] Remove Current Fabric Failed : src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:27:34.495 (Dummy-2) WARNING [chip.ChipDeviceCtrl] Failed to unpair device: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout
2026-04-13 16:27:34.495 (MainThread) WARNING [matter_server.server.device_controller] Removing current fabric from device failed: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout

Welche Hardware nutzt Du als Thread Border Router? Was hast Du bisher an Lösungsansätzen probiert?

IPv6 im Terminal aktiviert?

Irgendein Update von Core oder Thread Border Router in letzter Zeit gemacht?

Proxmox Server
OTBR ist ein Sonoff MG24 geflasht…

Lief ja alles ohne Probleme

Das sieht komisch aus?! Irgendwie ein Pingpong zwischen Primary & Secondary OTBR.
Gibt’s da 2 im Netz?

Nein, es gibt nur einen Router…

Was hast Du denn bisher probiert? Z.b. einfache Maßnahmen wie HA inkl. aller Hardware stromlos und neugestartet? den Sonoff-Dongle mal raus und wieder reingesteckt oder an anderem USB-Port versucht? Hast Du irgendwelche Veränderungen wie Updates o.ä. gemacht seitdem es lief?

Im Terminal mal “ha docker options --enable-ipv6=true” eingeben und HA komplett neustarten?

Ist jetzt Alles ins Blaue geraten. Meld Dich mal, wenn Du das Alles durchprobiert hast.

1 „Gefällt mir“

Alles ausprobiert, die neusten Updates sind installiert.

Hatte sogar ein Backup gemacht, alles wie Matter Server und OTBR neu installiert.

DocMarc

31 min

Was hast Du denn bisher probiert? Z.b. einfache Maßnahmen wie HA inkl. aller Hardware stromlos und neugestartet? den Sonoff-Dongle mal raus und wieder reingesteckt oder an anderem USB-Port versucht? Hast Du irgendwelche Veränderungen wie Updates o.ä. gemacht seitdem es lief?

Im Terminal mal “ha docker options --enable-ipv6=true” eingeben und HA komplett neustarten?

Ist jetzt Alles ins Blaue geraten. Meld Dich mal, wenn Du das Alles durchprobiert hast.

Das hat das Problem behoben….

Vielen lieben Dank @DocMarc

1 „Gefällt mir“

Ja, diese IPv6 forwarding Problematik treibt grad viel Matter-over-Thread Nutzer in den Wahnsinn. Hat bei mir auch reingehauen :roll_eyes:

Viel Spaß mit dem funktionierenden SmartHome! :wink: