Im experiencing zigbee problems since 13.1, i have few Tuya zigbee single buttons, just to control lights,night mode…all are visible and connected in developer page/zigbee, but they do just nothing, wouldnt activate any single flow…
Hi,
I’ve had very similar issues and made many changes to my Wi-Fi network because I suspected interference between Wi-Fi and Thread. My setup only includes Matter over Thread and Matter over Wi-Fi devices — no Zigbee, no Z-Wave.
At one point, everything suddenly became stable and stayed that way for more than three weeks. I honestly believed my Wi-Fi adjustments had fixed it. But about two weeks ago, the exact same problem started again. A whole bunch of devices disappear at once.
A Homey restart immediately brings most of them back, which already says a lot. But some devices, such as a Heiman smoke detector, do not reconnect afterwards. I can repair them and they work again — until the next incident. After that, they are gone again.
So yes, in my opinion this is clearly a Homey issue. Even devices shared through multi-admin from Apple Home disappear in Homey while they continue to work perfectly in Apple Home.
That is what makes this so disappointing. Homey is actually a very nice system, and I have even developed three apps for it myself. But I’m now seriously considering moving to another platform and keeping my Homey Pro only as an overpriced hub for my PV dashboard, because the devices in my Fronius app never disappear.
I already returned my Homey 2019 years ago because Zigbee was too unstable. And now, years later, I’m seeing the same kind of instability again — this time with Matter.
I have a Homey Pro 2026 with auto updates turned on.
My timeline says it was updated to 13.1.1 6 days ago.
I have devices with Matter over Wi-Fi and Matter over Thread (and Zigbee).
Two Matter over Wi-Fi devices (both Tapo S505D) and one Matter over Thread devices (Eve Energy Smart Plug) went offline in the Homey app today.
Pressing the Restart button on the Tapo devices and cycling power on the Eve device brought them back.
This happened to me in the past. It was typically Thread devices and only in Homey, not Apple Home.
A Homey reboot immediately fixed the issue until the early mornings of the following day, when it would recur.
I also noticed though that my Philips Hue lights were acting a fool as well, but in different ways. I changed the zigbee channel from 25 to 20 on my Hue bridge, which solved all of my issues…
… until about a week ago, when the Thread/Homey issues have returned in this same way, but my Zigbee channel is not the culprit.
I’ve previously considered other mdns issues/possibiities, but nothing is sticking out to me right now.
Hello,
I think this is still a hardware issue – more specifically, an issue with the built-in Zigbee or Matter chip – and therefore needs to be resolved primarily by Athom.
The problem is well known. Zigbee and Matter (over Thread) share a single chip, and this chip is no longer powerful enough, even in the new 2026 version. As has been widely reported and as I have tested extensively myself, stability breaks down with 50 or more Zigbee devices, and at best only holds up to that point if there are enough repeaters available.
In my opinion, the only solution at present is to split the Zigbee network, i.e. to use, for example, a Hue (Pro) or IKEA Digera Hub and/or other routers to run several parallel Zigbee networks, which are then integrated into Homey via the app, or – in my view, a much better option – to switch to Zigbee2Mqtt and use an external, stable Zigbee coordinator. My recommendation here is SLZB (e.g. MRW10 or the Nano Hub, if you don’t want to run your own Docker instance for Zigbee2Mqtt and Mosquitto). I believe the same applies to Homey’s Matter Border Router, precisely because of the shared chip. Here too, I would again opt for an external OTBR; the manufacturer’s recommendation remains SLZB.
That’s why the solution really can only lie with Athom, unless you (like me) want to rewire the hardware (running Homey SHS in parallel, migrating the Zigbee components to Zigbee2Mqtt, integrating the Zigbee devices in parallel on my HP2013 and the new SHS, gradually migrating the flows to the SHS, etc.).
However, if you’ve already gone down that route and deleted all your Zigbee devices, you can also re-integrate them into Zigbee2Mqtt and then back into Homey via the app. The flows would need to be adjusted anyway, one way or another.
As for Matter-over-Thread, I lack personal experience regarding how stable the network is when using sufficient repeaters, how many devices can ultimately be integrated or operated if Zigbee isn’t running in parallel on the same chip, and, above all, whether Zigbee can even be switched off if no devices are connected. I think the Homey coordinator runs in parallel in ‘no devices’ mode.
Perhaps Athom will release a satellite that complements or expands upon and replaces the Pro’s internal hardware, rather than just functioning as a repeater (IR etc. aside).
Started happening exacly the same here, also few weeks back. Every day some devices drops out of homey. Homey reboot fixes it and it works perfectly until next morning.
I have only thread and wifi (shelly relays) devices. All thread devices are shared to Apple home (apple tv 4k) via “share matter device” in homey, but Apple home doesnt have that problem, only Homey dropping devices - every morning.
it was working perfectly for almost a year until few weeks back.
Hi Pascal
I find your idea with the Wi-Fi Network interesting. You don’t happen to know what you did with your Wi-Fi back then?
I’ll just check. I haven’t installed a single device in Homey2023 at the moment anyway.
Greeting
Frank from Frankfurt
Hi Patrick
Oha… So just like Pascal, you changed something about WiFi Network. I urgently need to check my WiFi now. Maybe I’ll see something.
Greeting
Frank from Frankfurt..
Hey Frank,
it was actually not the WiFi network. This setting is on my Hue Bridge. If you don’t have Hue devices, you may not have this issue.
Patrick
Virgin from Virginia
Hi Frankman
I also believe that the error can only be fixed by Athom.
However, I have no problems at all with Zigbee devices. It is only my Matter or Thread devices that fail here once a day.
The workaround is actually always to restart Homey and to restart any apps as well.
I think it’s a software problem, since I only have this error image since the last update 13.1.0
Greeting
Frank from Frankfurt
Hi Frank,
I have ASUS XT AP and while you can configure a mass of settings, it is still very limiting. The main problem is that it acts as mesh and every setting is spreading over the entire network. That’s why I still consider to move to a more professional system. But if that means costs and numberus problems to solve while the problem is still on Homey’s side…
What I mainly did is the following:
- Reduce the wifi power from powerful to good.
- Limiting 2.4 Ghz Band to 20 Mhz, not allowing 40 Mhz.
- Turning of every form of beamforming.
- Set my 2.4 Ghz channel to 1
But, I also changed the channel on my Homey, and that is an adventure. There is no setting for this. In the developer tools (website) you can reset the network. This resets the Thread AND Zigbee network and attributes a new random channel to the network. So I had to reset it many times to get channel 15.
BEWARE! You loose all your Thread and Zigbee devices and have to pair them one by one. You also have to repair your flows.
Why ?
Reducing the power should automatically lead to less interference.
While channel 1 and 15 are away from each other, Thread has a 2 Mhz channel while Wifi defaults to 20 Mhz. That means that the channel 1 has his middle at 2412 MHz and Thread has it’s middle at 2425 MHz. If Wifi uses 40 Mhz the middle is at 2422 Mhz and that’s very near to Thread.
Beamforming means that the antenna can amplify the wifi signal in the direction of a client. This powerfull beam can cross Thread network connections.
I hope this helps.
In my setup the local network is all Unifi. For 2.4GHz I explicitly disallow the upper channels to be used - the highest available is channel 9
The IoT network that everything Homey - wifi related is restricted to 2.4GHz only.
The Homey zigbee network is on channel 25 - seen on tools.developer.homey.app/tools/zigbee
That said, all the Matter devices I have are all Matter-over-wifi, no Thread devices. The ones that keep dropping off are all MOES switches. Yet the other Meross, Quectel, Aqara devices are all solid. The Aqara ones are all paired to an Aqara M100 hub which then presents them to Homey.
Interesting - tools.developer.homey.app/tools/matter only shows the Aqara M100 hub, not the individual devices (U100 door lock, water leak sensors etc.). Yet all of those devices present in Homey as Matter devices - right-click→settings→advanced_settings shows the nodeID and bridge name (the M100).
Every couple of days a bunch of the MOES switches drop off as a group, all at once. Not ALL of them, just a sub-group. And not always the same ones.
Hi Frank,
Looking at your list of devices, I still have my doubts as to whether your rather extensive network will run stably. As for the Ikea devices, I’m not sure whether these are the old Zigbee devices or the newer Thread ones. It’s well known that some Thread devices have had, or still have, stability issues. Ikea intended to address this with a firmware update.
Another problem is and remains the shared chip for Zigbee and Thread. As Homey definitely stops at around 50 devices for Zigbee, I think you’ve already reached the limit. On top of that, a stable Thread network would need to be set up, which I doubt, patches from Athom or not.
The question is also whether you have enough repeaters running to integrate the number of end devices into the mesh properly. This applies to both Zigbee and Thread. Please also bear in mind that light bulbs only stabilise the mesh to a limited extent if they are not permanently switched on and are only controlled via radio. For a stable network, sockets or built-in switches and sockets are likely to remain the gold standard.
Before you start jumbled up all the channels, you should bear in mind that the generally recommended channels in the EU have been chosen for a reason. Changing channels is primarily advisable if you notice a demonstrably excessive amount of foreign data traffic on the channels in your immediate vicinity.
In terms of stability, and above all to update your many Ikea devices to the latest firmware, I might spend another €60 (or look in “Kleinanzeigen”) on a Diregera hub to update the firmware of the devices, primarily the Threads. Once you have the device, it would be a promising option to split your networks and at least isolate the Ikea components, integrating them via the app through the Ikea hub. Of course, you would then need (even) more repeaters, as you might end up setting up two Thread and two Zigbee meshes.
Alternatively, there is still the option of offloading all Zigbee devices and integrating them via Zigbee2Mqtt. Your Homey would then only be responsible for the Thread mesh. Perhaps the chip is sufficient for this. As far as I know, you cannot disable the Zigbee coordinator in Homey, even if no devices are connected. I’ve checked the developer tools again; the Zigbee coordinator is running in idle mode because all devices are integrated via Zigbee2Mqtt.
I doubt that Athom will be able to stabilise your network in the long term with newer patches.
Good luck.
Regards, Frank
Hi Frank
I have been working on my problem permanently until now. I could only get my WiFi router to establish a more stable connection and I gave the LAN box on which the homey hangs a higher priority. I have not changed the channels, they are as always on “automatic”.
Unfortunately, the Homey developer tool has shown no effect either. It reacted as you described, namely not at all.
Until yesterday at noon, it got so worse that I couldn’t even learn new Matter devices.
In my desperation I did the 3rd time a factory reset.
See, I was able to teach all my Matter over Thread devices again. That went really fast.
I don’t have a single cigarette on my Homey only Matter devices.
In addition, I have an Eve-Energy in all rooms which, as I believe, serves as a border router and thus stabilizes my thread network, at least I hope so.
I’ll enclose my screenshots. I’m a little proud that I made it in a few hours.
Now I’m just waiting for 2:00 a.m. to see if devices fail again.
Thanks again for your tips.
Greeting
Frank from Frankfurt
Heh, I realized that 2nd fabric must be the Aqara one managed by the Aqara M100 hub I have to handle all the water sensors etc. Pity it’s not tagged as “Aqara” …
Discovered something interesting with the MOES matter switches that keep falling off the network. If I don’t do anything, they just stay broken, nothing happens.
I have been going around and putting them back into pairing mode, then going through the whole rigmarole of scanning the QR code and getting them re-paired/re-added. Pain. In. The. Butt.
BUT, putting them into pairing mode and then leaving them alone for an hour or so, and they re-join the network all by themselves. No QR code scanning needed. It does take a while, maybe an hour maybe less, I haven’t timed it. When I happened to check an hour or so later, they were re-paired.
Every MOES product I have tried has been a hot heap of garbage, they always fail.
Since Homey v13.1, my Thread network (60+ devices) has been incredibly strong.
I only have two WIFI devices left in my home, two Sonoff MINI 2GS matter over wifi relays.
Really solid device.
Yeah, I’m thinking to rip them out. Of the 8x MOES switches (all Matter), only 1x has never had a single problem. All the others have been dropping off every so often for the last few weeks. They were zero-problems before that.
I have several Lutron Caseta switches/dimmers (uses Lutron hub) and they’re absolutely rock-solid. I also have some Aqara H2 switches (uses M100 hub), also solid.
- Lutron Caseta Clara switch - $70
- Aqara H2 switch 1-button/2-button - $50
- Aqara H2 switch 4-button - $55
I need several 1-button, 2-button and 4-button switches for 1-gang Decora locations. Any recommendations ?
I see Sonoff has one (ZBM5-3C-120W) but it says “requires Sonoff zigbee hub”. I’m not adding yet another hub without really good reason … They also have the M5 Matter switches, but they’re not Decora-compatible, requires their faceplate.
You likely don’t need a Sonoff zigbee bridge. They show that on the listing because they don’t expect users to another hub like Homey (most users just want to control it from a mobile app/Google Home, and since those users don’t know that they need additional hardware for that, they mention that on the listing).
What about the Pico switches?
