- revert to ignoring rgb in color+white+cct case by resetting all its
inputs to minimum and only controlling white channels
- ignore ww and cw in rgb+cct case; use approximated color, thus allowing
us to set a different 'cold temperature' limit
- fix webui layout rules based on root element class(es) and consistent
order for our control elements that does not depend on the order in which
`processData` handles configuration kvs
- internal refactoring to flatten input processing funcs selection
(to possibly replace our boolean flags with a simple list)
Use the first three channels as RGB channels. This will also enable the color picker in the web UI. Will only work if the device has at least 3 dimmable channels.
When device is configured as RGB + WW (warm white), use RGB to balance the "warm white" channel, while the "Cold channel" is still configurable.
When device is configured as RGB + WW (warm white) or RGB + WW CC (cold white), use RGB to balance the "warm white" channel output, leaving "Cold channel" for manual adjustments.
<br>This option hides <strong>RGB</strong> and <strong>WW</strong> sliders!
<br>This option hides <strong>RGB</strong> and <strong>WW</strong> sliders!
Balance between "cold" and "warm" when channel configuration has WW (warm white) and CW (cold white) channels available. When RGB is also available, replace its values with an approximation based on the current "Mireds" value.
Balance between "cold" and "warm"color temperature when channel configuration has WW (warm white) and CW (cold white) channels available. When RGB is available but <code>Use white channel(s)</code> is disabled, replace RGB values with an approximation based on the current "Mireds" value. Otherwise, RGB channels will be disabled.
<br>This option hides either <strong>WWn class="p"></strong> and <strong>CW</strong> channel sliders, or <strong>RGB</strong> color picker.