[RELEASE] Lock User Management (LUM)

Sequence of events and priotities are controlled by SmartThings and depends
on the cloud/account. There two reasons for delays:

  1. Z-Wave mesh issue as you know and have investigated - this is relatively
    easy to fix, add a few repeaters, reboot the hub and do a z-wave repair
  2. SmartThings cloud execution scheduling

Apps don’t have control over scheduling. In an ideal world all apps,
routines etc should get the same priority but in reality it depends on
which server your account is running and it’s scheduling the actions
(SmartThings runs on Amazon and across multiple

For some folks routines run faster than apps, while for others, routines
run slower than apps. There’s no way to control it, the best you can do it
figure out what works better for you. In your case routines seem to have
higher priority or the servers are less loaded than the ones running your
SmartApps, so maybe you should put your action in routines instead of the
SmartApp itself.
Just for comparison, in our test lab account, routines run super slow, I
mean it takes upto 30 seconds to turn on a switch, where as the SmartApps
are 2-3 seconds.

I have six Schlage BE468 deadbolts at my rental property which I manage with the Lock User Code Manager.

This evening around 7:30pm, I first updated the device handler to 03.05.01 (not sure exactly what the previous version was, no earlier than 03.03.06), and then I updated the SmartApp to version 05.10.00 (the previous version was either 05.08.00 or 05.08.01). I followed the instructions here (https://smartthings.rboyapps.com/InstallDH.htm) and here (https://smartthings.rboyapps.com/InstallSA.htm) exactly.

About 20 minutes later, I get several notifications from the SmartThings app that too many invalid codes had been entered on one of the locks and that the keypad had been temporarily de-activated. Over the course of the next hour or so, after some frantic texting via her roommate who was away (my tenant had been locked out of her apartment with the oven on without her phone), I was able to get her back in by unlocking the door remotely for her.

After going through the notification logs to see if anything unusual had happened after the update, I decided to go back into the SmartApp configuration in the SmartThings app. It turns out that the user code in her slot had reverted back to the previous tenant’s code somehow.

The new tenant moved in yesterday, 11/20/17, and I set and tested her code on 11/19/17, so I know for sure that her code was set and working correctly. How could the lock manager have reverted to the previous tenant’s code?

One thing I noticed afterward, when I was trying to change the code in her slot back to the new code, was that I kept getting an error when I tried to press “Save” in the SmartApp. I had to try three or four times before it finally saved without an error.

I’m happy to provide logs or any other information to help troubleshoot this issue. Just let me know what you need with explicit instructions on how to get it to you.

Sounds like your ST server account was having issues, the fact that it took a couple of tries to save the settings is the prime indicator that it’s a server error. Once data is saved it’s all in the cloud and the app does not modify it, that seems to indicate data corruption on your account (not the first time on SmartThings, it’s happened before).

Another user also posted another thread about some random ST server errors with their SmartApp. Keep on eye on it. If the data continues to have issues you may want to contact ST support investigate why your account has data consistency issues.

I have got the app and using the rboy device handler with my Yale Conexsis L1. I have a routine where the hall light comes on when the door is unlocked, which works when manually unlocked or via my phone as I arrive home. It does not work with the rfid tags and no lock activity is reported in the smart hub when using them.

I will admit to being very new to SmartThings and wondered if there was a step by step,guide for configuring the app and device handler so I can get rfid reporting working correctly.

Many thanks

Some of the locks don’t transmit RFID data over Z-Wave, if you aren’t seeing any activity over the logs when using the RFID tags then your lock isn’t transmitting that information over Z-Wave.

Now all features are compatible with the stock SmartThing Z-Wave and ZigBee device handlers

Door Lock Code Multi User Management with Notifications and Actions - Version 06.00.00

  • Compatible with the new SmartThings Z-Wave and ZigBee device handlers
  • Added support for running custom actions on Manual Unlocking and Manual Locking (with delayed actions option)
  • Code based locking (and actions) now works with the stock SmartThings Z-Wave and ZigBee device handlers

Lock User Management is the most reliable and comprehensive commercial grade User Management SmartApp with many (unique) features:

  • Unlimited users and locks
  • Works with the built in SmartThings device handler (Z-Wave and ZigBee)
  • Easy and intuitive setup
  • Sure-Programming engine: verifies that programming was successful
  • Support for different types of locks (keypad, bluetooth, RFID, etc)
  • Define custom individual Unlock AND Lock actions for users such as:
    • Exit delay actions (wait for X minutes before running actions)
    • Separate actions for Keypad and Manual locking/unlocking and per door actions
    • Running routines
    • Changing modes
    • Arming/Disarming SHM
    • Turning on lights if it’s dark outside
    • Turning on/off switches
    • Define rules when to run and not run actions
    • Notifications on type of lock/unlock (manual, code, keypad, bluetooth, rfid etc)
  • Define Door Open/Close actions such as
    • Automatically relocking the door when it’s closed
    • Automatically unlocking the deadbolt if it’s extended, while door is open
    • Ringing chimes when door is opened
    • Notifications if door is left open
    • Define actions for each door separately
  • Multiple types of users such as permanent, one time, expiration (start and end date/time), scheduled (daily/weekly etc) with multiple schedules per user, presence based, mode based and many more
  • Lots of built in safety mechanisms to ensure users have a reliable experience
  • and lots more…

Some examples of how folks are using this app:

  1. I give my landlord an access code for the lock but I want it disabled when I’m at home (presence based users)
  2. When my children are at home and the parents aren’t home, then allow the babysitter’s code to work (presence based users)
  3. When we’re away, allow my neighbor’s code to work (mode based users)
  4. I can schedule a code for my nanny with multiple schedules per day (morning and evening)
  5. I can program ahead for my vacation rental properties with a start and end date/time for my guests

Copyright © RBoy Apps


Will the Schlage app also be modified to use the stock Device Handler?

If you’re referring to the Schlage Lock Alarm Mode and Sensitivity Change and Monitor here, that’s a separate SmartApp that utilizes the specific features of the Universal Enhanced Z-Wave lock device handler which aren’t provided by the stock SmartThing device handler.

However, this Lock Code User Management SmartApp is now completely functional with the new stock Device Handler thanks to the patches and upgrades incorporated by ST into the Z-Wave and ZigBee handlers.

Can you remind me what the stock one is (zwave lock or zwave lock with codes or not any of those).

The stock (default) Lock Device Handlers from SmartThings are Z-Wave Lock and ZigBee Lock

1 Like

Quick question - on the delay action setting in the door lock app. I saw a comment earlier in the thread from a few years back about anything above 20secs would cause issues. Is this still the case or can I set it 10 mins. and this will work?

also is the delay going to wait and to execute and check the do not do list of presence sensors?

1 Like

It should be okay now. No reports of any issues yet. It will check the sensor state before taking action, we did take into account while designing the delayed actions features.

thanks for quick response. I noticed when the delay action is set in the ST app notifications section the messages thread for the locking of the door itself if delay is configured does not show up, but the activity feed displays the lock command with user x right away. I assume that when the delay time is up the message thread will display the message of the door lock and any routines that are configured?

reason I am asking is if I forgot something and go back in and use the keypad to unlock those messages show up right away and presumably cancels the delay timer on the door lock keypad actions that follow the delay. ---- I can confirm it does not cancel the delay actions they will run 10 minutes after the first keypad lock action. If this is not how it supposed to work where do we report this as a bug and what info do you need from me?

I have tested this Door lock app and the Universal Device Handler with a Schlage lock with good performance.

Took a few tries but eventually paired a brand-new Kwikset 910 Traditional keypad lock, and it is using the same device handler. Then, I logged into the IDE console to check if the hub and Kwikset are talking to eachother. So far so good.

One question I have is, I am noticing fewer features on the ST app controls for the Kwikset 910 lock compared to the Schlage. I see Lock, Unlock, Auto-lock on/off, Battery %, and Audio on/off. Is this all I can expect to use or is there anything missing, e.g. Code Entry on/off, Forced/Tamper modes?

@RBoy or @maddie: Now that all features are compatible with the stock SmartThing Z-Wave Lock, would you recommend I change my Yale Assure locks away from the Universal Enhanced Z-Wave Lock to the stock Z-Wave lock DTH?


You can definitely use the new stock device handler.

Do keep in mind that the enhanced handler has some additional features like alarms, one touch locking, auto lock, tamper etc which doesn’t exist with the stock handler.

Also new locks like August Pro, Danalock v3, RFID locks etc aren’t completely supported by the stock device handler.

The biggest advantage of the stock handler is local processing.

1 Like

I started using your door lock code/lock user management app last week after using Eric Thayer’s Lock Manager. Both apps work great, but I just noticed I’m no longer getting text alerts on lock unlocking. Are text alerts a feature of your app, or EThayer’s, or both? I see the Notifications on the SmartThings notification page, but no more texts are coming in.

This morning I replaced the old dollar-store batteries with fresh Duracells on the Kwikset lock.After performing several refreshes, closing and reopening the ST app, something is not syncing with the RBoy app. So both the app and the hub dashboard are showing the battery power stuck at 30% instead of 100%.


Yes it works fine. This also supports texting multiple recipients (see instructions in app). Depends on how you’ve setup texts in SmartThings, if you’re using the address book feature or just entering the number directly. Either way try to use the E164 standard e.g. +15551235678 while saving your phone numbers otherwise ST tends to ignore them and not deliver it

how does one go about submitting bugs? line 1322, ‘def msg="…’ needs to be moved up ~6 lines, to be outside the if/then scope, otherwise sendNotifications(msg) on line 1371 (which is outside the if/then scope) is a null-text notification. Let me know if there’s a better way to send this info.