addons: OpenThread Border Router not working anymore

Describe the issue you are experiencing

OpenThread Border Router not working anymore

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

OpenThread Border Router

What is the version of the add-on?

2.4.2

Steps to reproduce the issue

Install OpenThread Border Router with a SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2

System Health information

There are currently no repairs available

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

No response

Anything in the add-on logs that might be useful for us?

[22:38:38] INFO: The otbr-web is disabled.
s6-rc: info: service mdns: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service mdns successfully started
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
[22:38:38] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Jan  5 2024 07:38:38) starting

-----------------------------------------------------------
 Add-on: OpenThread Border Router
 OpenThread Border Router add-on
-----------------------------------------------------------
 Add-on version: 2.4.2
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.3  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.1.2
 Home Assistant Supervisor: 2023.12.0
-----------------------------------------------------------
 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 universal-silabs-flasher: starting
[22:38:41] INFO: Flashing firmware is disabled
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[22:38:42] INFO: Setup OTBR firewall...
[22:38:43] INFO: Starting otbr-agent...
otbr-agent[177]: [NOTE]-AGENT---: Running 0.3.0-27ed99f-dirty
otbr-agent[177]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[177]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[177]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyACM1?uart-baudrate=460800
otbr-agent[177]: [NOTE]-ILS-----: Infra link selected: end0
otbr-agent[177]: 00:00:00.033 [N] RoutingManager: BR ULA prefix: fde3:a3ba:48df::/48 (loaded)
otbr-agent[177]: 00:00:00.034 [N] RoutingManager: Local on-link prefix: fdb0:b576:5265:eab1::/64
otbr-agent[177]: 00:00:00.147 [N] Mle-----------: Role disabled -> detached
otbr-agent[177]: 00:00:00.161 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[177]: 00:00:00.232 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[177]: 00:00:00.234 [W] Platform------: [netif] ADD [U] fe80:0:0:0:8446:9bb6:dbbb:b5f9 failed (InvalidArgs)
otbr-agent[177]: 00:00:00.235 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:00.236 [W] Platform------: [netif] ADD [U] fd0c:e555:5a16:eafb:d40f:b219:d370:701f failed (InvalidArgs)
otbr-agent[177]: 00:00:00.236 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:00.236 [W] Platform------: [netif] ADD [U] fd0c:e555:5a16:eafb:0:ff:fe00:ac00 failed (InvalidArgs)
otbr-agent[177]: 00:00:00.236 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:00.238 [W] Platform------: [netif] Failed to process request#6: No such process
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
s6-rc: info: service otbr-agent-configure: starting
s6-rc: info: service otbr-agent-configure successfully started
[22:38:44] 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
otbr-agent[177]: 00:00:27.525 [N] Mle-----------: RLOC16 ac00 -> fffe
otbr-agent[177]: 00:00:27.527 [W] Platform------: [netif] Failed to process request#8: Operation not supported
otbr-agent[177]: 00:00:28.140 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[177]: 00:00:32.141 [N] RouterTable---: Allocate router id 43
otbr-agent[177]: 00:00:32.141 [N] Mle-----------: RLOC16 fffe -> ac00
otbr-agent[177]: 00:00:32.143 [N] Mle-----------: Role detached -> leader
otbr-agent[177]: 00:00:32.622 [N] Mle-----------: Partition ID 0x709fbc1a
otbr-agent[177]: 00:00:32.672 [W] Platform------: [netif] Failed to process request#9: File exists
otbr-agent[177]: 00:00:32.673 [W] Platform------: [netif] ADD [U] fd0c:e555:5a16:eafb:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[177]: 00:00:32.674 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[177]: 00:00:32.749 [W] Platform------: [netif] ADD [U] fd0c:e555:5a16:eafb:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[177]: 00:00:32.749 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:32.753 [W] Platform------: [netif] ADD [U] fd0c:e555:5a16:eafb:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[177]: 00:00:32.753 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:35.022 [W] Platform------: [netif] ADD [U] fde3:a3ba:48df:1:bc57:f6af:1c52:f035 failed (InvalidArgs)
otbr-agent[177]: 00:00:35.022 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:00:43.352 [W] Platform------: [netif] ADD [U] fd0c:e555:5a16:eafb:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[177]: 00:00:43.352 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[177]: 00:03:44.197 [N] RouterTable---: Allocate router id 50
otbr-agent[177]: 00:03:44.270 [W] Mle-----------: Failed to process Child ID Response: Security



### Additional information

_No response_

About this issue

Original URL
State: open
Created 6 months ago
Reactions: 10
Comments: 25 (7 by maintainers)

Most upvoted comments

I’m using KVM on Ubuntu, but I just did a fresh install on bare metal Raspberry Pi 4B and have the exact same issue, so I don’t think it’s a VM issue.

josh-hemphill on Jan 16, 2024

I understand that with Silicon Labs Multiprotocol add-on, the OTBR used is not the one installed in HA but an OTBR which is embedded to the add-on. Is my understanding correct ? So I think we should uninstall the OTBR add-on before installing the Silab multiprotocol. I’m not sure I have done this during the various tests I have done.

Technically, both add-on can be installed, but they should not be running both at the same time. Make sure that one is always disabled. However, there can be only one OTBR integration on Home Assistant Core side. And they get added/removed on add-on install/uninstall through the Supervisor/Core discovery mechanism. You can manually switch the OTBR integration between the two, but that needs manually adding them with the right URL (core-...)

Long story short: Easiest is to just have only one them installed 😅

I had an issue with credentials when I was switching around networks. The syncing didn’t seem to work. I had to completely clear the storage for Google Play Services each time before they would sync over. I’d give that a try if it works for one network but not the other.

@azerioxal you likely run into this issue: https://github.com/home-assistant/android/issues/4146

agners on Mar 18, 2024

I am running Home Assistant OS 11.4 + SkyConnect + 4.3.2 on a Fujitsu x86-64 machine here a nd the OTBR is running just fine, so there isn’t a general issue.

Also note that I do get some of the errors as well (InvalidArgs, , but they do not seem to prevent the OTBR from working:

otbr-agent[187]: [NOTE]-AGENT---: Running 0.3.0-657e775-dirty
otbr-agent[187]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[187]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[187]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800&uart-flow-control
otbr-agent[187]: [NOTE]-AGENT---: Radio URL: trel://enp1s0
otbr-agent[187]: [NOTE]-ILS-----: Infra link selected: enp1s0
otbr-agent[187]: 00:00:00.055 [N] RoutingManager: BR ULA prefix: fdf8:76ab:ebd6::/48 (loaded)
otbr-agent[187]: 00:00:00.056 [N] RoutingManager: Local on-link prefix: fd2f:7fe0:dc78:8e15::/64
otbr-agent[187]: 00:00:00.111 [N] Mle-----------: Role disabled -> detached
otbr-agent[187]: 00:00:00.141 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[187]: 00:00:00.165 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[187]: 00:00:00.166 [W] Platform------: [netif] ADD [U] fe80:0:0:0:101e:c3e7:fb0f:c5a3 failed (InvalidArgs)
otbr-agent[187]: 00:00:00.166 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[187]: 00:00:00.167 [W] Platform------: [netif] ADD [U] fd15:3b16:79a7:541a:2c35:a38e:4c3d:945d failed (InvalidArgs)
otbr-agent[187]: 00:00:00.168 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[187]: 00:00:00.168 [W] Platform------: [netif] ADD [U] fd15:3b16:79a7:541a:0:ff:fe00:1400 failed (InvalidArgs)
otbr-agent[187]: 00:00:00.168 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[187]: 00:00:00.168 [W] Platform------: [netif] Failed to process request#6: No such process

@fuomag9 (original poster) you reported this as a regression. Can you confirm that downgrading (using the backup) fixes the problem for you? You are saying “not working anymore” how does this manifest exactly?

For everyone else:

a) if this is a regression for you too (as in, downgrading from Backup fixes the problem again), please report your exact system configuration and the error. b) if you are running a fresh installation/you’ve had always problems with Thread, please open a new issue along with all details what your system configuraiton looks, what you trying to do and what the problems look like exactly.

agners on Jan 16, 2024