Bug in RGB lamps properties/values reporting
Hi,
In order to try to read the current values of a Philips Hue RGB lamp; the aim being to set back to the Hue lamp a setting I (i.e. my wife) liked, I created a TestSwitch to read all current values from the Hue lamp, see attached rule.
Each of the values available in the sensor pulldown was assigned to a specific variable, the contents of which was sent as email. The resulting e-mail is as follows:
LV25ZT:
Salongbord: 0.0 ${variables.get("ValueRGB")} 0.0
true true 100
No matter what the lights settings are, the values for Hue and Saturation remain at Zero.
The RGB value is invalid or NIL; the variable doesn't get a value and therefore also never gets initialized and thus also not created (hence the unresolved variable in the mail),
Values for On and Off are True if Brightness > 0, and remain True even if Brightness = 0.
On and Off become False only if the lamps have received an "Off" command.
They remain "false" if Brightness is changed (and lights are on), and need an "On" command to change.
My conclusion is that the implementation of RGB/RGBW is faulty, at least with respect to Hue.
What can be done about this, so that we can read correct values and also set the correct values from/to Hue lamps, directly from Zipastuff?
The same problem 
Hi Roberts,
about the ON/OFF and brightness, I dont know if this can be addressed by zipato, but seems to be something documented in the HUE api (https://developers.meethue.com/documentation/lights-api) :
"Brightness is a scale from 1 (the minimum the light is capable of) to 254 (the maximum). Note: a brightness of 1 is not off."
so seems that the bri and on/off are not linked. Setting the bri >0 should not turn light on by itself (or off for bri=0). Following the apis, you should always pass the "on: true; / on: false;" command if you want the lights be really on/off.
But i never used in the variable because i dont have the pro features, so maybe it is a different issue.
Hi Roberts,
about the ON/OFF and brightness, I dont know if this can be addressed by zipato, but seems to be something documented in the HUE api (https://developers.meethue.com/documentation/lights-api) :
"Brightness is a scale from 1 (the minimum the light is capable of) to 254 (the maximum). Note: a brightness of 1 is not off."
so seems that the bri and on/off are not linked. Setting the bri >0 should not turn light on by itself (or off for bri=0). Following the apis, you should always pass the "on: true; / on: false;" command if you want the lights be really on/off.
But i never used in the variable because i dont have the pro features, so maybe it is a different issue.
Robert,
In my opinion, Phillips hue integration to Zipabox is half way done. What you can do for sure is to set your bulbs through hue app, read their values using Hue API and then using HTTP requests to call those values. You could also create a Hue Scene on Hue App and then call it through HTTP.
Also as M4 comments, phillips hue are different than Z-wave bulbs, brightness 0 doesn't mean the bulb is OFF I remember I read that on hue developers site too.
Robert,
In my opinion, Phillips hue integration to Zipabox is half way done. What you can do for sure is to set your bulbs through hue app, read their values using Hue API and then using HTTP requests to call those values. You could also create a Hue Scene on Hue App and then call it through HTTP.
Also as M4 comments, phillips hue are different than Z-wave bulbs, brightness 0 doesn't mean the bulb is OFF I remember I read that on hue developers site too.
Replies have been locked on this page!