Thanks for this, I used it to validate some of my own settings, and like you ignored the _0 entity.
In case anyone else comes looking for more info, here are some of my other findings…
It looks like the Entities mentioned for RGB and W and be largely ignored for basic usage.
Using main and its colour picker leads to:
- RGB being used for white if only brightness is set
- W being used if a “white” is chosed from the colour picker (i.e very top row).
- RGB are blended in if a “less white” (or lower in the picker) colour is added.
- You will notice that as colours are mixed, HASS will switch on the other channels on the dashboard.
- The same channel switching occurs when you turn say green to 100% rightness and then click on its colour wheel, that is, the other channels are enabled with brightness set to hit the desired colour.
This means that there is a lot of repetition in the console and for the sake of simplicity your HASS web portal can be cleaned up for human driven changes by hiding RGB and W and leaving main. The specific channels can still be used via api/config to call specific combinations, but based on the below, this also might be unneeded.
Contrary to what you’d expect, using a snippet like the below (3_0_2 is my “Main”) , you actually end up with the white bring composed of RGB and not W. if however you set RGB to 255,255,255 and white to 0 it uses the white channel and not RGB, which feels a little backwards.
“rgb_color”: [0 , 0 , 0 ],
This isn’t a major issue, and I it just means I’ll need to call an RGB code to get my warm white on, instead of using a white level, and adding an RGB code to tint