I’ve recently purchased a SkyConnect USB for the Zigbee + Thread use, and have nothing but issues trying to make it work.
I’m using a HASSIO VM on Unraid with the SkyConnect USB as a passthrough. The ZHA integration worked after the next VM boot, as HA prompted to configure. I’ve setup the Silicon Labs Multiprotocol addon and Multi-PAN and enabled the Multiprotocol option via Settings → System → Hardware. They are both on the same radio channel (have tried 15 and 25 as initially the SkyConnect radio and ZHA radio integrated on different channels) and I can integrate my Zigbee sensors (Aqara Motion FP1s). That’s where the smoothness ends and the issues begin…
I have ~a dozen Nanoleaf Essential bulbs and had paired them all through BLE on the Android app. I’ve read that to make the migration into Thread that the bulbs may need to be reset, so I’ve been testing with one. The Thread Network option in the Android app can see a network named ‘home-assistant’ but is greyed out. Unfortunately I don’t know how far along this process that appeared as I’ve been at this for a few days.
In HA, I have the official Matter, OTBR and Thread add-ons configured (HA prompted to configure automatically after the Multiprotocol addon was enabled and the Multi-Pan addon was installed). This all looked good. The Android app cannot see the same radio settings that are currently configured on the OTBR, so I ended up resetting all 3 addons after a few days of troubleshooting. The unique identifiers in OTBR are all different to what they were initially, and still the Android app cannot see the Thread network.
While pairing one of the bulbs, I was looking at the Matter logs in debug mode and found a pairing attempt had come through from the Android app! Great, I thought… except the app still did not see the Thread network and continued to pair by BLE. I borrowed an iPhone to install the Discovery DNS-SD app check whether the HA Thread integration was even showing up, and it was (under _meshcop._udp.) listed as 'Home Assistant Silicon Labs Multiprotocol #. It could see the v4 address of the VM and 3 iterations of v6 addressing, as well the Thread version (1.3.0). For what it’s worth, my network is all Ubiquiti/Unifi with VLANs in place, so I initially throught that UDP broadcasting across VLANs may have been an issue, however I also have several Chromecasts sitting on the network on one VLAN which are accessible by others without issue, so I dismissed this being a problem (for now, anyway).
I know there are a lot of moving parts and fairly new integrations have their teething issues, but I’m at a loss as to how to progress from here. I would rather not use HomeKit with this integration at all as I do not own any Apple products or devices.
Any help would be appreciated. Thanks.