In Smart Automation 2.0, the “WHEN” trigger only activates ONCE, even if the are intended for interval triggers when the condition remains true over time. In version 1.0, this worked correctly — the trigger would repeat in intervals as long as the condition was met. This seems to be a major issue that requires adjustment.
Context
Automation 1.0
User Story:
I’d like to receive a sound or text notification when the outside temperature drops below 12 °C, if the indoor humidity is below 55% or the indoor temperature is below 22 °C, after a door or window has been open for at least 5 minutes to let in fresh air.
Reason:
Sometimes, the children leave a window or balcony door open, causing the temperature to drop critically low. Therefore, reminders need to be sent at regular intervals until the door or window is closed.
Automation 1.0 handled this correctly (see attached).
Automation 2.0 Issue:
In version 2.0, the WHEN trigger only once when the condition is met, and no further notifications are sent while the condition remains unchanged.
Hello, welcome to the forum.
Yes, this problem exists, it was announced for 2.0 developers. At the moment, I recommend creating this type of automation in 1.0. 1.0 and 2.0 work in parallel without problems.
Hello Unfortunately, not all conditions are in “IF” in addition, the size (conditions) of automation will increase significantly. It is better to use 1.0
I just started with Aqara and didn’t use automation version 1.0 a lot.
The WHEN section in version 2.0 looks like to be purely trigger based.
Everything you put in the WHEN section will be regarded as a trigger.
The confusing part is that with the door sensor what looks like a state, will be handled as a trigger.
When you use the Opened for over 5 min. in the WHEN section it will be regarded as a trigger and the automation will start when the door is opened.
The automation will wait 5 min, do its thing and stops.
It will start again when the door is openend.
In my opinion there is nothing wrong with the automation of strmi.
Ok, it doesn’t do what he wants it to do, keep running until the door is closed. But based on the WHEN section it does what it has to do.
I don’t know if it’s wise to have constantly running automations on your Zigbee network.
A possible solution is adding a repeat option (just like the trigger once option) which bypasses the WHEN section. I don’t know, maybe?
