#OTBR add-on fails to initialize device on Home Assistant Yellow

1 messages · Page 1 of 1 (latest)

scarlet hawk
#

Hi,

I received a Home Assistant Yellow a little while ago to get Matter and Thread support. I migrated my HAOS installation to it and everything went smoothly. After some struggling, I got the built-in radio working in Zigbee mode with some Philips Hue devices that I have.

Now I have an Aqara presence sensor that is Matter over Thread and I would like to switch. The OTBR add-on flashed the radio to the Thread firmware successfully.

The add-on croaks on startup, unable to initialize the radio:

[NOTE]-AGENT---: Radio URL: trel://end0
[NOTE]-ILS-----: Infra link selected: end0
[INFO]-RCP_HOS-: OpenThread log level changed to 5
49d.17:21:07.352 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:0, cmd:RESET
49d.17:21:07.352 [D] P-SpinelDrive-: Waiting response: key=0
49d.17:21:09.353 [W] P-SpinelDrive-: Wait for response timeout
49d.17:21:09.353 [I] P-SpinelDrive-: co-processor self reset successfully
49d.17:21:09.353 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.17:21:09.353 [D] P-SpinelDrive-: Waiting response: key=1
49d.17:21:11.355 [W] P-SpinelDrive-: Wait for response timeout
49d.17:21:11.355 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.17:21:11.355 [D] P-SpinelDrive-: Waiting response: key=1
49d.17:21:13.357 [W] P-SpinelDrive-: Wait for response timeout
49d.17:21:13.357 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
49d.17:21:13.357 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.17:21:13.357 [D] P-SpinelDrive-: Waiting response: key=1
49d.17:21:15.359 [W] P-SpinelDrive-: Wait for response timeout```

I've tried with and without hardware flow control. I've found a few similar bug reports but no apparent solutions. Any ideas?

-- Mike
celest prawn
#

Is ZHA still trying to use the radio?

scarlet hawk
#

No

#

I deleted it

scarlet hawk
#

In the past I've gotten Python exceptions about the device being locked by another process, but not the case here

scarlet hawk
#

Bump - I was travelling for a few days, but I'm home now and would like to get back to this issue and see if I can resolve it. Any ideas out there?

celest prawn
#

Is the baudrate set to 460800?

scarlet hawk
scarlet hawk
#

Anything else I can check?

scarlet hawk
#

Well, I got it working. I downgraded the firmware to OpenThread RCP 2.2.3.0 and disabled hardware flow control.

#

With that firmware and hardware flow control enabled, it times out

#

I found a bug report on github or Silicon Labs where they introduced the uart-init-deassert URL parameter

#

And I think I only got the zha integration working when I removed both hardware and software flow control

#

Is it possible to edit the URL that the OTBR add-on uses?

celest prawn
#

No. The add-on always uses the hostname core-openthread-border-router on the Docker network.

scarlet hawk
#

Sorry, I meant the radio URL it opens

# 
Radio URL: spinel+hdlc+uart:///dev/ttyAMA1?uart-baudrate=460800&uart-flow-control
celest prawn
#

That's likely defined by the add-on settings.

scarlet hawk
#

I should probably file a bug. Do you think ha-core is the right place?

celest prawn
#

No, in this case the add-on repository on GitHub is the right place.

scarlet hawk
#

Thanks

#

Well, pairing is failing. There are a bunch of network errors. I have an appointment so I'll get back to this shortly

scarlet hawk
#

And now pairing worked

#

Plenty of errors like

00:02:48.835 [I] Mac-----------: Frame tx attempt 1/1 failed, error:NoAck, len:84, seqnum:251, type:Data, src:0xc400, dst:0xc404, sec:yes, ackreq:yes, radio:15.4
```, which I wonder if these are because the HA Yellow is in a small cabinet right next to my Ubiquiti Dream Machine (WiFi access point) and Philips Hue hub
#

Probably a very noisy environment

dapper sinew
#

That post shows the Zigbee channels ably. But Zigbee and Thread use the same channel scheme.

#

I do not use 2.4GHz WiFi channel 11, only 1 and 6. My HueBridge is configured to Zigbee channel 20 and my Thread network uses Thread channel 25. Thread channel 25 is the default, when you have Apple Thread Border Routers.