#Delays and blocking automation actions

1 messages · Page 1 of 1 (latest)

weak basalt
#

I'm sure there's an easy answer for this but I don't find searching for it trivial. I have ventilation units in multiple rooms and a bunch of helper functions defined per each. One such is an exhaust mode for some minutes then turn back to defaults. As long as the delay's running, the toggle flip is not considered complete, blocking actions from automations from progressing. Is there a "run in background" / "do not wait" flag somewhere, or am I doing something fundamentally wrong here? As a bonus question, is there a saner way of defining the same helper action for different helper devices? Thanks!

placid cargo
#

I would set it up as a script set to run in parallel, then you can just send the device you want to run "exhaust mode" to the script and it will handle it independently of anything else