Andy Can you please look at your book for the lock on the back page. Please tell me the date of manufacture and the FW level. Thanks. I still am having no luck.
If your lock has FW 5.8 or higher it should work. It was the really early ( before 2013 ) FW that had the issues.
Eh… If they are sending a new one out I would let them. They hopefully verified the firmware information and notated that you need one with a higher firmware. It took about a year before mine failed. You’ll end up with 2 locks 
1 Like
Just got my v2 hub yesterday. Tried paring my two Schlage deadbolts. One paired immediately the other is having the same issue as AndyC. I haven’t tried a factory reset yet so that’s next on the list. Thanks for all of the great info.
I’m sorry you’re still having trouble Walter - see if the factory reset works for you - ST support suggested that too. It did work for me - I’ve checked and the lock that was giving me trouble was has a manufacture date of 7/9/2015 and FW version “MAIN_6.8”
I’m wondering if my problem had something to do with the failed pairing of this lock to my old hub when the old hub was too far away for the initial private key exchange - maybe the FW left some software crud that then made it unable to pair with a hub no matter how many exclusions I did on the old hub and the new hub - but the factory reset cleared out the crud. …“crud” is a technical term obviously 
1 Like
Doing the factory reset on the lock worked for me as well after many frustrating hours working at this. Thanks for the tip!
I’m having similar issues…had it connected to Hub v1 now trying to get connected to Hub v2 with the same security errors.
If I do the factory reset, what will be the original programming code?
Unfortunately, I have 4 of these and I think I only kept the original programming code with one of the instructions!
There should be a sticker on the backside of the lock that has the programming code(s).
+1 on the factory reset fixing pairing issues… tried 5 or so times before Google led me here. Maybe the original poster can edit their post to indicate this seems to do the trick for most people?
If the lock is an older model and has never paired, don’t waste your time trying to pair it. Contact Schlage, give then the serial number, and explain what you’re trying to do. The first many runs of these locks were flawed from a hardware perspective. As others have said - Schlage has bee great about making this right.
On a personal story note, I got the BE469 a few years ago so my wife could go out running without having to bring a key along. That turned out to be my gateway to HA. I was exploring Wink, MiCasaVerde, and others over the past couple years… finally I settled on Smartthings. Despite the various issues, I’m glad I chose this system.
TLDR: if you see “This lock failed to complete the network security key exchange…" unregister and reset lock and perform the registration process holding the hub NEXT to the lock (< 1ft).
After 3 aggrevating hours Schlage support could resolve the connection issue for me. I had tried everything above (factory reset / add-remove cycles / etc). The closest I could get was the “This lock failed to complete the network security key exchange…" error message but the lock status in the iPhone app was always ‘unknown’. For me the problem was that the 4ft that the lock and hub were apart during registration were too far.
I retried the procedure while holding the hub right next to the lock and suddenly it worked and I was able to control the lock via the app. According to the support rep the secure key exchange requires much closer proximity of the device to the hub than normal registration. So any secure device should be registered before being installed.
Hope this saves somebody some time but I guess people only end up here after having spent countless hours unsuccessfully …
old thread… but…had the same issue. putting the lock within an inch of the hub during pairing solved this issue. I did run it through general exclusion 3 times prior… just for good measure.
++1 on factory reset, fixed my pairing issue as well.
Factory reset on what, the lock or ST hub?
I have over 30 devices, I’m not going to reset my hub and reprogram my whole house for one lock. It would be easier to just buy another brand of lock.
Factory reset on the lock only. Not the hub.
Thank you Kevin for the clarification and a quick response.
I was having a problem with a lock that was working just fine. I even had it 2 inches from the hub and tried multiple times to pare and kept getting the same message. I went and bought a new lock and I’m a still having the same issue.
Hi Daniel,
It only happened to me once. The lock was working fine for two or so months and it stopped working one day. That was when I found this thread. I did a factory reset on the lock and pair again. I have also done device exclusion on Smartthings app a couple of times too before factory resetting the lock and pair again.
Luckily, it has been working since that time (May 23, 2017 till today Dec 21 ,2017)
Kelvin,
I worked with Dominic at ST support and he gave me a solution that worked on the first attempt. He had me pull the air gaps on all my z-wave switches than pair the lock to the hub. The lock paired and the security key went through right away.
The problem was that I had so many switches that the lock was jumping on the mesh network and that was preventing the security key from being established. I have so much going on in my system that even when I had the lock 3" away from the hub the SK couldn’t reach the hub.
Thanks for you assistance. Hope you have a blessed Christmas and New Year.
This worked for me too! Thanks.