See this comment: https://github.com/home-assistant/home-assistant/issues/28412#issuecomment-548704325
This is really painful. I’m just using scenes so as to have a universal setting per light, e.g. light profiles like I would just copy the default scenes (warm, cool, daylight, etc.) and just change the entiity.
However, after these changes, those scenes that sets the kelvin on lights that doesn’t have kelvin on its attribute doesnt work anymore.
Since I have different type of lights (hue, xiaomi zigbee, xiaomi wifi, yeelight), I need to figure out which scenes are working or not.
Seems to me the only thing you can’t still do is set a transition time - to use that you have to use a script. Everything else seems to have an equivalent state you can set.
To find out what states are valid, just switch the light on and then in developer tools>states you can see what states are available for each light.
Yeah it’s a mega PITA but once you either migrate the options to the correct state or migrate everything to a script if you use transitions - once done done for good.
Another option could be to set the transitions times first with a script then use a scene to turn on or off the needed lights. However I don’t really use scenes myself, and usually use the default transition times. 
That also presumes you want to set all the entities on the same transition, which isn’t always the case.
Yes this is a major inconvenience as all of my scenes are used to set light colors, temperatures, and brightness throughout the day without changing the state of the bulb. The fact that I have to define a state now completely destroys all of my scenes (ie… set all of the lights to 100% brightness in the morning without changing any of the bulb states that way my bedroom lights aren’t turning on and waking us up)
2 Likes