I have some automations that perform actions that could possibly retrigger the automation while it is still running. I have always dealt with that by turning off the automation (now with the stop_conditions parameter set) and then turning it back on after the action has completed.
# turn off automation to prevent recursive call
- service: automation.turn_off
data:
entity_id: automation.radio_morning_radio_finished
stop_actions: false
- service: input_boolean.turn_off
entity_id: input_boolean.radio_morning_preset
- service: automation.turn_on
entity_id: automation.radio_morning_radio_finished
With the new automation modes this is no longer necessary when the automation mode is single as it just created a warning in the log, which is why I left that logic intact.
My question is with the new max_exceeded option, is there any point performance wise to continue turning automations like this off? Logically it seems that I could save a couple of service calls whenever this automation is called by taking that logic out and setting the max_exceeded parameter.
I’m probably nit picking here as I doubt there would be a noticeable difference either way.