Matter over Thread mit Sonoff Stick P funktioniert nicht

Hi zusammen,

Konstellation:

HomeServer mit Proxmox, HA in einer VM. Genutzt bis jetzt mit einem Sonoff Stick P und Zigbee2MQTT, funktioniert auch.

bin nun locker 5 Stunden dran Matter over Thread bei mir zu relisieren. Ich hatte noch einen zweiten Sonoff Stick P hier rumliegen, diesen mit der Firmware CC1352P2_CC2652P_launchpad_ot_rcp_2025_3_1.hex geflasht, und eingerichtet. Sobald ich aber einen Sensor ( Ikea Myggbet ) Pairen will, stürzt es ab.

Log OTBR:

Add-on: OpenThread Border Router

 OpenThread Border Router add-on
\-----------------------------------------------------------
 Add-on version: 2.16.7
 You are running the latest version of this add-on.
 System: Home Assistant OS 17.2  (amd64 / qemux86-64)
 Home Assistant Core: 2026.4.2
 Home Assistant Supervisor: 2026.03.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 otbr-agent: starting
[17:37:34\] WARNING: IPv6 routing/forwarding is not enabled! Make sure the Home Assistant host has IPv6 forwarding enabled.
[17:37:34\] INFO: Migrating OTBR settings if needed...
2026-04-12 17:37:34 homeassistant asyncio\[241\] DEBUG Using selector: EpollSelector
2026-04-12 17:37:34 homeassistant zigpy.serial\[241\] DEBUG Opening a serial connection to '/dev/ttyUSB1' (baudrate=460800, xonxoff=False, rtscts=False)
2026-04-12 17:37:34 homeassistant serialx.platforms.serial_posix\[241\] DEBUG Configuring serial port '/dev/ttyUSB1'
2026-04-12 17:37:34 homeassistant serialx.platforms.serial_posix\[241\] DEBUG Configuring serial port: \[0, 0, 3248, 0, 4100, 4100, \[b'\\x03', b'\\x1c', b'\\x7f', b'\\x15', b'\\x04', 0, 0, b'\\x00', b'\\x11', b'\\x13', b'\\x1a', b'\\x00', b'\\x12', b'\\x0f', b'\\x17', b'\\x16', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00', b'\\x00'\]\]
2026-04-12 17:37:34 homeassistant serialx.platforms.serial_posix\[241\] DEBUG Setting low latency mode: True
2026-04-12 17:37:34 homeassistant serialx.platforms.serial_posix\[241\] DEBUG Setting modem pins: ModemPins\[!dtr !rts\]
2026-04-12 17:37:34 homeassistant serialx.platforms.serial_posix\[241\] DEBUG TIOCMBIC: 0x00000006
2026-04-12 17:37:34 homeassistant zigpy.serial\[241\] DEBUG Connection made: <serialx.platforms.serial_posix.PosixSerialTransport object at 0x7f825f2703d0>
2026-04-12 17:37:34 homeassistant universal_silabs_flasher.spinel\[241\] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=0, network_link_id=0, flag=2), command_id=<CommandID.RESET: 1>, data=b'\\x02')
2026-04-12 17:37:34 homeassistant universal_silabs_flasher.spinel\[241\] DEBUG Sending data b'\~\\x80\\x01\\x02\\xea\\xf0\~'
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Immediately writing b'\~\\x80\\x01\\x02\\xea\\xf0\~'
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Sent 7 of 7 bytes
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Event loop woke up reader
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Received b'\~\\x80\\x06\\x00p\\xeet\~'
2026-04-12 17:37:34 homeassistant universal_silabs_flasher.spinel\[241\] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\\x80\\x06\\x00p')
2026-04-12 17:37:34 homeassistant universal_silabs_flasher.spinel\[241\] DEBUG Parsed frame SpinelFrame(header=SpinelHeader(transaction_id=0, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_IS: 6>, data=b'\\x00p')
2026-04-12 17:37:34 homeassistant universal_silabs_flasher.spinel\[241\] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=3, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_GET: 2>, data=b'\\x08')
2026-04-12 17:37:34 homeassistant universal_silabs_flasher.spinel\[241\] DEBUG Sending data b'\~\\x83\\x02\\x08\\xbc\\x9a\~'
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Immediately writing b'\~\\x83\\x02\\x08\\xbc\\x9a\~'
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Sent 7 of 7 bytes
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Event loop woke up reader
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Received b'\~\\x83\\x06\\x08\\x00\\x12K\\x00\*\\x1a\\xf3\\ruq\~'
2026-04-12 17:37:34 homeassistant universal_silabs_flasher.spinel\[241\] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\\x83\\x06\\x08\\x00\\x12K\\x00\*\\x1a\\xf3\\r')
2026-04-12 17:37:34 homeassistant universal_silabs_flasher.spinel\[241\] DEBUG Parsed frame SpinelFrame(header=SpinelHeader(transaction_id=3, network_link_id=0, flag=2), command_id=<CommandID.PROP_VALUE_IS: 6>, data=b'\\x08\\x00\\x12K\\x00\*\\x1a\\xf3\\r')
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Closing at the request of the application
2026-04-12 17:37:34 homeassistant zigpy.serial\[241\] DEBUG Waiting for serial port to close
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Closing connection: None
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Closing file descriptor 7
2026-04-12 17:37:34 homeassistant serialx.descriptor_transport\[241\] DEBUG Calling protocol \`connection_lost\` with exc=None
2026-04-12 17:37:34 homeassistant zigpy.serial\[241\] DEBUG Connection lost: None
Adapter settings file /data/thread/0_124b002a1af30d.data is the most recently used, skipping
[17:37:34\] 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-init-deassert
[NOTE\]-AGENT---: Radio URL: trel://enp0s18
[NOTE\]-ILS-----: Infra link selected: enp0s18
49d.17:11:27.318 \[C\] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.025 \[N\] RoutingManager: BR ULA prefix: fd83:d8f5:c02a::/48 (loaded)
00:00:00.025 \[N\] RoutingManager: Local on-link prefix: fd6a:aa94:ed9c:56ae::/64
00:00:00.041 \[N\] Mle-----------: Role disabled -> detached
00:00:00.052 \[N\] P-Netif-------: Changing interface state to up.
00:00:00.060 \[W\] P-Netif-------: Failed to process request#2: No such process
00:00:00.060 \[W\] P-Netif-------: Failed to process request#6: No such process
Connection to 172.30.32.1 8081 port \[tcp/tproxy\] succeeded!
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-configure: starting
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
00:00:00.373 \[W\] P-Daemon------: Failed to write CLI output: Broken pipe
[17:37:35\] 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:27.478 \[N\] Mle-----------: RLOC16 0800 -> fffe
00:00:28.177 \[N\] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:34.677 \[N\] RouterTable---: Allocate router id 2
00:00:34.677 \[N\] Mle-----------: RLOC16 fffe -> 0800
00:00:34.678 \[N\] Mle-----------: Role detached -> leader
00:00:34.679 \[N\] Mle-----------: Partition ID 0x3850a68f
[NOTE\]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:39.076 \[W\] DuaManager----: Failed to perform next registration: NotFound

Wenn ich dann in der App den Sensor hinzufügen möchte, steht in der App Gerät wird gesucht, dann wird es gefunden und danach Verbindung zu thread netzwerk wird hergestellt. dann scheint der Stick abzustürzen.Neustarten des Boarder Router reicht nicht,ich muss den Stick ziehen und wieder neu einstecken.
Log:

[17:47:26\] WARNING: otbr-agent exited with code 1 (by signal 0).
Chain OTBR_FORWARD_INGRESS (0 references)
target     prot opt source               destination         
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            
[17:47:26\] INFO: OTBR firewall/NAT64 rules teardown completed.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service otbr-agent-rest-discovery: stopping
s6-rc: info: service otbr-agent-rest-discovery successfully stopped
s6-rc: info: service otbr-agent-configure: stopping
s6-rc: info: service otbr-agent-configure successfully stopped
s6-rc: info: service otbr-agent: stopping
s6-rc: info: service otbr-agent successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service banner: stopping
s6-rc: info: service mdns: stopping
s6-rc: info: service banner successfully stopped
Default: mDNSResponder (Engineering Build) (Apr 10 2026 12:15:27) stopping
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: warning: service s6rc-oneshot-runner is marked as essential, not stopping it
[17:47:26\] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped

:crayon:by HarryP: Code-/Logzeilen formatiert (bitte immer in </> einbinden)
s.a.: (Neues Update & Features - Hier in der Community 🫶)

Für mich sieht das nach fehlendem IPv6 aus.

Guck mal, ob du durch meine Notizen hierzu durchblickst:

https://github.com/J-Paul0815/SmartHome/blob/main/Projects/Matter/IPv6_im_LXC.md

Die Einstellungen für LXC brauchst für die VM ja nicht

Hi,

danke dir für deine schnelle Antwort. Also, nachdem ich ein wenig gesucht habe scheint so als ob in der Stick Firmware 3.1 ein Fehler drin ist ( laut GitHub ) .Habe nun die wohl funktionieren soll, und komme nun weiter. ABER den Sensor bekomme ich noch immer nicht angelernt:Fehler im Log:

00:02:16.527 [W] P-RadioSpinel-: Error processing result: NoAddress

00:02:16.527 [W] P-RadioSpinel-: Error waiting response: NoAddress

So geschafft. Nachdem ich in der Console IPV6 in Docker Altiviert habe,konnte ich den Sensor nun endlich Pairen..nach 6h…Die fehlerhafte Firmware hat mich 5h davongekostet…

Jetzt wäre es auch noch gut wenn Du hier verraten würdest welche Firmware Du jetzt installiert hast, damit auch andere User etwas davon haben. :wink: Denn die von Dir genannte Version

scheint ja vermutlich diese hier mit angebotene zu sein

und die soll ja dann lt. Dir nicht funktionieren.

Ich vermute mal das Du diese Github-Diskussion dazu meinst:

VG Jim

Hi,

Ja aus diesem GitHub habe ich dann die unten verlinkte genommen: