Color_temp, hs , xycolor, light_profiles.csv

Goal: when a light is turned on, let it start with a predefined color/brightness
so, I’ve found light_profiles.csv.
But, light_profiles.csv defines colors with xy values. And, as I write it, it defines COLORS.
I see my lights support two color modes: color_temp and hs.
When I set my light to a color (using some app), the color_mode is hs and hs_color,rgb_color and xy_color can be found in the development tools…
When I set my light to “white”, I have to select color temperature… and in the development tools, I see color_mode “color_temp” and nothing about hs_color,rgb_color,xy_color
So,
color_mode “hs” means, the light is in “color” mode
color_mode “color_temp” means, the light is in “white” mode (from cold white to warm white)

So, the light_profiles.csv only accepts xy_colors. What means, you can only define a color in the profile???
And, using xy_colors, I can not make the light shine the same as “cold white” or other whites.

So, how can I fix this? I already tried it using pyscript, and react on the “turn_on” (when the light was off) event, and send an addtional “turn_on” with the right color_temp… but, that’s not a nice way to do it, because, actually two “turn_on” events are sent this way…

Someone has a solution for this?

did you solve your issue ?

My goal was: being able to define color (in white mode or color mode), brightnes,… for a light, so when that light is turned on, it turns on with those settings. For now, apparantly, only color profiles are possible to be defined in light_profiles.csv. And, you cannot dynamicly change them…
The only solution I found: (and other suggested this too).
Make a trigger program that, when a light is turned on, it does turn on that light again, but with the right settings.
In pyscript (hacs), you can make an “app”. Which can use a yaml config file, and in that config yaml file, you can even use input_ entities… what makes it dynamic.
So my trigger app has a trigger function, that is called, when a light is turned on.
It checks if that light entity is found in the config yaml file. If it is, it gets the settings, a calls the turnon service again, with those settings.
So, the downside is that lights, that are treated this way, will turn on twice…

I would be nice they just added “startup” value attributes to the light entity.