Skyconnect switched to OTBR

carstenb · January 11, 2024, 11:29am

I am using a Skyconnect and used to run the multi protocol firmware. As I have watched the “state of matter” stream where they mentioned the pure Thread firmware is better, I decided to switch:

I stopped the multi protocol addon
I installed the Openthread addon
Rebooted the whole OS

But the addon keeps crashing:

[12:22:54] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[12:22:54] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-01-11 12:22:54.646 homeassistant universal_silabs_flasher.flash INFO Extracted GBL metadata: NabuCasaMetadata(metadata_version=1, sdk_version='4.4.0', ezsp_version=None, ot_rcp_version='SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0), fw_type=<FirmwareImageType.OT_RCP: 'ot-rcp'>, baudrate=460800)
2024-01-11 12:22:54.647 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-01-11 12:22:56.659 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2024-01-11 12:22:57.775 homeassistant universal_silabs_flasher.flasher INFO Detected ApplicationType.SPINEL, version 'SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0) at 460800 baudrate (bootloader baudrate None)
2024-01-11 12:22:57.775 homeassistant universal_silabs_flasher.flash INFO Firmware version 'SL-OPENTHREAD/2.4.0.0_GitHub-7074a43e4' (2.4.0.0) is flashed, not re-installing
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[12:22:58] INFO: Setup OTBR firewall...
[12:22:58] INFO: Starting otbr-agent...
otbr-agent[183]: [NOTE]-AGENT---: Running 0.3.0-657e775-dirty
otbr-agent[183]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[183]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[183]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800&uart-flow-control
otbr-agent[183]: [NOTE]-AGENT---: Radio URL: trel://enp6s18
otbr-agent[183]: [NOTE]-ILS-----: Infra link selected: enp6s18
otbr-agent[183]: 00:00:00.051 [N] RoutingManager: BR ULA prefix: fd63:a04:9439::/48 (loaded)
otbr-agent[183]: 00:00:00.051 [N] RoutingManager: Local on-link prefix: fdfa:1f03:5e4d:4de2::/64
otbr-agent[183]: 00:00:00.100 [N] Mle-----------: Role disabled -> detached
otbr-agent[183]: 00:00:00.115 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[183]: 00:00:00.124 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[183]: 00:00:00.125 [W] Platform------: [netif] ADD [U] fe80:0:0:0:5402:9efd:e664:d6f7 failed (InvalidArgs)
otbr-agent[183]: 00:00:00.125 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:00.125 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:ded5:b4e8:c20d:24ac failed (InvalidArgs)
otbr-agent[183]: 00:00:00.125 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:00.125 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:3000 failed (InvalidArgs)
otbr-agent[183]: 00:00:00.125 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:00.125 [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
[12:22:58] 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[183]: 00:00:26.167 [N] Mle-----------: RLOC16 3000 -> fffe
otbr-agent[183]: 00:00:26.170 [W] Platform------: [netif] Failed to process request#8: Operation not supported
otbr-agent[183]: 00:00:26.335 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[183]: 00:00:32.836 [N] RouterTable---: Allocate router id 12
otbr-agent[183]: 00:00:32.836 [N] Mle-----------: RLOC16 fffe -> 3000
otbr-agent[183]: 00:00:32.839 [N] Mle-----------: Role detached -> leader
otbr-agent[183]: 00:00:32.840 [N] Mle-----------: Partition ID 0x526332d5
otbr-agent[183]: 00:00:32.890 [W] Platform------: [netif] Failed to process request#9: File exists
otbr-agent[183]: 00:00:32.890 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[183]: 00:00:32.890 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[183]: 00:00:33.782 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[183]: 00:00:33.782 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:33.783 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[183]: 00:00:33.783 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:35.391 [W] Platform------: [netif] ADD [U] fd63:a04:9439:1:e8af:6905:431c:c12d failed (InvalidArgs)
otbr-agent[183]: 00:00:35.391 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:42.684 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[183]: 00:00:42.684 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:01:02.095 [W] P-RadioSpinel-: Wait for response timeout
otbr-agent[183]: 00:01:02.095 [C] Platform------: HandleRcpTimeout() at radio_spinel.cpp:2066: RadioSpinelNoResponse
[12:24:00] WARNING: otbr-agent exited with code 6 (by signal 0).
OTBR_FORWARD_INGRESS  all opt    in * out wpan0  ::/0  -> ::/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
OTBR_FORWARD_EGRESS  all opt    in wpan0 out *  ::/0  -> ::/0  
Chain OTBR_FORWARD_EGRESS (0 references)
target     prot opt source               destination         
ACCEPT     all      anywhere             anywhere            
[12:24:00] INFO: OTBR firewall teardown completed.
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service otbr-agent-rest-discovery: stopping
s6-rc: info: service otbr-agent-configure: stopping
s6-rc: info: service mdns: stopping
s6-rc: info: service otbr-agent-rest-discovery successfully stopped
s6-rc: info: service otbr-agent-configure successfully stopped
s6-rc: info: service otbr-agent: stopping
Default: mDNSResponder (Engineering Build) (Jan  9 2024 18:57:09) stopping
s6-rc: info: service otbr-agent successfully stopped
s6-rc: info: service universal-silabs-flasher: stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
[12:24:00] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped

wmaker · January 11, 2024, 5:59pm

I myself did the migration a couple of days ago, and the mistake I made was I thought I could keep the SiLabs Multiprotocol installed but turned off. It turns out something (I think its HA core) restarts the SiLabs AddOn behinds the scene regardless and this caused problems with the OTBR AddOn. I ended up removing the SiLabs AddOn, then OTBR AddOn seemed to work.

carstenb · January 11, 2024, 6:18pm

My gosh, you are right, thanks for the hint.
The only messages left which look a bit strange are:

otbr-agent[183]: 00:00:26.192 [N] Mle-----------: RLOC16 3000 -> fffe
otbr-agent[183]: 00:00:26.195 [W] Platform------: [netif] Failed to process request#8: Operation not supported
otbr-agent[183]: 00:00:26.860 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[183]: 00:00:33.360 [N] RouterTable---: Allocate router id 12
otbr-agent[183]: 00:00:33.360 [N] Mle-----------: RLOC16 fffe -> 3000
otbr-agent[183]: 00:00:33.364 [N] Mle-----------: Role detached -> leader
otbr-agent[183]: 00:00:33.364 [N] Mle-----------: Partition ID 0x9ebded4
otbr-agent[183]: 00:00:33.409 [W] Platform------: [netif] Failed to process request#9: File exists
otbr-agent[183]: 00:00:33.409 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[183]: 00:00:33.409 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[183]: 00:00:34.037 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[183]: 00:00:34.037 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:34.037 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[183]: 00:00:34.038 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:36.360 [W] Platform------: [netif] ADD [U] fd63:a04:9439:1:e8af:6905:431c:c12d failed (InvalidArgs)
otbr-agent[183]: 00:00:36.360 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[183]: 00:00:46.025 [W] Platform------: [netif] ADD [U] fd53:9bb5:e2ae:a172:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[183]: 00:00:46.025 [W] Platform------: [netif] Failed to process event, error:InvalidArgs

invalidargs doesn’t look normal to me…

wmaker · January 11, 2024, 6:22pm

The other two things I had to do was

add the OTBR to the preferred network so as to pick up the dataset/credentials the SiLabs Multiprotocol Addon was using.
The OTBR Integration was failing to communicate. I had to delete the OTBR Integration, then reboot HA Core and Core recreated the OTBR Integration and successfully connected.

carstenb · January 12, 2024, 8:01am

I did the same but the strange errors from above persist.
But I found the same netif errors in a bug report:

github.com/home-assistant/addons

OpenThread Border Router not working anymore

opened 09:47PM - 08 Jan 24 UTC

fuomag9

### Describe the issue you are experiencing OpenThread Border Router not workin…g 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? ```txt [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_

wmaker · January 12, 2024, 1:55pm

I seem to recall (but could be badly mis-remembering) seeing those same errors until I got the dataset/credentials back to what they were originally which is what “adding” the OTBR to original “preferred” network should have done.

Chv1 · January 13, 2024, 9:49pm

What do you use as a OTBR Url in the configuration
“Provide URL for the Open Thread Border Router’s REST API” ?

carstenb · January 14, 2024, 7:16am

OTBR URL: http://core-openthread-border-router:8081