Wled Intergration, RGBCCT not working correctly. (Analog RGBCCT Strip)

[ccm19931993]

The problem

Using the color wheel in Home Assistant, when choosing a color there is no issue, the strip goes to that corresponding color, but the bubble in the wheel goes from the color chosen to the middle (which would be white) on its own. But the color chosen does not change. In this situation going to the Warm White, Cold White slider does not turn on the WW or CW leds.

Now if you move the White Brightness to 51 from the default 50. then the Warm White, Cold White slider functions as expected. If you then chose another color the Warm White, Cold White slider does not function again.

Also when sending a rgbww command in dev tools the cold white does not turn on. for instance: [0,0,0,255,0] The WW led comes on [0,0,0,0,255] The CW led does not come on

Everything works correctly in the WLED App.

diagnostic dump of controller: config_entry-wled-01J4ZE40PSPX6RHWS7T84RRH0P.json

Hope all that makes sense

What version of Home Assistant Core has the issue?

2024.8.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

WLED

Link to integration documentation on our website

https://www.home-assistant.io/integrations/wled

Diagnostics information

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Wled Controller: Athom WLED RGBCCT Analog and Digital Light Strip Controller

WLED version : 0.14.4

[home-assistant[bot]]

Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration (wled) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of wled can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign wled Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

wled documentation wled source _{^{(message by IssueLinks)}}

[designerno1]

Same issue here with the Ericsity wled controller and ws2805 rgbcct Installed version:WLED 0.15.0-b4 ESP32_audioreactive Can't get only cw or ww to work with HA. You turn down Color brightness to 0 the whole strip goes off, then turn up white level to 100 nothing happens turn color to 100 and white to 100 then turn off color turn both off color and white. In Wled app it works as expected.

[frenck]

This is likely caused by the fact Home Assistant doesn't have a notion of RGBCCT. The light "work", but we won't be able to replicate the same functionality as seen in WLED itself into Home Assistant.

Can you provide a diagnostic dump of this specific device and attach it to this issue?

Thanks! 👍

../Frenck

[ccm19931993]

/Frenck

I have attached the Info.

Thank You

[frenck]

Can you please attach it? Instead of copy and pasting the contents?

[Suxsem]

This is exactly what I was referring to in my PR (https://github.com/home-assistant/core/pull/123477)

I understand that in HA a light cannot be in two different color modes (RGB and COLOR_TEMP) at the same time (@frenck is that correct?)

So how cloud this be addressed? Maybe adding a new, specific, color mode (RGBCCT)?

[ccm19931993]

@frenck Was just wondering , im not a coding expert, but curious on your thoughts as it relates to the RGBWW command in Home Assistant. Could that not be used to tell WLED to turn on all 5 channels. The RGBW part works fine, the Red , Green , Blue Warm White Function Correctly. Why cant we tell WLED to turn on the other "W" for the Cold White. (Of coarse im talking analog) Were just one W away Lol. Thanks

[Suxsem]

@frenck any chance you could take a look?

[frenck]

Not anytime soon; I'm traveling with my fam for a few weeks.

[Suxsem]

@frenck enjoy your vacation!!! 😃

[robertwigley]

I believe this is the same problem I am experiencing with Home Assistant not displaying the correct colour and brightness settings when using an analogue RGBCCT strip.

I set the colour in HA and it changes the colour in WLED and on the strip, but HA immediately (within a second) reverts back to a warm white. WLED and the strip do not change, meaning what is displayed in HA is incorrect. Likewise, changing the Colour Brightness or White Brightness from within HA changes in WLED and the strip, but the HA interface reverts back to 100% Colour Brightness and 50% White Brightness while the settings prevail in WLED, again meaning the values in HA are incorrect.

However, I think I may have found an albiet clunky workaround to this problem. What I have done is set two LED Outputs up and ticked the "Make a segment for each output" checkbox. I then renamed the Segments in the main control page and can now operate these as two separate light sources (i.e. a CCT one and an RGB one) and one master correctly in Home Assistant. It might need a couple of automations to deal with switching one light source off when the other turns on if you don't want CCT and RGB to be on at the same time, but that's simple enough to do. Not ideal, but it seems to work and maybe until Home Assistant can deal with RGBCCT natively it could create two separate light sources when it's RGBCCT automatically?

[Suxsem]

Unfortunately the workaround is not possible for digital RGBCCT strips becouse there is only on output for this kind of strips

Inviato da Outlook per Androidhttps://aka.ms/AAb9ysg

---

From: Robert Wigley @.> Sent: Thursday, September 26, 2024 7:09:47 PM To: home-assistant/core @.> Cc: Stefano Semeraro @.>; Comment @.> Subject: Re: [home-assistant/core] Wled Intergration, RGBCCT not working correctly. (Analog RGBCCT Strip) (Issue #123614)

I believe this is the same problem I am experiencing with Home Assistant not displaying the correct colour and brightness settings when using an analogue RGBCCT strip.

I set the colour in HA and it changes the colour in WLED and on the strip, but HA immediately (within a second) reverts back to a warm white. WLED and the strip do not change, meaning what is displayed in HA is incorrect. Likewise, changing the Colour Brightness or White Brightness from within HA changes in WLED and the strip, but the HA interface reverts back to 100% Colour Brightness and 50% White Brightness while the settings prevail in WLED, again meaning the values in HA are incorrect.

Home.Assistant.States.png (view on web)https://github.com/user-attachments/assets/2c95b661-5a70-4c99-bcad-261046d83b68

WLED.States.png (view on web)https://github.com/user-attachments/assets/97bb17db-929d-4de9-947f-9b294a573333

However, I think I may have found an albiet clunky workaround to this problem. What I have done is set two LED Outputs up and ticked the "Make a segment for each output" checkbox. I then renamed the Segments in the main control page and can now operate these as two separate light sources (i.e. a CCT one and an RGB one) and one master correctly in Home Assistant. Not ideal, but it seems to work and maybe until Home Assistant can deal with RGBCCT natively it could create two separate light sources when it's RGBCCT automatically?

WLED.Setup.png (view on web)https://github.com/user-attachments/assets/40043dc8-b769-4460-b971-3c0901596d90

WLED.Segments.png (view on web)https://github.com/user-attachments/assets/3d1900ac-1809-4849-8ff8-145d135371fe

— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/123614#issuecomment-2377499944, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGK2NI2TYBA77Q33S7XGB3ZYQ5VXAVCNFSM6AAAAABMLADYU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZXGQ4TSOJUGQ. You are receiving this because you commented.Message ID: @.***>

[Suxsem]

@frenck I hope you enjoyed holidays! Do you think you can have a look at RGBCCT in home assistant for wled? Thx

[TFenby]

It seems like it's almost working correctly? The color wheel correctly updates the RGB color in WLED, and the temperature slider correctly updates the white balance in WLED. The only things not working from the HA UI are the "Color brightness" and "White brightness" sliders. They don't correctly adjust the corresponding sliders in WLED.

Anyway, in case it's useful to anyone, I did get my analog RGBCCT light strip working with esphome. I'm using a QuinLED-An-Penta so your GPIO may vary.

LED STRIP.txt

[InnovoDeveloper]

I am not sure if this helps, but I have recorded a screen grab of this behavior. The happens with my Athom RGB+CCT bulb and Analog RGBWW light strips as well.

https://github.com/user-attachments/assets/04687f4a-2e93-4200-a97b-a4b82a7630b7

[mitchkeller]

I'm seeing the same behavior as @InnovoDeveloper with my WS2805 strips. Would be great to see some progress on this, as HA is essentially unusable on RGB+CCT strips.

[CDank]

Unfortunately I also have the same behavior with an RGBCCT strip. Is there already a possible solution for the problem? Firmware is WLED 0.15.0 (build 2412100)

[CodingGhost]

Also have the same issue... Is there any workaround? Does anybody know why this even happens? Would the PR by @Suxsem solve this? If yes I would try patching my HA with that PR.. @frenck ?

[TFenby]

FWIW the esphome solution I mentioned above has been working great for me:

[CodingGhost]

Need Wled though as Im running some other stuff that connects to wled only.. also I think this just needs to be solved as I just like Wled alot :D

[HeyItsJono]

I also don't have the option of ESPHome with my WLED athom bulbs. The other undesirable side effect of this bug is HA doesn't retain memory of what colour is actually set on the bulb (since it just always flicks back to that warm orange default on the colour wheel, even if the light is actually displaying blue or whatever you try to set it to). This means that when you save a scene it doesn't actually know what colour the bulb was set to, and loading a scene results in it not changing the bulbs colour (since it always thinks the bulb is constantly set to this warm orange default).

[CodingGhost]

What is wled doing different on rgbw vs rgbcct? My wled rgbw stripes are working as expected, and my other tuya bulbs that have the option to set the white temperature are also working as expected.. so what exactly is it?

[CodingGhost]

I have found a workaround, its basically the same idea as @robertwigley had, but with a few changes. I set two LED outputs, one as RGBW, and one as PWM White. now one segment behaves like a normal RGBW, and you have one additional entity that controls color temperature. That is fine for me. One problem now is, that you cannot control the color temperature if the brightness slider on the left (in PC Mode view) is set to 0, as Homeassistant controls the segment brightness (the one in the segment view). To get around this, I created a Preset in WLED that has the brightness of the CCT segment turnd to max, and the brightness in the segment view to min. Then select this preset as the default preset in led settings so it gets applied after a reset. With this configuration everything now works as I want, and I dont mind having an additional slider for cct.

Here is the config for my Athom 15W bulb:

[rybackisback]

i have the same problem in home assistant with ws2805 and wled 0.15.0. no control over brightness or control over the colour wheel as the cursor keeps jumping back even though the colour changes on the led strip

[burnt-past]

I can also confirm the same issue, where only the CCT values show in Home Assistant. RGB can be set, but it does not update in Home Assistant.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Suxsem]

Still relevant, don't close

[mkielarv2]

https://github.com/home-assistant/core/pull/123477#issuecomment-2278440860

Please note; the concepts of WLED do not match Home Assistant.

@frenck Does that mean It is not expected to be fixed anytime soon? Are both platforms so conceptually different that they are incompatible on this particular feature?

[vtzk]

Hi folks, I am also facing the same problem and did some investigation on my end. I wish I could contribute and attempt to fix, but unfortunately I have not much experience yet on compiling/testing the HA Core.

From my investigation it might be that the issue lays on this line which seems to always set the color_more to first element of available color modes — which is color_temp. Even tho the WS2805 also supports RGBW mode, it will never be set, and probably that's why HA won't ever fulfill the rgbw_color property, which should properly set the values on the UI state and sliders accordingly. Instead it always sets the rgb_color only.

Even tho if I manually set the state from Developer Tools, it won't persist them in HA, but apply properly to WLED.

supported_color_modes:
  - color_temp
  - rgbw
effect: Solid
color_mode: color_temp
brightness: 158
color_temp_kelvin: 2000
color_temp: 500
hs_color:
  - 30.601
  - 94.547
rgb_color:
  - 255
  - 137
  - 14
xy_color:
  - 0.598
  - 0.383
rgbw_color: null
friendly_name: WLED Test Light
supported_features: 36

I truly hope this helps, and someone will be able to find a quick fix for that 🙏

[darrylsyms]

Same issue :(