Schlage Camelot Pairing Issues

I got that part. What I’m saying is that neither your internet service nor any WiFi/ethernet based communication have anything to do with the connection between your hub and your Schlage lock.

When you say you “have the hub right next to the door”, just how close are we talking? An inch? 6 inches? A foot? Something else? And in your earlier post you say you’ve “Gone thru many many batteries.” How many times have you changed batteries, and over what time period in total? I’ve had a Schlage Connect for well over a year now, and have only replaced the batteries once (although I rarely use the motor to open/close the lock).

Also, you said “Called schlage and since it wasn’t their app wouldn’t help.” Which app are you referring to? We’re simply talking about getting the lock to pair/connect with/to the ST hub, and they should certainly help with problems with that bit of advertised functionality, given how central it is to the product.

I didn’t realize the internet strength was unrelated to the hub. So thanks for clarifying that. As for batteries, it stopped doing the auto lock after i kept trying to connect the lock with the hub. I read that strong batteries are key to get the key transfer, sp i would change them. Probably about 6 months ago, it was working great and, yes the batteries lasted long then. As for the schlege cs, they were the first ones to tell me to get a fresh set of batteries for the lock to get the key transfer to work. But once the lock was working well, he told me that they do not provide support for other apps like smartthings and working relationships for individual problems.

Smatthings hub is touching the lock.

I’d call back and explain that helping you get the lock to connect…and stay connected…to your hub has nothing to do with supporting anybody’s app. It has to do with supporting the functionality of the Schlage product you paid for.

The only thing I would add from my experiences is you MUST learn how to implement a strong mesh network for the devices you are attempting to use. IMHO the easiest and probably most cost effective is to deploy Iris plugs with both zwave and zigbee.

Once you properly setup a mesh network, device dropouts will not be an issue.

1 Like

When I first installed my locks they were eating through batteries very quickly. That stopped after installing beaming switches/dimmers in close proximity of the locks and re-paring them. @Redfam60 mentioned having to change batteries often so that might be an indication of poor connectivity between the hub and the lock…

On a side note, I have 3 of these locks and they are literally dreadful to pair. I believe I did most of what @SteveWhite suggested except turning off the HEM in my main electrical panel. ST has told me more than once that my network is too busy likely causing the issues I am having.

On another note, Schlage just released the ZWAVE PLUS version which I am hoping has improved on this. I am tempted to replace one of my 3 locks with a new one to see if it is any better… other users on this forum did not seem to notice any major benefit so I am undecided.

1 Like

Arufell,

I was extremely lucky as I set this up at our second home near Yellowstone, many thousands of miles away. I have been back twice since the initial installation of both the Schlage lock and smarthings deployment and have not had any issues with the lock. Batteries till at 98% per the app, though the lock has been used relatively infrequently by friends. Snow drifts in front of that door are now an issue haha, and will be adding another Schlage lock to the covered/protected door. The lock has been invaluable for allowing and monitoring contractors, family and friends to access the property.

I initially had issues with some other sensors dropping offline but not the lock, and on my most recent trip out installed a half dozen Iris and monoprice plugs in a more thoughtful manner, repaired the networks.

I have had only one other unrelated issue which i plan to address by adding a wifi plug for the Smarthings Hub so that I can power cycle the Hub if needed.

I have all my equipment on an APC rack PDU that allows remote control of the outlets. A nice feature is that you can tell it to cut power to an outlet, wait a few seconds, and restore power so that you can also reboot networking equipment that might cause you to lose connection.

My locks have been solid since so no complaints. At times it appears they take a super long time to report their status but every time I start testing to see what the issue is, they behave. The delayed reports are evident as I have an announcement that states the entry point status (open/close/locked/unlocked).

I have a similar issue with manual unlock and code unlock events. It seems that they sometimes fail to report. Which is frustrating because I use the events to disarm SHM (on a delay). But it seems like it resolves itself when I try to observe the failure in real time. At one point it seemed like “touching” (opening and re-saving) the smart app that handles my keycodes, etc, was enough to make it behave again, but it may have been that simply opening the ST app and opening the Device was correcting it… I never saw a consistent rhyme or reason to it, and it’s still driving me crazy. I believe my mesh is strong (z-wave outlets and switches throughout the house in close proximity), and my locks have no problem responding to commands.

1 Like

Thanks for the suggestion re the APC rack

I found an older version of this for cheap on eBay:

Works great. CyberPower has a nice one too but still pricey:

https://www.amazon.com/CyberPower-PDU81001-Switched-Metered-Rackmount/dp/B06XMR4BZF

Ok. Finally got thru to schlege and they are sending me another lock. (Thanks for suggesting calling them again and stating the smartthings app was the only reason i purchased this lock). Now, so i don’t have problems again, i do have a zwave ge plug right near the door, is there anything else i should do to make it work correct the first time?

I factory reset mine before attempting the first join as a matter of course… Other than that sounds like you are on a good track…

2 Likes

I’ll just agree with @nathancu’s suggestion.

I will reiterate, learn how to setup a strong mesh network. IMHO, one ge zwave plug does NOT create a strong mesh network.

I want to do this right, so to set up a strong mesh network what else do i need.? I have comcast internet and then 3 google wifi access points which show a strong mesh network, plus in my smartthings app i have 2 of those ge zwave plus plugs, numerous other devices like moisture sensor and lights along with amazon Alexa which sl have been working fine, not like the schlege Lock.

Your Internet service provider and your wifi have NOTHING to do with your zigbee and zwave mesh.

I would suggest this link as a start, take your time and digest the information. There’s a lot of information in these forums. Search, read and digest. The only reason I stress this is I overlooked this initially.

It is a long thread and addresses locks, aND devices you mentioned that DO NOT participate in your mesh network. Read slowly and thoroughly!

1 Like

It’s been many years (3 +) since people were having issues with these Schlage locks and they still have not improved the firmware?

I remember when I first got mine - it took me couple weeks to make it stable. And dummy me removed the device by accident from ST. Was lazy for a few months to work on it (knowing what is waiting for me) but the day has come.

The idiotic thing would not pair. Followed every single advice her and dozen other threads. The lock, and the hub seemed to talk to each other because: after hit the programing code and 0, hub front LED (of course I have the hub budding the lock) starts flashing rapid (green) for a few seconds and then it goes solid. But the app (classic) doesn’t recognize any devices nor I can see anything in the live log. The lock also confirms that it was paired, with single beep and 3 green flashes.

Most idiotic thing ever.

EDIT: Just went out and bought brand new lock from a local store as I need this working asap - guess what. Same f****** result. Lock confirms pairing but Smartthings app says no device founds. This the most f**** frustrating sh1* ever. Hub is next lock, touching it. Tried with all other Z-wave devices on or off (turned of circuit breakers in the whole house and powered smartthings V2 hub and internet modem of my UPS).

EDIT2: Installed the new ST app. For some weird reason, it had two locations in it. It was probably something that happened when accounts were migrated as I had non active ST account with same email as the Samsung account.The ghost location had dozens of “unknown devices” (only visible thru the new app). After clean up, I still can’t get the ST app to acknowledge the lock was added. The lock it self still says it was associated with Z-Wave network (confirmed by flashing alarm light when power to lock is restored).

The amount of frustration (I am IT specialist) with this multi-year issue and lack of any work on ST to resolve it urges my desire to grab a hammer.

Edit 3:
Spoke with ST support - they have no idea. I also found out that the hub even is different from live logging. The hub even shows ZWJOIN. They are escalating to tier 2.

EDIT 4 and SOLUTION: Tier 2 support came back advising that a custom DTH is preventing successful inclusion. Deleted an old DTH by @RBoy that I was not even using previously and it included perfectly fine. It’s weird that I did not see this advice anywhere so if some one can added to the Schlage FAQ - please do!

UGH!! I am stuck and not sure where to go. I’m in the process of setting up my new house with our devices. We’ve added a new Schlage to the mix and the activity feed says "Universal Z-Wave Lock with Alarms for Schlage, Yale and Kwickset (Lock is securely included) but I can’t find the dang device anywhere. I see my old Schlage which we did not remove from the hub before moving (that’s a whole 'nuther thing in itself) but can not find this new lock. Where is it hiding? I’m still using the classic app and a 1st gen hub. Can anyone help???

I believe you have the same problem as I did (just added solution above) - a @RBoy DTH was preventing successful inclusion. That’s judging by the word “Universal”.

1 Like