Closed ghost closed 8 years ago
Hi Patrick, I think HomeKit should not send an ON command at all when controlling brightness. At least it doesn't do in my configuration. I noticed you use the same response addresses (Rückmeldeadressen) for both On and Brightness - that is very strange as On is DPT1 (1 bit Boolean) and Brightness is DPT5 (8 bit integer )
I think you should fix these and try again.
Best regards Raoul
Hi Patrick,
as Raoul already wrote, you will need a different GA on different KO of your dimmer for Brightness/Listen.
Have a nice day ! Dariusz
Hi,
Thx for your help, but its the same behavior:
"type":"Lightbulb", "name":"Kuche", "On":{ "Set":"0/0/3", "Listen":[ "0/2/14" ] }, "Brightness":{ "Set":"0/7/1", "Listen":[ "0/2/3" ] } },
Hi Patrick, I just made a group monitor screenshot of the addresses thatare sent when I change the brightness using Homekit.
As you can see there is no ON (EIN) command, only a ON response. You might have somehow mixed the response addresses or something. Homekit (and homebridge-knx) does not send the ON if the brightness is changed. I know that this is different with Hue Bulbs that require the ON before they accept brightness values. So I do not know where the ON is coming from in your configuration!
Regards Raoul
No traffic on that issue - stale, closing.
Hello,
I get some strange race condition, I have two lightbulbs:
Both should behave the same way, but "Küche" doesn't work, if I set "Küche" to 15% for example, it just switches to 100%.
So i debugged the issue and found the error using Busmonitor in ETS:
As you can see, set and on is in the wrong order, but why?
Thx,
Patrick