I’ve had my Home Hub 2 (aka v4) since early November 2025. Prior to this I was using the Aeotec v3 device.
I have a collection of devices , bulbs, temp sensor, motion sensors, outlets etc.
A good selection of this was zigbee. But before getting the v4 I added about 10 Nanoleaf matter over thread bulbs and a couple of matter over thread (MoT) outlets.
The swap process to v4 was mostly painless and I’ve recently started replacing devices and adding a few more MoT devices, mostly from IKEA, 2 motion sensors, a few bilresa buttons, a timmerflotte temp sensor and a Alpstuga air quality monitor and a Meross MoT human presence sensor, a myggbett contact sensor, 2 MoT leak sensors.
As I’ve expanded my portfolio of devices I’ve noticed some instabilities.
Some devices go offline, and when they do sometimes I can’t get them back even after removing batteries and replacing them. If I force the issue by re pairing the existing device again a new device appears and gets paired leaving a ghost non-functional one remaining. Screen shot 1
The onboarding process can be flaky for me, especially with android app (). Often it asks which st thread network I want to connect to (I only have one) so it gives a list of one to choose from. Then it will often prompt for the network key, which won’t be remembered if prompted again for another device. Sometimes I can add the device without it prompting for the network key but I typically need a hub reboot for this.
screenshot 2
I’ve tried also adding matter devices to Alexa using either the share from St app or adding from Alexa as a matter device. When matter devices are shared with Alexa using either approach their appearance comes and goes in Alexa, sometimes forcing a refresh in the app brings it back, sometimes not.
This evening I had one of the IKEA motion sensors not respond to motion even though it appeared online. It came back after a hub reboot.
I’ve had quite a few reboots in last 2 months now, maybe one a week? Whilst the reboot itself seems fast enough it can take up to 10 to 20 mins for MoT devices to come back online.
Not sure it’s significant, but it looks like the contact sensors are especially prone to dropping offline and not coming back. Although both Meross and lafaer human presence sensors have also dropped off too, and a bilresa has too and an Ikea MoT motion sensor too.
This all sounds quite negative but it’s probably not as bad as it sounds when I write it down.
Zigbee devices have mostly been ok, but then again, I’ve mostly been removing these rather than adding more zigbee gear. I’m just noting down my experiences in case it’s of use to other members, or if you’ve had similar experiences and know a way of improving stability let me know.
Same thing happened to me today! Rebooted the hub, some IKEA buttons became offline. After a while they wanted to be paired again and the old devices remained offline as ghosts.
Had to power cycle the hub, because a bridged Matter device disappeared, which reappeared shortly after.
What’s weird: I now have another temperature sensor device in my living room that I’ve never seen before. It shows a sensible, but different temperature than all of the other devices.
No. I have only one TBR and therefore only one Thread network.
As for the weird behavior of the IKEA devices, I’m hoping they’ll receive a firmware update (with Thread 1.4 support). They seem to have a problem when the TBR goes down temporarily.
Same here, it’s prompting for the network key of the SmartThings tbr. Obviously odd because that information should be available to the ST app so it ought not to prompt for it,
About 10 minutes ago my hub just went bonkers. I was sitting watching tv and basically everything in the whole house toggled, things that were off turned on and thing that were on turned off. Even the back room tv came on and it isn’t smart, can only be triggered with an ir transmitter, so this came on via a linked service (smartlife integration). Further some virtual switches flipped state, and our dishwasher was turned off.
Really weird. Dunno what’s going on, never experienced anything like it.
I guess smartthings ran a scene on smartlife which triggered the ir transmitter to send the signal to turn the TV on. Why it happened is a mystery though
I still haven’t worked out the root cause for this , but I have a suspicion of what caused it, but not why or how.
I was watching tv at the time and had just switched sources on my Samsung tv. My Samsung tv has a SmartThings app (which is pretty rubbish and I don’t use it, but it is connected to my SmartThings account) I’m wondering the the tv app is the culprit here. If it is I can’t see how it managed to flip the state of every device in the house, there’s no option to do that in the app, and there’s certainly no automation to do it.
@Andreas_Roedl
Timmerflotte temp sensor has gone offline tonight. It’s in a room with 6 other mains powered matter over thread devices so ought not to be struggling with finding a thread connection.
I’m going to leave it a while and see if it comes back itself
Realised it had been offline for over 24 hours and got fed up waiting. Managed to get it to rejoin network by holding down pairing button till first flash and releasing, ie dont wait till it starts blinking for pairing mode.
I think all of this on the overloaded 2.4GHz band is destined to be a house of cards. Wifi competing with bluetooth competing with zigbee competing with thread (competing with the neighbor’s all-of-the-above if you’re in a dense area). It was insanity IMO for ST to drop ZWave.
