Color_temp causes Automation to disappear

Hey team,

any ideas why adding a color_temp to Action section of an automation makes the automation disappear from the list of available Automations? I’m using a GLEDOPTO Zigbee module to control my CW/WW LEDs. I’m able to turn them on/off, change the brightness without any issues. Furthermore, I can even use the color_temp from a script, or using a call from Services section of the Developer Tools (and it works). As there is no way of adding the color_temp in UI, I have to use “Edit as YAML”.

YAML code:

action:
  - brightness_pct: 100
    device_id: 49bf898e2dc946228a468a19a36e4892
    domain: light
    entity_id: light.gledopto_1
    color_temp: 200
    type: turn_on

I’m using Home Assistant Core 0.111.3

Thank you.

Don’t use a the device action. Use a service call instead. Device actions are limited and rather new.

That’s my current workaround. I have a script and I’m calling it from the Automation.

Ok, will use this approach. Thank you.

Now the script is not working at all (starting to think it never was), just the Service Call from Developer tools.
Script:

brightness_pct: 99
color_temp: 499
device_id: 49bf898e2dc946228a468a19a36e4892
domain: light
entity_id: light.gledopto_1
type: turn_on

Service:

entity_id: light.gledopto_1
color_temp: 394

I even upgraded to Home Assistant Core 0.111.4. Any help is appreciated.

does your light support color temp? What is the supported features number on light.gledopto_1.

This time it’s definitely sorted. When you said “service call” in your previous post, from some reason I thought you mean script. If I use a “service call” and feed in the configuration data, it works without any issues.

So the final statement can really be “Setting color_temp (and probably other more custom settings) only works using Action type “Call service” with Service set to “light.turn_on” with Service data used”.

At least for my GLEDOPTO Zigbee module.

Thank you.

1 Like