Yep. If you encounter issues with matter / thread. For me it was first and foremost pairing issues. But my problem with Thread Devices’ connectivity went away as well.
I did ask it about other adapters and it recommended some, but of course said it can only guarantee that it works stable if I get the official one (which I did to end my odyssey). 
That was my primary issue. Get an Ethernet adapter. I didn’t want to believe it either. And don’t listen to deejayreissue (“it’s IPv6, stop tinkering”) he’s wrong about this.
Get it, connect your devices. Just make sure to create a matter code from within google home in order to connect an already elsewhere connected device to another matter controller (Homey).
// Edit: just realized you have SHS on probably your own hardware. Then my fix probably won’t work of course. You can still try to connect whatever you use to Ethernet if you didn’t already. No guarantees though.
I’d blame your hardware.
Same issues with Onvis here. But (!) you can update them. Just not via matter but via the Onvis app. It’s an entire ordeal and I only did it for 2 of my plugs so far as it takes ages and doesn’t always work the first time, etc.
However, the updated ones are more stable and won’t just drop out after a while. Give it a shot.
Apple home will also update the plugs without the app
IPv6 is one of the main culprits for Thread issues and this is widely known
I had serious issues with IPv6, because I was running a separate router for IOT behind my ISP router.
Just because it might not be the issue here, doesn’t mean it isn’t worth looking into for other people
Could be an ipv6 issue, although my (local) ipv6 stack seems to work fine. I was able to link my matter devices to the Smartlife app.Pairing starts out fine, but times out. Would be helpful if it showed more info (both shs and the homey app)
Homey [log][ManagerMatterLocal] [Pairing:0xa7c1845b] Starting pairing with ip
Homey [log][ManagerMatterLocal] [Pairing:0xa7c1845b] Pairing to device…
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat
Homey [log][ManagerApiLocal] IO homey:manager:drivers:emitPairingHeartbeat → Success 204
Homey [err][ManagerMatterLocal] [Pairing:0xa7c1845b] Finished with error: Could not pair node (Matter code: TIMEOUT (0x0032))
Homey [err][ManagerMatterLocal] [Pairing:0xa7c1845b] Could not stop pairing: Could not stop pairing (Matter code: INVALID_DEVICE_DESCRIPTOR (0x0033))
Homey [err][ManagerMatterLocal] [Pairing:0xa7c1845b] Failed: Could not pair node (Matter code: TIMEOUT (0x0032)) (at stage: unknown)
The Smart Life app does not use Matter, it uses the regular Tuya connection like any other Tuya device. You can add your device using this Homey app as well:
I would recommend using this official Tuya app for your device, it works a lot better and more reliable than Matter
You cant check the preferred thread network on SHS - the app gives you a red warning banner. Homey support said thats normal and they will remove it in time.
I only have one thread network active in my home now.
I gave ipv6 on and ive tried with firewall on and off!
When I had the HP23 it was fine. Shs is not
They’re not Tuya devices but Ikea Kajplatz lightbulbs. I only stated that I was able to share a matter device to the Smartlife app, in the same way I would share it with Homey.
But then you likely have the new Tuya Matter/Thread gateways. You can use the Tuya Homey app for these as well
I finally got it working thanks to a post on the Home Assistant community forum. I’m running Homey SHS on a Synology NAS which apparently lacks certain capabilities to get it working easily.
Before pairing, start this container:
Pairing was instant after that. Afterwards, you can stop the container, it doesn’t need to be active anymore. It adds a route to the NAS making connecting to the edge router possible.
I’m too unfamiliair with ipv6 too understand why it didn’t work before.
My ipv6 prefix for my lan is fd00, but my thread network is fdb8 apparently. This container made a route between the two, since my Synology couldn’t do it on it’s own.
