Hi,
I saw that @tobiebooth corrected the disarm_after_trigger variable in 0.27.
I tried to use it, but I believe it is still not working properly.
the test I did was to trigger the alarm twice in a row, respecting a few seconds to let the states adjust.
My alarm config is as follows:
- platform: manual name: "full" pending_time: 5 trigger_time: 60 disarm_after_trigger: false
When I setup the alarm, open the sensor, close the sensor, open the sensori got the following sequence:
status: disarmed → set the alarm
status: pending → for 5 secs ±
status: armed_away → open the sensor and trigger the alarm
status: pending → for 5 secs ±
status: triggered → for about 60 secs ±
status: armed_away → open the sensor and trigger the alarm
status: pending → for 5 secs ±
status: triggered → forever…
I believe when it is re-setting the alarm after the 1st trigger event, the program “see” the last valid state the triggered, and after the second trigger is timed out, it sets the alarm to … triggered again (it is just my guess).
would be possible for someone smarter than me to double check that?
thanks!
Luis