Does anyone write/have a driver for this other than just using the generic one?
Is there something the generic doesn't give you?
5 Likes
Fingerprint management for one....
It seems to be really slow to lock and unlock...though that's likely the lock itself. It take almost 10 seconds. In my trigger rules that can add another 8 to reaction time. For most people this is probably fine. In my situation I'm often to that door long before it unlocks. I've disabled everything that I thought might be slowing it down.
But as far as the driver...fingerprint management would be awesome!
!
Highly unlikely that this is possible over z-wave, unless the device communicates the fingerprints as lock codes. Would need a sample device and/or full engineering specs to make that determination.
Do you have it paired as Long Range? If so, the slowness could maybe be a range issue or possibly just the lock itself is slow to respond to zwave comms. Normally it should pick up the FLIRS beam within 30-60 seconds and then do the requested action right away.
If it is paired as Mesh, it could be a mesh traffic issue, either hops or general congestion. The FLIRS beam to wake a lock is very intense on the mesh for up to 60 seconds.
2 Likes
I'd mainly be looking for deletion of fingerprint users. You have to be at the door to load them.
Yes, it's LR about 30 feet in direct line of sight of the hub...but there is an inside door in the path. It's more reliable than my mesh Schlage lock was...but often slower. Slow is still better than a complete failure to respond...especially when locking. If I remember right a device close to the mesh lock should have acted a not only a repeater...and I forget the term...but kind of a duplicator of the command...and it still often failed. There were 3 z-wave light switches within a foot of the Schlage.
