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

Thanks - I reported earlier today.

1 Like

This is the exact same issue I am having with the BE369. I added it, can control it, but it won’t assign codes. It acts like it’s working every time but none of the codes function at the lock. I’ve done everything possible (exclude, include, cold cycle hub, etc) to no avail. Anyone have this issue and solve it? This lock worked perfectly on Vera and Nexia in the past.

I put in a support ticket with SmartThings and they had me jump through all the hoops - resetting, unpair/pair, exclusion, etc. I finally got it working - but as Francky reported, it only worked for a few days and is no longer working.

I am noticing similar issues with random devices not working - it’s really getting frustrating now.

Macvangelist - I’d suggest submitting a ticket with SmartThings support and reference this thread.

I’m now seeing the same sort of things with locks not behaving properly, status wrong, etc. A few times I’ve been able to use the app to trigger the lock to change state but the app doesn’t refresh to show it. You have to physically look at the door to know if it is locked or not. I was initially thinking it was a signal problem somehow. I moved a wi-fi repeater that was near the locks (and has been for many months with no problems) and then did a z-wave repair. That seemed to help a bit but it is still not working properly.

Are others still having this issue, too?


Yes, I’m still having issues. In fact, it’s not responding at all and I’ve given up trying to get it working for now.

SmartThings support has been helpful, but they say it’s not due to the firmware update and it’s more of a mesh issue on my system.

Going to just wait it out for a bit and see if there’s an actual fix.

A question to the community/users for some feedback, there are some capabilities which are unique to some locks e.g.:

  • Fire alerts for IDLock
  • Door open/closed state for IDLock
  • Motion tamper alerts for Schlage

If we enable all these capabilities by default the lock Device Handler will report itself as a Smoke detector, Motion sensor and Door Open/Close sensor. Obviously, for locks which don’t support reporting these states they will show by default as “clear”, “no motion” and “closed” respectively.

The question is, what should be the default (out of the box) capability state of the Device Handler w.r.t these lock specific capabilities (vote below):

  • The device handler enables these capabilities by default, it reports the default states if the lock doesn’t support them
  • Users have to enable these capabilities in the code (uncomment the respective capability lines) if their lock supports reporting them

0 voters


UPDATE: After re-reading your previous post, I agree with the poll. Most of us should have the know-how to edit code if we are at this level of using custom DHL’s. There is always the risk of a typo (PEBKAC error), but still think it is worth it to make the devices not pop up additional capabilities that it can’t use/support.

I have a Schlage Touchscreen Handle Lock Set.
I am using your DHL for this, which works amazing! However was curious about the “Smoke Sensor” that shows up when connecting via HomeBridge.

It threw me off for a bit… I looked up on the internet about this lock and couldn’t find anything in regards to the Smoke Sensor so guessing this is not applicable to this lock? Or is there a bonus feature I wasn’t aware of?

For the meantime, I commented out the capability for Smoke Detection, which made the sensor no longer show up in HomeBridge. The lock appears to be function fine. I did want to run this past you to see if there are any ill/side effects of doing this?


First there is nothing wrong in commenting or uncommenting it. Infact this
is the exact poll I’ve setup in my previous post. Since ST does not allow
dynamic enabling and disabling of capabilities what’s the best way to
handle some capabilities like Smoke and Motion Detection and Door position
sensors which some locks support but others don’t.
It just a visual discomfort if these are enabled but not supported by the
lock. Should the users have to comment or uncomment the capabilities?

Do vote on the previous post.

poll completed.

1 Like

Could you perhaps use a CASE statement to have the user select the kind of lock and thus have the features enabled off of that? I am wondering about whether commenting or uncommenting code will need to be repeated by the user on every code update?

ST doesn’t allow for dynamic enabling/disabling of capabilites otherwise this wouldn’t be an issue. We can identify the lock model and features in the code without any user intervention.

Yes for every code update

Do vote!

Hi everybody.

I am about to head home and connect my brand new Samsung ST to my network and start experimenting. I have spent the last few days reading this and other forums and I must say I am eager to start my project.

One of the device I am about to connect is the Id-lock door lock. I expect it to work and maybe even better with your custom application @rboy but I do have a question:

The ID-lock is limited to two access codes: one master and one user. Does your software - in one way or another - support creation and programming of temp codes on this lock? (Maybe utilizing the slot for the user code) If so - can these codes be enabled/disabled based up on time and date?

I have asked the manufacturer if they plan to extend this functionality but I have not yet gotten an answer.

Thank you kindly.


@rboy I have

IDLock RFID interface requires a special programming interface which currently isn’t supported by this DH yet. It can report on usage etc but can’t program just yet. If there is enough demand we may consider making a new DH which allows it to remotely program the codes (which isnt’ as straight forward as a standard Z-Wave lock and is far more complicated).
Meanwhile you can program the codes in locally and then use the DH to configure the lock and report on the usage, and then use the User Management App to execute events etc based on those notifications.

If folks haven’t voted for the default functionality please do VOTE here.

Have just subscribed, and have to say that I love your work… I’d love to see more around universal camera support, if you’re looking for a next project :slight_smile: I can’t believe all this functionality is lacking in SmartThings.

I have a few queries:

I have a Yale Keyfree (Gen6 UK)

Firstly, my Code Entry icon is missing from the tiles… I would have expected to see it for this model.

Secondly, I tried switching off the auto lock, thinking that it would allow me to set when and how I want to manually lock the door… but as soon as I manually locked the door again, the AutoLock was re-enabled. Is this a Yale thing, or is this a Device Handler thing?

Thirdly, when I did that (even though she’s in Silent Mode) she Shouted “PASSAGE MODE ENABLED”… that was a surprise, and probably woke up the wife. lol

I also have the User Manager installed, but in the logs, it still identifies the code as User 1, rather than by the name defined in the manager… expected behaviour?

EDIT: Regarding the speaking it need to be configured on the lock and
can’t be done remotely (it only be turned on / off remotely and the language can be changed remotely (why??)).

As for the name I think you’re confusing the SmartApp and the DH. The DH
has no idea about names that’s defined in the SmartApp. The DH only goes by
users. The SA maps it to names and when the SA notifies you it will map the
user to the name.

Adam I’m in the UK with the same lock. I also thought the design of the auto lock was rather stupid. If you don’t want auto lock on then every time you unlock the door you have to remove the plastic cover and press the button for passage mode. So I have a piston in core running that switches passage mode on every time it sees the door unlocked. Also all the speech drives you mad so the same piston enables silent mode.

Also what seems wrong is if you go to silent mode it turns off the key pad beeps so I have another person which disables silent mode when the door is locked.

1 Like

I have just made my vote and I appreciate the work put into both the app and DH. I have now gotten as far as using the master slot for my family access code and the other slot can be used as a temporary - timed - code for service personell etc. Love it. (But I do hope Idlock implements the positiblity for more codes to be added making the lock more personal)

Another question has popped up: Is it possible to trigger the “enable/disable autolock” in events? Right now it seems to be a manual operation that has to be executed from the device itself.


Hi @RBoy, not sure what you mean by configuring the speaking on the lock… isn’t that just what silent mode does?

I’m using Stringify to run most of my rules, So I noticed that the auto lock and audio off didn’t pass through as a switch capability. I guess for that I’ll have to create a virtual button? Could the DH be configured to present those as switch capabilities so that they can be configured by Stringify?


@NOITAIDAR I’m going to request @eskdale to share a screenshot of his CoRE rule for his Yale Keyfree speaking setup :slight_smile: