[OBSOLETE] Lock User Management (LUM)

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

@simonselmer

I found out that the lock only takes 2 codes, a master code and a 2nd “service code”.
In your app, the 1st user is the master code, so that user1 will overwrite the mastercode.
The 2nd user will be the “service code”.
And then there are now more users in the lock, which is at least why I couldn’t get my 3rd test user to work.

That’s correct IDlock only allows for 2 keypad codes, master and service which correspond to User 1 and User 2 in the SmartApp.
However do note that the RFID codes are also reported by the lock, while they can’t be programmed by the SmartApp it can report on it. So if you enter say User 3 information and then use a RFID key which is programmed to RFID user 3 it will show up on the SmartApp notifications. Do note that RFID has user 1 and so does the master code (keypad user 1), Similarly RFID user 2 and service code (keypad user 2). But since the App can only accept 1 one name for user 1 and 2 you will get a notification like Lock unlocked by User Name (as written in smart app) via Keypad or RFID (depending up on the source). So if you’re using RFID keys I would start programming at User 3 to avoid this issue OR you can install this separate app to get notification/take actions for the RFID users.

[RELEASE] Lock User Unlock/Lock Door Notifications and Actions

User Unlock/Lock Door Notifications and Actions This is a Lock Manager for locks which cannot be programmed through SmartThings but can report events through Z-Wave/ZigBee to SmartThings. It provides functionality of managing actions and notifications when users unlock door and lock doors but with using the existing codes programmed into the lock. (i.e. no lock programming). However, while this app replicates all the functionality of the Lock User Management (LUM) app, related to taking actions and notifications for users, it does not program the lock codes but rather uses the locks existing programmed users. This is great for folks who don’t want to expose their user codes through the ST platform, don’t want/change the codes often, cannot program codes remotely (e.g. RFID cards, FOB’s, …

The above SmartApp is identical to this SmartApp except it doesn’t program codes. So you can use this SmartApp to program you keypad master/services codes and the above SmartApp to manage your RFID users. That way you have no conflict and can use the full range of the locks’ capabilities.
Alternative if you want just one app use this app and start your RFID codes at User 3 (just note that it can’t be programmed from the SmartApp and I would set the type to inactive for the RFID uesrs (3 and beyond) otherwise the SmartApp will keep trying to program the lock and the lock won’t respond).

@simonselmer

some people recommended using the locks own autolock, and not rely on smartthings to do it.

This is true to some extent because of ST’s less than perfect scheduler and z-wave network issues the lock based auto lock is more reliable. However the downside is that you can’t coordinate with door sensors which the SmartApp can do (e…g don’t autolock while door is open etc).