Just so you know. This lock can program 250 user codes. It is limited to 20 if you use it without a Z-Wave/ZigBee module
Edit: This is correct for the Yake Keyfree lock, not the Yale Keyless. It can only program 20.
Ah, all right. Thatās good to know, but it still wonāt make managing the locks any easier.
I apologize. I gave you bad information. The keyfree lock will increase to 250 users with a Z-Wave/ZigBee module. The keyless lock is maxed at 20. All of the other Yale locks support 250 users, suprised this one is different.
Anyway, I agree with your suggestion above. Based on how I understand the code works, that may be a big undertaking.
Ah too bad, never mind. Yes, strange that the Keyless lock is limited to only 20 if the other Yale locks can have up to 250 when using the Z-Wave module.
Either way, if I could only get the disable lock functionality to work with my lock I may get away with the 20 available slots for my own purposes 
I was playing around testing the Lock Manger [Beta] app a fair bit yesterday and at some point I miraculously got it to lock/unlock, but Iāve lost count on the amount of tries I needed for this and I havenāt been able to re-create my efforts consistently. I will make another post about this when (if?) I work out whatās causing it to fail most of the time and only work occasionally.
As a side note I also got [quote=āRudiP, post:125, topic:63022ā]
error java.lang.NullPointerException: Cannot get property āidā on null object @ line 171
[/quote] in Live Logging a lot of the time, but Erik mentioned that this can be ignored.
Like I said it very well could have just been coincidence or more likely the ST type communication problem. My hub isnāt so reliable with getting everything right on the first attempt.
All I meant by update was that I tried to add a new user and associated code but the lock wouldnāt recognize the code. It was unlocked during that process. Later, when the it was licked I tried to delete/re-add that user and code and it worked.
Since it worked I didnāt try to go back and test the locked/unlocked theory just made a mental note to try the difference if I had trouble in the future.
I havenāt had any other errors with this setup, it has been quite reliable. Many thanks!
Has anyone explored core with this for notifications? The current setup always notifies me, but Iād like to customize that so that if my wife is home, or certain modes are active that it wouldnāt send the notification. That isnāt a problem with the smart app as that is the way it is designed, Iām just looking to do a bit different setup.
Erik, what would it entail to add different constraints to the notify options? Would you be willing to entertain adding that as future development with low priority? Or maybe it can be added as options in core, but I think we will lose user info doing it that way?
Thanks for this change - it should be quite useful. There seems to be a bug preventing me from selecting more than 1 person in the contact book. I took a look at your last commit and found the source of the problem:
input("recipients", "contact", title: "Send notifications to", submitOnChange: true, required: false)
Removing āsubmitOnChange: trueā from lock-user.groovy allows me to select multiple contacts. I assume the same change needs to be applied to lock-manager.groovy as well.
2 Likes
Thanks for the input, thatās not quite the solution.
Removing that is going to cause issues because thereās logic called that displays other options and values depending on what you select in the notifications screen. It also hides options that arenāt used if you select contact list items.
What youāre actually looking for is multiple: true
Iām not sure how to interface with core or if core can respond to custom location events and variables, but if it canā¦ that sounds like it could be powerful.
I can look into this, and yeah letās add it to the list of requested features.
go to https://github.com/ethayer/lock-manager/issues
add an issue and tag it as āenchancementā
I just submitted an issue for the keypad support with the code Iām currently using (slightly modified from the original pull request that I had sent for the old SmartApp).
Also, I was wondering if you had the option to prevent running a Routine if the house is already in that mode. I.E. donāt run āIām Backā when someone unlocks the door if the home is already in āHomeā mode.
Hello,
I wanted to say thank you for creating such a great smartapp. I have it up and running with my Kwikset 916 and the codes seem to be working fine. I have noticed that the ālocksā area of the app, where you would find the logs, does not populate with any data.
It says āNo lock data received yet. Requires custom driverā¦ā
I have the āzwave lock reportingā DH installed and I see the logs on the IDE. Is this a known issue? Am I missing something?
Thank you,
Danny
I created a contact for notifications. Now I need to delete that contact but cannot figure out how to do so. Some advice on how to delete a contact who is receiving notifications would be very helpful. Thanks.
I received a couple of locks from schlage over the weekend and installed one of them. Iām looking forward to adding some functionality using the added features of the touchscreen locks. Super excited, thank you Schlage!!
Please update to the most recent code. This should be fixed now.
3 Likes
Great news (and about time). Schlage owes you big time for making their locks so much more functional and fun to use! Have fun.
1 Like
Hah! I wouldnāt say they owe me anything, but itās certainly a great gesture!
I bet apps like this one drives sales of their locks at least by some measurable percentage, and by them giving me one I can play with the added features and hopefully incorporate them into the app. I know that this app sold me on buying more smart locks, so Iām sure some of you also bought in more because of it. win/win!
Also I may try harder to pronounce āShlageā correctly in the future.
1 Like
New little updateā¦ Icons through out the app because I like images and reading is for suckers [/s]. Also fixes a bug I missed when initializing new users.
/s = sarcasm
1 Like
Absolutely! I purchased my Shlage lock in large part due to the fact that there was an active developer supporting it!
1 Like
So pretty!
Erik,
Love the new Beta. Works better than the old version in my opinion. One issue I am having is the battery level will not update. It has been stuck at 80% for months and I know it is not 80%. It was this way since 4.1.4. If you can offer any suggestions it would be appreciated.
BTW I am using the Z-Wave Lock Reporting device manager.
Thanks
Try using the device handler in the current appās repo. That has the most updated version of the default device handler offered by smartthings.
z-wave lock reporting
The device handler only has a couple of added lines of code, it shouldnāt be causing your battery report issue. IF that doesnāt work or if thatās the code youāre already using, try rebooting the hub.
If THAT doesnāt work, contact SmartThings support. It really shouldnāt be caused by this app.
The new Lock Manager is awesome! Well done. Is there a means of seeing a log of whos entered and when, I assume its an alternative App? Any recommendations?
Thanks