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

You asked the same question on the LUM topic and I had answered the same question 2 posts before your post. Assuming the battery is good, your hub/lock are having trouble with the mesh.

To answer your other question, yes this DTH supports Schlage Z-Wave Plus modules.

Thank you for the detail. That’s pretty interesting. My house has 38 z-wave plus light switches throughout with tons of them all around the locks and not too far from the hub. Maybe it’s getting to be too much. I’ll reboot the hub and try to do a z-wave repair and see what happens.

1 Like

If the hub is closer to the lock than the buffering devices, then the lock will connect directly to the hub and the devices won’t help with the buffering/mesh. See the 2nd post on the FAQ link above, it talks about positioning of the repeaters vs the hub and it’s impact when the lock is too close to the hub.

NOTE: You should be on version 04.03.00 or newer to be compatible with the new 25.x firmware for V2 and V3 hubs

Universal Enhanced Z-Wave Lock for Schlage, Yale, Kwikset, IDLock, DanaLock, August Pro, Samsung, Locstar, Delaney, KeyWe, Philia and Popp Z-Wave Keypad Device Handler - Version 04.03.08

  • Added support for more KeyWe and Locstar models
  • Added support for Phialia locks with door sensors
  • Improved support for Yale Keyfree/Keyless models
  • Improved compatibility with IDLock 101
  • Alternative identification of lock model if lock has pairing has errors (missing NIF reporting all 0’s)

Schlage Lock Alarm Mode and Sensitivity Change and Monitor - Version 02.02.00

  • < no changes >

A SmartApp like Lock User Management (LUM) or SmartLocks is required for programming user codes.

This Device Handler has been tested and verified and optimized on the following lock models:

  • Yale Z-Wave locks (Assa Abloy, YRD2xx, YRD4xx, YRL2xx, YRC2xx, B1L, T1L, Keyfree, Assure, Conexis, Touchscreen, Deadbolt, RealLiving, nexTouch) (DPS sensor)
  • Schlage Z-Wave locks (FE469, BE469, BE468, FE599, BE369)
  • Kwikset Z-Wave locks (910, 912, 914, 916)
  • DanaLock Z-Wave locks (V2/V3)
  • August Pro Z-Wave locks (door sensor)
  • IDLock Z-Wave locks (101/150) (door sensor)
  • Samsung Z-Wave locks (SHP-xxx, SHS-xxx)
  • Delaney (ZWxxx)
  • Locstar Z-Wave locks
  • Monoprice Z-Wave locks
  • KeyWe Z-Wave locks (door sensor)
  • Philia Z-Wave locks (door sensor)
  • Popp Z-Wave keypad

Key features include automatic discovery of lock features:

  • Lock/Unlock
  • Privacy/keypad control
  • Autolock
  • Audio control
  • One touch/Lock n leave
  • Alarm mode
  • Alarm sensitivity
  • DPS/Door sense
  • Fire/smoke alarm
  • Tamper/motion alerts
  • Emergency alerts (police/fire)
  • Battery life optimization
  • Configuration of one time parameters
    • Yale -> relock timeout, wrong code reporting limit, volume level and dps
    • Danalock ->turn speed, brake n go, turn n go and relock timeout
    • IDLock -> volume level, unopened relock
  • Enhanced programming communication for a weak mesh
  • Handling of missing information while pairing locks

Tap the refresh button in the Classic ST app to query the locks capabilities and the supported tiles will show up.

You can find the installation instructions here.

If you’re looking to capture specific events (e.g. invalid codes) and create custom actions/rules in CoRE/WebCoRE refer to this post.

To enable real time updates with the Smart Locks dashboard

Change the name of the device handler in metadata section around line 152 from

name: “Universal Z-Wave Lock With Alarms”


name: “Z-Wave Lock”

Click Save -> Publish

Copyright © RBoy Apps

I have installed and all works perfectly except battery level. Keeps changing from 32% to 1%. Actual value is around 45. Any ideas?

The 1% is reported when the lock sends a “low battery” alert.
Then the locks sends the actual battery level which is 32% in your case. (The lock sends the absolute levels to the DTH). So that’s probably why it’s flipping between the two. It’s time to replace your battery. Also check out this topic for additional info on battery levels. [RELEASE] Configurable Low Battery Warning/Notification/Monitor and Device Monitoring Alerts

I’m trying to figure out why my August Smart Lock Pro isn’t showing up on Google Home. I can get the contact sensor to show up, but the lock itself won’t. Any ideas?

Does all of this work with the SmartThings Hub V.3 and the SmartThings app, not just the Classic app?

These are two separate questions, independent of each other (yes it can be confusing, the hub is used to communicate with the lock, the ST app is used to configure/control the lock)

  1. V3 hub -> yes the DTH works with the v3 hub (irrespective of which ST app you’re using)
  2. New ST app -> The new ST app uses a different User Interface and it doesn’t support/display all the additional controls that are available in the Classic app (as yet). However the core DTH functionality is identical between the two apps (because it runs in the cloud).

See @maddie release notes above for screenshots of the Classic App vs the new ST app: [RELEASE] Universal Enhanced Z-Wave Lock, Schlage, Yale, Kwikset, IDLock, DanaLock, August Pro, Samsung, Locstar, Delaney, KeyWe Locks and Popp Z-Wave Keypad Device Handler with Alarm Control, Notification, RFID, Door Sensor and advanced features

Updated comparison table of Z-Wave features available across the various popular lock brands. Capabilities but they tend to similar across models (e.g. Most brand models share very similar features). Schalge BE469/FE599 have been singled out since they are quite different from each other. This is a good starting point for folks to understand what features they would like to have and then go from there:

Comparison table moved to first post

Would also recommend reading these posts about limitations of specific lock models


I"m trying to do an update for the first time since installing your app.

The app update went fine and I verified it in the ST Classic app.

The DH code update went fine.
But I can’t figure out how to update/verify in the ST Classic app…

Per Your instructions:

  • Click on “Publish” and then click “For me”
  • Open the Device page on your phone in the Classic ST app, check/update your preferences (little gear icon on the top right) and tap “Done” or “Save”. Now tap the “Refresh” tile (with the circular arrow).

I have looked all over the ST App and can’t find the check/update your preferences.

Hi. I’m looking for some help, and I think this might be the right place.

I’m looking to use my Yale YRL226 in SmartThings, but to also allow me to check if the door is open/closed.

I can currently use the lock from the SmartThings app, but I can’t tell if it is open/closed. The lock came with a sensor. Part of the sensor is in the door lock, the other is attached to the side of the door (on the frame/molding).

Will the universal enhanced zwave lock app work to sense the door w/ the unit that came with it?

If you have a Yale DPS (door position sensor), then yes this device handler does support reporting it to SmartThings. You’ll have to enable the Yale DPS option in the device preferences page using the ST Classic app -> open device page (click the gear icon on the top right corner of the device page, see the first post for a screenshot).
If your lock supports reporting the DPS/Door sensor position over Z-Wave, then it will be captured and reported by the DTH.

Is there a demo/way to test before buying? I’m not 100% sure if it will work or not.

I ended up just paying :slight_smile:

I set up a new device handler using the ‘code’ option.

I got it set up in the new smartthings app, but I don’t see the door open/closed options. I went into the settings and turned on DPS.

Hi there. If the lock is reporting the door / close status it will show up at the tile below the auto lock tile. You can find a screenshot in first post of what it looks like.
But first the configuration needs to be successfully activated. Make sure your lock is within 20ft if a repeater and then open the preferences page and tap Save, you may have to do this a few times before it takes effect depending on your mesh quality. This forces a configuration update on the lock, once it activates, the sensor state should start showing up when you open/close the door (make sure the magnet sensor is aligned).

If you’re having trouble with the feature activation you can send our support desk an email and I can look into your device live logs and see what’s going on with your lock/mesh.

Hi there. Thanks. I sent in an email and included the screenshot from earlier and the live logging from the SmartThings website.

I have two of the schlage connects working fine using this device handler until one of them started to act up.

Its been showing unavailable and locked but its not.

Aside from removing/excluding and pairing it back, is there another way to fix this?

I have tried z-wave repair but this did not fix the problem.


I’m looking into getting a Kwikset 888 deadbolt. Kwikset 888ZW500-15S Smartcode 888 Electronic Deadbolt with Z-Wave Technology https://www.amazon.com/dp/B07BLJ38SJ/ref=cm_sw_r_cp_apa_i_bjh7Cb5F4GEQA would this work?

Yes it’ll work but you want to be aware of a few things about this lock:

  1. It uses certain plastic components internally (rather than metal)
  2. It’s okay for casual use, if you’re planning on using it for rental property with automatic code generation apps like RLA, because it shares numbers on buttons, the lock can’t tell the difference between 1234, 2134, 1144, 1233, 1243 etc (thousands of numbers are unavailable to use across the 5 buttons) and so programming will fail in these cases. See this post.
1 Like