Wondering what locks work with LCM. I'm new to Hubitat. I had a Schlage BE469 lock and I linked it to hubitat. It linked fine and hubitat see the lock status. I'm installed LCM and it was able to see that the Schlage codes that were already in the lock. Brought them in as named Code1 and Code2. I'm not able to LCM to succesfully download any new naes/codes to the lock. Wondering if others have had success with a particular brand/model of lock.
That is the exact lock I have (Z-Wave Plus model--not sure if they gave the new ZigBee one the same model number) and Lock Code Manager works perfectly. I did go into the lock itself and delete the two existing/default codes, but since I think it's supposed to allow up to 30, you're probably not hitting any limits or anything there, so that shouldn't matter.
Two things I can think of: first, did Lock Code Manager actually save your settings? In Hubitat apps that contain dynamic pages, it's easy for me to click too fast and not actually have things saved that I think should have been there. (If you don't see any "Existing users" listed in the app, you'd know.) Second, does the lock otherwise work OK for you in terms of sending/receiving Z-Wave commands? If it's far from the hub and you don't have any repeaters--ideally ones nearby that support beaming (check their spec sheets on the ZigBee Alliance webpage if you aren't sure), which will keep sending messages to battery-powered devices like this until they wake up and receive them--you may just need to address that.
1 Like
I wasn’t aware Schlage was shipping the 469 in a ZWave plus version. Even their website only shows the non-plus model. Do you have the part number or UPC? I have two within their return windows and would love to exchange them.
It’s always a good idea to factory reset the lock and delete codes in the device (driver) page after pairing. The BE469 is a tough one to use with Hubitat right now. If you can get it to pair securely you should probably run out and buy some lottery tickets.
1 Like
Sorry! You're right. I misremebered mine as Plus and figured it was new enough that it was. It isn't, and if they do make one, I can't find it either. 
I paired mine well before the secure thing went awry. Mine works great with LCM. I did factory reset before I implemented it with lcm. I don't plan on any changes. I did see a post that someone actually figured out why it wasn't pairing and posted it. I believe they were slightly bitter about it, but all the same. I hope it's been communicated to the developers.
It started working. I was able to download users and codes successfully multiple times. This happened after setting up a dashboard to control the lock. At first the dashboard would not control the lock. Then it started working for no apparent reason. After this i tried LCM and it as working flawlessly. A few hours later I attempted to setup some new users and it's not working. Either is lock control tile on the dashboard. Although Hubitat can still read the lock status. I'm needing something with more reliability as I need to send lock codes remotely for an AirBNB home.
I'm not saying this is your problem, but I do recommend reading this thread (on the ST Community forum, but the same thing should apply to any Z-Wave network, including Hubitat) about Z-Wave locks, specifically the benefit of "beaming" repeaters, written by the knowledgeable user JDRoberts: FAQ: why would I need another beaming repeater if my zwave lock is already close to my hub? - FAQ - SmartThings Community
He also wrote a post in a thread specifically about AirBnB and this lock that may be worth reading too (not that anything he writes isn't).
I think most people find this lock to be pretty reliable, aside from recent difficulties in getting it to pair. I have one and love it, but I don't change codes very often (and usually unlock with the code, not Z-Wave) and so make minimal use of Z-Wave besides status reporting. But if what you're experiencing is a Z-Wave issue, it's likely to appear with any lock...except, I guess, the ZigBee model.
Well damn... Got my hopes up for nothing. 
That was my post, at least the one about the devs understanding the issue. I hope I didn't come across as too bitter. lol
IMHO you had every right to be a bit bitter. And mentally exhausted. I commented a request to reach out to the developers with your findings so that your pain would be worth it.
I appreciate the help. If there's a bug in any system I typically find it. When I was on the Iris v2 Beta I experienced and reported a lot of issues nobody else ever noticed. But those locks are a sore subject for me and probbaly why I sounded a bit irritated over the matter. I have four of them total, the two oldest go back to 2015. I was having issues with the older ones not being able to set codes, or suffering delays of 30+ seconds when controlling those 2 locks in SmartThings for a very, very long time. ST support was very dismissive of the issue as being mesh related and kept suggesting adding more beaming devices. Ugh...
I finally got escalation on the issue and a developer to look into the issue. Turns out both locks were flooding the network with garbage data at a rate of about 10 messases per second over 10-20 seconds, which explained the lag. Those locks were running v6.8 firmware. Schlage support told me the locks could not be upgraded, and was not willing to offer any out of warranty replacements.
So $400 and two locks later, I was able to set codes and get response times of around seconds on all locks, but had to throw out 2 otherwise usable locks. Now, those same 2 locks, only a couple months old, won't pair with Hubitat no matter how many times I try, well North of 50 attempts at this point.
It should not be this hard.
I can see no reason why Hubitat would not be responsive to you handing them the information that they need to fix it. At leas that's what I looked like to me. But, I'm just a girl with no super powers.
1 Like
