Conclusion Currently, no single door lock natively supports both HomeKey and Z-Wave or Zigbee in one model. The Schlage Encode Plus (HomeKey, Wi-Fi) and Yale Assure Lock 2 (HomeKey with Wi-Fi or separate Z-Wave/Zigbee versions) are the closest contenders, but you must choose one protocol per lock. For a hybrid solution, consider a smart home hub to unify control across these ecosystems. If you find a lock claiming dual support, double-check the specs—marketing can be misleading! Let me know if you want deeper research into specific models or integration setups.
I guess I'll stick with the Kwikset 914 that arrives from Amazon today.
I installed a Schlage BE469ZP a year ago. I struggled with pairing as, when following HE's recomendation, to not use security I learned later you must pair with security. So bear that in mind. I also had proximity to the hub issues for pairing which I resolved with a long ethernet cord.
I bought Schlage so I could key all the house locks to the same key. So that was nice and DIY Schlage re-keying is pretty easy (lots of kits available).
I do not find the dead bolt motor very strong however. In fact I've had to tweak the fit of the strike plate a couple times so the deadbolt closes under a very light turn. I even chamfered the edge of the deadbolt for better self alignment but the motor isn't strong enough to overcome much misalignment on an exterior door with weather striping. In the end the deadbolt needs smooth actuation by hand or the motor will simply try to close twice and then abandon and stay unlocked after that.
Yes I am sure but this warning is a tad off putting.
......"This device supports S2 security. Most devices do not need security and will generally perform better without security. Typically this is only needed for security devices like locks, keypads, etc."...
If, as you state, S2 isn't a concern why the unnecessary drama about enabling S2 security??
The early days of S2 were pretty rocky, so I'll bet anything that advisory is a remnant left over from that period.
S2 offers advantages beyond just security (e.g. better error-checking). I've been using S2 for all my ZW devices for years now - I've never had an issue due to it.
Yes exactly, and I have strongly recommended they take that warning out completely. I got a compromise which was they added the info about locks in there. Before it just said not to use security (period), which is probably the issue @CuriousB had. It came up multiple times on the forums after people were banging their heads against the wall for days.
Why not two messages depending on the security modes of the device being paired?
......"This device supports S2 security. While not essential, S2 security provides enhanced security and better transport reliability but adds X, Y and Z (things that are undesirable about S2, added overhead??)."...
......"This device supports S0 security. Most devices do not need security and will generally perform better without S0 security. Some devices, however, such as locks and keypad must have security enabled.”…
I think a message indicating that security is required/S2 recommended for locks/garage door openers is still a good idea. Mainly to help keep people out of trouble by choosing no security during pairing, since in some cases the S2 key is hard to find on a door lock or other device you've already installed, and choosing no security during pairing could be taken as an easy/lazy way out.
Or they just look at the info from the device as its pairing and force security for the ones it should be applicable for, then only give the option for the rest. Even more fool proof that way. Then the message could just say something to the effect that based on the device type security is required. For other devices no message would be needed.
Here's a quick update on my Hubitat <=> Schlage BE469ZP touchpad malfunction (freezing) debug testing.
When I first installed the new Schlage BE469ZP and configured it into my Hubitat LCM and other Hubitat apps/rules, the BE469 touchpad started to malfunction almost immediately, even after the door lock was power reset. I had the touchpad malfunction at least 3 times within 24 hours. A factory reset of the new BE469ZP and then reconnecting to my C-8 still had the touchpad malfunction.
As I mentioned previously in this thread, I was wondering if the touchpad malfunction could possibly be related to connecting the door lock to my Hubitat C-8. Maybe connecting the Schlage to the Hubitat is causing the Schlage door lock to "crash" in some way that causes the touchpad to stop working - possibly through Hubitat status update communications, Lock Code Manager, or Rules.
To debug, I did another factory reset of the BE469ZP, but this time I did not connect it to my Hubitat at all.
It has now been about 48 hours, and the touchpad hasn't failed at all. So, there might be a problem with connecting the Schlage to Hubitat that is causing the touchpad to lockup.
My next debugging step: I will now pair the BE469ZP to my Hubitat C-8, but not do any further configuration. The door lock will just be providing status to the Hubitat, and nothing more. If the touchpad starts to lock up in this configuration, it will provide some information on to what might be causing the problem ...
I think that the cable is not a likely contributor.
I haven't touched that cable at all (or any other hardware other than the battery pack) since the original installation, but I am already seeing differences in operation by disconnecting from the Hubitat hub.
When I reconnected my Schlage BE469ZP deadbolts to my C-8 hub, they started acting flakey again, and it started happening almost immediately. The touchpads locked up even more frequently after I added functionality like Lock Code Manager to the mix. At one point, one of my Schlage deadbolts froze in a manner where the green checkmark was always lit, and the keypad backlight also stayed lit. The touchpad was also dead again. The only way I could get the deadbolt out of this state was to pull the battery.
I am now 99% sure that connecting a Schlage BE469ZP to my Hubitat C-8 hub can (but, not necessarily will) cause the touchpad to randomly freeze. I don't know if it is because of a firmware problem with the C-8, a firmware problem with the BE469ZP, or because of a misconfiguration or miscommunication of some sort between the lock and the hub. Nothing obvious is apparent in the C-8 device logs.
Since it is a LOT easier for me to do something about a system misconfiguration than it is for me to do something about firmware or miscommunication, I figured I would wipe my hub and device configurations for my next debugging analysis.
So, I have taken the following steps:
I deleted all Hubitat Built-In Apps, Rules, and Notifications for all my Z-Wave devices.
I have removed ("Excluded") all my Z-Wave devices from my hub, avoiding a Forced Removal wherever possible.
I performed a Factory Reset of all my Z-Wave devices.
I deleted all of the "Factory Default" 4-digit access codes on each BE469ZP (I did this so that I wouldn't confuse LCM with the "???" factory codes when LCM is reinstalled later).
I re-paired each Z-Wave device to my C-8, only enabling Security on the BE469ZP deadbolts.
I enabled Hub Mesh on all the Z-Wave devices.
I reinstalled the Hubitat Lock Code Manager app.
I readded all my User Codes in LCM.
I recreated all my Z-Wave device Rules and Notifications.
I now have a clean slate for my C-8 Hub configuration, and for all my Z-Wave devices - especially the Schlage BE469ZP Deadbolts.
I will update y'all again in a few hours ... or a few days ... whenever the next interesting thingy happens.
