Automations "reload/parallel/queued" better than "single"

Configuration
1

Is it better to make all automations in parallel or reload instead of the default (single).

Especially when using on-off triggers it seems to miss if the triggers, if they are very close and the automation takes some time to do something. But actually the last state is the most important one.

For example motion > light on > no motion > light off. If the action to set the light on takes longer it will never switch off. But if queued is used it will switch on first, then switch off. I guess with single it would only switch off, because the switch on trigger is restart and then the condition is different.

I guess only time critical (like a series of events) should be done with single to make sure it runs through completely.

Does this make any sense? :slight_smile:

2

it really depends on the use case.

the vast majority of my automations use the (default) single mode and i never have any issues.

there are a few that get run in parallel. one of which toggles a light based on two door sensors of a small pantry cabinet. so both sensors could trigger within a ms of each other when both doors are closed together.

and several get restarted. an example of one of those is that my deck light fades from 0 to full brightness over 15 minutes at sunset. if it gets interrupted for some reason I restart from the current brightness to finish the transition.

So it just depends on the uses.

1 Like