Tuya RGBW Strips don't show the "White" slider

[EpicLPer]

The problem

Referencing this issue here (which was falsely closed by the stale bot...): #58906

Essentially the same as this user wrote, just with a "Action LSC Smart Home Outdoor LED Strip", but long story short some RGBW Tuya devices seem to not show the White slider at all, and setting the RGB picker to White instead just turns all RGB LEDs on to the same value but never uses the proper White LEDs.

What version of Home Assistant Core has the issue?

2022.8.6

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

Tuya

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

Here are all the "Device Debug" values for my particular LED Strip (LSC Smart Home Outdoor) from the Tuya IoT Cloud for my particular LED strip:

switch_led  
"{true,false}"

work_mode   
{
  "range": [
    "white",
    "colour",
    "scene",
    "music"
  ]
}

bright_value    
{
  "min": 10,
  "max": 1000,
  "scale": 0,
  "step": 1
}

colour_data 
{
  "h": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 360,
    "step": 1
  },
  "s": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
  },
  "v": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
  }
}

scene_data  
{
  "scene_num": {
    "min": 1,
    "scale": 0,
    "max": 8,
    "step": 1
  },
  "scene_units": {
    "unit_change_mode": {
      "range": [
        "static",
        "jump",
        "gradient"
      ]
    },
    "unit_switch_duration": {
      "min": 0,
      "scale": 0,
      "max": 100,
      "step": 1
    },
    "unit_gradient_duration": {
      "min": 0,
      "scale": 0,
      "max": 100,
      "step": 1
    },
    "bright": {
      "min": 0,
      "scale": 0,
      "max": 1000,
      "step": 1
    },
    "temperature": {
      "min": 0,
      "scale": 0,
      "max": 1000,
      "step": 1
    },
    "h": {
      "min": 0,
      "scale": 0,
      "unit": "",
      "max": 360,
      "step": 1
    },
    "s": {
      "min": 0,
      "scale": 0,
      "unit": "",
      "max": 1000,
      "step": 1
    },
    "v": {
      "min": 0,
      "scale": 0,
      "unit": "",
      "max": 1000,
      "step": 1
    }
  }
}

countdown   
{
  "min": 0,
  "max": 86400,
  "scale": 0,
  "step": 1
}

music_data  
{
  "change_mode": {
    "range": [
      "direct",
      "gradient"
    ]
  },
  "bright": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
  },
  "temperature": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
  },
  "h": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 360,
    "step": 1
  },
  "s": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 255,
    "step": 1
  },
  "v": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 255,
    "step": 1
  }
}

control_data    
{
  "change_mode": {
    "range": [
      "direct",
      "gradient"
    ]
  },
  "bright": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
  },
  "temperature": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 1000,
    "step": 1
  },
  "h": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 360,
    "step": 1
  },
  "s": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 255,
    "step": 1
  },
  "v": {
    "min": 0,
    "scale": 0,
    "unit": "",
    "max": 255,
    "step": 1
  }

[probot-home-assistant[bot]]

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

[probot-home-assistant[bot]]

Hey there @tuya, @zlinoliver, @frenck, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[Andrerm124]

I also have this issue, tempted to return my LED controller while I can and get a Shelly RGBW2

[Djbusje]

You can use local tuya for RGBW support. Use the following settings.

[EpicLPer]

While I would love to use Local Tuya I've kinda "given in" to just keep using their cloud, since any update could break the Local Tuya connection and I've heard about some issues already with it. Simply made a new VLAN that has 0 access to any other internal stuff, so it shouldn't matter much :)

[EndlessEden]

I have a RGBCW droplight with this issue; i do have tuyalan also installed. but with 40+ devices... not really sensible to make individual entities for each device.

[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.

[EpicLPer]

Bump...

(I really dislike Stale bots so much...)

[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.

[EpicLPer]

Anti-Stale comment...

[rickbeec]

This doesn't seem like it would be tooooo hard, but I have a feeling nobody has really looked at it? The other thread started in 2021. Problem exists still.

[thomasboegl1]

bump: same issue

[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.

[EpicLPer]

Anti-Stale.

[RensterGB]

I'm getting similar with an RGBW bulb. I've defined 2 scenes in HA - one to set the bulb to a colour, and dimmed, the other to set it to max brightness pure white:

- id: '1700844456099'
  name: Colour
  entities:
    light.charlie_s_room:
      supported_color_modes:
      - brightness
      - hs
      friendly_name: Charlie's room
      supported_features: 0
      color_mode: hs
      brightness: 50
      hs_color:
      - 231
      - 3
      rgb_color:
      - 247
      - 248
      - 255
      xy_color:
      - 0.317
      - 0.322
      state: 'on'
  icon: mdi:lightbulb-night
  metadata: {}
- id: '1700844516362'
  name: White
  entities:
    light.charlie_s_room:
      supported_color_modes:
      - brightness
      - hs
      friendly_name: Charlie's room
      supported_features: 0
      color_mode: brightness
      brightness: 255
      hs_color: 
      rgb_color:
      xy_color:
      state: 'on'
  icon: mdi:lightbulb-on
  metadata: {}

The colour scene works, but the white scene sets the RGB leds to equal values it seems - creating a white, but nothing like it should be!

[mijnmodelbaan]

bump: same issue with a RGBCW bulb

[andersgenberg]

I also have this problem, but with the garden spolights, DELTACO SH-GLK01.

[grainsoflight]

Have this same problem with Merkury Bulbs

[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.

[EpicLPer]

Anti-Stale... again...

[grainsoflight]

Still seeing this on bulbs and strips

On Thu, Aug 15, 2024, 10:40 PM EpicLPer @.***> wrote:

Anti-Stale... again...

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/77126#issuecomment-2292671545, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHANMY2I2IECPXR2EMQPJPDZRVYBJAVCNFSM57GFMIX2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMRZGI3DOMJVGQ2Q . You are receiving this because you commented.Message ID: @.***>

[nibiru5]

I have this issue as well - please fix because I have to open the tuya app to turn the lights white Booo

[konnostech81]

So... I had the same issue in LocalTuya. My solution was that... Well, I know that my bulb have the modes "White", "Colour" (Yes! "Colour". Isn't working with "Color") and "Scene" (+"Music"), as shown in the original tuya app. So what I did was that I create a select entity (in LocalTuya integration always) with id "21" (for modes) and with select values the "White" and "Colour" modes. And that's it, problem solved!

I also create a template button helper, which I associate with the list entity with "if->then->else" statements, for convenience and for not have to always go throw a select list.

P.S.: If the "ID:21" isn't working for you, you can always create sensors with all the IDs of the device and see which ID return what, as testing it parallel from the app.

the second "Colour" you can possible write it just as "Color" if you want.