Extended Mode about node-red-contrib-huemagic HOT 1 CLOSED

Hi lespatots!
Thank you for this nice feedback and sorry for my late response!

Setting "on" to "false" should work as expected now with v1.3.1. I also added a brightness setting validation (can't understand why I didn't before…) and lights / groups are now turning off if the setting is "0". You were right, for some reasons Philips' API is not turning off the lights if the brightness setting is 0.

The saturation setting is something that I totally missed from the API docs – but now obviously added with the update ;)!

With the improved input "algorithm" in v1.3.1 all nodes are now working "additive". You also don't have to pass in the "msg.payload.on" parameter anymore and all future commands are simply updating the light / group / sensors. I added this info in the features section in the README file with a simple sentence. You're totally free to contribute if you have some improvements for the README of even the actual code :)!

I decided to use own customized parameters for HueMagic because of three reasons:

1. You also mentioned it. They are cryptic in some cases and not easy to remember (often).
2. If they were all identical then users would probably think, that they also work the same. With Philips Hue API for example you have to pass in a value between 0 and 254 to set the brightness level of a light bulb. In HueMagic this setting is a more convenient "percent" parameter which makes things easier for users – I guess (I hope).
3. With customized parameter names HueMagic is able to keep it's nodes and API "alive" with internal recalculations and without having the user to manually update all the nodes, just because Philips changed / removed / unnamed some parameters in their API.

I am closing this issue for now. Feel free to answer back if you don't agree with my last arguments 👍 !

from node-red-contrib-huemagic.