[OBSOLETE] Lock User Management (LUM)

@RBoy Yes, All the codes were cleared and the hub is not even 3ft away from the deadbolt. The funny part is that I can set as many users I want but is just that one last user that allways gives me problems. Going to restart the hub and see. Will report back.

You’d think that should be good but in practice we’ve seen one hub just isn’t make for a reliable Z-Wave mesh. You will see a dramatic difference if you add just a single Z-Wave repeater device. If you don’t want to add another device try moving the location of the hub, due to antenna design and signal reflections, it does create havoc with communication (which is why having even one repeater is a great idea as it makes for a better signal coverage). One person have a hub just below the lock and it was quite reliable, when he moved it up to be inline with the lock with line of sight, it started working perfectly without any communication retries.

1 Like

@RBoy I am sorry, I thought I mention that I do have 2 other repeaters. A Honeywell Tux acting as a secondary and a Aeotec Repeater… It only hangs in the last code. :frowning:

Thanks for your help!

Have you tried moving the hub and repairing the z wave network. There nothing special about any code, first or last. It’s just getting the communication network stable. Meanwhile the app will continue to retry programming until the locks responds with a successful confirmation.

I am working on it!
Thanks :slight_smile:

1 Like

@RBoy just checked on your site but didn’t see anything in the device handlers section…do you have one that supports the zigbee Yale yrd220?

I have a monoprice deadbolt, using @RBoy’s DH & SmartApp. It does not seem to always update it’s status. ie. I left for work this morning, and it was still reporting being locked from last night. I keep seeing a lot of these in the logs:

7e9d2857-62d3-4295-a648-ae7bdab5ea4b  7:28:27 AM: debug Unsupported device with MSR 0109-2006-0621, Audio/Beeper feature may not be available
7e9d2857-62d3-4295-a648-ae7bdab5ea4b  7:28:27 AM: debug Getting auto lock state
7e9d2857-62d3-4295-a648-ae7bdab5ea4b  7:28:27 AM: debug Getting audio/beeper state
7e9d2857-62d3-4295-a648-ae7bdab5ea4b  7:28:27 AM: debug Unsupported device with MSR 0109-2006-0621, Alarm Sensitivity feature may not be available
7e9d2857-62d3-4295-a648-ae7bdab5ea4b  7:28:27 AM: debug Unsupported device with MSR 0109-2006-0621, Auto Lock feature may not be available
7e9d2857-62d3-4295-a648-ae7bdab5ea4b  7:28:27 AM: debug Unrecognized device with MSR 0109-2006-0621, CodeUnLock feature may not be available
7e9d2857-62d3-4295-a648-ae7bdab5ea4b  7:28:27 AM: debug Lock Alarm mode not configured or not supported, deferring getting Alarm sensitivity level.
7e9d2857-62d3-4295-a648-ae7bdab5ea4b  7:28:27 AM: debug Unsupported device with MSR 0109-2006-0621, Alarm feature may not be available 

Are these just due to unsupported features, or could they be contributing to my deadbolt not reporting properly?

@rboy does not have a ZigBee DTH for locks on his website but you can use mine below. It does all the features of the Z-Wave DTH for Yale locks and works with @rboy’s lock manager SmartApp.


I didn’t even consider the thought that I may need to buy another zwave device just for the sake of repeating the signal…all I was planning on having was the hub and either a zigbee Yale yrd220 or a zwave schlage connect about 20 feet apart.

What is the cheapest zwave or zigbee device I could install that would serve that repeating purpose?

NEW ST user here. I have question concerning my zwave kwikset lock. im using the universal enhanced zwave handler and the lock programed successfully with no issues for most will touch on that later if need be. the problem im getting is the lock will go unavailable and then come back online randomly. not sure what could cause this. batteries at last registrer were 90%. when its online it works flawlessly. though the reason for it going offline is unknown. it seems to happen or i notice it happen when my other types of automations kick in IE alarm blink camera, etc… any ideas would be great.

I’d recommend an Iris plug (linked below). These devices are both ZigBee and Z-Wave Plus repeaters. The outlet itself runs on ZigBee commands, the Z-Wave repeater does nothing but repeat signal.


You can find more information and a DTH for the Z-Wave repeater below. Plug in the module to pair with ZigBee first. Then hit the button 7 times fast to pair the Z-Wave repeater. To reset the device, unplug, hold in the button and plug it in. Next, release the button.


Thanks, unfortunately I’m in Canada, where we like to source all things cool from abroad lol. Would replacing a standard light switch right next to the door with a zwave switch suffice? Otherwise I’ll have to find a more readily available repeater.

The Monoprice lock is a basic lock with no advanced features which is what you’re seeing the logs. Monoprice has stopped selling the lock as of earlier this year, not sure if they’re going to replace it with an updated model. If the status isn’t consistent it’s likely a Z-Wave network issue, make sure your lock is no further than 10-15ft from the nearest repeater.

You may want to follow up on this thread which is dedicated to the lock’s and DH.

I’m having a weird issue that maybe you can recommend an approach for. I have two BE469 locks. Both of them seem to be working with, I am able to update codes and set schedules. They both seem to receive the updates just fine. I set a switch to turn on when the doors are unlocked with a code, and then turn off that same switch when the locks are locked manually by hitting the schlage button. One door does this successfully, the other does not. I do not have the “separate action for each door” option enabled.

They are both using the same DTH “Universal Z-Wave Lock With Alarms” as well. I replaced the batteries, just in case as well.

Could be a couple of reasons, the event isn’t reaching ST or the platform is timing out when trying to execute the actions.
For the lock with the issue, open IDE Live Logging, hit the lock button on the lock and then PM me what you see in the live logs. Don’t forget to the filter the logs to show only the messages coming from the SmartApp (not the lock).

I away from home, but will do this tonight. I will say that I can lock and unlock the door from the app, so I think that smartthings is reaching it. I did a zwave repair just in case, and it finished with no issues. Maybe the logs will help. I guess worse case, I can delete the lock and re-add it

@jhamstead I just went and bought one right now. It automatically got detected as a zwave device.
Thanks for the advice!

@rboy would I miss out on any features of your smartapp if I used @jhamstead’s handler for my Zigbee Yale Yrd220?

@jhamstead’s ZigBee is the best DTH to use for ZigBee locks and is perfectly compatible with the SmartApp.
Having said that do note that ZigBee and and ZWave locks from the same manufacturer may have different features. That being said if you have a ZigBee lock, this is the right DTH to use.

Cool. Having never used a smartapp yet, or the st app itself (still waiting on hardware), I just waned to confirm that whether I go with a zwave or zigbee lock, and assuming they both offer the same built in features, that the device handler won’t be what limits me from using your smartapp to its full potential. Needing access to a full activity log, names dates times and actions