If you see New User was added in the log then it worked.
The problem is the Kwikset keypad with two numbers on one button. If your code is one of the first numbers on the button then it should work like 1357 or 9175. I think if you use the second number on the button then you must press the button twice.
The code button was leftover from a test I was doing I removed it from github.
Ahā¦ Okay, that make sense @bigpunk6. I wondered if it might be something like that. Does you keypad have two numbers per button?
So if I want my code to be 12345678 what I need to enter as my code in the smartapp is: 11335577. Iāll translate my code into odd numbers and give it another shot tonight.
Now, next question: Is there a way to wipe out a code? For instance, Iām thinking of writing a app that would create a temporary code for a user. For example, letās say Iāve got a repair man whoās coming between 8 and 12 on a day when Iām at work. My program idea would let me specify a day and time. At that time it would āinjectā the code. Then after the time allowed was up, it would remove the code. I could then give the repair man the code so he could get in the house during those times.
If there isnāt a way to remove the code, then I could simply over write a new code into it, but Iād prefer to wipe it out if possible.
@bigpunk6 you are awesome. We have a white hot laser on this behind the scenes right now focused on how to ensure lock status is correct and doing core codes management. Some fundamental improvements coming, and will love to work with you guys on further improving function once we have the basics nailed.
Separate question: in general, would you guys be psyched if we formalized open source and community contributions to the device handlers for all device types?
Alex,
First of all, thank you for stopping in here and giving us your time. Secondā¦ āYESā is the answer to your question. The more tools and hooks we get, the more we can bend, twist, stretch and invent things. Which in turn will help grow SmartThings for everyoneās benefit.
Again, thanks,
Twack
@alex_hawkinson,
What @wackware saidā¦ exactly. The more options the better.
Testing last night proved successful. Once I translated my code into all odd numbers and pushed it to the lock it worked perfectly.
Thanks much for your work on this.
OK, just started with Smartthings. I have the hub, 2 proximity sensors and 2 schlagge nexia locks on my mesh. I have gotten the smart apps to work for the doors to lock and unlock with the proximity sensors. Yeah!!
Now I want to be able to do the code assignments. Can someone walk me thru the process to change the device definition to the one that is listed above.
thanks.
Scott
muddled my way through and created both the device definition and the smart app. got them installed and the app works with my Schlagge Nexia lock. Success and also much happier with with Smartthings can do.
Guess it is time to write a few more apps to play with.
Thanks @alex_hawkinson
That would be great. Until then it would be nice to know when things change like a blog post or version number in the code.
I updated the app and device type to allow you to delete users and some other small things.
Iām still working on implementing the scheduling within the Lock.
I tried getting these to work with my Nexia FE599 with no luck so far. The error message I get is:
Command āusercodechangeā is not supported. Supported commands: [lock, unlock, refresh, unlockwtimeout]
I havenāt changed any of the code, though - @Scott - did you have to make changes to the code for the Schlage?
You must add that command as a custom command in the device type properties.
Instructions are in the read me on GitHub.
ahhā¦got it - I think. I had my lock associated with one hub, and now I am at a second hub and I forgot to disassociate it with the first. I reset the lock to the factory settings, but I now canāt associate with the new hub (and I am not longer near the original hub to test). I guess Iāll try resetting again or something.
@bigpunk6- Thank you so much! This was the last piece I was missing to be able to completely change over from my old z-wave system to SmartThings.
I still canāt associate the lock with the second hub. The instructions say a hard reset doesnāt unenroll from the hub. Anyone have any ideas? I donāt have access to the first hub right now.
@bigpunk6 We need more people like you around here. Instead of complaining and throwing temper tantrums while swearing to boycott all things SmartThings, you simply did something about it instead.
Hats off to you man, good work.
In the ST app open your hub settings and under zwave utility select Generial Device Exclution. Then on the Kwickset Lock press the top left button.
Then bring the hub and the lock close together and re-pair.
Is there a way to know which āusersā are already setup and what there codes are? It can be confusing to pick a user to push a code to because you arenāt sure what is already setup.
If anyone could private message me Iād like to hear about the functionality of this. I appreciate any help you can provide. Thanks for all the work.
@bigpunk6
sorry to revive an old thread but after creating the device type with the install instructions you specified, are we supposed to copy and past the code from lock.device-type.groovy that you have into the new device type code that we created?