Scene issues with Mqtt colored lights

I just hooked up some Tuya colored (Tasmota flashed) lights to home assistant and they work great. Changing brightness, color temp and colors all work just fine. The only strange issue I am having I that when I try to set a color temp in a scene they automatically turn a saturated purple. But calling. the service color_temp: 500 works just fine. So this seems to only be a scene issue.

Anyone has any idea why this is happening?

Hi, I’m facing a pretty similar issue with an MQTT light. For me the issue is the following. I adjust the color of the light in the scene editor which works fine but when I save it and then activate the scene my light turns just white.
A quick look into the scene.yaml file shows that the xy_color is set correctly but the rgb_color value is just 255 for all three colors.

- id: '1582893336076'
  name: Sonnenuntergang
  entities:
    light.tv_licht:
      brightness: 200
      effect: solid
      effect_list:
      - solid
      friendly_name: TV Licht
      hs_color:
      - 0
      - 0
      icon: mdi:creation
      rgb_color:
      - 255
      - 255
      - 255
      state: 'on'
      supported_features: 61
      xy_color:
      - 0.323
      - 0.329

The config for the MQTT light is the following:

- platform: mqtt
  schema: json
  name: TV Licht
  state_topic: "led_strip/TVLicht/state"
  command_topic: "led_strip/TVLicht/command"
  effect: true
  effect_list:
    - solid
  brightness: true
  rgb: true
  optimistic: false
  qos: 0

I think the problem is a bug in the scene editor not saving the correct rgb_color value. But I have no clue why that’s the case.

@tyrsen could you take a look into your scene.yaml file as well and find out if the save option from the scene editor is not working properly

Mine also sets RGB to 255,255,255 but I can see why my values would be that since in my scene I control the color_temp and not RGB. The scene editor stores ALL the lights current info but does not set what value to actually set the light to when the scene activates. So my color_temp is being overrides by other values like RGB even though for that specific setting I want the color temp set.

I have no problem when saving a color for my lights in a scene, only when I try to control the color_temp.

Are you calling color_temp and rgb_color in the same scene?

Both of these attempt to change the color, so you’re not allowed to have both in the same scene.

You’d think it would be added to the documentation for scenes.

If your light.turn_on command auto sets a color or color_temp, it wont work either.

In the scene editor you don’t have an option of what values it should store. So when I set my lights with the scene editor it stores all values and that is what creates this issue.

For now I have to make manual scenes outside of the editor to get it to work.

I can just agree to what @tyrsen says. The scenes editor stores all values the specific device offer at most (like color_temp and rgb_color) even tho you only set one of them. This somehow creates an override problem because I guess there either must be some type of hierarchy involved when calling the service or the order in which e.g. the values are called matters.

Adding in my two cents ^ I have the same issue with the same hardware / firmware on the lights. Running 108.9. I made a big jump from 102? Love the changes. Hope this gets sorted out so I can use the UI. I, for one really don’t like YAML.

I opened an issue because the problem is still present for me.

For me it was the wrong formatting of the MQTT message as described in the issue (which I closed already). Probably this is the same for some of you. To see wheather the MQTT message of the state topic is in the correct format use the onboard MQTT tool of the developer options in HA.

Same problem here

Hi,
same for me when using H801 controller with tasmota, controlled via mqtt.
When I set the color to red, the scene will save correctly. Then I turn on the scene, light blinks in red and then turns white.

PS. I don’t use manual config, it’s autodiscovered by MQTT plugin.

I’m having the same problem with a Shelly RGBW2 combined with a RGBWW led strip. It does save the RGB settings, but it doesn’t save the warmwhite channel percentage in the scene.

I’m getting this as well, over 2 years on it still doesn’t seem to be fixed.
Anyone have a workaround?