@firstof9 a not entirely related question. Where can I read about lovelace card data points that can be passed as parameters. For example {{h}}, {{s}}, {{brightness}}, {{color_temp}}, {{effect}}. Are they standard or any card maker can define its own?
Below is what is working for me in both the UI and Google Home. Note that I only have the input-text so I can map a logical device to a physical device (because I keep moving things around).
Hello @michaelblight !
I have a same problem: hs_colors sends data to my py script according to UI, but it works only with local variables (for example, I can’t send {{ brightness }} in the set_color).
I have started to use state_attr variables to send all the light states to my scripts, but hs_color doesn’t initialized in the attributes. However, it initialized if I use set_temperature in config, but it works only if I choose orange color in UI.
I have no ides why it happens.
Can you help me, please? I see only one principle difference between your and my config files: I haven’t color_template. If it can be the reason, tell me please what is input_text and where you define it and how?
My input_text is just a way of separating logical devices from physical ones because I sometimes move/update things and don’t want to update the code. Currently states('input_text.lily_mirror_light') is set to “light.controller_rgb_9dfa6a”. color_template just gets the current color. Since I am just creating a template light that is a ‘copy’ of another light, I am just getting its hs_color attribute. Similarly, when setting the color, I turn on the other light and pass the “h” and “s” parameters to hs-color.