#How often is too often to run an automation?

1 messages · Page 1 of 1 (latest)

blissful vale
#

I appreciate this is a bit of a "how long is a piece of string?" type of question because hardware varies and different automations take different amounts of time, different systems have different numbers of automations etc

But is there any general guideline like "You'll usually be fine down to once every 5 seconds, you'll likely run into issues once you dip under 1 second between runs, in between those it mostly depends on the scenario" or something to that effect?

gusty talon
#

what is your use case where you think you are going to be having an automation spam? maybe there's a better option?

blissful vale
#

It's more about just not wanting to break anything tbh, I don't mind if they overlap

I'm just checking a temperature and flash some LEDs based on temperatures, so I can see if the baby's room gets too warm

I did it with triggers based on the temperature as the most obvious way to do it, but ran into the "it only triggers once" issue (which mean I could miss it) so I've added a "check every minute" trigger too so that it flashes at least regularly if the temperature remains above a warning level

Realistically I probably don't need it to be real-time but was just wondering how responsive I can make that without causing problems

gusty talon
blissful vale
#

Thanks, is that less resource intensive than re-triggering on a timer?

gusty talon
#

probably doesnt make a huge difference. i dont think you will have any issues

#

something like this for example

#

so that will turn on light for 1s then turn off and repeat every 5 seconds until temp goes down again

#

just a random example to illustrate what i was getting at

blissful vale
#

Thanks, so running a trigger/condition and a couple of actions every second isn't going to be an issue in general?