Hoping someone here has experience with KNX + Homey and can help me figure out what’s going on.
I’ve just moved into a new house where the electricians installed a full KNX lighting system, including a lot of DALI spots connected via a KNX DALI gateway. They also recommended and set up a Homey Pro (2023) as the smart home hub to handle automations and scene control. The KNX IP interface is a Schneider Electric SpaceLogic KNX IP interface.
So far, I’ve added all the lights into Homey, and everything works perfectly when I control the lights one by one — both via Homey and ETS. Telegrams show up correctly in ETS when I test: GroupValueWrite, DPT 1.001, value 0, coming from Homey’s KNX address.
The issue comes when I try to use the built-in “Turn off all lights” function in Homey.
If I trigger this in a small zone like the kitchen, it works perfectly.
But when I try to turn off a larger zone like the entire 1st floor or the whole house, some lights don’t turn off. It’s not consistent — different lights fail each time. But I can see in ETS group monitor that all the telegrams are sent from Homey. For the 1st floor 12 telegrams shows up in ETS when I trigger all lights of in Homey.
If I take the same group addresses and send them manually from ETS, all the lights respond.
So there’s nothing wrong with the addressing or the device setup.
It just seems like something can’t keep up when all the telegrams are sent at once above a certain threshold.
Since many of the affected lights are DALI spots, I’m wondering if the KNX DALI gateway is being overwhelmed when too many telegrams are sent in a burst?
I’d prefer not to build a bunch of Advanced Flows with delays between each light just to get this working — this feels like something the system should handle out of the box.
Anyone run into something similar with Homey + KNX + DALI?
Is it possible to have a “delay” in Homey with KNX when using the “all lights off function” so that not all telegrams is sent in one batch?
Yes, that’s exactly the one – the KNX app which, according to the Homey app store, is developed by “Athom B.V.” itself.
That’s actually the core of my frustration. When I contacted Athom support about an issue, they told me they no longer provide official support for it, claiming it’s essentially “handed over to the community.”
It’s pretty annoying to hear that, especially when their own app listing names Athom B.V. as the developer and it is an “offical” app. It makes their stance on not supporting it quite confusing.
I’ve actually got the whole support conversation attached here, and this experience is making me question Homey’s support for their own products.
If this is how Athom treats support for its “official” apps, I would strongly advise anyone considering Homey to look elsewhere if they expect accountability and dependable support.
I have seen post that users experience the same problem with lamps directly connected to Homey. Is seems that when Homey switches a large group of lamps, Homey has to send a lot of messages and some of these messages get lost. This is a general Homey problem, existing for quite some time. Looks like a message buffer overflow.
See [Feature Request] Groups - #3 by robertklep
