I recently installed a Z-wave August door lock (Smart Lock Pro).

I am able to get the lock status and lock it from the ISY just fine, but am unable to unlock it.

 

When adding the lock to the Z-wave network, the August iPhone app mentioned something like the network was using S0 vs S2 security (or something like that, going from memory).

 

Could this be the reason?

(I am on 4.6.2 ISY and 4.55 Z-wave.)

 

 

Hi gzahar,

 

If you are getting status and can lock the lock then it is very unlikely to be a security issue (S0/S2).

 

I don't have one of these locks, but I suspect the problem is based on a Z-Wave change for locks.  There are two low-level Z-Wave commands to unlock a lock, they are unlock and unlock w/timer.  All of the older locks required unlock w/timer (which is what ISY currently uses), but it seems as though the new locks require unlock.

 

We've added this to our bug list, and hopefully will have a solution soon.

Any chance it will be addressed for the version 4 firmware?

The status of the lock (locked vs unlocked) is always updated in the ISY. (assuming you have good Z-wave communications)

No separate API is needed.

See this similar topic that I started about the same issue with not being able to unlock. Michael mentioned this will be fixed in 5.0.11

 

https://forum.universal-devices.com/topic/22237-unlock-command-not-working-for-yale-lock/

How do you like the august lock with ISY?

How do you like the august lock with ISY?

I like the lock fine.  Don't use much with ISY since I can't unlock it from ISY.  (Actually don't use the lock on a regular basis.)

I do use the ISY to warn me if it remains unlocked at a given time.

gzahar,

 

What firmware version are you on? The unlock issue should have been solved in 5.0.11C.

 

With kind regards,

Michel

gzahar,

 

What firmware version are you on? The unlock issue should have been solved in 5.0.11C.

 

With kind regards,

Michel

As stated above, I'm on the version 4 released s/w.

If you think the version 5 is stable enough, I have no problem upgrading.

Is that a straight forward process?  I have been toying with the idea of moving to version 5, but didn't know what was involved.

I have found the 5.0 series to be very stable. The only issue I've found with 5.0.11c is my Fibaro sensors always report on. Any other test devices (insteon & zwave) work without issue

Running 5.0.14 and the lock actuation does not work from the ISY, however I am reliably getting status information from the August lock (unlock, lock and battery level).  The August lock application works fine (it doesn't use zwave tho).

 

pace

I have this lock as well. What I have noticed over the past year with ISY 5.0.14 and this lock is that I can manually lock and unlock the door via the ISY admin console HOWEVER, the current status of the lock when I check at a given time later will usually be "Unlocked."  Somehow the auto re-locking of the lock after the door closes doesn't make it back to ISY. 

 

 

I just upgraded from 4.7.3 to 5.0.15 and added my August to the network.   When I first added, it shows up as "ZW 009 Door Lock" (ZW009_1 - Door Lock) under Network then the first the time the Lock was unlocked (happened to be from the August App not ISY) I see it appears a second time as "ZW 009 Door Lock 2" (ZW009_111 - Door Lock) in Network. The first instance has Battery status, Write to Changes where the second does not.   Has anyone else experienced this?  

I just upgraded from 4.7.3 to 5.0.15 and added my August to the network.   When I first added, it shows up as "ZW 009 Door Lock" (ZW009_1 - Door Lock) under Network then the first the time the Lock was unlocked (happened to be from the August App not ISY) I see it appears a second time as "ZW 009 Door Lock 2" (ZW009_111 - Door Lock) in Network. The first instance has Battery status, Write to Changes where the second does not.   Has anyone else experienced this?  

I have the same thing.


Sent from my iPhone using Tapatalk

Yes, This lock seems to always create two nodes in ISY. I've excluded and included several times and result is always the same.

Does anyone know if this is still an issue where it shows unlocked?