This is very interesting. I just added a Myggspray half an hour ago. It does not stop working.
Ever so quickly I saw an entry in on Homey-SHS concerning an IKEA “over-the-air update”.
My question was going to be that I was wondering about those OTA Updates. Matter devices, connected directly to Homey Pro or mini, are able to receive updates if IKEA pushes them. My question would be if this would also be the case for Homey’s that have no direct-thread support (like Homey-SHS or Homey 2019, etc.) Does the message mean that an update was pushed / received? My Myggspray is now on v1.0.7. What about yours?
(Might explain the reason why mine is still working and yours is not, dunno?)
I ran into something that might be related to what you’re seeing.
I have a Bilresa rotary knob that also became unavailable after some time. When I tried to recover or re-pair it (following the standard steps), I got an error saying that the device had reached the maximum number of instances it could be paired with.
After removing the device from my Homey Pro, I was able to pair it again successfully, and it has been working without any issues on my SHS since then.
This made me wonder if the issue could be related to Thread devices still being shared with multiple ecosystems (Homey Pro, Google, etc.).
Maybe worth checking:
Are these Ikea devices shared with multiple instances?
If so, try removing them from one first and then re-pairing them to SHS.
Not saying this is the cause, but it was the key difference in my case and might be worth a try.
My experience is also that all my IKEA Matter devices works very well on Apple TV, and the ones on Homey Pro 23 Matter network is very unstable. The IKEA Homesmart app also has serious flaws. I see that sometimes the view is OK on Homey
I’ve tried numerous approaches, including reinstalling SHS multiple times and resetting the Apple TV, but eventually gave up.
As a last resort, I disabled the firewall on the Synology DS918+ and restarted the system—and that solved the issue!
Technically, I should re-enable the firewall and test again to confirm, but I’m hesitant to touch anything now that it’s working. The firewall on the DS918+ appears quite basic, and I can’t find any options to adjust IPv6 settings. As a result, it seems the Thread network is likely blocked by default.
All my light bulbs worked, but my battery operated devices lost connection, probably caused by blocked ICMPv6 or multicast.
Athom should really implement better mechanisms to detect when something is wrong with the Thread network.
First of all I’m glad you find the culprit on your end.
But if it was the firewall, how could it have been functional before the SHS update?
(I’m just wondering a bit from a technical point of view)
I can’t be certain that it was the firewall that caused my problems.
I will get a definitive answer if I turn the firewall back on and test again, but I don’t want to do that right now since everything seems stable.
I’ll try again when/if I manage to move SHS to Proxmox.
I installed a Myggspray motion sensor, light bulbs, and a Dual Switch.
I tested them a few minutes later, and everything worked fine.
In the meantime, SHS was updated.
After a few days, when I was going to create an automation, I couldn’t reach the battery‑powered devices, but the light bulbs worked.
I removed the devices and tried again — they worked fine for a few minutes before dropping out.
I restored SHS, same thing happened — the devices worked for a few minutes.
I reset the Apple TV and did another restore, and the devices worked again for a few minutes.
After a few days, I gave up the “Thread project.”
During some other testing, I had to turn off the firewall on the Synology.
By coincidence, I then noticed that the Myggspray started reporting motion again, and it has been stable since.
According to AI, this may be because the firewall blocked one or more vital functions in the Thread network, such as ICMPv6, NDP, or Router Advertisement (RA).
Battery-powered devices are end devices and depend on NDP and RA functioning, as I understand it.
I cannot be 100% sure about the cause of my issues.
What I can state is that everything started working within minutes after the firewall was turned off.
And it may well be that the SHS update is what triggered the problem.