[RELEASE] Lock User Management (LUM)

In Smartapps, select the Lock User Manager (LUM), then tap on ‘Manage Users’.
Your user list will come up.
Select (tap on) a user, then
Select (tap on) ‘Only on These Locks’.
Your list of locks will come up, for that user.
Select which lock or locks you want for that user.
The same menu choice, ‘Only on These Locks’, is given when you create a user.
HTH!

1 Like

my apologies in advance as my question may have been answered and buried deep on previous posts.

i haven’t been checking in as i used to just because this NEW SMARTHINGS APP is just so frustrating ( i do not think it works as well as the CLASSIC version) .

so i wanted to check the history of our 2 locks like i used to with CLASSIC app and i do not see it anywhere?

how do i get it back? thanks in advance. locks are both SCHLAGE BE469 @RBoy @maddie

This appears to be a duplicate post. You can check out this post for the various options available in the new SmartThings app for event and message history.

Hello, which is the best way of being informed about any smartapp or dth update?

i’ve brought this up before but i haven’t had any reply. right now, i’d have to log-in on their site and manually check and by then find out my apps and device handlers are a couple versions old.

wish they can do better job letting us subscribers know of updates. not all of us are on this forums full-time.

@RBoy @maddie

With the current platform, since it requires a manual update, this the way update notifications work for all our apps and device handlers:

  • Critical updates which requires a mandatory upgrade (security, platform changes, broken features etc), the app will notify you via a push notification within 1-7 days of the update being available (this is currently only available in rental apps like Rental Lock Automater and Lock Manager API)
  • A highly recommended update (important new features, important bug fixes etc), the app will notify you via a push notification within 1-7 days of the update being available IF you’ve enabled the Check for new version of the app option
  • Non critical updates (minor bugs, new features etc), please subscribe to our Facebook page or the community page for that app to get new release notifications
  • Minor updates (e.g. updating descriptions, code clean up etc) are announced as part of the next non critical update release notes (with the new major platform version all updates will likely be automatic)
1 Like

The smartapp has a an option to ‘Check for new versions of the app’

If / when I get notified I just go update both the smartapp and any other of the RBoy DTHs I’ve got installed. Works great.

1 Like

I have two schlage door locks Kitchen and Front door. How come im only getting push notifications on the Kitchen door and not for the Front door? Both are setup the same to send push notifications and sms. I never get sms though on both.

@RBoy @maddie

I recently changed from ADT hub to the new Aeotec hub. The Arm/Disarm functions worked great on ADT, but the STHM Arm/disarm doesn’t seem to work on the Aeotec hub. I have gotten around it with simulated switches, but has anyone else had this problem?

@RBoy Is there a way to disable the lock with mastercode notification from LUM. This is from the ID Lock 150 with Zigbee module. Every time you lock the door form the outside you receive a notification

[e357e904-e5b8-4bfe-b439-521a74b8ded4](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#e357e904-e5b8-4bfe-b439-521a74b8ded4) 21:15:08: debug Sending cached lock operation: [descriptionText:Locked, name:lock, value:locked]

[e357e904-e5b8-4bfe-b439-521a74b8ded4](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#e357e904-e5b8-4bfe-b439-521a74b8ded4) 21:15:05: debug Lock attribute report received: locked. Delaying event.

[e357e904-e5b8-4bfe-b439-521a74b8ded4](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#e357e904-e5b8-4bfe-b439-521a74b8ded4) 21:15:05: trace ZigBee DTH - Executing parseAttributeResponse() for device ID Lock Door Lock with description map:- [raw:EB800101010800003001, dni:EB80, endpoint:01, cluster:0101, size:8, attrId:0000, result:success, encoding:30, value:01, isValidForDataType:true, clusterInt:257, attrInt:0]

[e357e904-e5b8-4bfe-b439-521a74b8ded4](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#e357e904-e5b8-4bfe-b439-521a74b8ded4) 21:15:05: trace ZigBee DTH - Executing parse() for device ID Lock Door Lock

[e357e904-e5b8-4bfe-b439-521a74b8ded4](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#e357e904-e5b8-4bfe-b439-521a74b8ded4) 21:15:04: debug ZigBee DTH - parseCommandResponse() returning with result:- [[name:lock, displayed:true, isStateChange:true, data:[codeId:0, usedCode:0, codeName:Code 0, method:keypad, lockName:ID Lock Door Lock], value:locked, descriptionText:Locked , linkText:ID Lock Door Lock]]

[e357e904-e5b8-4bfe-b439-521a74b8ded4](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#e357e904-e5b8-4bfe-b439-521a74b8ded4) 21:15:04: trace ZigBee DTH - Executing DOORLOCK_RESPONSE_OPERATION_EVENT for device ID Lock Door Lock with description map:- [raw:0104 0101 01 01 0000 00 EB80 01 00 0000 20 01 0007000000FFFFFFFF00, profileId:0104, clusterId:0101, sourceEndpoint:01, destinationEndpoint:01, options:0000, messageType:00, dni:EB80, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:20, direction:01, data:[00, 07, 00, 00, 00, FF, FF, FF, FF, 00], clusterInt:257, commandInt:32]

[e357e904-e5b8-4bfe-b439-521a74b8ded4](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#e357e904-e5b8-4bfe-b439-521a74b8ded4) 21:15:04: trace ZigBee DTH - Executing parseCommandResponse() for device ID Lock Door Lock

[e357e904-e5b8-4bfe-b439-521a74b8ded4](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#e357e904-e5b8-4bfe-b439-521a74b8ded4) 21:15:04: trace ZigBee DTH - Executing parse() for device ID Lock Door Lock



[a03b25c8-820f-4220-8fed-133c782f398d](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#a03b25c8-820f-4220-8fed-133c782f398d) 21:15:04: trace Lock ID Lock Door Lock locked by Master Code, user notify true, notify count: null, user notify modes null, notify NOT present null, external notify null, external notify modes null, user override action null, Source type: via keypad

[a03b25c8-820f-4220-8fed-133c782f398d](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#a03b25c8-820f-4220-8fed-133c782f398d) 21:15:04: trace Processing ID Lock Door Lock lock actions: [name:lock, value:locked, displayName:ID Lock Door Lock, descriptionText:Locked , data:[codeId:0, codeName:Code 0, lockName:ID Lock Door Lock, method:keypad, usedCode:0], lockId:e357e904-e5b8-4bfe-b439-521a74b8ded4, lockMode:via keypad]

[a03b25c8-820f-4220-8fed-133c782f398d](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#a03b25c8-820f-4220-8fed-133c782f398d) 21:15:04: trace ID Lock Door Lock locked by user 0 via keypad

[a03b25c8-820f-4220-8fed-133c782f398d](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#a03b25c8-820f-4220-8fed-133c782f398d) 21:15:04: trace Processing ID Lock Door Lock lock event: [name:lock, value:locked, displayName:ID Lock Door Lock, descriptionText:Locked , data:{"codeId":"0","usedCode":0,"codeName":"Code 0","method":"keypad","lockName":"ID Lock Door Lock"}, lockId:e357e904-e5b8-4bfe-b439-521a74b8ded4]

[a03b25c8-820f-4220-8fed-133c782f398d](https://graph-eu01-euwest1.api.smartthings.com/ide/logs#a03b25c8-820f-4220-8fed-133c782f398d) 21:15:04: trace Lock event name lock, value locked, device ID Lock Door Lock, description Locked , data {"codeId":"0","usedCode":0,"codeName":"Code 0","method":"keypad","lockName":"ID Lock Door Lock"}

For security reasons LUM will always report master codes. Master codes should not be used for normal operation.

What you are seeing a bug with the ZigBee module firmware in how it’s reporting the manual event or an issue with how the ZigBee lock DTH is processing the manual lock event, it’s being sent to LUM as a master code being used to lock via the keypad.

So there is no way to turn of any of the mastercode notifications?

Looks like other locks also do this with zwave, but you dont map the codeid when using keypad lock for these locks in your zwave lock DH
// Kwikset and Schlage lock reporting code id as 0 when locked using the lock keypad button

I’m currently testing how the Zigbee version of the ID Lock works with LUM. It works very well so far. The only thing is the notification every time the door is locked from the outside.

You can try this ZigBee DTH instead which corrects the problem with the stock DTH: https://www.rboyapps.com/devices/Zigbee%20Lock.groovy.txt

@RBoy is there a way to Arm/Disarm STHM using the keypad on Yale Assure SL256?

Sure, we have a Yale YRD256 with Z-Wave Plus in the lab and it works just fine using these steps:

Thanks, will try with Virtual Switches.

Please excuse this question, but does anyone worry about the security risks of allowing a closed source app access to the smart lock on your house? Plus, since everything is connected to Wi-Fi I’m assuming it’s pretty trivial to determine your location/address if someone really wanted to. I’d like to purchase Rboy apps but I’m a little wary… I see this thread is at least 7 years old, so obviously people have been using it without issue for a long time.

No Im not concerned.

  1. the lock is ZWave not Wifi - you’d have to successfully bridge into the ZWave stack of the ST hub (edit: or another WiFi device also joined to my zwave network, in my case none) - no trivial task. Not impossible, but it would take a targeted attack. I don’t have anything that valuable worth that kind of effort.
  2. RBoy’s code is visible if you pay - I’ve read the whole thing.
  3. the weak point in the whole chain security wise is your SmartThings authentication - Use 2-factor auth there.
6 Likes

Ditto to what @nathancu said.

1 Like

Thank you for the explanation and putting my mind at ease.

1 Like