Configure flux_led to rgbw with Addressable v3 controller

Configuration
1

I have Addressable v3 controller (at least I think so, it shows firmware version A3.v1.27.7809-A). I’ve connected to it RGBW strip (SK6812RGBW).
Looks like flux_led detects it as rgb strip - and do not allow me to manage w channel. I still can turn LED strip on/off and change RGB color/brightness, but W will be in the state that I last configured in Magic Home application.
Per forum posts I see, that previously it was possible to set color mode rgbw though config, but looks like now with configuration though UI it dose not allow me to change color mode.
When I check attributes of entity, I see:

effect_list:
  - RBM 1
  - RBM 2
  ...
supported_color_modes:
  - rgb
color_mode: rgb
brightness: 255
hs_color:
  - 0
  - 100
rgb_color:
  - 255
  - 0
  - 0
xy_color:
  - 0.701
  - 0.299
effect: music
ip_address: 192.168.1.139
friendly_name: cabinet_led_test
supported_features: 36

I tried to override mode though config:

light:
  - platform: flux_led
    devices:
      192.168.1.139:
        name: cabinet_led_test
        mode: "rgbw"

But it have not helped.

2

Fixed here Bump flux_led to 0.27.28 to fix missing white channel on SK6812RGBW strips by bdraco · Pull Request #63154 · home-assistant/core · GitHub

If you want to try the new change before its released

mkdir /config/custom_components
cd /config/custom_components
git clone https://github.com/bdraco/flux_led_custom flux_led

Restart

If its using the custom one you’ll see something like this in the log 2022-01-01 22:33:00 WARNING (SyncWorker_6) [homeassistant.loader] We found a custom integration flux_led which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

3

That repo also has these changes in it which are not yet merged into dev

4

Thank you a lot, @bdraco - it works correct now! You’ve fixed it so fast!
I’m not sure if it is connected to the original question, or if it should be separate topic. With that fixed version, if I change color/brightness/white, each time when I turn it off and on it switch to some unexpected color - is there a way to make it preserve last color after turning on and off? Example:
Original:

color_mode: rgbw
brightness: 32
hs_color:
  - 0
  - 0
rgb_color:
  - 64
  - 64
  - 64
rgbw_color:
  - 0
  - 0
  - 0
  - 64
xy_color:
  - 0.323
  - 0.329

After turn off/on:

color_mode: rgbw
brightness: 204
hs_color:
  - 253.585
  - 62.353
rgb_color:
  - 132
  - 96
  - 255
rgbw_color:
  - 59
  - 0
  - 255
  - 153
xy_color:
  - 0.219
  - 0.126

Another example, original:

brightness: 128
hs_color:
  - 0.235
  - 100
rgb_color:
  - 255
  - 1
  - 0
rgbw_color:
  - 255
  - 1
  - 0
  - 0
xy_color:
  - 0.7
  - 0.299

After turn off/on:

color_mode: rgbw
brightness: 192
hs_color:
  - 254.118
  - 66.667
rgb_color:
  - 125
  - 85
  - 255
rgbw_color:
  - 59
  - 0
  - 255
  - 128
xy_color:
  - 0.212
  - 0.113
5

That’s unexpected. It looks like a bug. Would you please open a GitHub issue?

6

Opened issue: Color of light changes after turn off / on with flux_led · Issue #63421 · home-assistant/core · GitHub

7

To close the loop on this, the issue was resolved by rebooting the device.

There is a patch coming in 2021.12.9 to avoid setting the white level too quickly after setting the RGB level to try to avoid hitting the bug in the device firmware that triggers the condition.