15 Messages
Mode set to "Away" from keypad without keypad input
The other night, we set our alarm to Away mode using the App. We heard all the typical sounds (countdown beeps, voice announcement) and the Timeline in the app shows the "Countdown to Away Mode" and "System Armed in Away Mode" as expected. Several hours later I awoke to the system announcing AGAIN that it was being set in Away Mode. The Timeline shows that it was set via the Keypad at that time even though no one in the house had touched the keypad.
Anyone else experience this?
Note: I am aware---and have experienced---that setting the system mode concurrently using multiple devices can cause unexpected behavior. For example, hitting the Away button on the app at nearly the same time as the keypad will kick off two independent countdowns. If you cancel one, the other countdown will continue. As another example, if you set the system in Away mode and hit the Away button again after the countdown completes, the system will be re-set into Away mode with no countdown (the announcement will be made and the timeline will reflect that the keypad was used to set the mode). Even stranger behavior can occur when there is spotty internet service. Commands via the app can be delayed for minutes or hours, resulting in changes to the mode long after the input was provided.
However, I don't see how any of these concurrency issues or network latency could account for a unexpected message from the keypad.
Anyone from Simplisafe care to hypothesize?
davey_d
Community Admin
•
5.6K Messages
1 year ago
Hi @QuarkENess ,
There are some rare instances where the system may re-post its current status, which might appear as a new event. Though usually it's after certain alarm events - like if you had entered the Keypad Menu and forgot to manually exit (so it would re-post the status after automatically returning to the status screen). It might also happen if there's a spotty connection between the Keypad and the Base Station, through the local radio signal. Neither case involves the system actually setting a new alarm state - just repeating the current one.
If you're seeing the system actually set a different alarm state, that might be a different issue we'd need to look into. But for the above issue, a correction is coming soon in a firmware update.
2
0