Hmm… That’s an interesting approach. You’ve eliminated the need to press a button. Although you could potentially miss a trigger if you change things too quickly with different sliders if your network is sluggish. Adding a mode: queued to your automation would remedy that, tho, I think.
I’ve also added a button that sets the custom sliders to whatever values the current light group has at the time. This way, I can use the built-in color wheel or color temperature popup to play with hue, saturation, brightness, and once I get it where I want it, I can press this button and the sliders are all set to those values, and can be read off for easy reference (something you can’t do with the color-wheel, unless you look at the state in Dev Tools), or use with the Custom button. That script is here and works whether you use the color-wheel or the color temp option in the built-in color popup:
# Set Custom Input to Current Color
set_custom_input_to_current_color_scr:
alias: Set Custom Input to Current Color (SCR)
mode: single
sequence:
- service: input_number.set_value
entity_id: input_number.lr_accent_hue_in
data:
value: "{{ states.light.hue_lr_lights_lgrp.attributes.hs_color[0] | int }}"
- service: input_number.set_value
entity_id: input_number.lr_accent_saturation_in
data:
value: "{{ states.light.hue_lr_lights_lgrp.attributes.hs_color[1] | int }}"
- service: input_number.set_value
entity_id: input_number.lr_accent_brightness_in
data:
value: "{{ ((states.light.hue_lr_lights_lgrp.attributes.brightness)*100/255) | int }}"
- choose:
conditions: "{{ state_attr('light.hue_lr_lights_lgrp','color_temp') != None }}"
sequence:
- service: input_number.set_value
entity_id: input_number.lr_accent_color_temp_in
data:
value: "{{ states.light.hue_lr_lights_lgrp.attributes.color_temp | int }}"
- service: homeassistant.turn_on
entity_id: input_boolean.enable_color_temp_ib
default:
- service: homeassistant.turn_off
entity_id: input_boolean.enable_color_temp_ib
