That would be cool! I do have a door sensor that I could reinstall and probably set up a routine to lock the door after it closes too.
My battery life seems to be good. Iāve had the lock for 4 years and have probably changed the batteries once (maybe twice). I only used it with nexia for about 2 years before I cancelled. The keypad is unlocked usually 2-4 times per day.
1 Like
Edit: Sorry mixed up the posts.
As Erik said you may need a repeater.
Also thereās a potential bug in the latest hub firmware which causes beamable devices to lose one way communication with the hub. The symptom is that the lock will not respond to the hub commands but the lock can update status with the hub. So hub ā lock failed communication where as lock ā hub works or vice versa.
The solution is to exclude and repair the lock. Iāll post the link to the other thread where this is being discussed.
1 Like
Iāll address the lock code state āunknownā in the next release of this app too.
The next release will remove locks from the main app and ālocksā will be itās own child-app where it will store the info on locks then. Iāll add an option to poll a lock when it is closed and after N amount of seconds after an unlock to try to catch faulty reports.
āLock at specific timeā app will also become part of lock manager with this change, with added features in the future.
This is a big change in the architecture of the app, so this release may take some time, though Iām hoping this will be a V1 of the app. It MAY BE DATA BREAKING so, users might have to re-install the app on the next version, though Iām hoping to avoid this.
3 Likes
Thanks Erik.
My hub is about 6ā away from my front door. It is my only lock that I have at this point. I will check on the secure inclusion. I did not notice that. I have removed multiple times, done multiple zwave repairs and one factory default on the lock.
Thanks, it sounds like mine is reverse. I CAN lock/unlock from the app. I DONāT get status updates. Although yesterday I checked it and one time it showed to be locked which was the first time. I unlocked it and locked it again and status did not update. I will look at that link
just for fun, try with different batteries too. Sounds like a huge pain, but this device doesnāt seem to be behaving properly at all!!
Well, I had not put cover on so done. And what do you know - it worked! I did the whole process so not sure what did it. Remove device, repair network, replace batteries, factory default, and add back in. Immediately it reported correct status and codes were pushed and worked. I did get two unknown statusās but after issuing the lock or unlock it updated. This occurred during direct device interaction in ST App. Log implied it was a jam but it appeared to lock properly.
Thanks again for everyoneās help!
I donāt suppose you would consider a schedule of āevery otherā. As in every other Thursdayā¦
Doubt there is a great need for it but I figured I would ask. Setting one up for the maids and I cannot afford them every weekā¦ 
Hello everyone! I just got a brand new Kwikset 916 and set it up with this version of Lock Manager (just literally set it all up tonight, so itās all 100% up to date). Unfortunately, Iām having the same problem as @Keuka15 with the codes not burning appropriately. Was there ever any progress on that? Iām not seeing it in this thread, but figured Iād ask.
Does the usage increment when someone uses a code? I donāt have this problem but I also donāt have a 916.
No, it does not. I see 0s for all codes, even though Iāve used each of them several times (even the non-burner ones). I do get the Notifications like āsoAndSo Unlocked Front Doorā and the guest one says āGuest unlocked front door. Burning codeā or something similar.
Iām kind of going to blame ST for this one. Iām not sure whats going on but I tried to trouble shoot this for awhile last night. Mine wasnāt working either. I was getting a weird IDE log error that made no sense and I was just banging on the hammer so to speak.
I uninstalled the app completely and then installed it again and it worked. !?!?
I am currently have two Schlage Z Wave locks setup in my home (Schlage BE469)
Everything works well except when you go to Lock Manager, under Locks section. The first locks shows all the info (eg: passcode, name, and number of entries). However, the 2nd lock says āNo lock data received yet. Requires custom device driver, will be populated on next poll eventā. Is this normal?
Thanks.
Could be a bugā¦ Maybe you forgot to put the custom device on the 2nd lock?
Iām working on refactoring all of this, so Iām not going to go troubleshoot itā¦ all the code is going to be different very shortly!.. And this problem should go away (new code wonāt even require custom lock handler)
2 Likes
Thanks for the quick reply.
I did chose device type as āZ-Wave Lock Reportingā for both locks.
Iāll wait for the new code from you and give them a try.
Thanks.
I finally got around to installing this new Lock Manager. Itās so much nicer that the original SmartApp, I can finally only have one instance of Lock Manager installed! A few things Iāve noticed so far;
-
I could not figure out how to only get a notification if a single user code was used/enabled/disabled. I have a scheduled dog walker code that I would like to get a push notification when it is used/enabled/disabled but currently when I turn it on in that user I get notifications for all users.
-
The Keypad delay is not working properly. It looks like youāre running the desired routine immediately after the code is entered and then only using the delay for the SHM status change. You ideally would apply the delay to all actions. The flow would be Arm Keypad -> Send āsetExitDelayā command to keypad -> Wait for ādelayā seconds -> Run desired routine and change SHM status.
1 Like
Is there somewhere i can see the battery percentage for my Schlage 469?
This is usually found on the device handler page in the āThingsā list.
My Home (bottom nav) > Things (top nav) > then click on the NAME of your device.
As you can see, my battery isnāt posting very good values.
Thank you so much