OpenThread Border Router 3.1.0: otbr-agent crash-loops with "RCP device disconnected (EOF)" — works fine on 3.0.2

[spants]

Describe the issue you are experiencing

Title:

OpenThread Border Router 3.1.0: otbr-agent crash-loops with "RCP device disconnected (EOF)" — works fine on 3.0.2

Describe the bug

After updating the OpenThread Border Router add-on from 3.0.2 to 3.1.0, the add-on crash-loops. When the TCP link to the Thread radio (SLZB-MR2 via socat TCP client) is up, the add-on connects cleanly, becomes Thread leader, then ~9 minutes later the RCP connection drops mid-session with RCP device disconnected (EOF) and otbr-agent exits with code 1. The add-on restarts and repeats. Sometimes the radio is unreachable entirely and socat logs No route to host, then the migration script fails with TimeoutError and otbr-agent exits.

Restoring the add-on to 3.0.2 from a backup (same Core version, same Supervisor, same radio, same config) makes the crash-loop disappear completely and all Thread/Matter devices come back online.

The radio is confirmed healthy: fixed IP, PoE-powered, reachable at all times during the failure.

Environment

• Add-on: OpenThread Border Router 3.1.0 (broken) / 3.0.2 (working)
• Home Assistant OS 18.2 (amd64 / qemux86-64 VM)
• Home Assistant Core: 2026.8.0
• Home Assistant Supervisor: 2026.07.5
• Matter Server add-on: 9.1.1
• Thread radio: SLZB-MR2, TCP link via socat to 192.168.1.8:6638 (fixed IP, PoE)
• Radio URL: spinel+hdlc+uart:///tmp/ttyOTBR?uart-baudrate=460800&uart-init-deassert
• Radio EUI64: 38:5b:44:ff:fe:4a:5a:24
• otbr-agent build on 3.1.0: 0.3.0-ec16e396
• Devices affected: 8 window sensors + 1 Aqara U200 lock (all Matter over Thread)

Steps to reproduce

1. On Supervisor 2026.07.5 / Core 2026.8.0, update OpenThread Border Router to 3.1.0.
2. Wait ~10 minutes. The add-on enters error state (crash-loop).
3. Restore the add-on to 3.0.2 from a backup (only the add-on; keep the same Core/Supervisor/radio).
4. The add-on is stable and all devices return.

Expected behavior

The add-on should maintain the RCP connection over the socat TCP link indefinitely, as 3.0.2 does.

Actual behavior

• Clean start: socat connects to the radio, RCP negotiates, agent becomes leader.
• After ~9 minutes: RCP device disconnected (EOF), Failure → otbr-agent exited with code 1 → restart loop.
• Sometimes: No route to host to 192.168.1.8:6638 → migration script TimeoutError → exit.
• When the link stays up, NoAck errors to child devices precede the EOF.

Logs

Healthy start on 3.1.0 (then the crash ~9 min later):

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which app are you reporting an issue with?

Matter Server

What is the version of the app?

3.1

Steps to reproduce the issue

1. On Supervisor 2026.07.5 / Core 2026.8.0, update OpenThread Border Router to 3.1.0.
2. Wait ~10 minutes. The add-on enters error state (crash-loop).
3. Restore the add-on to 3.0.2 from a backup (only the add-on; keep the same Core/Supervisor/radio).
4. The add-on is stable and all devices return.

System Health information

all ok after downgrade

Anything in the Supervisor logs that might be useful for us?

Anything in the app logs that might be useful for us?

[22:33:40] INFO: Enabled socat-otbr-tcp.
[22:33:40] INFO: Starting socat TCP client for OTBR daemon...
[22:33:41] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-ec16e396
[NOTE]-AGENT---: Thread version: 1.4.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///tmp/ttyOTBR?uart-baudrate=460800&uart-init-deassert
00:00:08.455 [N] Mle-----------: RLOC16 4400 -> fffe
00:00:08.534 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:15.034 [N] RouterTable---: Allocate router id 17
00:00:15.037 [N] Mle-----------: Role detached -> leader
00:00:15.038 [N] Mle-----------: Partition ID 0x5fa4852
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:01:11.178 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:205, chksum:bdfe, ecn:no, to:ca493d45842d00a3, sec:yes, error:NoAck, prio:net, radio:all
00:06:57.533 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:408, chksum:2218, ecn:no, to:0x4401, sec:yes, error:NoAck, prio:low, radio:all
00:07:50.822 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:646, chksum:3f76, ecn:no, to:0x4402, sec:yes, error:NoAck, prio:low, radio:all
00:09:37.008 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:196, chksum:4ec2, ecn:no, to:36103ef7c090b473, sec:yes, error:NoAck, prio:net, radio:all
00:09:37.128 [C] Platform------: exit(1): Read line 207, RCP device disconnected (EOF), Failure
[22:43:18] WARNING: otbr-agent exited with code 1 (by signal 0).

Additional information

Installation method = Home Assistant OS
Core = 2026.8.0
Supervisor = 2026.07.5
Operating System = 18.2
Frontend = 20260729.5

Running on Proxmox

[puddly]

OpenThread RCP over TCP isn't a recommended configuration. From your bug report, OTBR exits because RCP device disconnected (EOF) and fails to reconnect to your adapter because of No route to host to 192.168.1.8. This sounds like a network and/or adapter issue, not something that can be fixed in OTBR.

[Aussie-Luftikus]

I can confirm the issue @spants describes here. I have exactly the same problem. Reverting to version 3.0.2 fixes all issues. This is incredibly annoying as most of my automations rely on sensor data coming in via Matter over Thread and consequently stopped working. Even more annoying is that some people involved in the maintenance seem to enjoy playing the “Blame Others” game. I also use the SLZB Thread radio with PoE and it works perfectly fine with OTBR 3.0.2, but it is broken with OTBR 3.1.0.

[puddly]

If you can reproduce a regression that shows up every time you upgrade to 3.1.0 but gets resolved when you downgrade back to 3.0.2, can you attach a debug log from both versions?

Very little changed between 3.1.0 and 3.0.2 and issues with OTBR + SLZB radios go back 2+ years at this point. The behavior is very consistent: the SLZB radio stops working, crashing OTBR, and the SLZB radio takes a while to start working again. RCP device disconnected (EOF), Failure is a new error in this OTBR release but it would have shown up under a different name in a previous one, fundamentally the error is the same: the OpenThread RCP radio connection is unreliable.

When things like No route to host for 192.168.1.8 show up, there genuinely isn't much that can be done. The IP connection to the radio is gone. Either the network has a problem or the device itself but either way it's outside of the control of OTBR. OTBR will try to recover once or twice in-process by reconnecting to the radio but it will inevitably crash, leaving recovery to HA's supervisor.

[spants]

The problem that I see:

1. Something has changed in OTBR 3.1.0 from 3.0.2
2. This something crashes the SLZB device
3. OTBR App errors out
4. Thread and Zigbee (also running on SLZB) networks are destroyed due to SLZB crashing
5. Zigbee devices usually need to be re-paired with Z2M due to dropping off the network

It seems that the SLZB firmware isnt as stable (!) as one would hope, but a change in the way that OTBR works has triggered this.

I have around 100 zigbee devices and around 10 thread devices (security locks) and it takes a long time to fix (as well as my wife chiming in about going back to manual switches), so I cannot keep switching between the two versions. Sorry.

[spants]

Checking the issue with Claude:

Possible upstream cause: The otbr-agent build bundled in 3.1.0 (0.3.0-ec16e396) corresponds to ot-br-posix v2026.07.0, up from the 78d9c289 build in 3.0.2/3.0.0. Comparing the two tags (v2026.06.0...v2026.07.0), the only non-test behavioral change is PR #3388 ("fix D-Bus method hangs on Spinel set-property failures"), which changes how NcpSpinel::HandleResponseForPropSet handles a SPINEL_PROP_LAST_STATUS response — i.e. how the host reacts when a set-property command to the RCP fails. Previously such a failure would leave the async task hanging indefinitely rather than propagating an error; the fix now completes it with the unpacked error status. Given that the failure surfaces here as RCP device disconnected (EOF) after ~9 minutes on a socat-bridged TCP link (rather than a hang), it's possible the newly-correct error propagation from #3388 is now triggering a teardown/reset of the RCP interface on a transient property-set failure that TCP-connected radios are more prone to (vs. a direct USB/UART RCP), where 3.0.2's older handling silently absorbed the same failure without tearing down the connection. Flagging this as the most likely candidate in the version diff, though I haven't confirmed the exact code path from failure → exit(1).

[jonnycastaway]

Same issue here,
after the Update OTBR stopps with:

00:30:00.198 [C] Platform------: exit(1): Read line 207, RCP device disconnected (EOF), Failure [23:46:07] WARNING: otbr-agent exited with code 1 (by signal 0).

The OTBR-RPC Device is not the Problem. The issue comes with the OTBR Update.

[puddly]

@jonnycastaway Please attach more debug logs (the whole log is fine), especially from both versions.

[topaDev]

Same here,

downgrade to 3.0.2 solved the issue - I am running a Ultima 3 as hardware device and Home Assistant on a Proxmox VE if that matters (pun intended):

Last log from 3.1.0 before downgrading:

[11:22:49] INFO: Stable mode enabled.
[11:22:49] INFO: The otbr-web is disabled.
[11:22:49] INFO: Enabled socat-otbr-tcp.
/run/s6/basedir/scripts/rc.init: info: hook /etc/s6-overlay/scripts/enable-check.sh exited 0
s6-rc: info: service socat-otbr-tcp: starting
s6-rc: info: service s6rc-oneshot-runner: starting
[11:22:49] INFO: Starting socat TCP client for OTBR daemon...
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service banner: starting
-----------------------------------------------------------
 Add-on: OpenThread Border Router
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
 OpenThread Border Router app
-----------------------------------------------------------
 Add-on version: 3.1.0
 You are running the latest version of this add-on.
s6-rc: info: service legacy-cont-init successfully started
 System: Home Assistant OS 18.2  (amd64 / qemux86-64)
 Home Assistant Core: 2026.8.0
 Home Assistant Supervisor: 2026.07.5
-----------------------------------------------------------
 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 socat-otbr-tcp successfully started
s6-rc: info: service otbr-agent: starting
[11:22:50] INFO: Setup OTBR firewall...
[11:22:50] INFO: Migrating OTBR settings if needed...
2026-08-07 11:22:50 homeassistant asyncio[253] DEBUG Using selector: EpollSelector
2026-08-07 11:22:50 homeassistant zigpy.serial[253] DEBUG Opening a serial connection to '/tmp/ttyOTBR' (baudrate=460800, xonxoff=False, rtscts=False)
2026-08-07 11:22:50 homeassistant serialx.platforms.serial_posix[253] DEBUG Locking serial port '/tmp/ttyOTBR'
2026-08-07 11:22:50 homeassistant serialx.platforms.serial_posix[253] DEBUG Configuring serial port '/tmp/ttyOTBR'
2026-08-07 11:22:50 homeassistant serialx.platforms.serial_posix[253] DEBUG Configuring serial port: TcsetattrFlags(iflag=0, oflag=0, cflag=3248, lflag=0, ispeed=4100, ospeed=4100, cc_vmin=0, cc_vtime=0) + cc=[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-08-07 11:22:50 homeassistant serialx.platforms.serial_linux[253] DEBUG Setting low latency mode: True
2026-08-07 11:22:50 homeassistant serialx.platforms.serial_linux[253] DEBUG Device does not support setting low latency
2026-08-07 11:22:50 homeassistant serialx.platforms.serial_posix[253] DEBUG Setting modem pins: ModemPins[!dtr !rts]
2026-08-07 11:22:50 homeassistant serialx.platforms.serial_posix[253] DEBUG TIOCMBIC: 0x00000006
2026-08-07 11:22:50 homeassistant serialx.platforms.serial_posix[253] DEBUG Device is not a serial port, cannot set modem pins
2026-08-07 11:22:50 homeassistant zigpy.serial[253] DEBUG Connection made: <serialx.platforms.serial_linux.LinuxSerialTransport object at 0x7f540aba5090>
2026-08-07 11:22:50 homeassistant universal_silabs_flasher.spinel[253] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=0, network_link_id=0, flag=2), command_id=<CommandID.RESET: 1>, data=b'\x02')
2026-08-07 11:22:50 homeassistant universal_silabs_flasher.spinel[253] DEBUG Sending data b'~\x80\x01\x02\xea\xf0~'
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Immediately writing b'~\x80\x01\x02\xea\xf0~'
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Sent 7 of 7 bytes
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Event loop woke up reader
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Received b'~\x80\x06\x00p\xeet~'
2026-08-07 11:22:50 homeassistant universal_silabs_flasher.spinel[253] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\x80\x06\x00p')
2026-08-07 11:22:50 homeassistant universal_silabs_flasher.spinel[253] 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-08-07 11:22:50 homeassistant universal_silabs_flasher.spinel[253] 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-08-07 11:22:50 homeassistant universal_silabs_flasher.spinel[253] DEBUG Sending data b'~\x83\x02\x08\xbc\x9a~'
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Immediately writing b'~\x83\x02\x08\xbc\x9a~'
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Sent 7 of 7 bytes
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Event loop woke up reader
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Received b'~\x83\x06\x08\xe0r\x91\xff\xfe\xb9\x97|\x98^~'
2026-08-07 11:22:50 homeassistant universal_silabs_flasher.spinel[253] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\x83\x06\x08\xe0r\x91\xff\xfe\xb9\x97|')
2026-08-07 11:22:50 homeassistant universal_silabs_flasher.spinel[253] 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\xe0r\x91\xff\xfe\xb9\x97|')
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Closing at the request of the application
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Backgrounding a close request: None
2026-08-07 11:22:50 homeassistant zigpy.serial[253] DEBUG Waiting for serial port to close
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Closing connection: None
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Closing file descriptor 7
2026-08-07 11:22:50 homeassistant serialx.descriptor_transport[253] DEBUG Calling protocol `connection_lost` with exc=None
2026-08-07 11:22:50 homeassistant zigpy.serial[253] DEBUG Connection lost: None
Adapter settings file /data/thread/0_e07291fffeb9977c.data is the most recently used, skipping
[11:22:50] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-ec16e396
[NOTE]-AGENT---: Thread version: 1.4.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///tmp/ttyOTBR?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://enp0s18
[NOTE]-ILS-----: Infra link selected: enp0s18
tiocmbic: Inappropriate ioctl for device
00:00:00.000 [C] P-RadioSpinel-: RCP => [C] Platform------: Reset info: 0x3 (EXT)
00:00:00.000 [C] P-RadioSpinel-: RCP => [C] Platform------: Extended Reset info: 0x301 (PIN)
[WARN]-UTILS---: /usr/src/ot-br-posix/src/rest/network_diag_handler.cpp:1302 lacking some attributes for deviceId eaf6898a77983379
[WARN]-UTILS---: /usr/src/ot-br-posix/src/rest/network_diag_handler.cpp:1246 cannot get LeaderData while detached
[WARN]-UTILS---: /usr/src/ot-br-posix/src/rest/rest_devices_coll.cpp:232 - AddItem - eaf6898a77983379
00:00:00.061 [N] Mle-----------: Role disabled -> detached
00:00:00.062 [N] P-Netif-------: Changing interface state to up.
00:00:00.066 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.067 [W] P-Netif-------: Failed to process request#7: 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
[11:22:50] INFO: Setting OpenThread mDNS local hostname to homeassistant-otbr.
Done
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
00:00:00.415 [W] P-Daemon------: Failed to write CLI output: Broken pipe
[11:22:50] 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:00.726 [N] Mle-----------: Role detached -> router
00:00:00.726 [N] Mle-----------: Partition ID 0x77f83fb3
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
1d.05:43:49.727 [C] Platform------: exit(1): Read line 207, RCP device disconnected (EOF), Failure
[17:06:40] 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            
[17:06:40] 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 socat-otbr-tcp: stopping
s6-rc: info: service banner successfully stopped
2026/08/08 17:06:40 socat[86] W exiting on signal 15
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service socat-otbr-tcp successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: warning: service s6rc-oneshot-runner is marked as essential, not stopping it

Log from 3.0.2 running since downgrade without issues:

[17:48:29] INFO: Stable mode enabled.
[17:48:29] INFO: The otbr-web is disabled.
[17:48:29] INFO: Enabled socat-otbr-tcp.
/run/s6/basedir/scripts/rc.init: info: hook /etc/s6-overlay/scripts/enable-check.sh exited 0
s6-rc: info: service socat-otbr-tcp: starting
s6-rc: info: service s6rc-oneshot-runner: starting
[17:48:29] INFO: Starting socat TCP client for OTBR daemon...
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
-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router app
-----------------------------------------------------------
 Add-on version: 3.0.2
 There is an update available for this add-on!
 Latest add-on version: 3.1.0
 Please consider upgrading as soon as possible.
 System: Home Assistant OS 18.2  (amd64 / qemux86-64)
 Home Assistant Core: 2026.8.1
 Home Assistant Supervisor: 2026.07.5
-----------------------------------------------------------
 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 socat-otbr-tcp successfully started
s6-rc: info: service otbr-agent: starting
[17:48:30] INFO: Setup OTBR firewall...
[17:48:30] INFO: Migrating OTBR settings if needed...
2026-08-08 17:48:30 homeassistant asyncio[257] DEBUG Using selector: EpollSelector
2026-08-08 17:48:30 homeassistant zigpy.serial[257] DEBUG Opening a serial connection to '/tmp/ttyOTBR' (baudrate=460800, xonxoff=False, rtscts=False)
2026-08-08 17:48:30 homeassistant serialx.platforms.serial_posix[257] DEBUG Locking serial port '/tmp/ttyOTBR'
2026-08-08 17:48:30 homeassistant serialx.platforms.serial_posix[257] DEBUG Configuring serial port '/tmp/ttyOTBR'
2026-08-08 17:48:30 homeassistant serialx.platforms.serial_posix[257] DEBUG Configuring serial port: TcsetattrFlags(iflag=0, oflag=0, cflag=3248, lflag=0, ispeed=4100, ospeed=4100, cc_vmin=0, cc_vtime=0) + cc=[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-08-08 17:48:30 homeassistant serialx.platforms.serial_linux[257] DEBUG Setting low latency mode: True
2026-08-08 17:48:30 homeassistant serialx.platforms.serial_linux[257] DEBUG Device does not support setting low latency
2026-08-08 17:48:30 homeassistant serialx.platforms.serial_posix[257] DEBUG Setting modem pins: ModemPins[!dtr !rts]
2026-08-08 17:48:30 homeassistant serialx.platforms.serial_posix[257] DEBUG TIOCMBIC: 0x00000006
2026-08-08 17:48:30 homeassistant serialx.platforms.serial_posix[257] DEBUG Device is not a serial port, cannot set modem pins
2026-08-08 17:48:30 homeassistant zigpy.serial[257] DEBUG Connection made: <serialx.platforms.serial_linux.LinuxSerialTransport object at 0x7fcb6e48d210>
2026-08-08 17:48:30 homeassistant universal_silabs_flasher.spinel[257] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=0, network_link_id=0, flag=2), command_id=<CommandID.RESET: 1>, data=b'\x02')
2026-08-08 17:48:30 homeassistant universal_silabs_flasher.spinel[257] DEBUG Sending data b'~\x80\x01\x02\xea\xf0~'
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Immediately writing b'~\x80\x01\x02\xea\xf0~'
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Sent 7 of 7 bytes
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Event loop woke up reader
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Received b'~\x80\x06\x00p\xeet~'
2026-08-08 17:48:30 homeassistant universal_silabs_flasher.spinel[257] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\x80\x06\x00p')
2026-08-08 17:48:30 homeassistant universal_silabs_flasher.spinel[257] 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-08-08 17:48:30 homeassistant universal_silabs_flasher.spinel[257] 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-08-08 17:48:30 homeassistant universal_silabs_flasher.spinel[257] DEBUG Sending data b'~\x83\x02\x08\xbc\x9a~'
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Immediately writing b'~\x83\x02\x08\xbc\x9a~'
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Sent 7 of 7 bytes
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Event loop woke up reader
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Received b'~\x83\x06\x08\xe0r\x91\xff\xfe\xb9\x97|\x98^~'
2026-08-08 17:48:30 homeassistant universal_silabs_flasher.spinel[257] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\x83\x06\x08\xe0r\x91\xff\xfe\xb9\x97|')
2026-08-08 17:48:30 homeassistant universal_silabs_flasher.spinel[257] 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\xe0r\x91\xff\xfe\xb9\x97|')
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Closing at the request of the application
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Backgrounding a close request: None
2026-08-08 17:48:30 homeassistant zigpy.serial[257] DEBUG Waiting for serial port to close
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Closing connection: None
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Closing file descriptor 7
2026-08-08 17:48:30 homeassistant serialx.descriptor_transport[257] DEBUG Calling protocol `connection_lost` with exc=None
2026-08-08 17:48:30 homeassistant zigpy.serial[257] DEBUG Connection lost: None
Adapter settings file /data/thread/0_e07291fffeb9977c.data is the most recently used, skipping
[17:48:30] INFO: Starting otbr-agent...
[NOTE]-AGENT---: Running 0.3.0-624a7d98-dirty
[NOTE]-AGENT---: Thread version: 1.4.0
[NOTE]-AGENT---: Thread interface: wpan0
[NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///tmp/ttyOTBR?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://enp0s18
[NOTE]-ILS-----: Infra link selected: enp0s18
tiocmbic: Inappropriate ioctl for device
57d.03:43:20.652 [C] P-SpinelDrive-: Software reset co-processor successfully
57d.03:43:20.671 [C] P-RadioSpinel-: RCP => [C] Platform------: Reset info: 0x3 (EXT)
57d.03:43:20.673 [C] P-RadioSpinel-: RCP => [C] Platform------: Extended Reset info: 0x301 (PIN)
00:00:00.052 [N] BorderRouting-: BR ULA prefix: fd69:a04a:1f91::/48 (loaded)
00:00:00.052 [N] BorderRouting-: Local on-link prefix: fd71:33f5:74dc:b5c3::/64
[WARN]-UTILS---: /usr/src/ot-br-posix/src/rest/network_diag_handler.cpp:1300 lacking some attributes for deviceId eaf6898a77983379
[WARN]-UTILS---: /usr/src/ot-br-posix/src/rest/network_diag_handler.cpp:1244 cannot get LeaderData while detached
[WARN]-UTILS---: /usr/src/ot-br-posix/src/rest/rest_devices_coll.cpp:232 - AddItem - eaf6898a77983379
00:00:00.064 [N] Mle-----------: Role disabled -> detached
00:00:00.064 [N] P-Netif-------: Changing interface state to up.
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
00:00:00.520 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.520 [W] P-Netif-------: Failed to process request#6: No such process
Done
[17:48:31] INFO: Setting OpenThread mDNS local hostname to homeassistant-otbr.
Done
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
[17:48:31] 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:12.732 [N] Mle-----------: RLOC16 e800 -> fffe
00:00:12.826 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:19.326 [N] RouterTable---: Allocate router id 58
00:00:19.326 [N] Mle-----------: RLOC16 fffe -> e800
00:00:19.329 [N] Mle-----------: Role detached -> leader
00:00:19.329 [N] Mle-----------: Partition ID 0x13ba9b01
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:00:20.158 [N] Mle-----------: Different partition (peer:2012757939, local:330996481)
00:00:30.528 [N] Mle-----------: Different partition (peer:2012757939, local:330996481)
00:00:44.138 [N] Mle-----------: Different partition (peer:2012757939, local:330996481)
00:00:51.468 [N] Mle-----------: Different partition (peer:2012757939, local:330996481)
00:01:03.047 [N] Mle-----------: Different partition (peer:2012757939, local:330996481)
00:01:08.073 [W] Mle-----------: Failed to process Link Request: InvalidState
00:01:09.078 [W] Mle-----------: Failed to process Link Request: InvalidState
00:01:10.078 [W] Mle-----------: Failed to process Link Request: InvalidState
00:01:11.827 [N] Mle-----------: Different partition (peer:2012757939, local:330996481)
00:01:13.697 [N] Mle-----------: Different partition (peer:2012757939, local:330996481)
00:01:17.347 [N] Mle-----------: Different partition (peer:2012757939, local:330996481)
00:01:18.362 [N] RouterTable---: Allocate router id 31
04:04:42.641 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:133, chksum:0144, ecn:no, to:861bef0469be5dca, sec:no, error:NoAck, prio:net, radio:15.4
04:04:42.642 [N] MeshForwarder-:     src:[fe80:0:0:0:e8f6:898a:7798:3379]:19788
04:04:42.642 [N] MeshForwarder-:     dst:[fe80:0:0:0:841b:ef04:69be:5dca]:19788
04:04:46.442 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:133, chksum:ef7b, ecn:no, to:861bef0469be5dca, sec:no, error:NoAck, prio:net, radio:15.4
04:04:46.442 [N] MeshForwarder-:     src:[fe80:0:0:0:e8f6:898a:7798:3379]:19788
04:04:46.442 [N] MeshForwarder-:     dst:[fe80:0:0:0:841b:ef04:69be:5dca]:19788
3d.00:32:57.421 [N] MeshForwarder-: Failed to send IPv6 UDP msg, len:90, chksum:aa9d, ecn:no, to:0xe806, sec:yes, error:NoAck, prio:low, radio:all
3d.00:32:57.422 [N] MeshForwarder-:     src:[fd69:a04a:1f91:1:3a96:a72c:b4ed:c5df]:49028
3d.00:32:57.422 [N] MeshForwarder-:     dst:[fd69:a04a:1f91:1:1c48:726a:5604:1463]:5540
 Live

[topaDev]

OpenThread Border Router 3.1.1 is available, release notes do not address this topic, so I guess installing it will break my setup again?

[spants]

I dont think it will address it. I personally think that it is a problem with the SLZB firmware crashing, caused by new information sent/managed by OTBR. I am waiting for someone else to test it :-) due to the problems it caused before.