5 tricks that help me keep my Home Assistant automations in check
When you create automations in Home Assistant, they don’t always behave exactly as expected. Sometimes, instead of triggering once as expected, your automation may trigger multiple times in a row. If this happens to you, there are several fairly simple ways to resolve it.
Use the appropriate automation mode
One of the easiest ways to prevent automations from triggering repeatedly is to make sure you’re using the correct automation mode. Home Assistant includes four different ways for automations to act when triggered again before all actions are completed.
With the default “simple” mode, even if an automation is triggered multiple times while it is still running, no new execution will start. You can choose to use one of the other three options instead.
“Restart” will immediately stop the current execution and start a new one. “Queued” will terminate the current execution and start the next triggered execution only after the full initial execution has completed. “Parallel” will start a completely new execution while the initial execution continues until completion.
These automation modes only apply when an automation is running. Once completed, they will not prevent an automation from triggering again.
How to create smart home automation that is personal to you and your family
Use this simple approach to identify what you can automate in your home
Debounce using “for”
One of the common reasons automations keep triggering is because the sensor that triggers the automation keeps hovering around the value used as a threshold or bounces quickly between two states. For example, if you have an automation triggered by a contact sensor, the sensor can often oscillate between open and closed when a door is closed, causing the automation to trigger repeatedly.
Debouncing is the process of removing unwanted fluctuations from a signal, and you can achieve this in Home Assistant by using the “for” option in your state-based triggers. This allows you to guarantee that the automation will only work when the trigger has been detected for a specific continuous period. For example, with a contact sensor, you could operate the automation only when the sensor has remained in the “closed” state for at least two seconds.
Two-threshold hysteresis
Hysteresis is another useful method to prevent automations from triggering repeatedly when sensors continue to rotate around key values. The concept is simple; Instead of having a threshold at which the automation turns on and off, you set two thresholds slightly apart from each other. When the sensor reaches the highest value, the automation is triggered and it will not turn off again until the sensor drops below the lowest value, leaving a buffer in between where no action will be taken.
One of the easiest ways to use hysteresis in an automation is to use the Threshold Wizard. You provide the input sensor you want to use as a trigger, set upper and/or lower limits and a hysteresis value (the distance between the input sensor value and a threshold before the state of the threshold sensor changes).
For example, with a temperature sensor with an upper limit of 20 and a hysteresis value of 1, the sensor would turn on when the temperature exceeds 21 and turn off when the temperature drops below 19. You can then use this sensor to trigger your automations instead of the value taken directly from the sensor.
Add a recharge timer
Another simple but effective way to prevent your automations from triggering too often is to use a recharge timer. You add a time restriction to your automation that ensures that it will no longer trigger until a set period of time has passed.
There are several ways to achieve this. If your automation is set to “simple” mode by default, you can add a “delay” action at the end of the automation. This will keep the automation running until the timer has finished, and by using “simple” mode, the automation will not trigger again until this first run has completed.
The downside is that this means your automation continues to run in the background, which isn’t ideal. A smarter option is to use a template condition based on the time the automation was last triggered.
You create a model condition that looks for the time difference between the current time and the “last_triggered” time. If this time difference is less than the threshold you add to the template, the automation will not run. An example of this type of template condition is:
{{ (now() - (state_attr('automation.your_automation_name', 'last_triggered') | default(as_datetime(0), true))) > timedelta(minutes=5) }} This will only allow the automation to run if it hasn’t run in the last five minutes. THE default(as_datetime(0), true) ensures that automation will still work if there is no value for last_triggeredas if the automation had never been performed before.
6 smart home automation systems that seem magical
Sometimes my smart home still makes me feel like a wizard.
Use edge triggering
Sometimes sensors lose connection to Home Assistant. If you have an automation that triggers when a sensor turns on, the automation can continue to trigger each time the sensor reconnects and the status changes from “unavailable” or “unknown” to “enabled”.
You can often resolve this problem by creating a trigger that includes both a “from” and “to” state. For example, your trigger might occur when the sensor status changes from “off” to “on”. This ensures that the automation only triggers on the “rising edge” and does not trigger when the state changes from “unknown” to “enabled”.
There are many reasons why automations may continue to trigger even when you don’t want them to. The best way to resolve this problem is to understand the cause. You can then find the right solution that will ensure your automations only trigger when you want them to.
