Repeat until automation was working until a few days ago

[armedad]

doing this i a tight loop i typically meta stable. this is because the call to change the brightness on a light is typically not synchronous (ie, it’ll return before the ligtht actually changes brightness)… and it might or might not queue up your requests. if it does queue up the request, what will it do when you’ve overloaded the queue?

it’s not uncommon for this tight loop approach to work for a while, then when timings change (due to an update, or other things happening) it may suddenly break.

the best way to do this is if your light natively supports transitions…

service: light.turn_on
target:
  entity_id: light.your light
data:
  transition: 25
  brightness: 0

or alternatively use @handcoding 's nifty light fader:

Ashley’s Light Fader 2.0✨: fade lights and/or color temperature with your choice of easing (curves), including ease-in, ease-out, and ease-in-out

I have a handful of lights that don’t support transitions natively, and so I wrote a script for that. Main features: If you fade a lamp linearly between two brightness values, that can look unnatural to the human eye. So this light fader lets you choose between any of these 12 easing curves—and there’s also an option to have the script do its best to automatically select one of these easing curves for you. [Ashleys Light Fader - easing types] ( new for 2.0) You can now…

which does the fading for you with all sorts of options and works with lights that do and don’t natively transition.