I sometimes find myself wanting a new automation mode that is somewhere in between “once” and “parallel”.
I want it to be able to run one instance per trigger, in parallel.
This can be worked around by duplicating automations, but it would be much neater for me if this mode existed.
A concrete example:
I have an automation that uses my security cameras to detect motion. I then run an AI query to determine if it’s important, and then notify me.
I have one trigger per camera, then all other code is shared.
If multiple cameras trigger motion at a very similar time, I would like to be able to have an instance of my automation running in parallel for each triggered camera.
I envisage it to be logically similar to “parallel”, but with an extra check that the automation isn’t already running with the activated trigger
. the unique set of running automations could be a new attribute, a bit similar to the current
running count attribute.
Thanks for reading!
PS. in the interests of covering many use cases, it could be that this behaviour should be applied to queue, loop and restart too. So it’s a checkbox that makes the mode act per-trigger, instead of for the whole automation…