Good day,
I don’t know exactly when the issue started, but everything was working fine up until a week ago. I am running a mini PC with Proxmox and Home Assistant. I had integrated a Sonoff Stick, which communicates via Thread. It was recognized as an OTBR and supplied my basement. Additionally, I have an Apple HomePod Mini in my apartment, which covered the apartment.
Now, the OTBR in the basement no longer appears in the Eve app, and the devices in the basement are no longer responding in HomeKit. They simply show “No Response.”
In the Open Thread Border Router addon, the following log is displayed:
e[34m-----------------------------------------------------------e[0m
e[34m Add-on: OpenThread Border Routere[0m
e[34m OpenThread Border Router add-one[0m
e[34m-----------------------------------------------------------e[0m
e[34m Add-on version: 2.13.0e[0m
e[32m You are running the latest version of this add-on.e[0m
e[34m System: Home Assistant OS 14.2 (amd64 / qemux86-64)e[0m
e[34m Home Assistant Core: 2025.2.5e[0m
e[34m Home Assistant Supervisor: 2025.03.2e[0m
e[34m-----------------------------------------------------------e[0m
e[34m Please, share the above information when looking for helpe[0m
e[34m or support in, e.g., GitHub, forums or the Discord chat.e[0m
e[34m-----------------------------------------------------------e[0m
s6-rc: info: service banner successfully started
s6-rc: info: service universal-silabs-flasher: starting
[06:39:17] INFO: e[32mChecking /dev/ttyUSB0 identifying Home Assistant Connect ZBT-1 from Nabu Casa.e[0m
[06:39:17] INFO: e[32mStarting universal-silabs-flasher with /dev/ttyUSB0e[0m
2025-03-11 06:39:18.285 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=2, sdk_version='4.4.4', ezsp_version=None, ot_rcp_version='SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4' (2.4.4.0), cpc_version=None, fw_type=<FirmwareImageType.OPENTHREAD_RCP: 'openthread_rcp'>, fw_variant=None, baudrate=460800)
2025-03-11 06:39:18.285 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2025-03-11 06:39:20.294 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2025-03-11 06:39:21.407 homeassistant universal_silabs_flasher.flasher INFO Detected ApplicationType.SPINEL, version 'SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4' (2.4.4.0) at 460800 baudrate (bootloader baudrate None)
2025-03-11 06:39:21.407 homeassistant universal_silabs_flasher.flash INFO Firmware version 'SL-OPENTHREAD/2.4.4.0_GitHub-7074a43e4' (2.4.4.0) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[06:39:21] INFO: e[32mSetup OTBR firewall...e[0m
[06:39:21] INFO: e[32mStarting otbr-agent...e[0m
[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-flow-control
[NOTE]-AGENT---: Radio URL: trel://enp0s18
[NOTE]-ILS-----: Infra link selected: enp0s18
50d.16:04:46.804 [C] P-SpinelDrive-: Software reset co-processor successfully
00:00:00.058 [N] RoutingManager: BR ULA prefix: fddd:3375:687::/48 (loaded)
00:00:00.058 [N] RoutingManager: Local on-link prefix: fdff:f6da:6a4:d251::/64
00:00:00.071 [N] Mle-----------: Role disabled -> detached
00:00:00.078 [N] P-Netif-------: Changing interface state to up.
00:00:00.084 [W] P-Netif-------: Failed to process request#2: No such process
00:00:00.084 [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
[06:39:22] INFO: e[32mEnabling NAT64.e[0m
Done
00:00:00.322 [W] P-Netif-------: Failed to process request#7: No such process
Done
Done
s6-rc: info: service otbr-agent-configure successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
00:00:00.416 [N] Mle-----------: Role detached -> router
00:00:00.416 [N] Mle-----------: Partition ID 0x745ef790
[NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
[06:39:22] INFO: e[32mSuccessfully sent discovery information to Home Assistant.e[0m
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:01.073 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:38, src:ee4822e6b756c38a, dst:0xffff, sec:yes, tag:355, offset:128, dglen:166
00:00:01.694 [W] DuaManager----: Failed to perform next registration: NotFound
00:00:12.832 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:88, src:ee4822e6b756c38a, dst:0xffff, sec:yes, tag:361, offset:128, dglen:224
00:00:12.835 [N] MeshForwarder-: Dropping rx frag frame, error:Drop, len:8, src:ee4822e6b756c38a, dst:0xffff, sec:yes, tag:361, offset:216, dglen:224
02:27:08.883 [N] Mle-----------: Different partition (peer:177276623, local:1952380816)
02:27:08.883 [W] Mle-----------: Failed to process Advertisement: LinkMarginLow
I think the issue is related to the following entries in the log file:
00:00:01.694 [W] DuaManager----: Failed to perform next registration: NotFound
02:27:08.883 [W] Mle-----------: Failed to process Advertisement: LinkMarginLow
I’m not sure if the problem started after I connected a Fritzbox repeater in the basement to my Ubiquiti UniFi system. I also have the feeling that the issue appeared after I plugged in two new Eve smart plugs to extend the Thread network.
What could the log file entries mean?
I have already restored a backup of my Home Assistant from version 2025.3.2 to 2025.2.5. Additionally, I uninstalled and reinstalled the addon.
I also connected a Home Assistant SkyConnect, but it generates the same log file and does not solve the issue. Furthermore, I applied the credentials under Companion App → Debugging → Thread, but unfortunately, nothing has helped so far.
