8 Messages
Keypad out of range even though it shouldn't be
I have had my simplisafe system for many years. Twice in the past week my keypad has displayed an out-of-range error message. It's close to my base station so that shouldn't be the cause (and it's never been an issue before), but even after putting it directly next to the base station the keypad still wouldn't reconnect. It eventually resolves itself. After the first time this happened I replaced the batteries in the keypad with completely new ones, but the problem occurred again. I don't know if a firmware update caused this problem, but my base station firmware was updated on Oct 13 (10 days ago). Has anyone else encountered this issue? In addition, around the same time that this problem occurs, some of my sensors stop responding (I start getting text and email alerts). They eventually reconnect. Not sure if these two problems are related, but it seems like they may be given that they happen around the same time (although there seems to be a sizeable delay for the sensors to disconnected after the keypad disconnects).
TimDudley
2 Messages
0
0
TimDudley
2 Messages
My system is doing the same thing and so is my cousin’s who lives next door to me. Very frustrating!
0
0
mhbmd
6 Messages
Yes, this just happened to me for the first time this morning. I moved the keypad next to the base station to no avail. I tried unplugging the base station several times but only got a text message that base station power was lost. The problem resolved itself after about 10 minutes. Just waiting now to see if the problem reoccurs.
0
0
SimpliSafe_Jordan
Community Admin
•
137 Messages
Hey everyone thanks so much for your patience while we investigated this recent development.
To ensure optimal performance of your sensors and Keypad(s), we recommend updating your Base Station firmware to 2.21.4.6. You can manually run an update by using the SimpliSafe® Mobile App and navigating to My System > Base Station Settings > Firmware and tapping on Update Available. If you're experiencing this issue and are already on 2.21.4.6, please follow the troubleshooting steps in this article.
11
0