[OBSOLETE] Lock User Management (LUM)

Brent_Cameron · September 26, 2017, 7:26pm

@RBoy I have a schlage lock that is already connected to ST and I want to use your DTH and Smart App. The instructions in your smart app say:

“CLEAR CODES IMPORTANT NOTE: Please reset your lock before installing this SmartApp and follow this “Clear Codes” procedure the first time you use the SmartApp or when you install a new lock (if you see the SmartApp stuck in a loop programming codes, run this procedure to fix it):”

What does “reset your lock” mean? Do I have to unlink the lock from ST first before installing? I figure after I install the DTH I just make sure the device is using the new DTH and then install Smart App. But that reset your lock thing is confusing me.

RBoy · September 27, 2017, 12:20am

Good question, some locks support a reset procedure, it is not excluding
and re pairing. Check your manual to see if it does.

If does not, don’t worry about it, follow the rest of the Clear Codes
procedure; those steps are more important as that gives the lock and device
handler a clean slate to start.

Brent_Cameron · September 27, 2017, 9:51pm

Thanks ofr the quick response. Another quick question. I have a Schlage lock with the alarm. I want to use your “Lock Multi User Management with Unlock Notifications, Advanced Scheduling and Automatic Lock/Unlock” Smart App and it recommends using the “Universal Enhanced Z-Wave Lock” DH.

But your other Smart App “Schlage Lock Alarm Mode and Sensitivity Change and Monitor” which I also want to use requires “Schlage Z-Wave Lock with Alarm”.

Which DH should I use if I want to use both Smart Apps?

RBoy · September 29, 2017, 2:42am

They both point to the same DH, “Universal Enhanced Z-Wave Lock DH” - it’s Universal for all purposes

RBoy · October 19, 2017, 1:32am

On popular request:

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

Added two new user programming options, Mode based users and Presence based users. You can now define which users will be activated in which Modes and which Users will be activated when people arrive/leave
Simplified the User Interface
Safety check, notify user if hardware AutoLock is enabled when trying to use SmartApp AutoRelock and AutoUnlock features
Added support for mode based notifications
Added support for code expiration past midnight

Recommend use the [Universal Enhanced Z-Wave Lock] ([RELEASE] Universal Enhanced Z-Wave Lock Driver for Schlage, Yale, Kwikset, IDLock, Popp, Danalock, August Pro, Keywe, Philia, Samsung) device handler version 03.04.00 or newer for full SmartApp and automatic update notification functionality

Some examples of what users have requested:

I give my landlord an access code for the lock but I want it disabled when I’m at home (presence based users)
When my children are at home and the parents aren’t home, then allow the babysitters code to work (presence based users)
When we’re away allow my neighbours code to work (mode based users)

flyize · October 19, 2017, 8:24pm

This reminds me. I don’t seem to be able to get a third access code assigned to my lock. It’s a Kwikset lock. If I look at events, I see a ‘codeReport’ for user 1 and 2, but nothing for user 3.

RBoy · October 19, 2017, 9:28pm

This indicates that commands are being lost. (there is no difference between any number of codes, more codes = more load on z -wave network). Make sure you lock is no further than 15-20ft from the nearest Z-Wave repeater (one hub sometimes isn’t enough to create a strong Z-Wave mesh and you need atleast one Z-Wave repeater between the hub and the lock).
The Smart App will detect lost network commands and retry the commands (unless you’ve disabled that option in the SmartApp) but in the long run it’s better to have a Z-Wave repeater, just makes for a better experience and mesh (not to mention battery life).

tranman329 · October 22, 2017, 1:41pm

Is there a way to program 6 pin or 8 pin codes. I am only able to do 4 pin codes.

RBoy · October 22, 2017, 2:33pm

That depends on your lock, the app doesn’t restrict the pin length unless the lock tells it otherwise. I’m assuming you’re using a Schlage lock and you need to program the pin length on the lock. Some locks like the FE599 have fixed length of 4 digits while others like the BE469 can be programmed to accept between 4 and 8 digits. Refer to your lock manual.

flyize · October 23, 2017, 2:35pm

The lock is probably 15 feet away from the ST hub, and less than 2 feet away from some Z-Wave switches that are repeaters.

ffuentes · October 23, 2017, 2:41pm

@flyize I had the same exact issue, @RBoy told me the same thing… and my reply was similar to yours… I had to bite my tongue and buy real repeaters to see if it was true… lo and behold, I never had issues again!

flyize · October 23, 2017, 4:05pm

Is there another way to test this, short of buying something?

flyize · October 24, 2017, 12:37pm

@RBoy I just checked the Live Logging, and I’m actually seeing this:

8:34:31 AM: debug Requesting Front Door Lock to add permanent code Steveggggg to user 3, code: 557755
8:34:31 AM: debug Invalid Input: Unable to set code 3 to 557755

maddie · October 24, 2017, 1:11pm

Hi @flyize, I’m Maddie and I lead support for RBoy Apps. This message doesn’t seem to be coming from the latest SmartApp or the Device Handler code. Can you check if you’re on the latest version of the code? Drop us an eMail along with the complete logs and I’ll be happy to help you figure it out.

flyize · October 24, 2017, 8:49pm

This is my DHT version (which is where the Invalid Input error is coming from):
/*

Universal Enhanced ZigBee Lock
2017-07-23 : 1.7 - Bug fix for when lock and DTH are no longer in sync

This is my SmartApp version:
def clientVersion() {
return “05.09.00”
}

maddie · October 24, 2017, 8:54pm

That makes sense, I was looking at the Z-Wave code. I would suggest to post the question here as it’s coming from the ZigBee device handler.

flyize · November 2, 2017, 7:20pm

Just as an update @jhamstead suggested I try the (un)official SmartThings DH located here:

github.com

SmartThingsCommunity/SmartThingsPublic/blob/master/devicetypes/smartthings/zigbee-lock.src/zigbee-lock.groovy

/**
 *  ZigBee Lock
 *
 *  Copyright 2015 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 */
import physicalgraph.zigbee.zcl.DataType

metadata {
	definition (name: "ZigBee Lock", namespace: "smartthings", author: "SmartThings") {
		capability "Actuator"

This file has been truncated. show original

It seems to work without issue. However, it seems to cause an error in your smartapp:

3:16:25 PM: error java.lang.NumberFormatException: For input string: “1 changed”

I assume it should be pretty easy to replicate.

maddie · November 2, 2017, 10:35pm

This SmartApp is currently designed to work with the the official handler from SmartThings. As you can see the above handler is under development and we are in communication with SmartThings on it (and other new upcoming handlers). Once they officially release it we will release an update to the SmartApp to be compatible with the new official Handlers.

Current the SmartApp works with the following Handlers:

Official SmartThings Z-Wave handler
Universal Enhanced Z-Wave handler (for additional features)
@jhamstead ZigBee handler (pending an official release from SmartThings for a ZigBee handler)

Meanwhile for your ZigBee issue I would recommend going back to @jhamstead ZigBee handler. I assume it was working until recently so something might have changed. There are a few things you can try:

One of the existing codes are conflicting with the lock. Locks have code limitations, for e.g. Some locks do not accept codes who’s first four or six digits match the master code or programming code. Similarly No two codes can be the same, sometimes the hash values of the code conflict causing the lock to reject the code. I would suggest try a different set of codes if one or two particular codes are giving trouble.
Do a clean setup, maybe something went wrong with the database or association. Exclude the lock, reset it, reboot the hub, repair it and run the clear codes procedure listed on our website for a fresh start.

Hope this helps.

flyize · November 2, 2017, 11:39pm

I’m in contact with him and just sent him over some additional logs this morning. The problem is that he doesn’t have a Kwikset lock to test with, and I need to be able to add more codes.

In the meantime, it seems to work with the ST DH. Other than it’s clearly under pretty heavy development, is there any reason I shouldn’t use it?

mjlewis · November 8, 2017, 5:20pm

I would like my front door lock to control my Ecobee thermostat.

For example:
Door unlocked -> Ecobee changed to “Home” mode
Door locked from keypad -> Ecobee changed to “Away” mode

is there a way to do that?

I kept playing with the settings yesterday, without luck.
I am able to use the Rboy app to change the Thermostat temperature. However what I would really want is to change the Thermostat mode (Home/Away/Sleep) while leaving the temperature as it was programmed

[OBSOLETE] Lock User Management (LUM)

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

Customers

Developers

Download the SmartThings App