That is the feeling I have also. I am trying to set up a small mesh of 15 devices, including Eve plugs, an Onvis plug (which consistently shows as End point and not Router using the Eve app), Ikea lights and endpoint accessories. Sounds very few I know but it’s in a single level house of only around 70m2 and I’ve taken the precaution of keeping the majority of devices (Zigbee) on channel 15, wifi on 11 while the Thread fabric with 2 TBR is on channel 25.
Everything pairs fast but after shariing, a couple of hours later, drop off line.
Guess I’ll have to forget multi platform for a while.
1 Like
I’m assuming this means the cloud to cloud integration route (eg smarthings to Amazon Alexa). The disadvantage of this approach is that not all the capabilities are exposed via this route, eg only the temperature of the IKEA air quality sensor is exposed to Alexa, so you can’t for example use Alexa to make announcements based on air quality settings .
Correct, the suggested workaround is the cloud to cloud integration.
And I don’t have any experience with Alexa. But as a workaround to cloud to cloud limitations, I used my BILRESA button paired in ST’s to increase or decrease the volume of my Google Home speakers using virtual switches. I also use that same button to turn on/off a ceiling fan in ST’s. So the same button is still triggering automations on both platforms. And all of my thread devices in ST’s are now staying online.
Following on from my earlier post I deleted all Thread endpoint devices, and also an Onvis plug, and re-paired to one hub, with no further sharing.
I have however maintained the router devices - IKEA lights and Eve plugs (which I use in API rules and Smartthings Energy), on 2 platforms. In the case of the Alpstuga sensor I have it shared also to Alexa, so far without issues.
1 Like
Let me know how you get on with the alpstuga share to alexa. I had stability issues when I had the share but still don’t know if it was the root cause or not. I suspect not but it is by far the chattiest device I have
Good luck. You may also want to check out this article which I found extremely helpful: Fixing Matter Connectivity: The Definitive Guide to Stable Multi-Brand Smart Homes in 2026 - The Daily Sroll
1 Like
Thanks for the URL.
I am playing with my new V4 hub and did a reboot via Advanced.
Now my Ikea MYGGBETT doorsensor is ofline. It was directly connected and just two meters from the hub.
Shall I wait first?
On the long rung I want to replace all my (ca 40) Zwave devices with Matter stuff… Wise decision?
I use 4 different locations. All remote, so taking out batteries is not an option if offline.
It’s more expensive than the IKEA Matter/Thread door/window sensor. Leave that one off and see whether things improve.
1 Like
Yeah, I took it off before Christmas, all my thread devices are now Onvis plugs, Nanoleaf lights and ikea motion,contact,temp,air quality sensors
Can you reboot your isp router remotely? If so, I would try that then wait for the mesh to rebuild.
I just “solved” it by keeping the device close to the v2 Hub. (I am on the location, but will leave tomorrow)
When holding it next to the ST hub, I removed the battery en did this 4 click on the button. But no light to be seen. And on a certain moment I got my Sharptools message that it was “open”.
This was during offlline diasnostics. But no idea if that was why its working again.
But you suggested to reboot the internet (isp) router? I may consider it next time. I cannot do that when not at home.
Here a part of “advanced” MYGGBETT door/window sensor
| main | firmwareUpdate | supportsProgressReports | ||
|---|---|---|---|---|
| main | contactSensor | contact | closed | 6 Mar 2026, 16:03 |
| main | battery | battery | 100 % | 6 Mar 2026, 15:16 |
| main | firmwareUpdate | currentVersion | 1.0.9 (16777225) | 4 Mar 2026, 13:37 |
| main | firmwareUpdate | state | normalOperation | 4 Mar 2026, 13:37 |
| main | firmwareUpdate | availableVersion | 1.0.9 (16777225) | 4 Mar 2026, 13:37 |
| main | firmwareUpdate | updateAvailable | false | 4 Mar 2026, 13:37 |
I did a ST hub reboot, but that did not help. I really have to study Matter and Thread much more.
Glad it’s resolved.
In my experience, most issues with matter over thread are caused by issues with the router, e.g. ipv6 issues, the setup, e.g. too many border routers or not enough thread routers, or matter limitations, e.g. multi admin and mesh bandwidth.
But it always appears on the surface as if there is something wrong with the device.
.
Aha I understand. Thanx
But the matter/thread IP6 are given by the ST hub, not by the ISP router?
and read this: Ikea alpstuga air quality sensor - #20 by Huib_o
The internal ipv6 thread mesh is created by the TBR.
But I had a problem with my netgear router. Likely poor handling of ipv6 prefix delegation. When the prefix chnages thread devices show offline.
I disabled ipv6 on my netgear router and my thread network is now stable.