Added PulseLight add-in #141
Conversation
| var newValue; //Value for Homekit | ||
| if(field === "On"){ | ||
| if((knxValue? 1:0) !== (oldValue? 1:0)){ | ||
| this.myAPI.setValue('On', newValue); |
There was a problem hiding this comment.
you never set newvalue to anything, what will be sent to homekit?
There was a problem hiding this comment.
I think this code might be removed, as Homekit is the only source for setting the light there is no state to be send. Homekit remembers the state itself based on the signal send to KNX. There is no status to listen to for this PulseLight. I used existing code as base and tested it so it worked. Might be that there is code that could be removed / does not do anything special?
| onKNXValueChange(field, oldValue, knxValue) { | ||
| var newValue; //Value for Homekit | ||
| if(field === "On"){ | ||
| if((knxValue? 1:0) !== (oldValue? 1:0)){ |
There was a problem hiding this comment.
why don't you compare old and knx values directly?
There was a problem hiding this comment.
I think this code might be removed, as Homekit is the only source for setting the light there is no state to be send. Homekit remembers the state itself based on the signal send to KNX. There is no status to listen to for this PulseLight. I used existing code as base and tested it so it worked. Might be that there is code that could be removed / does not do anything special?
|
Hi @coxfrederic Fréderic, thanks for submitting your PR. I have to admit I don't understand the code completely. I thought it should send a 1 to KNX regardless of the prior state? And it should remember the state somewhere (outside homekit)? I left some comments in the code view. |
I based it on an existing addin because I'm new to all this,sorry this might make it harder to understand the code.
This is correct
No, only inside of homekit it should remember the state
Thanks, I tried to reply to them, hope it is more clear now. Thanks for your time and help! |
|
One important detail: If in homekit the state is "off" it should not send a 1 to KNX if for automatisation reason the value should be set to off. I fixed it now and it works but before it would put the light on again. So the code from the PR works for me, been using it for a few days and works perfectly here. |
|
Can this be included? I just updated my homebridge-knx installation and it failed since PulseLight.js was missing for handling my knx_config file, so I added the PulseLight.js in lib/addins myself so the installation works now. |
|
Hi Fréderic, I would like you to add a comprehensive note what the pulselight add-in really does, what the use case is, because I think that is not self-explanatory. Best regards |
|
Hi Raoul, Regarding the use case: I have a KNX installation setup with multiple lights, and all work fine in HomeKit. There was one "light" that I could not add in HomeKit, and that was the light of my kitchen hood. This works with a special remote and it could not be connected to the KNX installation. So what I ended up doing (well actually my father-in-law) was to attach the remote to the KNX installation. By doing so (we actually pulled the remote apart and re-connected the wires) we now have a "hidden" remote behind our kitchen which gets a pulse from the KNX installation. This pulse will change the status of the light. So I can not switch it on or off, all I can do is say "change status" and it will change the light. So I tried using a regular light in HomeKit for this, but that didn't work, because it would not send a pulse if the light went off. Also I had some problems if the light was on, and HomeKit scenes would need it to be on, it would turn off again .. So then I create the PulseLight.js and tested with it until it worked for my use-case. Regarding the code: I need to take a closer look and run some tests, because I don't understand the code myself entirely. I just adjusted small parts to make it work for my use case. |
I needed a custom add-in for a lightbulb that should be able to be turned on/off in Homekit but always sends a value of 1 to KNX. This is because I simulate pushing a button on a 433Mhz remote to turn on / off my lights for the hood of my kitchen. The PulseLight does exactly this. Since it is not possible to read any status I didn't include this in PulseLight. This means that Homekit is responsible for remembering the state.