Hello. The article below says that the ZEN34 is now supported.
While it is working, with both Alarm.com scene control and direct associations via the IQ4 panel, I still seem to get the error message on the panel about unknown state (I presume since it is a battery device and it sleeps.). I would have assumed that if it was ‘supported’ that there would be a way to suppress that error message on the display of the IQ4? Or is this an issue of being supported by alarm.com but not necessarily by the IQ4?
It is annoying to see that message box constantly on the panel display because I don’t know if something ‘new’ is wrong or if it is this battery device. For now I’ve removed the device to keep the panel error free.
In general, it would be great for there to be a way to tell the IQ4 panel to ignore (or mark as acknowledged) certain types of benign errors like smart devices in an unknown state. Or at least keep it in the status list but don’t make it pop up on the panel screensaver.
I would have assumed that if it was ‘supported’ that there would be a way to suppress that error message on the display of the IQ4? Or is this an issue of being supported by alarm.com but not necessarily by the IQ4?
So that we can best assist can you provide a photo of the exact message you are seeing on the panel when this happens?
I can share it with Alarm.com and Qolsys to identify the cause.
Has that occurred the whole time since adding the device or did the error pop up some time later? If later, did it coincide with any other changes, new devices, rules etc.?
I know it has been a while, but just looping back on this issue. I was waiting for 4.6.1 to see if it solved the problem, but it has not.
This issue happens with both the ZEN37 and ZEN34. The error comes up immediately upon adding to the IQ 4 and never goes away.
I’ve installed them on my test panel to show you the errors.
Here are screenshots of the “Issue Detected” warning on the screensaver, and the error code on the “View Results” page:
Hi - I am also seeing this with Zen37 wall remote scene controller. I was wondering if there was any update to this or any way to ignore alerts from this particular device so that it doesn’t show on the panel?
There have not been any updates yet on this, the latest IQ Panel 4 firmware is 4.6.1 and this unknown status was confirmed to still occur on that version.
It would be great if we could somehow ‘permanently acknowledge’ unsupported or certain devices from that warning. I know these (zen34, etc) are on the official supported list, so you’d think this would be fixed at some point; but being able to dismiss this error on an individual device basis would make other devices more usable as well.
For example the Shelly i4 generally works with ADC/IQ4, but that annoying error on the panel makes me steer away from recommending it to anyone. What’s worse, is the i4 shows as 5 endpoints in the IQ, and it is only the one endpoint (root mirror) that causes the error. Hiding that endpoint in the IQ does not suppress the error (just takes it away from the light switch screen.)
I installed a ZEN34 and I’m still seeing this error message even though the device itself appears to be functioning correctly.
I wanted to add my feedback that this is a particularly frustrating bug from a user experience standpoint, especially since it appears to have been a known issue for quite some time now. Given that it’s been discussed for well over a year, I’m hoping someone from support or engineering can re-surface it internally and help get it prioritized for a permanent fix.
Seconding the frustration here. The way I see it: Alarm.com has listed the ZEN34 and ZEN37 as compatible, but Johnson Controls hasn’t properly coded the device definitions in the IQ panel software; so the two ecosystems are out of sync.
It raises an obvious question: did anyone at ADC actually coordinate with JC to get these devices added or updated in the panel software? You’d think that before publishing a compatibility listing, ADC would fully validate against their hardware partners’ firmware not just confirm the device pairs/functions.
I just updated to 4.6.2 hoping this had been quietly resolved. It hasn’t.
Meant to follow up with this earlier, we have pinged Qolsys about this issue but have not heard anything new at this time. Will follow up here once we have additional information.
