PWM CCT Bug

[oraclesod]

What happened?

For some reason WLED creates a secondary brightness bar when PWM CCT is enabled. I have a PWM strip with cool and warm white LEDs, when configured i see the Brightness bar (usual bar), I also have a temperature bar called white balance, but I also have another brightness bar called white channel.

This means there are two bars controlling the brightness of the LEDs and if the white channel is set to 0, the lights dont come on at all with the regular bar, and vice versa.

When using HomeAssistant with WLED, the white channel is not exposed and not visible in HA at all, and although I can set the white channel to 255, after power loss, it goes back to 0 and I have to manually adjust in WLED for HA to be able to adjust brightness/temp of the strip

It seems like this bar should have been removed when in CCT mode, and its a left over from RGB+CCT where there would be separate white channel control

To Reproduce Bug

1. Connect a PWM CCT strip
2. Set the GPIO for each channel
3. Turn the light on from the main screen, adjust brightness and white balance (nothing will happen if white channel is set to 0)

Expected Behavior

I would not expect there to be an extra white channel control on PWN CCT as this is only a White strip, i would expect to see brightness and white balance (temp) control

Install Method

Binary from WLED.me

What version of WLED?

0.15.3

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

Anything else?

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[DedeHai]

This is a feature, not a bug. You can set the white channel brightness with a boot preset, just like you do with any color.
There is some redundancy though but AFAIK this is intentional and/or for backwards compatibility. Maybe @softhack007 does know more about it?

[softhack007]

Yes I think its actually a feature.

If you only use a single CCT output, its best to use "Max", "Brighter", or "Accurate" as auto-white mode. This drives the CCT based on color information, so you can use lots of effects that were actually created for RBG color.

The second slider in "None" and "Dual" mode is actually meant for another use case - if you have a mixed setup with other ws2812b strips, then overall brightness controls your complete installation, and the second slider you found is actually to control the white LED independent from running effects.

https://kno.wled.ge/features/cct/#cct-handling

I agree that in case of only a single CCT LED in white mode "none", it appears somewhat redundant. But @oraclesod 's case is really not the typical use case.

[blazoncek]

If you only use a single CCT output, its best to use "Max", "Brighter", or "Accurate" as auto-white mode.

Unfortunately this will force White/CCT output to be considered RGB.

@oraclesod Apperance of White slider (atop White balance) is unfortunate consequence of having global brightness. WLED operates with "colors" and white has shades of gray as "colors". These shades of gray also correspond to "brightness" of white.

Why your "White" gets reset to 0 is an issue tha needs to be diagnosed separately. I would expect it is set to 0 via API call.