There is a small bug with the Zen34 and Zen37 when using on an IQ 4 panel with alarm.com. The issue is in the IQ 4, where it shows an error on the IQ4 which displays on top of the screensaver (picture frame) all the time. In System Check it displays them as ‘unknown’ smart devices. They work fine, but the constant error on the IQ 4 display is annoying.
I have an issue with this opened already with Surety and they have reported it, but perhaps you could somehow apply some pressure to IQ Security (formerly Qolsys, aka Johnson Controls) to fix this on the IQ 4? Maybe via Alarm.com since they advertised it as working?
Thank you for your help. Here are screenshots of what it looks like:
Thanks so much for sharing your experience with the ZEN34 and ZEN37 on the IQ4 Panel. We understand how important seamless integration is and truly appreciate you bringing this to our attention.
From what you’ve described, it looks like this may be a limitation in the current integration between the IQ4 Panel and Alarm.com. While the devices are working correctly on the Z-Wave side, full compatibility depends on how Alarm.com handles these command classes within their platform.
We’ll absolutely report this to Alarm.com and the IQ Panel team to advocate for improved support — your feedback helps push things forward! That said, the timeline for any changes or updates would ultimately be determined by Alarm.com and Qolsys.
Thanks again for your input — and please don’t hesitate to reach out if there’s anything we can do to help in the meantime!
This is specifically an artifact of the IQ panel approach to health checks, it likely doesn’t correctly factor in the sleep behavior of these devices when attempting to check their status. A work around to preventing that error from always displaying is to disable the IQ panels automated Health Checks, since that process is the source of this error dialog.
Thank you. And understood. However I do want those health checks for the rest of the zwave network.id rather not turn them off. So for now I’m just not using those particular Zooz devices with the IQ.
clearly it is a coding error (or omission) in the iq as there are other battery powered/sleeping zwave devices that don’t generate this error. (ADC temp sensors for example)
