Jump to content

Yale locks - Responds appropriately to lock/unlock commands and properly reports status, but "Unlocked" status is always reported upon Query


Recommended Posts

Posted

I just installed two Yale locks with Z-wave Plus (model YRL226 ZW2 OBP).  The locks connected fine and work great, with two Jasco modules as repeaters.  The locks respond properly to requests to lock and unlock and they change their status appropriately.  The issue is this:  When I initiate a Query on the locks the ISY always reports "unlocked" whether the lock is actually locked or unlocked.  If I hit the lock or unlock button, the lock responds and then reports the correct status.  I've tried different settings in the Z-wave options, but I haven't yet found the solution to the issue of "unlocked" status always being reported when I use "Query".  Has anybody else experienced this issue?  Solutions?  Thanks!  

Posted
13 minutes ago, cinbergs said:

I just installed two Yale locks with Z-wave Plus (model YRL226 ZW2 OBP).  The locks connected fine and work great, with two Jasco modules as repeaters.  The locks respond properly to requests to lock and unlock and they change their status appropriately.  The issue is this:  When I initiate a Query on the locks the ISY always reports "unlocked" whether the lock is actually locked or unlocked.  If I hit the lock or unlock button, the lock responds and then reports the correct status.  I've tried different settings in the Z-wave options, but I haven't yet found the solution to the issue of "unlocked" status always being reported when I use "Query".  Has anybody else experienced this issue?  Solutions?  Thanks!  

Firmware and UI of your isy?

  • 2 months later...
Posted

I am having the same issue with my Yale lock.  Whenever my 3am query executes, the lock updates to "unlocked" when it is actually "locked".  This occurs every night without fail.  Firmware and UI are a match at 5.3.0

 

Posted

I have just confirmed that unfortunately the issue with the Yale lock status is still present following the update to 5.3.4

 

Guest
This topic is now closed to further replies.

×
×
  • Create New...