That is great news!!! Before I delete it… is there a handler to replace the @RBoy one now? I think I paid for that (and the garage door opener one) and was hoping to use it again and transfer the settings over to the new lock.
Make a copy of it. I suspect after inclusion, you might be able to re-add the custom one and change the devices settings to it.
Any tips on how to do that? I installed it such a long time ago, I feel like an utter newb again.
Find the DTH in the IDE under “My Device Handlers”, edit - select all the code, copy and paste it into a text file/email or whatever back up you prefer.
Note: you may need to select your location after logging into ST IDE.
Thanks! Guess I’ll be trying that today!
616fun I need your help I’m having the same issues with pairing? Did you unplug your pocket sockets?
I deleted the handler and I was able to pair my lock finally. Thank you!!
Schlage recently released a Zwave Plus version of the Camelot lock. I am guessing that should improve things. You still have to have a robust zwave plus backbone (don’t care if they say zwave is totally backwards compatible, you still do not get 100% of the benefit if you have a mix) so beaming devices, longer range, faster speed, network wide inclusion, etc make things smoother. I was surprised to hear that NWI was turned off on the ST hub until recently (maybe just temporarily? not sure). Anyway, the previous non plus versions could not be upgraded so whatever bugs were on the lock when you purchased it, could not be corrected therefore I was not surprised with having super frustrating issues adding my 3 locks to ST v3 recently. Now that the zwave plus locks are out, I wonder whether it is still frustrating or things got better…
I suspect that many of the posts I read on people having issues, were new users with poor zwave mesh networks so they were dealing with the inherent difficulty of including Schlage locks, along with all the issues that arise with a poor mesh network.
There are several posts on this forum that give tips on how to increase your chances of a successful pairing so I won’t open that can of worms 
Some of the DTH’s being used appear to be from a few years ago. It’s highly recommended to keep the DTH current as it’s updated periodically to keep it in line with the latest ST platform and firmware changes / updates.
For example the latest DTH update is required for changes made in the 25.x hub firmware release
For anyone having trouble while pairing devices when using custom DTH’s, read this FAQ. There’s an issue with that platform when unused DTH’s are marked as “stale” and can prevent successful pairing. Republishing the unused DTH or deleting unused DTH’s is the fix. This article explains it more detail:
@Heather_A FYR, this should solve your custom DTH issue which was preventing the pairing from completing. Just republish your DTH and remove any old unused ones.
Any suggestions on why my lock isn’t showing up in the app? I’ve gone through most of the steps in this thread except relocating the smart hub (currently about 15ft, direct LOS).
The schlage connect excludes fine, always saying a device has been deleted even if I try to exclude it 5-6 times…
When I try to pair, I get a green check mark from the lock, but the app does not recognize the device and instead just keeps spinning / searching.
any custom device handlers? If yes, try opening them in IDE and Publish for Me again. Then exclude again and try to pair.
I would of never figured that out. Thank you. That fixed the problem.
Range appeared fine, which I suspected because it would exclude no problem. But from the discussion here, I was uncertain if it was a security key exchange problem when trying to pair.
I’m not sure why I was getting a green check mark but the device wasn’t showing up in the app.
Publishing my device handlers fixex this on the first try. (I did every handler I had, although perhaps only the lock’s specific one was necessary?)
I am not exactly sure. I generally tell folks to Publish for Me with the device handler specific to the device. But I have seen others say you need to publish for me with all device handlers. Here is a thread with more details on the stale device handler condition for anyone curious.
thank you so much!
Thank you! Waiting and checking for an unassigned lock was the key. Even though the lock displayed the red X the lock showed up in the smartthings app eventually.