There is a minor edge-case bug with the “away disarm” function that is easily replicable which causes the alarm to trigger immediately even if in delay mode and a code was entered to disarm it.
When exiting after arming the system in Away mode, if you re-enter near when the count-down is finished (so far I’ve done it with about 15 seconds and less on the timer but haven’t checked a max bound) and have the voice prompts for the door on, it will interrupt the countdown but not skip the seconds, then rush the countdown and trigger the alarm immediately even if you’ve entered the disarm code and it was in delay mode. The best I can textually reproduce the events is like this:
Arm away.
Countdown begins
Exit
4)Countdown 10…9…8…
Re-enter at 8 seconds
voice prompt (Front Door Open)
Countdown resumes at 7 seconds but is going as fast as possible trying to enunciate every number in less time than it has left do so (i.e. 7.6.5.4.3.2.1 said like an auctioneer might do it)… alarm goes off immediately.
Known condition(s) for the bug:
Voice prompts on for the door being exited/entered from must be enabled.
I believe it happened on the prior firmware as well. I don’t know about stay as I don’t have the countdown enabled for that.
It’s not shortened so much as it doesn’t account for the time used to make the announcement of the door opening, i.e. if you open the door at 10 seconds it will make the 1 or 2 second “front door open” announcement but then resume the count where it left off instead of how many seconds are actually left so the alarm is actually triggered before the count finishes, even though it speeds the count up to try and enunciate all numbers in time.
Sep 17, 2024, 09:09 by notification@support.suretyhome.com:
It’s not shortened so much as it doesn’t account for the time used to make the announcement of the door opening, i.e. if you open the door at 10 seconds it will make the 1 or 2 second “front door open” announcement but then resume the count where it left off instead of how many seconds are actually left so the alarm is actually triggered before the count finishes, even though it speeds the count up to try and enunciate all numbers in time.
Ok, thank you for confirming that. I’ll see if we can recreate the counting issue and forward this description to the manufacturer to address.