Lock user code notifications for Kwikset 914 Zigbee

Devices & Integrations
1

I have a couple of Kwikset 914 Zigbee locks. Originally added them to ST but LUM wouldn’t find them using default Zigbee drivers. Found a post where Mariano provided edge drivers that would allow LUM to find them. I uninstalled and re-added them using his drivers and now LUM finds them so I can add user codes. I want to create notifications based on the user code entered like I have for my one Schlage zwave lock but the user codes don’t show up on the Kwikset lock details like they do for my Schlage zwave lock so I can’t seem to create notifications for user codes like I can for my Schlage lock. Looking for any pointers on how to solve?

2

First, LUM is a legacy Groovy based SmartApp and all Groovy SmartApps were discontinued in Jan 2023 when ST shut down the Groovy hosting cloud.

Are you using the Z-Wave Lock Edge driver from philh30 for your Schlage lock? If so, he added the capability to use the unlock code name for Routines for Schlage locks only. Rboy has released an Edge version of his Universal Lock Driver that supports using code slot and code slot name in Routines. That driver is a paid version. You will find info here.

3

I did purchase Rboy’s paid driver but it is only Z wave, not Zigbee. My Schlage z-wave works the way I want it to. I’m trying to solve for Kwikset 914 Zigbee.

4

Ah, yes, my bad. I don’t know of any Zigbee driver that supports code slot and code slot name yet. Perhaps ask @Mariano_Colmenarejo if he could add support for it. Phil’s code is available in his repo, so there is a model for how to do it.

5

Hi @h0ckeysk8er @SteveHickenbottom

I don’t know how the locks work and the only thing I have done in my driver is add fingerprints to a version of the stock driver to solve problems for some user.

I’m not going to do anything that I’m not sure what I’m doing in these security devices.

If the changes made to the stock driver fix it, I’ll update my driver with the stock driver, but nothing else.

6

Phil started with the stock driver and embellished it. He added a custom capability for the unlock code name and wrote some code to populate it. He also updated the presentation to expose it for Routines.

7

That’s exactly what is needed!

8

@h0ckeysk8er @SteveHickenbottom

So I think the easiest thing to do and not duplicate efforts is Phil to add the fingerprints to his driver

9

Phil’sdriver is Z-Wave and the user’s lock is Zigbee.