# Schlage Camelot worked perfectly for almost 2 months now not

**URL:** <https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090>\
**Category:** Devices & Integrations\
**Created:** [February 24, 2017, 1:38pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090 "2017-02-24T13:38:53Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rhizzlebop](https://avatars.discourse-cdn.com/v4/letter/r/ecb155/32.png) [@Rhizzlebop](https://community.smartthings.com/u/Rhizzlebop)\
**Post date:** [February 24, 2017, 1:38pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090/1 "2017-02-24T13:38:53Z")

</div>

Suddenly, for no good reason, my Schlage connect no longer responds to app commands.

It still somewhat updates “Recently” but its hit or miss. However, if it shows locked status, I tap in smart things to unlock and it just tries and tries and doesn’t unlock. Same the opposite way.

I tried doing the “Replace” feature, but the instructions I found said it would spin a few minutes trying to find the device to replace, however it never finds anything.

I havn’t tried a force remove yet because I’ve got to find a long data cable because I think it’ll require me dragging my hub closer to reconnect it.

I did replace batteries (which were at 99%) and now they show 100% so it still somewhat is talking to the app. Does that seem odd?

When I first installed the lock, I connected it up and took it near my ST hub to do setup, then put it in the door.

Now, its acting up so I’ve got to find a long data cord to try and “remove” and reinstall it. I can’t understand why it worked perfectly for almost 2 months and now it is still somewhat alive in smart things, because the “Recently” history partially updates but I can’t control it from there.

Note: my front door is only about 15 feet and 1 wall away from the hub so I am not thinking its a signal strength issue. I’ve not changed or added anything in the system in 3 weeks.

Help appreciated.

---

<div class="post-metadata">

**Author:** ![RLDreams](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/rldreams/32/18109_2.png) [@RLDreams](https://community.smartthings.com/u/RLDreams)\
**Post date:** [February 24, 2017, 2:40pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090/2 "2017-02-24T14:40:07Z")

</div>

Starting another new thread posting the same question is not going to change the answers. If the lock is not working it is a connection issue. Improve your mesh and/or bring the hub next to the door and reset/reconnect it. If it was still showing 99% battery level after 2 months it was not reporting battery level properly so it not connected properly.

---

<div class="post-metadata">

**Author:** ![Rhizzlebop](https://avatars.discourse-cdn.com/v4/letter/r/ecb155/32.png) [@Rhizzlebop](https://community.smartthings.com/u/Rhizzlebop)\
**Post date:** [February 24, 2017, 3:36pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090/3 "2017-02-24T15:36:40Z")

</div>

Good info on the battery. I had no baseline to know if that was or wash not normal battery usage.

I started a new thread because I figured the other subject line was a diff topic and old news and figured noone was going in there to see.

Thanks. I’m gonna try and fight through a reset this weekend. I know little about this stuff other fighting through initial setup with accurate step by step instructions

---

<div class="post-metadata">

**Author:** ![RLDreams](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/rldreams/32/18109_2.png) [@RLDreams](https://community.smartthings.com/u/RLDreams)\
**Post date:** [February 24, 2017, 4:01pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090/4 "2017-02-24T16:01:32Z")

</div>

I have had these locks for going on 3 years with 3 different hub systems. They are rock solid, but a real PIA to get included properly because of the security protocols. Other than the rare actual physical failure of the lock it always comes back to signal strength and full proper inclusion.  
The best way to reset the locks is 1 do a general ZW exclusion through app and enter the command code into lock. Then do a full factory reset of the lock from the lock keypad. ( make sure you have record of command code, it is on the sticker inside battery compartment if you lose it )  
Have Erik or Rboys app and device handler installed. Grab extension cord or batteries and a LAN cable long enough to reach the door and start from scratch. Make sure you lock, unlock the lock a few times with the app once inclusion is done while hub is still within 3 feet of the lock. If is doesn’t respond IMMEDIATELY and show the proper state in app. I do mean immediately there should not be any delay or spinning wheel while it thinks about locking/unlocking. If any delay at all go back to step one reset the lock and start over.

---

<div class="post-metadata">

**Author:** ![Rhizzlebop](https://avatars.discourse-cdn.com/v4/letter/r/ecb155/32.png) [@Rhizzlebop](https://community.smartthings.com/u/Rhizzlebop)\
**Post date:** [February 24, 2017, 8:11pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090/5 "2017-02-24T20:11:30Z")

</div>

Ok, thanks for the tip.  
For the two months it worked, there was always about a 4 second delay of the lock responding to app command. I figured that was normal as I had no baseline.

Thanks, I’ll try it this weekend.

---

<div class="post-metadata">

**Author:** ![DParker](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/dparker/32/29993_2.png) [@DParker](https://community.smartthings.com/u/DParker)\
**Post date:** [February 24, 2017, 8:18pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090/6 "2017-02-24T20:18:06Z")

</div>

> [@RLDreams](#):
>
> If it was still showing 99% battery level after 2 months it was not reporting battery level properly so it not connected properly.

I’ve had mine installed for at least that much time now (connecting to ST was a breeze) and it vacillates back and forth between reporting 97% and 99% (but never 98%, oddly enough). But then again we’ve only used the motor to unlock the door maybe once every 2 or 3 weeks on average.

---

<div class="post-metadata">

**Author:** ![Rhizzlebop](https://avatars.discourse-cdn.com/v4/letter/r/ecb155/32.png) [@Rhizzlebop](https://community.smartthings.com/u/Rhizzlebop)\
**Post date:** [February 24, 2017, 8:58pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090/7 "2017-02-24T20:58:09Z")

</div>

So, I’m currently working through this link.

> [@\[Depricated\] Lock Code Manager](https://community.smartthings.com/t/lock-code-manager/12280):
>
> There’s a new app! Please go to [this thread](https://community.smartthings.com/t/release-lock-manager/63022/) for the new Lock Manager App, which is in active development. ##Legacy App: This app is no longer being maintained. Support and bug fixes are no longer being provided. Welcome to Lock Manager! Now with custom device type! Use the attached device type zwave-lock.groovy for added functionality. Minimal changes to SmartThings code. More reliable code set/delete. Codes will be reconciled on each poll() event. App will function without custom device type, but not as well. Features: Assign Codes to Multiple Users. Manage Multiple Locks. See what codes are active. See how many times a code is used (reset usage manually) Be notified when a user uses their code. Delete codes after they are used\*. Optionally Schedule Users so that they only have ac…

I have no idea what I’m doing except following steps.

I went through the first part “How to…install app”  
Went smoothly I think.

I went through the second part “How to add device handler”  
Went ok …I think…after I google the github thing from erik as that link didn’t seem to work.  
On step 4 it first says to paste in the same GITHUB code I copied above. seems odd because that was called an app, and this section is called a device handler. But the bullet under it said if it was a schlage lock to go to that other link,so I went to that other link, and it was a HUGE long piece of code, with paragraphs at the top talking about changing id lists and such. I changed NOTHING and copied that huge piece of code in as it said and saved and published. (I did NOT copy in the GITHUB thing.). Not sure if thats the problem or not.

On the third part, “Change the lock device handler” things went a little sideways.  
When I went to my devices, there are NO devices setup. It brings me to a form wanting me to enter name, label, and zigbee ID, and all sort of stuff.

I don’t know what I’m supposed to do here, or why it thinks a device is there, and there isn’t. I dont see any extra instructions for when there isn’t a device handler to change.

---

<div class="post-metadata">

**Author:** ![RLDreams](https://yyz2.discourse-cdn.com/smartthings/user_avatar/community.smartthings.com/rldreams/32/18109_2.png) [@RLDreams](https://community.smartthings.com/u/RLDreams)\
**Post date:** [February 24, 2017, 10:13pm UTC](https://community.smartthings.com/t/schlage-camelot-worked-perfectly-for-almost-2-months-now-not/79090/8 "2017-02-24T22:13:56Z")

</div>

> [@Rhizzlebop](#):
>
> So, I’m currently working through this link.

That is the old version. You should update to his new updated app and DTH

> [@\[OBSOLETE\] Lock Manager](https://community.smartthings.com/t/lock-manager-beta/63022?source_topic_id=12280):
>
> Lock Manager Incomplete List of features: Manage user codes on locks. Manage Keypads. Review and manage active lock codes. Set lock access based on schedules. Receive notifications when a user used their code. Run Hello Home phrases based on lock/unlock events. Manage Hello Home phrases based on keypad inputs. This app works using 3 child apps and 1 parent app. It is recommended that you install all 4 apps, however if you do not use keypad devices, it is not required to install the keypad child app. Note: If upgrading from any beta version, it is required to uninstall the app completely before installing. The architecture of this app has changed in a way that is incompatible with previous versions. How To Install User guide has old information. There is now only one app to insta…
