So you found the problemš
Maybe it is time to contact the developer or add the KNX dimmer to Homey.
As you have to define the IP-address of ETS, it looks like the special dimmer card is doing the same as the general ālisten to addressā card.
Adding the dimmer to homey results in actually the same thing
When defining the KNX dimmer, you have to assign the group addresses (switch/status/dim) to the dimmer. The group address DTP is configured in KNX (so dimmer card as well as KNX trigger I use, are based on the same)
I skip creating an actual dimmer card as I donāt need it as a card in Homey (I use the Philips Hue card which I linked instead)
When you talk about the developer, who would that be?
Itās not Philips Hue as that works correctly (triggering the flow manually)
So you mean KNX then?
According to KNX App voor Homey | Homey it is Athom.
You might search this forum for āKNXā, maybe this makes sense to you: KNX Dimmer
According to https://chatgpt.com/share/00db250f-c598-4c98-a628-c980e7e68b9e you need several groupadresses.
Hi all,
Iām bumping this thread as Iām facing the exact same problem described here, sbut with relative dimming (DPT 3.007).
Like others, Iām trying to dim Hue lights from a KNX switch. My flow is never triggered by the ādim upā or ādim downā commands. It seems the Homey app only receives the final āstopā (value 0) command when the button is released, making it impossible to know which way to dim.
Iāve confirmed this is a limitation in the app and even filed a issue on Athomās GitHub repository for the KNX app, but there has been no response:
Itās very frustrating. That repository has dozens of open issues with no replies, which makes it feel like Athom doesnāt really take KNX support seriously.
Since this thread was last active, has anyone found a creative solution or workaround for this relative dimming or absolute dimming problem?
