I have two ZEN32 scene controllers, and a few ZEN71/76 switches. Yesterday I happened to update my IQ 4 panel to the latest firmware 4.5.2, and noticed this problem ever since. not sure if this is directly related to that update, or if a coincidence.
The issue is that if I press any button sequence that should fire a scene in alarm.com it does not work.
When I look in ‘Activity’ in alarm.com, I do NOT see anything related to that scene being fired or that button being pressed on the switch.
However when I look in the IQ 4 Panel under Zwave Device Status, I DO see the button presses in the history log.
An update:
I removed one of these switches, and re-added it. Then setup a test scene on a double-press of Button 1. And it worked.
Ugh! Does this mean I have to remove and re-add all these controllers and switches? The re-programming on the scene controllers is a chunk of work I really don’t want to re-do. … and I hope this isn’t something that will happen each time I update the IQ 4 Panel?..
Hopefully there is a solution. Thanks.
I wonder if this could be related to enabling multi-channel z-wave instead of the firmware upgrade? Did you see the scenes working properly after we enabled multi-channel z-wave?
Although, I don’t think those switches are multi-channel are they?
Ugh! Does this mean I have to remove and re-add all these controllers and switches? The re-programming on the scene controllers is a chunk of work I really don’t want to re-do. … and I hope this isn’t something that will happen each time I update the IQ 4 Panel?..
Have you tried rebooting the panel first? I would do that before deleting and re-adding any more devices just to be sure.
Did you try just reconfiguring the button rule and saving without deleting the switch? If you try that on one is it then successful?
This definitely worked after multi-channel zwave was implemented, as I use these scene controllers many times a day. (I work from home often and my office lights are all on one of these controllers.)
I just tried reconfiguring a button rule, and it still does not work, nor show the button press activity in ADC.
(Note that I had to program it twice - the first time after I picked the device and button, I saw a popup: “Something went wrong” and the ADC website bumped me back to the rule wizard. But the second time it allowed me to add the rule. May be unrelated but I haven’t seen that before.)
I rebooted the panel, and no change. The one I re-added still works, the remainder do not. The Panel history shows the scene button press, but the ADC activity log does not, and resultant rules/scenes do not fire.
I tried re-sending the scene enable command to one of the switches just in case, but no change (parameter 10, 1).
I did see this older post which is not the same issue (luckily!) but similar in that it was after an update. Is there a history of updates causing issues?
Problems can happen but they are not expected. I have sent a troubleshooting command to resync some device status info which may have an effect given how specific this is. Let me know if you notice a difference in about 15 minutes.
So I can compare and check if there is anything that leaps out on our end, what is the name of the switch you relearned already where the scene was working?
The relearned switch is called “Upstairs Light”
I setup a double press of the top (button 1) to run scene “On Holiday (inside)”
At the moment, no zwave devices work at all. I’m assuming since that sync may still be running? Cant control at panel or alarm.com at the moment. I’ll give it time. I have to do a conference call for an hour anyway. Thanks
Yes if you have a lot of Z-wave devices that the panel will run a check on one by one so it can take a while. I am trying one more command to resync the device list with Alarm.com. Hopeful that it isn’t necessary to relearn those devices.
It would be good to also run a network rediscovery first before deleting any more, just in case.
Update: I waited for all to settle, and then ran a network rediscovery and let that settle as well. Now, I’m back to my previous state - everything works except for those scene controllers that have not yet been re-added since the panel upgrade.
Also I have some non-zooz devices that are seen as ‘remotes’ and while I never used them, they do not respond either when setup with a scene, so this doesn’t seem to be just a Zooz hardware issue, but I’m not 100% sure.
I also tested my multi-channel devices via ADC app and Website, and they do seem to still be working properly, fyi… so this issue seems to be limited to just those Zooz scenes. The panel sees the button press but ADC doesn’t see it at all. Strange.
I even tried power cycling the switches/scene controllers by turning off the breakers for a few minutes. No joy.
This is a real pain.
I’m thinking, though, the issue is either the IQ panel isn’t sending the code to alarm.com about the button press, or Alarm.com isn’t accepting or hearing it. It would make sense that something needs to be re-synced on the back end and the action of deleting / re-adding is really a work-around for the real issue and resolution. Hmm…
This would be a case of the panel not sending them from what I can tell. We’ve sent all the sync commands from Alarm.com and in ADC the devices have no reported differences between the old ones and the new one you re-enrolled.
Speaking with Qolsys support, this isn’t a common issue, but they suggested relearning the remotes as the step to fix the issue.
Z-wave devices cannot be backed up and re-applied to the panel through Alarm.com, they need to be deleted and relearned individually. I know it is frustrating with a lot of devices. I am reaching out to some reps at Qolsys to see if they can identify why this might’ve happened with those particular remote config rules.
I have Alarm.com looking at it as well in case they have any additional info but the rep said they haven’t seen this particular failure before, and we’ve already taken the steps they have recommended.
ok. I’ve removed and re-added all. I’m back with full functionality now. Thanks again for your help!
This time around I documented all the DSK codes so I don’t have to pull switch plates if this happens again. Also documented all the custom parameters, and rules.
