Hi.
I’ve and OpenThread Border Router installed on an ESP router board.
All seems works fine an I can access to it via web GUI:
I’ve Matter Server installed on my HA:
and on Thread device I can see my Thread border router:
Than, by launching HA app on my Android Phone, I try import credential:
but after few seconds it say to me that there aren’t credential to import:
And, finally, I can’t add thread border router and , than, Thread devices
Where am I wrong?
Any idea?
Thanks in advance
Did you install the open thread border router integration ?
You should have something like that
Try to click on openthread-Ox99 and make it the preferred Open Tread border router
Hi Francis.
Thanks for your reply.
I’ve tried to install OpenThread Border Router addon but it start and after few seconds stop.
If I look into register I see this:
[16:39:01] 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
[16:39:01] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Feb 29 2024 14:39:08) starting
s6-rc: info: service legacy-cont-init successfully started
-----------------------------------------------------------
Add-on: OpenThread Border Router
OpenThread Border Router add-on
-----------------------------------------------------------
Add-on version: 2.5.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.2 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2024.4.4
Home Assistant Supervisor: 2024.04.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
[16:39:02] INFO: The selected serial port is not a USB device.
[16:39:02] WARNING: No firmware found for the selected device, assuming firmware is installed.
s6-rc: info: service universal-silabs-flasher successfully started
s6-rc: info: service otbr-agent: starting
[16:39:02] INFO: Setup OTBR firewall...
[16:39:03] INFO: Starting otbr-agent...
otbr-agent[168]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[168]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[168]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[168]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyAMA10?uart-baudrate=460800&uart-flow-control
otbr-agent[168]: [NOTE]-AGENT---: Radio URL: trel://end0
otbr-agent[168]: [NOTE]-ILS-----: Infra link selected: end0
otbr-agent[168]: 49d.17:46:46.151 [W] P-RadioSpinel-: Wait for response timeout
otbr-agent[168]: 49d.17:46:48.151 [W] P-RadioSpinel-: Wait for response timeout
otbr-agent[168]: 49d.17:46:48.151 [C] P-RadioSpinel-: Failed to communicate with RCP - no response from RCP during initialization
otbr-agent[168]: 49d.17:46:48.151 [C] P-RadioSpinel-: This is not a bug and typically due a config error (wrong URL parameters) or bad RCP image:
otbr-agent[168]: 49d.17:46:48.151 [C] P-RadioSpinel-: - Make sure RCP is running the correct firmware
otbr-agent[168]: 49d.17:46:48.151 [C] P-RadioSpinel-: - Double check the config parameters passed as `RadioURL` input
otbr-agent[168]: 49d.17:46:48.151 [C] Platform------: HandleRcpTimeout() at radio_spinel.cpp:2092: RadioSpinelNoResponse
[16:39:07] WARNING: otbr-agent exited with code 6 (by signal 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
Chain OTBR_FORWARD_EGRESS (0 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere
[16:39:07] INFO: OTBR firewall teardown completed.
s6-svlisten1: fatal: /run/s6-rc/servicedirs/otbr-agent failed permanently or its supervisor died
s6-rc: warning: unable to start service otbr-agent: command exited 1
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service universal-silabs-flasher: stopping
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service mdns: stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: stopping
Default: mDNSResponder (Engineering Build) (Feb 29 2024 14:39:08) stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
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
[16:39:07] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped
Anyway it seems to me that this addon is used when you want that your HA is a Thread Border router.
In my case I want that my ESP board is the border router and don’t my HA that is hosted on a Raspberry Pi5
Normally, IP of your ESP router :8081
e.g. 10.0.0.66:8081 or http://10.0.0.66:8081 (don’t remember exactly)
Hi Francis.
A step forward.
With ip address of OTBR now works:
Anyway when I try to add an ESP matter device (created fro ESP Zerocode platform) from HA app on my Android phone, after connection to device, I see this (The device require an OTBR):
Probably I’m missing the last step.
Maybe try this:
