I am running Home Assistant supervisor via docker on a Debian Bookworm based X86 box. I have setup Open Thread Border router and skyconnect however I can’t seem to pair the Aqara P2 sensor.
I have tried a few of the things mentioned on the forum, none have worked.
I have noticed I cannot get disable the OTBR firewall setting. If I do so I get the following error.
It might have paired somewhere else already,
Not a matter user, but this is a thing where they pair once with the barcode and then you have to share them or transfer them around or some weirdness.
Press and hold the button on it until it flashes pink once to reset it then power cycle your network and the vm and power cycle your phone then you should be able to connect it to the HA instance you have.
If you already have it linked to another service then you need to unlink it first or use the share function as you can only pair a matter device to a single primary hub/host at any given time and share it out from there to allow synced use between them.
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
[20:40:46] INFO: Starting mDNS Responder...
Default: mDNSResponder (Engineering Build) (Apr 26 2024 10:02:08) starting
-----------------------------------------------------------
Add-on: OpenThread Border Router
OpenThread Border Router add-on
-----------------------------------------------------------
Add-on version: 2.6.0
You are running the latest version of this add-on.
System: Debian GNU/Linux 12 (bookworm) (amd64 / qemux86-64)
Home Assistant Core: 2024.5.5
Home Assistant Supervisor: 2024.05.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
[20:40:47] INFO: Checking /dev/ttyUSB0 identifying SkyConnect v1.0 from Nabu Casa.
[20:40:47] INFO: Starting universal-silabs-flasher with /dev/ttyUSB0
2024-05-28 20:40:48.012 miniserver1 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), cpc_version=None, fw_type=<FirmwareImageType.OT_RCP: 'ot-rcp'>, baudrate=460800)
2024-05-28 20:40:48.012 miniserver1 universal_silabs_flasher.flasher INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2024-05-28 20:40:50.019 miniserver1 universal_silabs_flasher.flasher INFO Probing ApplicationType.SPINEL at 460800 baud
2024-05-28 20:40:51.136 miniserver1 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-05-28 20:40:51.137 miniserver1 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
[20:40:51] INFO: Starting otbr-agent...
otbr-agent[175]: [NOTE]-AGENT---: Running 0.3.0-2279c02-dirty
otbr-agent[175]: [NOTE]-AGENT---: Thread version: 1.3.0
otbr-agent[175]: [NOTE]-AGENT---: Thread interface: wpan0
otbr-agent[175]: [NOTE]-AGENT---: Radio URL: spinel+hdlc+uart:///dev/ttyUSB0?uart-baudrate=460800&uart-flow-control
otbr-agent[175]: [NOTE]-AGENT---: Radio URL: trel://enp2s0
otbr-agent[175]: [NOTE]-ILS-----: Infra link selected: enp2s0
otbr-agent[175]: 00:00:00.050 [N] RoutingManager: BR ULA prefix: fd30:6117:6108::/48 (loaded)
otbr-agent[175]: 00:00:00.050 [N] RoutingManager: Local on-link prefix: fde8:145e:6600:b3f5::/64
ipset v7.17: The set with the given name does not exist
otbr-agent[175]: 00:00:00.062 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[175]: 00:00:00.073 [N] Mle-----------: Role disabled -> detached
otbr-agent[175]: 00:00:00.097 [N] Platform------: [netif] Changing interface state to up.
otbr-agent[175]: 00:00:00.106 [W] Platform------: [netif] Failed to process request#2: No such process
otbr-agent[175]: 00:00:00.106 [W] Platform------: [netif] ADD [U] fe80:0:0:0:7438:cd42:2048:618e failed (InvalidArgs)
otbr-agent[175]: 00:00:00.106 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:00.106 [W] Platform------: [netif] ADD [U] fd73:af30:73ae:1866:f02e:6c72:7c31:ed52 failed (InvalidArgs)
otbr-agent[175]: 00:00:00.106 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:00.107 [W] Platform------: [netif] ADD [U] fd73:af30:73ae:1866:0:ff:fe00:a400 failed (InvalidArgs)
otbr-agent[175]: 00:00:00.107 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:00.107 [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
Done
s6-rc: info: service otbr-agent-configure successfully started
[20:40:52] 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[175]: 00:00:27.249 [N] Mle-----------: RLOC16 a400 -> fffe
otbr-agent[175]: 00:00:27.803 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[175]: 00:00:34.303 [N] RouterTable---: Allocate router id 41
otbr-agent[175]: 00:00:34.303 [N] Mle-----------: RLOC16 fffe -> a400
otbr-agent[175]: 00:00:34.307 [N] Mle-----------: Role detached -> leader
otbr-agent[175]: 00:00:34.307 [N] Mle-----------: Partition ID 0x32efe765
ipset v7.17: The set with the given name does not exist
otbr-agent[175]: 00:00:34.316 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[175]: 00:00:34.336 [W] Platform------: [netif] ADD [U] fd73:af30:73ae:1866:0:ff:fe00:a400 failed (InvalidArgs)
otbr-agent[175]: 00:00:34.336 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:34.337 [W] Platform------: [netif] ADD [U] fd73:af30:73ae:1866:0:ff:fe00:fc00 failed (InvalidArgs)
otbr-agent[175]: 00:00:34.337 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
ipset v7.17: The set with the given name does not exist
otbr-agent[175]: 00:00:34.668 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[175]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
otbr-agent[175]: 00:00:34.675 [W] Platform------: [netif] ADD [U] fd73:af30:73ae:1866:0:ff:fe00:fc38 failed (InvalidArgs)
otbr-agent[175]: 00:00:34.675 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
otbr-agent[175]: 00:00:34.676 [W] Platform------: [netif] ADD [U] fd73:af30:73ae:1866:0:ff:fe00:fc10 failed (InvalidArgs)
otbr-agent[175]: 00:00:34.676 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
ipset v7.17: The set with the given name does not exist
otbr-agent[175]: 00:00:36.736 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[175]: 00:00:36.754 [W] Platform------: [netif] ADD [U] fd30:6117:6108:1:574d:74b7:7b73:a81b failed (InvalidArgs)
otbr-agent[175]: 00:00:36.754 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
ipset v7.17: The set with the given name does not exist
otbr-agent[175]: 00:00:37.580 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[175]: 00:00:41.350 [W] Mle-----------: Failed to process Child ID Request: Security
ipset v7.17: The set with the given name does not exist
otbr-agent[175]: 00:00:44.502 [W] Platform------: Failed to update ipsets: Failed
otbr-agent[175]: 00:00:44.507 [W] Platform------: [netif] ADD [U] fd73:af30:73ae:1866:0:ff:fe00:fc11 failed (InvalidArgs)
otbr-agent[175]: 00:00:44.507 [W] Platform------: [netif] Failed to process event, error:InvalidArgs
OK, that’s good. Anyway here is a writeup I did last year (I did it then on Multiprotocol, but now I’m using OTBR). There wasn’t anything in particular I did, it just happen to commission without much of a problem
Thanks, I did come across that post at one point in my search for an answer.
Out of curiosity what firmware are you running? I setup the multiprotocol option. Now I can’t seem to flash the firmware from the web tool and the device to HA only shows as /dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_80abc3cea296ed11b893c898a7669f5d-if00-port0
it doesn’t show as /dev/ttyUSB0 which I can see in the OS if I ssh into the box.
I haven’t yet looked at flashing the firmware from CLI yet to see if that helps.
I have also added an automation in the last few days to reload the silicon labs multiprotocol core addon after a switchbot turns off then on the usb hub port I have the skyconnect plugged into when my instance is restarted just to make sure everything loads up properly.
For reference as well here are the settings in my instance at this time
Its not sharing, I only have one Thread border router, my HA server with Skyconnect. I have factory reset the Aqara P2 and rebooted the server many times. All times the Android HA app gets stuck at ‘checking network connectivity’ and the server addon logs just show similar to my last set of logs.
eidt: I had 3 more delivered today which were detected and connected as they should once hitting add device on the popup then picking home assistant in the other app list.
i stucked at the same step. aqara p2, Skyconnect network check fail.
this so complicated, so many components… almost impossible to debug, where the problem is.
i tried everything i found on the web, but no luck.
I got this mostly from following the discussions on HA’s Discord Thread channel. However I did find some updated documentation on it here:
“We now do not recommend using this firmware [multiprotocol], and it will be experimental for the foreseeable future. Instead, we will focus on making sure the dedicated Zigbee and Thread firmwares for Home Assistant SkyConnect deliver the best experience to users. … The experimental multiprotocol firmware will remain available, but we will not recommend it to new users.”
Ever since I put my skyconnect into zigbee only mode and got a dedicated GL-S200 as the thread border router in my setup it’s been the best investment into keeping things stable so far.
This is the best path for users in the long term currently until more dev time is put into multipan.
