Closed mclayan closed 2 years ago
That is indeed new behaviour. Unfortunately I have given up on the tradfri hardware. After several bugs/crashes and even hardware failures I switched to Philips Hue (yes yes I know you get what you paid for, but waking up in the middle of the night because all lights turned on since there was a firmware update was not fun anymore). I will make a note in the docs that this is going on, since previously the light would stay on but would return to the default color.
There may be a bug in the latest firmware of the RGB Bulb "TRADFRI bulb E14 CWS opal 600lm" that causes it to completely turn off when setting red colours via HSV (as used by the Home Assistant Tradfri integration). I'm not sure how they calculate the HSV values but I suspect that they use the UINT16 range as a scale (0 = 0%, 65535 = 100%). However, when passing any value above 65278 for Hue ("5707"), it just turns off. I detected that because Home Assistant always uses HSV values and passes e.g.
'5708': 65279, '5707': 65535
for full red colour.My assumption is that they use this convention to calculate HSV values:
Example:
Ideally this would set the bulb to a deep red, instead it will lead to the bulb being physically off but reporting as on ("5850": 1):
Also note the HEX color code
"5706": "f1e0b5"
, which is something like beige (maybe a default colour).They must have introduced this behaviour in the last FW update because until then my automations were working.
Maybe this would be worth mentioning in the documentation?