Schlage keypad lock with lever (FE599) doesn't send lock status to ST when auto-locking

[kevdliu]

Hello,

I’ve been experiencing some issues with my Schlage keypad lock with lever (FE599) and SmartThings and was wondering if anyone else has experienced the same.

When I unlock the lock by entering my user code, the lock is designed to stay unlocked for a few seconds before locking itself again. From the ST event log, I can see that it registers the unlock event correctly, but does not register the lock event when it auto-locks after a few seconds. I have to manually push the lock button for it to register. As such, most of the time ST shows my lock as unlocked even though it is in fact locked.

Has anyone else experienced this?

Thanks

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Yes that’s an issue with the lock firmware. If you have access to RBoyApps you can use this Enhanced Z-Wave Device Handler that fixes this and many other firmware issues:

[RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung

A “future proof” Universal Enhanced Z-Wave Lock driver This driver is enhanced to fix bugs in the stock ST ZWave Lock driver, include patches for bugs in lock firmwares and bring out additional features for Schalge, Yale, Kwikset, IDLock, Popp, Samsung, Delaney, August Pro, Danalock, KeyWe, Philia, Vivint, Locstar etc zwave locks (see below for a full list of models and features). This works with all ZWave locks and newer ZWave Plus locks (see below for a list of locks tested). It discovers/learns the lock features and automatically configures them. If a feature is not supported by the lock it will not show up or say Unsupported. You need SmartThings Smart Lock Guest Access (SLGA), Advanced Web UI or a SmartApp like Lock User Management (LUM), Rental Lock Automater (RLA) to program user …