I’m learning to make my own scripts and I have this one script (the contents of which I will apply to other blueprints and scripts I’m currently working on), see below. As you might see, I want the lights to turn on at 50% brightness and 3500K and gradually brighten over a span of 10 minutes to 500…

I don’t see a condition in your script.

[image] 37153: lights to turn on at 50% brightness and 3500K and gradually brighten over a span of 10 minutes to 5000K and 85%. [image] 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-i…

Oops, I forgot to add it back. sequence: - condition: template value_template: >- {{ state_attr(light.keuken, 'context') is not none and state_attr(light.keuken, 'context')['user_id'] != context.user_id }}``` - condition: template value_te…

Thanks! But I’d like to learn to make it myself so can understand what’s happening and how to adjust the settings for my specific situation

Unless you’re going to do something fancier than a linear fade, why use a loop at all? Just use two light.turn_on actions after each other with a transition parameter on the second. If you insist on doing it with a manual loop, you cannot put the break condition inside the loop as that will only sk…

[image] 37153: I’d like to learn to make it myself You can also learn by reviewing the code of the linked example. It’s more feature-rich and you may wish to borrow from it for your own use.

context and user_id are not attributes of an entity. They are properties of an automation’s trigger variable. [image] Request for Generic Thermostat "heater" switch to act as a thermostat physical switch Feature Requests This should help you get started: alias: Override …

Condition: template messing up

Configuration

123 (Taras) January 8, 2025, 3:25am 3