Curious as to what you’re using scripts for? I have 88 automations and have so far found no need for a single script and I feel like I’m missing a trick somewhere.
Yes, I do have some automations that share functionality but it’s one or two actions and it seems redundant to call a separate script.
Scripts are used for a lot of things! Generally any time I want to do the same thing under multiple automations, I use a script as the middleman.
For example, I built a script for turning off all of my lights each night but it has to be fed a time scaling variable to determine specifically how quickly to turn them off (sometimes I want them turned off quickly vs slowly). Automations trigger said script with the right scale factor.
I have air purifiers that I ramp up and down conditionally, they don’t have a built in ramping function so I built a script to ramp them to a target % in their allowed 10% increments, over a variable time period. This can be then be called in one line from any automation or script.
When I’m turning off lights each night, I want them to ramp down to a specific level/color/temperature before turning off but only if they are currently on. Rather than build an if statement for every light, a script takes a input list of lights and runs through each one to determine whether or not to ramp.
Finally, my Google Home device is able to call scripts directly, (“hey Google, activate Cozy Time” triggers the “Cozy Time” script) so some things I use Google Assistant to trigger use scripts directly since that was at least easier at the time than using an automation. If I automate the same thing (e.g., a “Cozy Time” button above), I can just call the script from the automation in one line, easy peasy.
Can I ask about your light script? I have a bunch of smart bulbs that either don’t support or don’t expose the ‘power-on behaviour’ option, so in a power cut they come on full bright when power is restored, often in the middle of the night.
My HA is on a UPS so I’ve been trying to have it store the states of lights when the UPS switches to battery power (before they go to unavailable) and then restore those states when power comes back, but it’s apparently way beyond my skill set. Curious as to how your “input list of lights” works and whether it could help me…
Here is the full script in case it’s helpful. took a hot second of searching to set everything up, but now it’s really easy to use. When you call the script inside an automation it has input fields just like if you’re calling a built-in function like light.turn_on
For your specific use case though, it may be easier to just take advantage of the built-in Scenes function. You can use an “entity snapshot” with “Scene: Create” a scene of the current state of your “bad” lights when the power goes out, then “Activate” that scene, perhaps with a couple of seconds transition time to smooth things out as soon as power is restored.
I use a similar scene based function to create flashing colored light alerts based on certain conditions.
Curious as to what you’re using scripts for? I have 88 automations and have so far found no need for a single script and I feel like I’m missing a trick somewhere.
Yes, I do have some automations that share functionality but it’s one or two actions and it seems redundant to call a separate script.
Scripts are used for a lot of things! Generally any time I want to do the same thing under multiple automations, I use a script as the middleman.
For example, I built a script for turning off all of my lights each night but it has to be fed a time scaling variable to determine specifically how quickly to turn them off (sometimes I want them turned off quickly vs slowly). Automations trigger said script with the right scale factor.
I have air purifiers that I ramp up and down conditionally, they don’t have a built in ramping function so I built a script to ramp them to a target % in their allowed 10% increments, over a variable time period. This can be then be called in one line from any automation or script.
When I’m turning off lights each night, I want them to ramp down to a specific level/color/temperature before turning off but only if they are currently on. Rather than build an if statement for every light, a script takes a input list of lights and runs through each one to determine whether or not to ramp.
Finally, my Google Home device is able to call scripts directly, (“hey Google, activate Cozy Time” triggers the “Cozy Time” script) so some things I use Google Assistant to trigger use scripts directly since that was at least easier at the time than using an automation. If I automate the same thing (e.g., a “Cozy Time” button above), I can just call the script from the automation in one line, easy peasy.
Thank you, that’s food for thought at least.
Can I ask about your light script? I have a bunch of smart bulbs that either don’t support or don’t expose the ‘power-on behaviour’ option, so in a power cut they come on full bright when power is restored, often in the middle of the night.
My HA is on a UPS so I’ve been trying to have it store the states of lights when the UPS switches to battery power (before they go to unavailable) and then restore those states when power comes back, but it’s apparently way beyond my skill set. Curious as to how your “input list of lights” works and whether it could help me…
Here is the full script in case it’s helpful. took a hot second of searching to set everything up, but now it’s really easy to use. When you call the script inside an automation it has input fields just like if you’re calling a built-in function like
light.turn_onFor your specific use case though, it may be easier to just take advantage of the built-in Scenes function. You can use an “entity snapshot” with “Scene: Create” a scene of the current state of your “bad” lights when the power goes out, then “Activate” that scene, perhaps with a couple of seconds transition time to smooth things out as soon as power is restored.
I use a similar scene based function to create flashing colored light alerts based on certain conditions.