I've finished migrating everything over from ST to HE except for 2 Schlage BE468 door locks and door contact sensors (Using RBoy also).
From what I'm finding, the BE468 model is just very problematic, at best, on HE (and NONE of the Schlage locks are even officially supported).
So....if I decided to replace the locks entirely, I'm looking for recommendations for an alternate. I really want something that is either fully supported or is at least known to work VERY well (even though not officially supported?).
No preference for Zigbee or ZW. Currently have mixture of both. TIA!
As long as your locks have above the 7.10 firmware they should be fine. Factory reset them before pairing and pair them within 3 feet of the hub. (There is a low power whisper that goes on during pairing for security). Also before pairing, make sure there are no ghosts in your z-wave details page. I have 3 of these locks and they all work excellently. The main reason for removing from the offical list is because of older firmware and some of the older locks are 300 series z-wave which can have a problem connecting to the 700 series chip.
468 and 469 use the same guts, just different styles. Driver is native to hubitat. Follow my instructions above and you should be good. If you have a failed pairing STOP! Check your z-wave details page for ghosts and remove. Reset the lock again. (ghosts are bad. They will be shown by not having anything in the routing column)
I've used both and I prefer Zigbee - it's easier to pair and very quick to respond. Battery life might better on Z-Wave. Definitely try @rlithgow1's suggestion first though.
Yep, stuck right now getting the ST app to successfully delete the lock. It tries for about 30 sec and then gives me this message:
"The device wasn't deleted. Try following the manufacturer's instructions again, or force delete the device".
Not sure if I want to use the 'force delete' option or not.
Using the Delete option in the ST IDE, it ends with this error:
Object of class [physicalgraph.app.EventSubscription] with identifier [058a97be-4c57-49a0-b6f9-b91a6746d2c8]: optimistic locking failed; nested exception is org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [physicalgraph.app.EventSubscription#058a97be-4c57-49a0-b6f9-b91a6746d2c8]
Okay...I've got 1 of the locks now paired with the HE hub.
Now...going through process of trying to actually setup codes and such. Supposed to use the LCM, right? Gotta say, after using the RBoy app in ST, the LCM is pretty clunky. Having trouble right now just getting a single code entry made. And where are all the various lock options???
[EDIT]
Finally able to get a single code working...but what a total PITA. LCM needs a lot of work, IMHO. Only way I could even do this was by manually deleting all codes on the lock using the keypad and also manually changing the PIN length. Then had HE discover what was on the lock...then rename it. Pretty sad.
That is the way the locks work, not just on this hub. You have to delete the old codes to work with codes in a new hub. Maybe it is for security, I don't know.
This is a known issue with these locks, not LCM.. That said, LCM does what it does. It's good for multiple locks but for single locks, just use the device page. I have 3 locks and LCM works just fine. Put in a name, then a code and push it to all the locks and wait about a minute or 2 and it's done.
That's one of the only things I miss from ST - RBoys lock app. Was very handy..
I have Yale and Kwikset locks and use LCM - they work fine in a set and forget kind of way. Would love to have more definable user schedules.. like "every other monday" etc.
I'm not sure where it stands at this point. I think there has been interest but the details like how the developer can get paid and still fit within HE's terms of service / vision is one issue. Don't know if there are any others.
I have a 469 lock with firmware 6.8. Works fine with RBoy and ST. Is it possible to update to 7,.1, or am I destined to a painful or failed transition to Hubitat?
Schlage doesn’t provide firmware so no way to upgrade it. I had one on v6.8 and it worked ok for a long while on HE. Moved a bunch of things over to Zigbee as I was retiring all non Zwave Plus and decided to replace that lock with a Schlage Zigbee lock.
I moved away from August lock and many mechanical and electronic issues.. Went to Alfred Lock and haven't looked back . I have the DB2 lock and it works great with the Z wave controller.
