Problem with Schlage and Hubitat

🛎️ Get Help
1

I can add PIN to the Schlage Smart deadbolt BE469 via both LCM and device setting but they have to be 4 digits. For some reason, when it is longer than 4 digits it will fail. Please help. It is very frustrating.

2

I believe you have to change the pin length in the lock first, when I installed mine I was using 4 digits and I had the same problem when I wanted 6 digit, I removed the lock from HE, then factory reset the lock, then changed it to 6 digit then added it to HE, now it works fine. Good luck and welcome to HE.

1 Like
3

If you do factory reset the lock, be sure to manually remove the default lock codes from the lock before trying to add codes with the device or LCM in HE.

1 Like
4

Thank you very much vjv. Just want to double check did you check to 6 digits PIN on the lock itself before adding it to HE?

5

Yes, do all that before adding to HE.

1 Like
6

Yes.

1 Like
7

Thank you you guys much. Will try it tonight when I get back home.

1 Like
8

I just tried Hepburn it did not seem to work. Maybe I did something wrong. Here are the steps I did. Please let me know if I did anything wrong.

  1. Exclude the lock from HE
  2. Factory reset
  3. Select all user codes
  4. Set up number of digits for PIN
  5. Add the lock to HE
  6. Went to APP
  7. LCM
  8. Set up PIN
    It did not work for me but it is possible I screwed up somewhere along the way.
9

What it's doing that doesn't work, still showing the red x after the fourth digit?

10

It says it failed (using LCM). I tried doing at the device setting on hubitat too and it does not work as well.
This time I cant set up 4 digit pin either

11

Did you check if the lock paired secure?

Screenshot_20191211-214840_Chrome
Screenshot_20191211-214840_Chrome.jpg928×446 60.9 KB

12

After the factory reset, did you manually delete all the codes from the lock? A reset restores the 2 default codes. Delete those before setting up the PIN code length. Then add the lock back to HE.

Here's what I suggest:

  1. Remove from HE
  2. Factory reset
  3. Delete all lock codes from lock
  4. Set PIN code length to 6
  5. Add lock back to HE
1 Like
13

Thank God it worked finally. I was a wink user. This is quite a learning curve and a lot of getting use to. Thank you guys!

1 Like
14

Thank you very much. Since last weekend I was trying to properly set my Schlage lock user code. I was easily able to add to HE but was not able to set any code (all failing from the device or LCM). What you have describe here fixed it right away. (Reset / delete all code / set code length to 6 ) then add to HE and manage from there.

I was going nuts !

1 Like
15

Dear all I recently have more problem with the Schlage BE469. I had enrolled the lock to my HE successfully but then it acted weird. The status of the lock was not up to date and lagged significantly. Then I decided to exclude it from the hub and start it over. While I was excluding it, the lock showed a red X which generally means it was unsuccessful. However, the lock disappeared from the HE. Since then I was not able to include it HE ever again even with factory reset. I also tried to include it back to even my Wink hub 2 (which I was working well with the Schlage lock before) but it was not successful. Seems like now it won’t work with any hub. Has anyone had similar proble before?

16

I see the following in bursts in my logs. It looks like it happens at noon and midnight and repeats once per second for one minute. It only happens with my front lock, not my back lock.

error Lock - Front groovy.lang.MissingMethodException: No signature of method: schlageBE468andBE469.scheduledPoll() is applicable for argument types: () values: [] (scheduledPoll)

Has anyone else seen this? I searched the community for that error and didn't find it.

Thanks for any suggestions

17

I have not seen anything like that sorry. I am having a problem with one of my Schlage locks myself and I still don't have solutions for it. I wish someone in this community can help you out.

18

I had some issue similar but never to the point where it would not go back to the Wink 2. However you must perform an exclusion from any of the hub even if it does not officially shown as a device on the Hub. I found a few cases in my tests where the lock would still be included even if none of the Hubs were showing it.

What seems to have been a success every time so far was a full reset, delete all codes, set code length and even the first code manually before inclusion. After that Lock Code Manager had no issue. Problem with Schlage and Hubitat

19

I'm not entirely sure how it happened, but apparently a recurring schedulePoll existed for this device. I added an unschedule() call in a temporary driver, switched drivers to run it and then switched back. The poll is gone now.

20

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.