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

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

Thanks for the response. I’m replacing a monoprice deadbolt, so this should be an upgrade right? My monoprice deadbolt just stops responding sometimes and I need to power cycle it to get it working again.
To be honest, I’m more interested in the convenience than the security of it, I have other locks and cameras in place for that.

I sent in the requested logs and also a screenshot showing that “Contact” only appeared in the events list 5 days ago. There are no events for “Contact” or “ContactX” anywhere else.

For anyone with a Yale YRL226, the device handler won’t work with the August door sense.

I’ve tried support and also Yale. Yale says there is no way to get the zwave module to work with door sense.

From Yale:
The door sense is only designed to work with the August app.

EDIT - Model is YRD226 not YRL226

Has anyone used this on the Kwikset 888 series? I didn’t see it as a supported device, but was wondering if it worked anyway and if there was an advantage to using this over the defaults DH.

Universal Enhanced Z-Wave/Plus Lock/Keypad Device Handler - Version 04.04.01

  • Added support for Schlage (ZP series) and Yale Z-Wave Plus locks
  • Auto enable DPS on Yale locks when detected
  • Added option to enable Eco mode on Yale Z-Wave plus locks (when supported)
  • Added option to select vacation/privacy/passage mode when code entry is disabled for Yale locks
  • Added support for Kwikset Z-Wave Plus locks and 8xx series
  • Kwikset 888 features
    • Remotely enable/disable Auto Lock
    • Configure Auto Lock timeout (30,60,90,120,180 seconds)
    • Remotely enable/disable Audio

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

  • < no changes >

NOTES:

  • The Yale Eco mode switches the locks to low power mode with reduced sound and LED brightness (supported by some newer Z-Wave Plus modules)
  • The newer Kwikset Z-Wave Plus 8xx series supports remote control of AutoLock and Audio features
  • The Kwikset Obsidian (954) Z-Wave Plus and other Kwikset 9xx models which have DIP switch controlled features only support reporting AutoLock and Audio status (not changing remotely)

It helps to add a buffering device/repeater within 20ft of your lock for best performance

You need a SmartApp like Lock User Management (LUM) , Rental Lock Automater (RLA) or SmartLocks to program user codes, create actions for locking/unlocking/user codes and notify you.

Refer to the first post for more details and on how to enable Real Time Dashboard with SmartLocks

We have compiled a comparison of different lock model features on this link to get started with buying locks

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

I just installed the new Zwave Plus Schlage lock BE469ZP.

Is it normal that the security level shown is not S2 but S0?
I have a lot of Zwave plus repeaters around

image

Yes that’s normal. ST doesn’t support S2 yet.

1 Like

I just installed & fitted a Yale Keyfree with the latest Z-Wave 2 module (blue). I bought this DH last night and have been able to successfully create a user code from the associated SmartApp but this morning when trying to enable passage mode or turn off audio I get an error logged in the lock

AutoLock feature not supported MSR 0129-0600-0000

From other people in the thread it looks like this feature should be enabled and is what the Yale interprets as Passage mode.

Any ideas?

Hi there. That message is printed because you tried to operate a feature that your lock reported isn’t supported. I will need to see your IDE Live Logs to see specifically what your lock is returning on the discovery request, it could be incomplete discovery request or possibly your model doesn’t support it. You may want to check that you lock is within 20ft of a buffering device to aid with the discovery request.

I will send your the instructions via PM.

FYI when I change the Yale z-wave module to be the original type (had to get via ebay) rather than the new Z-wave 2 module things worked as expected.

I have 2 Yale YRD220 locks with the V1 ZWave module. I am having issues with current state and notifications in general. It last worked about 9 months ago. I reset lock to factory settings, Removed the Rboy App and DH. Rebooted smartthings and then set it all up again. Then recently I bought another YRD220 and zwave module hoping it would resolve the issue.
Below is breakdown of behaviour

Unlock from Keypay = Lock will unlock, but will not send a notification nor will the Lock Status change to unlocked

Unlock from ST App = Lock will unlock and status changes to unlocked, but after 180 seconds when autolock activates the lock will lock, but the status remains unlocked

Adding/changing users from the app = No issues here, just takes a little time to process

Rboy SmartApp version “07.06.06”
Rboy DH version 04.02.02
Yes I know they are a little out of date, but dont want to spend anymore money on this issue unless I know it will work as expected
I have also tried using the generic DH within ST Z-Wave with and without codes

Both locks are within 15ft of the smartthings

Anyone have any ideas what I could try
In live logging I noticed this, not sure if related

10d9f00a-ae24-4e65-b83a-6e057f84a117 13:30:04: warn Ignoring command from A Lock: NotificationReport(eventParametersLength: 0, eventParameter: , zensorNetSourceNodeId: 0, v1AlarmType: 22, reserved61: 0, notificationStatus: 0, sequence: false, event: 0, notificationType: 0, v1AlarmLevel: 1)

ST had made changes to the hub firmware which is why we work hard to keep the apps and DTH’s up to date with the environment. See this release. You should also consider adding a repeater close to your lock.

Thanks for that. Both seem to be working now. Just a little slow. Will give it time to settle down and do all its syncing.

Hi,

Total newbie at this, so please bear with me. :slight_smile:

I have an Idlock 150. Installed the device handler (and the app) yesterday following the installation guide at the RBOY side, but I am having a struggle making it work. After enabling the code in IDE, the door locked by itself, and several sounds came from the lock. But, from the classic ST app, the only thing that actually works, is toggling audio. Battery status is also null.

What have I tried:

  1. Moving the ST hub practically next to the door.
  2. Z-wave repair
  3. Changing batteries.

I would really appreciate any assistance.

/depple

Hi there. If your lock is having trouble with the mesh, this may not help. On the contrary you will need to move the hub away and add a buffering device (like a repeater) close to your lock. See this topic for more details.

Suggestion for new feature… when I am modifying a user I would be interested to see a button that generates a new random code, with a desired number of digits, that I haven’t already used.

1 Like

Unable to update the first post, so folks who’re looking for the app to configure the built in Schlage Alarm/Siren, see this topic:

RBoy Apps is now an officially approved partner for IDLock

Universal Enhanced Z-Wave/Plus Lock/Keypad Device Handler - Version 04.05.00

  • Updated to support IDLock z-wave firmware 1.6


It helps to add a buffering device/repeater within 20ft of your lock for best performance

You need a SmartApp like Lock User Management (LUM) , Rental Lock Automater (RLA) or SmartLocks to program user codes, create actions for locking/unlocking/user codes and notify you.

Refer to the first post for more details and on how to enable Real Time Dashboard with SmartLocks

We have compiled a comparison of different lock model features on this link to get started with buying locks

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

Just purchased. I have Schlage touchscreen. When using Lock User Management and trying to add a user, I type a name , a code and done, it blanks out. I can’t create a user in any of the slots.
If I change a setting such as notify on use it blanks out what i typed. example logging after trying to add user 1.

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:51 PM: debug Front Door Lock user 3 is empty, code already deleted

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:51 PM: debug Front Door Lock user 2 is empty, code already deleted

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:51 PM: debug Front Door Lock user 1 is empty, code already deleted

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:51 PM: trace The date/time on the hub now is Sat Oct 19 2019 12:51 EDT

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:51 PM: warn READ THIS BEFORE PROCCEDING: IT IS NORMAL TO SEE DEBUG MESSAGES EVERY MINUTE, IT CONFIRMS THAT THE APP IS HEALTHY AND RUNNING IN THE CLOUD. IT DOES NOT COMMUNICATE WITH THE LOCK UNLESS YOU SEE A MESSAGE BOX SAYING ‘REQUESTED LOCK TO XXXXX’.

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:12 PM: trace Configured lock fixed code length: 4, max code length: null, min code length: null

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:12 PM: trace Initial 1 Name: null, Code: null, Notify: null, NotifyModes: null, ExpireDate: null, ExpireTime: null, StartDate: null, StartTime: null, UserType: null

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:12 PM: trace User Codes Page, user:1, name:null, passed params: [nextPage:userConfigPage, settings:[userType1:[name:userType1, value:Permanent, type:enum], userNames1:[name:userNames1, value:Rich, type:text], userCodes1:[name:userCodes1, value:9246, type:text], userNotifyModes1:[name:userNotifyModes1, value:, type:mode], userXNotifyPresence1:[name:userXNotifyPresence1, value:, type:capability.presenceSensor], userNotifyUseCount1:[name:userNotifyUseCount1, value:, type:number], userNotify1:[name:userNotify1, value:true, type:bool]], modes:, label:Lock User Management, params:[:]], saved params:[id:4cca91b5-fa38-4066-b49a-6ceddb03699c, name:userConfigPage, passed:true, user:1]

4cca91b5-fa38-4066-b49a-6ceddb03699c 12:51:12 PM: trace Passed from submitOnChange, atomicState lookup for user:1