Just to clarify the lock is working fine with the hub aside from the lock info error. The hub is probably 4 feet away. I’m still having problems with the lock info though.
Here is my log when I Refresh Lock Data looks like their might be an error?
a1778b71-a6f7-46f6-8401-c62402817830 6:20:47 PM: debug "zw device: 03, command: 9881, payload: 00 62 03 FF 00 00 FE FE " parsed to ['name':'lock', 'value':'locked', 'isStateChange':false, 'displayed':false, 'linkText':'Z-Wave Schlage Touchscreen Lock', 'descriptionText':Z-Wave Schlage Touchscreen Lock lock is locked]
51ebaf6d-60c0-43a0-a9c4-1a4718d09d7d 6:20:44 PM: debug sendCodes fix is: [["code1",""]] Error: 1/10
a1778b71-a6f7-46f6-8401-c62402817830 6:20:45 PM: debug code1 remains unchanged.
a1778b71-a6f7-46f6-8401-c62402817830 6:20:45 PM: debug updateCodes called with: '[["code1",""]]'
a1778b71-a6f7-46f6-8401-c62402817830 6:20:44 PM: debug poll is sending ['9881006202']Check the pull requests in the GitHub repo. I sent a PR to fix the lock info issue. It’s a simple fix.
F**k yeah! I was trying to debug why codes wasn’t getting set and you are totally right, assigning to state instead of atomicState fixed the issue. You rock.
Sweet! Glad I could help. Now if we can only figure out why lock codes are lost when the batteries are pulled that would be awesome. Hell I wouldn’t mind forking this and help keep it up to date if we could figure that out.
Hello,
I followed the procedure until getting the app into MY APPS. Unfortunately, once I open it up and need to select a lock. It says “there are no devices of this capability”.
I have a Kwikset 916 deadbolt. Does that mean it is not supported?
thanks for the help!
Sounds like you need to check what device handler your lock is set to. What is it set as? It should be z-wave lock or z-wave lock reporting
What do you mean by change codes, disable codes and then re add them?
So for example I had 3 codes, slot 1, 2 and 3.
Slot 1 was the only code active, this is the one I “lost” use of. Meaning I can still use that same code just not in that slot, no matter what I put in that slot, the system will not unlock with that code.
So I just shifted everything down by one. So now I am using 4 codes 1: empty, 2: Active, 3-4: Disabled.
How did you get to regain use of that “lost” slot?
Have you tried deleting codes from the lock itself?
Replace the codes with different codes, then disable them. Then go back and add the codes you want into the lock. That will place the codes correctly back into the lock
The 916’s do no store the codes directly on the lock when codes are set remotely. Its stored on the z wave module.
So if the hub goes down,the Internet is acting up the lock or there is a power outage the code does not work?
edit:
This post talks about codes getting “sent down” so they must be stored on it.
and the manual talks about deleting codes from the keypad
Disclaimer. I haven’t read that post but I know that they’re not stored in the same manner that manual lock codes are stored. I have a lot of these locks installed at an apartment community and spoke to the VP of engineering at Kwikset regarding this because the lock codes were being lost when the batteries were pulled. Turns out it was this app causing that loss during battery removal. That’s why I say these codes aren’t stored on the lock but on the module. To my understanding they’re stored on the module when being programmed remotely. Give it a try, pull the module and see if your codes work.
I haven’t tried to do it but I’m not sure deleting the codes manually would work if they’re stored on the module.
That post is not exactly correct either. The codes are set immediately there’s no “sent down” other than the hub setting the codes on the module. it’s the subsequent codes that need some time in between each store to get stored on the locks module. when you’re dealing with a few codes there aren’t issues but when you deal with 7,8,9+ and set them for hundreds of locks you’ll notice this app misses a few here and there and you have to go back and hit “Done” on the app.
The big misconception with the 916’s and possibly others is that the remotely programmed codes are stored in the same manner as the manual codes and as far as the 916’s go it’s not necessarily true and I imagine it’s due to security concerns.
I use kwikset 912…I programmed them from the keypad…and use smartthings to lock and unlock them. The codes have never been lost during battery changes, and using the code at the door works even when the Internet is down or power is out.
Correct. That does not occur when internet is down since its stored on the z-wave module. However, with this app (I’m not sure what version you are on) the codes started getting lost on battery changes.
I do know SmartThings made changes that may have affected this smart app. Rboy’s smart app and device handler do not have this problem.
Did you mean 916? Also if you programmed them from the lock you hard coded them into the lock. There’s no issue with battery changes there on the 916.
@desertblade to answer your question. Yes the codes work if the hub goes offline. They’re stored on the module, the lock doesn’t look to the hub to give lock/unlock commands based on what code is entered.
If they were worried about security they would ditch the smartkey and add a master code to the locks. Looks like out of the box anyone can add a code by just pressing the “program” button on the back.
the manual states:
“It is recommended that you add and delete all user codes through your Z-Wave or ZigBee control system. If your system does not allow this, the following sections will provide instructions for how to add and delete codes at the lock.”
Sounds like you should still be able to delete from the keypad. I would still give it a shot, trying to delete the code from the lock.
I have a Schlage and had a similar issue. Deleting the code from the lock cleared up the issue.
Edit:
This doesn’t surprise me, networking/zwave/queues with hundreds of commands a few would get lost. I don’t think zwave has a try again, but with lock code manager on certain events it resends them so they should get set.
Deleting them from the app is essentially the same thing. It’ll remove the remotely programmed code and it really is the way you should do it. You’re going to come across issues deleting from the lock and then trying to set it via the app. It’s not guaranteed to fix the issue. For example, I just deleted my code via the lock, the events show the deletion but unless I change the code in that slot to an entirely different code via the app the code is not getting set again because the app still has that code in the settings and it hasn’t changed. Which really makes you have to do an extra step by erasing manually.
If you just override the code with a different code your issue is fixed and then can go and set it again. That’s the only way I’ve been able to get this lock manager to fix lost codes when the batteries were pulled. Just disabling them does not work. They need to be overridden with a new code. You don’t need to pull out the Allen key and open up the lock on the 916.