HAOS 18 regression on Raspberry Pi 5: Matter Server and OpenThread Border Router connectivity failure

Installation Home Assistant OS
,
1

Summary of my troubleshooting regarding HAOS 18 regression on RPi5
"After upgrading to HAOS 18, I encountered a critical issue where my Matter and OpenThread Border Router add-ons failed to function, resulting in a persistent restart loop. Below is a summary of my troubleshooting and findings:

The Symptom:
Immediately following the upgrade to HAOS 18, the Matter Server add-on failed to initialize. Log analysis indicated connectivity issues, specifically errors related to netwerk interface binding, such as Unknown interface: end0.

My findings:

Kernel/OS Regression: HAOS 18 enforces the new end0 interface naming convention on the Raspberry Pi 5, replacing the standard eth0.

Add-on Incompatibility: While standard Docker containers (like Zigbee2MQTT, utilizing /dev/serial/by-id) remained perfectly stable, add-ons relying on deep network-stack integration (Matter Server, OTBR) failed. These add-ons appear to require a strict bridge binding to the host's primary network interface; when the host interface name changes, this binding breaks, causing the connectivity loop.

Hardware Isolation: I have confirmed this is not a hardware, cable, or USB-dongle issue. The issue is 100% reproducible when moving from HAOS 17.3 to 18.x.

Successful Workaround: Rolling back to HAOS 17.3 while updating Core to 2026.7 (retaining the 17.3 kernel) restored full system functionality, including stable Matter and Thread operations.

My Conclusion:
There is a fundamental incompatibility between the new network stack introduced in HAOS 18 and how existing Docker containers for Matter and Thread handle network bridging on the Raspberry Pi 5.

Recommendation:
For users running on a Raspberry Pi 5 with critical Matter/Thread dependencies, I suggest postponing the upgrade to HAOS 18.x. The 17.3 kernel currently provides superior network stability for this specific hardware configuration compared to the new network architecture introduced in HAOS 18."

Hardware environment for reference:

Host: Raspberry Pi 5 (8GB RAM)
Boot medium: SD Card (Standard)
Zigbee/Thread Controller: Sonoff Zigbee 3.0 USB Dongle (EFR32MG21 based)
OS Version: Tested on HAOS 17.3 (Stable) vs HAOS 18.1 (Regression)
Network Setup: Ethernet connection (Encountering end0 naming issue)

3

Home assistant ova version. After update Matter app was stuck on starting.
Uninstalled matter.
Reinstalled Matter app, my thread router was still connected, but I had to re add my front door lock.
Luckily I only have one matter device.
ZHA ZigBee is so much more reliable.
So yes I think I think there is a definite problem with the HAOS 18.1 update.

4

Maybe I'm lucky or don't fit the requirements to expose the issue, but I have HAOS 18 running in a QEMU/KVM VM on an RPI5 8Gb (ethernet) with the matter integration, with no issues...

5

In general, already HAOS 17.3 used end0 as naming for the Ethernet interface, so there is nothing new. The apps also get the primary interface through Supervisor dynamically, whatever NetworkManager reports as primary interface. So even if the interface name changes, the apps learn that last name at runtime.

In general I ran my production on Yellow with CM5, and have a test system where both apps work fine. There is not a generic problem here.

This must be a system specific failure. Maybe Z2M accessing the same serial device? Can you share the logs when the OTBR/Matter Server doesn't start?

6 
2026-06-19 13:22:12.840 (MainThread) INFO [aiorun] Closing the loop.
2026-06-19 13:22:12.840 (MainThread) INFO [aiorun] Leaving. Bye!
[11:22:13] INFO: matter-server service exited with code 0 (by signal 0).
s6-rc: info: service matter-server successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
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: Matter Server
 Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
 Add-on version: 8.5.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 18.0  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2026.6.3
 Home Assistant Supervisor: 2026.06.2
-----------------------------------------------------------
 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 matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[13:25:14] INFO: Starting Matter Server...
[13:25:14] INFO: Using Python Matter Server
[13:25:15] INFO: Using 'end0' as primary network interface.
[13:25:15] INFO: Successfully send discovery information to Home Assistant.
2026-06-19 13:25:22.092 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2026-06-19 13:25:22.093 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1781868322.746689][117:117] CHIP:CTL: Setting attestation nonce to random value
[1781868322.763826][117:117] CHIP:CTL: Setting CSR nonce to random value
[1781868322.825823][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1781868322.861435][117:117] CHIP:DL: Wrote settings to /tmp/chip_kvs
[1781868322.861730][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1781868322.888182][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1781868322.893067][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1781868322.905521][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1781868322.905564][117:117] CHIP:DL: NVS set: chip-counters/reboot-count = 73 (0x49)
[1781868322.906002][117:117] CHIP:DL: Got Ethernet interface: end0
[1781868322.906229][117:117] CHIP:DL: Found the primary Ethernet interface:end0
[1781868322.906428][117:117] CHIP:DL: Got WiFi interface: wlan0
[1781868322.906449][117:117] CHIP:DL: Failed to reset WiFi statistic counts
[1781868322.906454][117:117] CHIP:PAF: WiFiPAF: WiFiPAFLayer::Init()
2026-06-19 13:25:22.906 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2026-06-19 13:25:22.906 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...
2026-06-19 13:25:23.059 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2026-06-19 13:25:23.059 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2026-06-19 13:25:23.060 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...
2026-06-19 13:25:23.060 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2026-06-19 13:25:23.061 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2026-06-19 13:25:23.061 (MainThread) INFO [matter_server.server.server] Matter Server initialized
2026-06-19 13:25:23.061 (MainThread) INFO [matter_server.server.server] Using 'end0' as primary interface (for link-local addresses)
2026-06-19 13:25:23.062 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2026-06-19 13:25:23.081 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2026-06-19 13:25:23.081 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2026-06-19 13:25:23.365 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable
2026-06-19 13:25:23.371 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 287 ms, for event type 2
2026-06-19 13:25:23.398 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2026-06-19 13:25:23.407 (MainThread) INFO [matter_server.server.vendor_info] Loaded 437 vendors from storage.
2026-06-19 13:25:23.408 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2026-06-19 13:25:27.744 (MainThread) INFO [matter_server.server.vendor_info] Fetched 436 vendors from DCL.
2026-06-19 13:25:27.744 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2026-06-19 13:25:27.769 (MainThread) INFO [matter_server.server.device_controller] Loaded 19 nodes from stored configuration
2026-06-19 13:25:27.805 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
2026-06-19 13:33:02.153 (MainThread) INFO [matter_server.server.device_controller] <Node:4> No new update found.
2026-06-19 13:33:02.153 (MainThread) INFO [matter_server.server.device_controller] <Node:9> No new update found.
2026-06-19 13:33:02.153 (MainThread) INFO [matter_server.server.device_controller] <Node:17> No new update found.
2026-06-19 13:33:02.154 (MainThread) INFO [matter_server.server.device_controller] <Node:2> No new update found.
2026-06-19 13:33:02.154 (MainThread) INFO [matter_server.server.device_controller] <Node:7> No new update found.
2026-06-19 13:33:02.154 (MainThread) INFO [matter_server.server.device_controller] <Node:8> No new update found.
2026-06-19 13:33:02.157 (MainThread) INFO [matter_server.server.device_controller] <Node:23> No new update found.
2026-06-19 13:33:02.162 (MainThread) INFO [matter_server.server.device_controller] <Node:22> No new update found.
2026-06-19 13:33:02.162 (MainThread) INFO [matter_server.server.device_controller] <Node:10> No new update found.
2026-06-19 13:33:02.162 (MainThread) INFO [matter_server.server.device_controller] <Node:25> No new update found.
2026-06-19 13:33:02.169 (MainThread) INFO [matter_server.server.device_controller] <Node:11> No new update found.
2026-06-19 13:33:02.176 (MainThread) INFO [matter_server.server.device_controller] <Node:5> No new update found.
2026-06-19 13:33:02.178 (MainThread) INFO [matter_server.server.device_controller] <Node:12> No new update found.
2026-06-19 13:33:02.178 (MainThread) INFO [matter_server.server.device_controller] <Node:20> No new update found.
2026-06-19 13:33:02.178 (MainThread) INFO [matter_server.server.device_controller] <Node:21> No new update found.
2026-06-19 13:33:02.183 (MainThread) INFO [matter_server.server.device_controller] <Node:13> No new update found.
2026-06-19 13:33:02.185 (MainThread) INFO [matter_server.server.device_controller] <Node:6> No new update found.
2026-06-19 13:33:02.186 (MainThread) INFO [matter_server.server.device_controller] <Node:24> No new update found.
2026-06-19 13:33:02.226 (MainThread) INFO [matter_server.server.device_controller] <Node:14> No new update found.
2026-06-19 13:33:29.281 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:33:29.285 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:33:38.205 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:33:38.205 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:49:04.620 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:49:04.620 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:22:12.840 (MainThread) INFO [aiorun] Closing the loop.
2026-06-19 13:22:12.840 (MainThread) INFO [aiorun] Leaving. Bye!
[11:22:13] INFO: matter-server service exited with code 0 (by signal 0).
s6-rc: info: service matter-server successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
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: Matter Server
 Matter WebSocket Server for Home Assistant Matter support.
-----------------------------------------------------------
 Add-on version: 8.5.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 18.0  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2026.6.3
 Home Assistant Supervisor: 2026.06.2
-----------------------------------------------------------
 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 matter-server: starting
s6-rc: info: service matter-server successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[13:25:14] INFO: Starting Matter Server...
[13:25:14] INFO: Using Python Matter Server
[13:25:15] INFO: Using 'end0' as primary network interface.
[13:25:15] INFO: Successfully send discovery information to Home Assistant.
2026-06-19 13:25:22.092 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Logging...
2026-06-19 13:25:22.093 (MainThread) INFO [matter_server.server.stack] Initializing CHIP/Matter Controller Stack...
[1781868322.746689][117:117] CHIP:CTL: Setting attestation nonce to random value
[1781868322.763826][117:117] CHIP:CTL: Setting CSR nonce to random value
[1781868322.825823][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1781868322.861435][117:117] CHIP:DL: Wrote settings to /tmp/chip_kvs
[1781868322.861730][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_factory.ini
[1781868322.888182][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_config.ini
[1781868322.893067][117:117] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /data/chip_counters.ini
[1781868322.905521][117:117] CHIP:DL: Wrote settings to /data/chip_counters.ini
[1781868322.905564][117:117] CHIP:DL: NVS set: chip-counters/reboot-count = 73 (0x49)
[1781868322.906002][117:117] CHIP:DL: Got Ethernet interface: end0
[1781868322.906229][117:117] CHIP:DL: Found the primary Ethernet interface:end0
[1781868322.906428][117:117] CHIP:DL: Got WiFi interface: wlan0
[1781868322.906449][117:117] CHIP:DL: Failed to reset WiFi statistic counts
[1781868322.906454][117:117] CHIP:PAF: WiFiPAF: WiFiPAFLayer::Init()
2026-06-19 13:25:22.906 (MainThread) INFO [chip.storage] Initializing persistent storage from file: /data/chip.json
2026-06-19 13:25:22.906 (MainThread) INFO [chip.storage] Loading configuration from /data/chip.json...
2026-06-19 13:25:23.059 (MainThread) INFO [chip.CertificateAuthority] Loading certificate authorities from storage...
2026-06-19 13:25:23.059 (MainThread) INFO [chip.CertificateAuthority] New CertificateAuthority at index 1
2026-06-19 13:25:23.060 (MainThread) INFO [chip.CertificateAuthority] Loading fabric admins from storage...
2026-06-19 13:25:23.060 (MainThread) INFO [chip.FabricAdmin] New FabricAdmin: FabricId: 0x0000000000000002, VendorId = 0x134B
2026-06-19 13:25:23.061 (MainThread) INFO [matter_server.server.stack] CHIP Controller Stack initialized.
2026-06-19 13:25:23.061 (MainThread) INFO [matter_server.server.server] Matter Server initialized
2026-06-19 13:25:23.061 (MainThread) INFO [matter_server.server.server] Using 'end0' as primary interface (for link-local addresses)
2026-06-19 13:25:23.062 (MainThread) INFO [matter_server.server.server] Starting the Matter Server...
2026-06-19 13:25:23.081 (MainThread) INFO [matter_server.server.helpers.paa_certificates] Skip fetching certificates (already fetched within the last 24h).
2026-06-19 13:25:23.081 (MainThread) INFO [chip.FabricAdmin] Allocating new controller with CaIndex: 1, FabricId: 0x0000000000000002, NodeId: 0x000000000001B669, CatTags: []
2026-06-19 13:25:23.365 (Dummy-2) CHIP_ERROR [chip.native.DIS] Failed to advertise records: src/inet/UDPEndPointImplSockets.cpp:417: OS Error 0x02000065: Network is unreachable
2026-06-19 13:25:23.371 (Dummy-2) CHIP_ERROR [chip.native.DL] Long dispatch time: 287 ms, for event type 2
2026-06-19 13:25:23.398 (MainThread) INFO [matter_server.server.vendor_info] Loading vendor info from storage.
2026-06-19 13:25:23.407 (MainThread) INFO [matter_server.server.vendor_info] Loaded 437 vendors from storage.
2026-06-19 13:25:23.408 (MainThread) INFO [matter_server.server.vendor_info] Fetching the latest vendor info from DCL.
2026-06-19 13:25:27.744 (MainThread) INFO [matter_server.server.vendor_info] Fetched 436 vendors from DCL.
2026-06-19 13:25:27.744 (MainThread) INFO [matter_server.server.vendor_info] Saving vendor info to storage.
2026-06-19 13:25:27.769 (MainThread) INFO [matter_server.server.device_controller] Loaded 19 nodes from stored configuration
2026-06-19 13:25:27.805 (MainThread) INFO [matter_server.server.server] Matter Server successfully initialized.
2026-06-19 13:33:02.153 (MainThread) INFO [matter_server.server.device_controller] <Node:4> No new update found.
2026-06-19 13:33:02.153 (MainThread) INFO [matter_server.server.device_controller] <Node:9> No new update found.
2026-06-19 13:33:02.153 (MainThread) INFO [matter_server.server.device_controller] <Node:17> No new update found.
2026-06-19 13:33:02.154 (MainThread) INFO [matter_server.server.device_controller] <Node:2> No new update found.
2026-06-19 13:33:02.154 (MainThread) INFO [matter_server.server.device_controller] <Node:7> No new update found.
2026-06-19 13:33:02.154 (MainThread) INFO [matter_server.server.device_controller] <Node:8> No new update found.
2026-06-19 13:33:02.157 (MainThread) INFO [matter_server.server.device_controller] <Node:23> No new update found.
2026-06-19 13:33:02.162 (MainThread) INFO [matter_server.server.device_controller] <Node:22> No new update found.
2026-06-19 13:33:02.162 (MainThread) INFO [matter_server.server.device_controller] <Node:10> No new update found.
2026-06-19 13:33:02.162 (MainThread) INFO [matter_server.server.device_controller] <Node:25> No new update found.
2026-06-19 13:33:02.169 (MainThread) INFO [matter_server.server.device_controller] <Node:11> No new update found.
2026-06-19 13:33:02.176 (MainThread) INFO [matter_server.server.device_controller] <Node:5> No new update found.
2026-06-19 13:33:02.178 (MainThread) INFO [matter_server.server.device_controller] <Node:12> No new update found.
2026-06-19 13:33:02.178 (MainThread) INFO [matter_server.server.device_controller] <Node:20> No new update found.
2026-06-19 13:33:02.178 (MainThread) INFO [matter_server.server.device_controller] <Node:21> No new update found.
2026-06-19 13:33:02.183 (MainThread) INFO [matter_server.server.device_controller] <Node:13> No new update found.
2026-06-19 13:33:02.185 (MainThread) INFO [matter_server.server.device_controller] <Node:6> No new update found.
2026-06-19 13:33:02.186 (MainThread) INFO [matter_server.server.device_controller] <Node:24> No new update found.
2026-06-19 13:33:02.226 (MainThread) INFO [matter_server.server.device_controller] <Node:14> No new update found.
2026-06-19 13:33:29.281 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:33:29.285 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:33:38.205 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:33:38.205 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:49:04.620 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's
2026-06-19 13:49:04.620 (MainThread) INFO [matter_server.server.device_controller] <Node:17> Node could not be discovered on the network, returning cached IP's

OpenThread Border Router

/run/s6/basedir/scripts/rc.init: info: hook /etc/s6-overlay/scripts/enable-check.sh exited 0
s6-rc: info: service s6rc-oneshot-runner: starting
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 add-on
-----------------------------------------------------------
 Add-on version: 3.0.1
 You are running the latest version of this add-on.
 System: Home Assistant OS 18.0  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2026.6.3
 Home Assistant Supervisor: 2026.06.2
-----------------------------------------------------------
 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
[13:45:41] INFO: Setup OTBR firewall...
[13:45:41] INFO: Migrating OTBR settings if needed...
2026-06-19 13:45:41 homeassistant asyncio[233] DEBUG Using selector: EpollSelector
2026-06-19 13:45:41 homeassistant zigpy.serial[233] DEBUG Opening a serial connection to '/dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_3c5b45666d12f011a5490714773d9da9-if00-port0' (baudrate=460800, xonxoff=False, rtscts=False)
2026-06-19 13:45:41 homeassistant serialx.platforms.serial_posix[233] DEBUG Locking serial port '/dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_3c5b45666d12f011a5490714773d9da9-if00-port0'
2026-06-19 13:45:41 homeassistant serialx.platforms.serial_posix[233] DEBUG Configuring serial port '/dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_3c5b45666d12f011a5490714773d9da9-if00-port0'
2026-06-19 13:45:41 homeassistant serialx.platforms.serial_posix[233] 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-06-19 13:45:41 homeassistant serialx.platforms.serial_linux[233] DEBUG Setting low latency mode: True
2026-06-19 13:45:41 homeassistant serialx.platforms.serial_posix[233] DEBUG Setting modem pins: ModemPins[!dtr !rts]
2026-06-19 13:45:41 homeassistant serialx.platforms.serial_posix[233] DEBUG TIOCMBIC: 0x00000006
2026-06-19 13:45:41 homeassistant zigpy.serial[233] DEBUG Connection made: <serialx.platforms.serial_linux.LinuxSerialTransport object at 0x7f93bfc350>
2026-06-19 13:45:41 homeassistant universal_silabs_flasher.spinel[233] DEBUG Sending frame SpinelFrame(header=SpinelHeader(transaction_id=0, network_link_id=0, flag=2), command_id=<CommandID.RESET: 1>, data=b'\x02')
2026-06-19 13:45:41 homeassistant universal_silabs_flasher.spinel[233] DEBUG Sending data b'~\x80\x01\x02\xea\xf0~'
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Immediately writing b'~\x80\x01\x02\xea\xf0~'
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Sent 7 of 7 bytes
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Event loop woke up reader
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Received b'~\x80\x06\x00p\xeet~'
2026-06-19 13:45:41 homeassistant universal_silabs_flasher.spinel[233] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\x80\x06\x00p')
2026-06-19 13:45:41 homeassistant universal_silabs_flasher.spinel[233] 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-06-19 13:45:41 homeassistant universal_silabs_flasher.spinel[233] 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-06-19 13:45:41 homeassistant universal_silabs_flasher.spinel[233] DEBUG Sending data b'~\x83\x02\x08\xbc\x9a~'
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Immediately writing b'~\x83\x02\x08\xbc\x9a~'
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Sent 7 of 7 bytes
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Event loop woke up reader
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Received b'~\x83\x06\x08\x04\xe3\xe5\xff\xfe\xa23\xed\xa5\xc8~'
2026-06-19 13:45:41 homeassistant universal_silabs_flasher.spinel[233] DEBUG Decoded HDLC frame: HDLCLiteFrame(data=b'\x83\x06\x08\x04\xe3\xe5\xff\xfe\xa23\xed')
2026-06-19 13:45:41 homeassistant universal_silabs_flasher.spinel[233] 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\x04\xe3\xe5\xff\xfe\xa23\xed')
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Closing at the request of the application
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Backgrounding a close request: None
2026-06-19 13:45:41 homeassistant zigpy.serial[233] DEBUG Waiting for serial port to close
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Closing connection: None
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Closing file descriptor 7
2026-06-19 13:45:41 homeassistant serialx.descriptor_transport[233] DEBUG Calling protocol `connection_lost` with exc=None
2026-06-19 13:45:41 homeassistant zigpy.serial[233] DEBUG Connection lost: None
Adapter settings file /data/thread/0_4e3e5fffea233ed.data is the most recently used, skipping
[13:45:41] 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:///dev/serial/by-id/usb-Itead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_V2_3c5b45666d12f011a5490714773d9da9-if00-port0?uart-baudrate=460800&uart-init-deassert
[NOTE]-AGENT---: Radio URL: trel://end0
[NOTE]-ILS-----: Infra link selected: end0
49d.17:24:16.463 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.051 [N] BorderRouting-: BR ULA prefix: fdc5:7eef:f582::/48 (loaded)
00:00:00.052 [N] BorderRouting-: Local on-link prefix: fde8:b9a3:4455:e027::/64
[WARN]-UTILS---: /usr/src/ot-br-posix/src/rest/network_diag_handler.cpp:1300 lacking some attributes for deviceId ae911d5471d58f9b
[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 - ae911d5471d58f9b
00:00:00.067 [N] Mle-----------: Role disabled -> detached
00:00:00.068 [N] P-Netif-------: Changing interface state to up.
00:00:00.072 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.073 [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
[13:45:42] 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
[13:45:42] 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:11.665 [N] Mle-----------: RLOC16 0000 -> fffe
00:00:12.240 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
00:00:13.025 [N] Mle-----------: RLOC16 fffe -> c001
00:00:13.028 [N] Mle-----------: Role detached -> child
00:01:09.429 [N] Mle-----------: RLOC16 c001 -> 3800
00:01:09.433 [N] Mle-----------: Role child -> router
00:01:09.433 [N] Mle-----------: Partition ID 0x774646d0
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
00:07:02.946 [W] P-InfraNetif--: failed to send ICMPv6 message: Cannot assign requested address, suggests infra link might be down, checking status.
00:07:02.946 [C] BorderRouting-: RsSender: Failed to send RS 1/3: Failed
7

Have you check that you have the correct settings for this device like:
Hardware flow control (OFF)

And with Matter you also need to enable IPV6.

8

Hang on. Are you running MultiPAN (Zigbee & Thread on a single coordinator)?

9

I use separate dongles for matter and zigbee

10

Hardware flow control is off.
ipv6 is on and running.

On 17.3 and before I have never had issues with matter and have 20 devices running on it. Very stable.

Everything is up to date on my home assistant except the HAos 18.x upgrade.
HAos 18 seems to break it pretty good.

11

I've been investigating the connectivity issues on HAOS 18.0, and the logs consistently point to a failure in the network-interface binding for the OTBR-agent.

The issue follows a predictable pattern:

  • The OTBR-agent correctly identifies and selects end0 as the Infra link upon startup.
  • Initially, the connection appears stable, and the device successfully joins the Thread network as a router.
  • However, after approximately 7 minutes, the process fails with: [W] P-InfraNetif--: failed to send ICMPv6 message: Cannot assign requested address.
  • Immediately following this, the RsSender (Router Solicitation) fails, resulting in a total loss of IPv6 communication between the border router and the rest of the network.

This indicates that HAOS 18.0 is failing to maintain the IPv6 address assignment on the end0 interface, effectively breaking the border routing functionality. As this occurs on a system with separate dongles, correct IPv6 configuration, and hardware flow control disabled, it strongly points to an underlying OS regression rather than a configuration error.

12

I am running HA, the latest and the greatest.

image
image680×243 15 KB

With two Sonoff usb dongles in a very tight env.

image
image1193×194 12.8 KB

With a RPI 3B with just 1GB

image
image330×324 26.8 KB

With Matter with threads (one Sonoff) and Zigbee (the another Sonoff), and it all working well.

One thing that I haven't configured that I don't use is IPV6 network, so my RPI is configured like this:

image
image600×439 14.8 KB