I bought a ZBT-1 (says Home assistant ZBT-1 on the back) to connect a Aquara P2 motion sensor to my home Assistant OS on a raspberry Pi 5.
-I have disconnected the USB hub and coral that was on it.
-My phone is on the 2.4GHz wifi network and has blue tooth on.
- In the threads add on configuration I have enabled NAT64 and enabled IPv6 on my AT&T router.
- I have disabled the OTBR firewall.
- My OTBR add on says it is running, here is a snapshot of some of the logs
Add-on: OpenThread Border Router
OpenThread Border Router add-on
-----------------------------------------------------------
Add-on version: 2.13.0
You are running the latest version of this add-on.
System: Home Assistant OS 15.2 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2025.4.4
Home Assistant Supervisor: 2025.04.1
-----------------------------------------------------------
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
[21:04:10] INFO: Checking /dev/ttyUSB0 identifying Home Assistant Connect ZBT-1 from Nabu Casa.
[21:04:10] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2025-04-28 21:04:11.402 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-04-28 21:04:11.403 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2025-04-28 21:04:13.409 homeassistant universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2025-04-28 21:04:14.521 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-04-28 21:04:14.521 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
[21:04:15] INFO: Setup OTBR firewall...
[21:04:15] INFO: Starting otbr-agent...
[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=115200&uart-flow-control
[NOTE]-AGENT---: Radio URL: trel://end0
[NOTE]-ILS-----: Infra link selected: end0
[INFO]-RCP_HOS-: OpenThread log level changed to 5
49d.18:36:16.092 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:0, cmd:RESET
49d.18:36:16.092 [D] P-SpinelDrive-: Waiting response: key=0
49d.18:36:18.094 [W] P-SpinelDrive-: Wait for response timeout
49d.18:36:18.094 [I] P-SpinelDrive-: co-processor self reset successfully
49d.18:36:18.094 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.18:36:18.095 [D] P-SpinelDrive-: Waiting response: key=1
49d.18:36:20.097 [W] P-SpinelDrive-: Wait for response timeout
49d.18:36:20.097 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.18:36:20.097 [D] P-SpinelDrive-: Waiting response: key=1
49d.18:36:22.099 [W] P-SpinelDrive-: Wait for response timeout
49d.18:36:22.099 [C] Platform------: Init() at spinel_driver.cpp:83: Failure
49d.18:36:22.099 [D] P-SpinelDrive-: Sent spinel frame, flg:0x2, iid:0, tid:1, cmd:PROP_VALUE_GET, key:PROTOCOL_VERSION
49d.18:36:22.099 [D] P-SpinelDrive-: Waiting response: key=1
49d.18:36:24.101 [W] P-SpinelDrive-: Wait for response timeout
[21:04:23] WARNING: otbr-agent exited with code 1 (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
[21:04:23] 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
s6-rc: info: service mdns: 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.
Default: mDNSResponder (Engineering Build) (Jan 14 2025 21:08:25) stopping
s6-rc: info: service universal-silabs-flasher successfully stopped
s6-rc: info: service banner: 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
[21:04:23] INFO: mDNS ended with exit code 4 (signal 0)...
s6-rc: info: service mdns successfully stopped
I don’t know how to get to /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. So I can’t post those.
-I have changed the batteries on the P2
- I have done a factory reset, not just removing the batteries.
And after all of this, I always get the same error:
-The phone sees the device, I have to type in the code ( the QR is too small for my phone to see it). It says “connecting to device” while the P2 flashes blue rapidly, the
The device requires a thread border router. Connect your border router, then try setting up your device
Oh, and I have set in in pariing mode after selecting add device and looking for it in HA-> devices, a well as before.
My device is plugged into the USB3.0 port with a the 18" cord it comes with three feet away from the router.
Any ideas?