I am having a recurring issue with a Zooz ZEN37 800LR wall remote paired to an Alarm.com system using a 2GIG GC2e panel.
The remote includes successfully using the standard Z-Wave inclusion process. I did not specifically select any Z-Wave Long Range inclusion mode.
After inclusion, everything works perfectly. I program the buttons, scenes run correctly, and the remote responds as expected.
The problem is that if the remote sits unused for a few days, Alarm.com eventually reports a malfunction and states that the device is unable to communicate with the panel. Once this happens, the remote becomes completely nonresponsive and button presses no longer trigger scenes.
The only fix I have found is to exclude the device and add it back to the network. That restores functionality immediately, but I then have to reprogram all button assignments and scenes.
Additional details:
- Panel: 2GIG GC2e
- Platform: Alarm.com
- Device: Zooz ZEN37 800LR
- Battery is fully charged
- The remote worked flawlessly for the first 2-3 months after installation
- The issue started recently without any intentional configuration changes
- I have tried various button presses and combinations to wake the device, but none restore communication
- The remote may sit unused for weeks at a time, so requiring periodic button presses is not practical for my use case
Questions:
- Is there a way to reconnect or re-establish communication without excluding and re-including the remote?
- Is there a specific wake-up procedure for the ZEN37 that I may be missing?
- Has anyone successfully used a ZEN37 800LR with a 2GIG GC2e long-term without it going offline?
- If the device loses communication, is there a way to recover it while preserving the existing button programming?
Any suggestions would be appreciated. The remote works great when online. I’m mainly trying to understand why it drops off after inactivity and whether there is a way to recover it without rebuilding all of the button programming every time.
Thanks!