Trying to setup a Thread network via SkyConnect

I’m trying to set up a Thread-enabled Aqara door P2 sensor. I have purchased a Skyconnect USB dongle and flashed it with Thread RCP (instead of the dual-protocol Zigbee & Thread because I already have a functional Zigbee antenna). I have installed and setup the Matter Server and Open Thread Border Router add ons as well as the Matter (BETA), Open Thread Border Router, and Thread integrations. I see nothing unusual in the logs of the add ons and the Integrations aren’t reporting any errors that I can find. When I go to add the sensor to my HA instance using the Companion app, I can see that the device is able to establish a connection to my phone (an iPhone 13 Pro running iOS 16.6) because the P2 starts blinking fast but then the Companion app gives me an error stating “Thread Border Router Required.” I don’t understand why the Companion app doesn’t see the established TBR since HA isn’t showing me anything (that I have found) that resembles a configuration or runtime error. I’ve been beating my head on this off & on for a week, have worn out Google trying to solve it, and am completely out of ideas. Can anyone help me figure out what I’ve done wrong or missed in trying to get this working, please?

One bit that seems suspicious is that the logs of the Matter Server addon does report a warning which had me rabbit holed for hours:

2024-02-15 16:55:04 core-matter-server zeroconf[126] WARNING Error with socket 69 (('::1', 5353, 0, 0))): [Errno 101] Network is unreachable
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 1200, in sendto
    self._sock.sendto(data, addr)
OSError: [Errno 101] Network is unreachable

But after setting the log level to debug, it immediately prints these additional statements which seem to indicate that it is actually connected to the network and listening for activity:

2024-02-15 16:55:11 core-matter-server matter_server.server.client_handler[126] DEBUG [547839923600] Connected from 192.168.1.176
2024-02-15 16:55:11 core-matter-server matter_server.server.client_handler[126] DEBUG [547839923600] Received: {
  "message_id": "25e69c9789794a529adcd93bd4f8b7a6",
  "command": "start_listening",
  "args": null
}
2024-02-15 16:55:11 core-matter-server matter_server.server.client_handler[126] DEBUG [547839923600] Received CommandMessage(message_id='25e69c9789794a529adcd93bd4f8b7a6', command='start_listening', args=None)
2024-02-15 16:55:11 core-matter-server matter_server.server.client_handler[126] DEBUG [547839923600] Handling command start_listening

My HA instance is running HAOS on a RPi4. It is physically located ~10 feet away from the sensor that I’m trying to pair with it with an interior wall between them. The Skyconnect is connected to the USB port with an extension dongle per recommendations related to potential interference.

The problem is that the HA iOS Companion App has an issue/bug (I think within Apple’s SDK) that doesn’t allow the companion App to get/store the Thread network dataset/credentials. This has been a problem from day one, but the developers on Discord talk about a fix coming soon.

The alternative for now is to use an Android based HA Companion App.

1 Like

Thanks for the informative response, @wmaker . I don’t own any Android devices; is there any other alternative?