I was able to integrate my SmartCode™ 916 Touchscreen Electronic Deadbolt with HomeConnect™ technology to my Smartthings hub on the first try using the Kwikset sync button on the inside of the lock. My Smartthings hub is about 15 feet from the door lock. I am using the User Lock Manager v3.5 Copyright 2015 Erik Thayer to monitor & control the lock.
The door lock responds to my control commands within 1-2 seconds of touching the Unlock/Lock tile on my iPhone.
Not to dredge up an old thread, but I found this page searching for issues with my 916. I installed and programmed the lock for user PINs but after that I could not get it to pair. I tried many times but it never paired. Long story short, a second 916 arrived and it paired immediately. I assume the radio on the first was defective. Just something to consider when troubleshooting.
I’m having issues with this too. I have gone through 2 of them and neither want to connect to smartthings. Had no problems when I had a schlage or other model kwikset… I have tried it from far away and from on top of it the hub and everywhere in between but it just doesn’t find it! I’ve also tried adding it as a general device and a more specific lock…Anyone have any suggestion?
I was lucky and my Kwikset Smartcode 916 paired right away. I would contact the Kwikset technical support line and see if they can determine if there is a hardware/firmware issue with the lock series you have.
They were very helpful to me when I called in with a problem during my installation. They also remained on the line while I fired up the lock and it connected with the SmartThings Hub.
I was able to pair my SmartCode 916 lock with my SmartThings hub. It worked on the first try. The hub is about 4-6 ft from the front door. I can lock/unlock the lock. I was hoping the app would allow me to set code but it doesn’t look like it.
I wish the instructions that came with the lock were a bit clearer in how to pair. I didn’t see any information on where the pairing button was on the lock until I found this forum.
Hum… I cannot remember, but did you install the Lock Manager by @ethayer in the SmartThings developer IDE? I have this app installed and configured and it allows quite a lot of added functionality to the Kwikset 916 from within the SmartThings.
@ethayer: Next update to your code, you can add Kwikset 916 to the “Confirmed Locks” list in the readme.markdown:
Yes, I’m working on this. The instructions on the LockManager are a bit confusing. I’ve never used the SmartThings IDE and was hoping to be more of a consumer of this rather than a developer. I’ll have to see how to get it working.
It’s really not that difficult. The SmartThings Develoiers IDE allows you to cut-and-paste in the plug n play code and then do a save, publish and voila you have more functionality.
You do not have to be a developer. Just create an account, cut and paste code as a SmartThings and My Device, save, publish and it shows up in the SmartThings GUI.
I was able to pare my SmartCode 916 to my Smartthings hub 2 with no problem. My only problem with it is I don’t have full control of the lock, just lock and unlock. I have tried LockManager and all it does is lets me set the title and set mode (away, home and night). I can’t set codes, connect it with other devices or set security options.
Did you change the default device type to Z-Wave Reporting (zwave-lock.groovy)?
I had a similar issue with my 916 as well. It paired first time without an issues. Then I installed the User Lock Manager and used the Z-Wave Reporting device type. Tried to install the user codes and it would not take. I was able to lock the door from the ST app and use it in routines without issue. However it would take a very long time to report the lock status. I had to re-pair for it work correctly. I probably went a little overboard but it works as it should now. Her is what I did.
Because I did not want to write done my the smart apps that were associated with the lock, I created a simulated device with the Z-Wave Lock. Then removed what smart apps I had on the real and added them to the simulated lock. Except for User Lock Manager which I removed completely.
Exclude the lock from ST and rebooted the hub.
Factory reset the 916 and pickup in the lock instructions at the door handling steps.
I did not have to do this because my hub was close to the lock but I recommend moving the hub as close as possible to the hub.
Paired the lock with ST.
Updated the device to use the Z-Wave Reporting device type and rebooted the hub again.
Verified that the lock was reporting the correct status right away. Also made sure that I could interact with the lock via ST.
Installed the User Lock Manager and made sure that I was able to add codes and that the door worked with the codes.
Transfer the Smart Apps from the simulated device to the newly paired 916.
Removed the simulated lock.
Overkill but my lock is working as it should with the exception of the battery level status.
Hope it helps. This is a guess but I think the encryption in the lock requires the pair process to be close to the hub.
Pat
The Battery level mysteriously shows up after either a few days or a week! Not sure why, but many people have reported this strange behavior… Just keep watching for it to arrive!
I had this some problem happen to me when I had a new 2GIG controller added, and I tried switching it to Secondary to ST. Then I tried removing the 2GIG and neither controller saw the device. I couldn’t remove it either.
I even did 3 factory resets and it would not include to either controller.
Finally, I went to the 2GIG after separating it and making it Primary, and went to REMOVE DEVICE in the Toolbox, even though it claimed nothing was connected. Then as it was searching I went to the 916 and pressed A to put it in Exclude mode. This worked! The 2GIG said “DEVICE REMOVED from another network”.
Since then, I was able to re-add the 916 to ST with the 2GIG as secondary.
Hope this helps anyone with 2 controllers.
I had this issue and almost returned the lock!
I had to take the lock out of my door, reassemble it much closer to my hub. Then run the exclusion process on the lock and most importantly put the smartthings V2 hub in exclusion mode and then press the A button on the lock so as to force it to exclude itself from the hub.
And ONLY THEN, was I able to pair this lock to my hub.
I had to call kwikset to find this out. Maybe this will help others.
Open the SmartThings app that is connected to your hub.
Dashboard
Then reconnect your lock.
The exclusion tool is hidden away/hard to find.
Brad,
Thanks so much for your clear directions here.
I have one of the first 916 z-wave to market that had never been able to pair with my ST v1 or v2
I assumed maybe it was a dud.
You gave me the courage to try again and the explicit exclusion step worked like a charm!!
Yeah, chalk up a victory for the ST community. Thanks
Will
Oh my god! I literally made an account just so I could post here and thank you eternally! This worked for me.
@yurioyoko - What worked? I am having trouble getting both a 912 and a 916 to pair. I even tried going to the bathroom as @JoshFink suggested above.
Brad_Whitehead’s method worked for me:
I had to call kwikset to find this out. Maybe this will help others.
Open the SmartThings app that is connected to your hub.
Dashboard
Then reconnect your lock.
The exclusion tool is hidden away/hard to find.
For the life of me, I can’t get the 916 to pair at all. Tried every method, including the exclusion. I’ve also tried it in the locked and unlocked position. Yet, no matter what, no success. While I have other devices that work just fine, the lock thing is by far the most troublesome. I have a Kwikset 910 that I’ve tried to pair, also to no success. And that’s why I got the 916, as I looked for something that perhaps was supported better.
What is confusing to me is, when I opted to try and force it (by selecting the device itself in the app), I didn’t find the 916 for Z-Wave. Instead it lists the 916 under ZigBee. So now I’m even more confused, besides the overall frustration. I’m about to return the 916 and completely forget about the lock part as something of a myth.
If anyone has suggestions, please please please do share. I did check the post that I thought was relating to what locks are supported by ST. But there was no list. Just discussion of this or that.