To add to the above, the source code for Hubitat's built-in BE469 driver (and almost all of the built-in drivers...did you come from SmartThings, by chance? ) is not public, so no community member will be able to modify it, nor will you be able to "customize" it.
However, if you have a specific problem you're trying to solve (e.g., the above is good advice if your lock doesn't seem to report physical state changes back to the hub), someone can probably suggest something that will help.
I agree with Ashok. I have two BE469ZP locks on my C-7 running 2.2.3.148, and they are rock solid. However, to get to that point, I had to use April Brandt’s (@april.brandt) insistence to put beaming repeaters (I use the Ring Extender 2 devices because they have internal battery backup, but have also used Aeotec Range Extender 7 devices, and they work well, too) by each of the locks and the hub. Rock solid.
Sorta = it'll lock, unlock and report that it unlocked and locked. but wont' tell me what code was used or a code id, doesn't look like I can add/edit them using zwave either.
Is there a better driver to use? or is this the best one for me.
Also,
is there a way for Rules 4.0 to know if it was a physical unlock or digital (code), I'd like unlocking my door dawn/dusk via code to turn on my foyer lights. right now it'll turn them on even if I'm inside unlocking the door.
I don’t understand. Are you using the built-in Lock Code Manager? Did you do as the LCM documentation and these forums instruct? (Delete all codes, including the two default codes, from the lock, then add users and codes using LCM?)
Don’t know what you are looking for, but the events show fine for me (also in logs).
Thanks, I think I have it. I'm going to call it lack of sleep and the fact that I just paired 15 Zooz switches. I can't believe I didn't see the drive matches the lock...without the color code.
Hey, I am switching from SmartThings to Hubitat C7 running 2.2.5.131 and I was adding my Schlage BE469ZP (firm. ver. 0.10.9). They show up as S2 Access Control, which is cool and secured, but are never added as devices and stay like that:
Yes. You may think you have added them, but it’s a bad pairing (“ghost node”), indicated by empty in, out clusters.
First thing you have to do is get rid of the ghost node. Remove the battery connector (can’t remove if hub can still ping the device). Then hit repair until remove button comes up, then remove.
Then shut down hub (settings, shutdown) to red light. Then remove power from hub at wall (not at micro USB, which is fragile and can break solder joints at PC board). Leave power off 30 seconds, then power on, boot To green light. This is the only way to reboot the Z-Wave radio.
Then reset the BE469ZP to factory defaults, start pairing over. You will need a long ethernet cable, have hub within a few feet of lock during pairing. You are correct to use S2 pairing.
Unrelated to this, yes, you will need a beaming Z-Wave repeater near the lock to make it work reliably with Hubitat. I use the Ring Alarm Extender v2, which has battery backup and can also give you power fail events so you can shut the hub down cleanly on power fail.
Oh, and welcome to the Hubitat community. Post back if difficulty, someone will help.
Thanks all for the feedback.
I didn't remove the ghost device (yet - just saw the procedure above), but I used the pairing within few inches with a long ethernet cable.
The device paired as a "Device" with "S2 Access Control" Yeah!
Control works with Hub within few feet, further it is lost => So, beamer repeater mandatory, and I'll remove the ghost device.
Thanks all. I was worried I couldn't transfer my 3 deadbolts.
Love this Hubitat, reactive, reliable... Thanks.
Glad you were able to get it going. My two BE469ZP Schlage locks work fine with the beaming repeaters. I believe that the Hubitat antennas don't have as much gain as the Wink and SmartThings antennas. I just shrug my shoulders and got the beaming repeaters, and it works reliably, which is all that I care about.
My BE469ZP seemed to install easily. The hub within 5 feet and the Aeotec Range Extender 6 within 10 feet. I am using the 469 driver. In the app, I have to double-tap the lock or unlock buttons to get it to lock or unlock.
I have the BE469ZP and have come here looking for the driver. I can't seem to find it anywhere. I do see pic where you guys installed it but I don't the the code anywhere please help
It is a built-in driver. Just use the drop-down menu to add the driver. I have 2, they work fine but require a beaming repeater near each lock because the locks are FLiRS. I use Ring Alarm Extender Gen 2, which have the added benefit that they have an internal backup battery and can give power fail alerts so you can cleanly shut down your hub (on a UPS, of course) with an appropriate rule.
Out of desperation I ordered the range extenders and then thought what the heck. Guessing that the new code I set prior z-wave connection was position 3 (there are 2 by default). I entered the pin code for position 3. I then entered 4 for set code length. Clicked set Code Length. Clicked set code and waited a few minutes. Pressed the unlock button and it works just fine. However it requires two presses of the lock button for it to lock. The front door is maybe 25' from the hub and 10' from the closest z-wave smart switch. There really needs to be better support from Hubitat. The initial installation process and related videos are poor at best. Nothing on the specific Schlage locks. There was a lot of back and forth between the videos and web interface as well as the phone app. Had to reboot repeatedly to get most stuff to connect and work. This was most of the online complaints and I must agree. I would not recommend it to anyone not already very familiar with the product.
You are supposed to do a factory reset before including these, otherwise the previous codes are still there and a new hub cannot read the old codes. You can delete the old codes, and add them right back in and it should fix this.
I have been on both sides of this, these locks working great, and these locks having issues. There are many threads about these locks on this forum, and it sounds like you may have read some of them. Some research will reveal that staff are aware of the issues, and they are not likely to support these in the future. In short, they cannot guarantee these will work consistently with Hubitat so they are not supported. Staff were nice enough to leave the driver in place though, so if someone wants to attempt to use these locks, go for it.
There is a Reliable Locks app that some have used that seems to make these work better and not have to press lock twice. Might be worth a try? [Release] Reliable Locks
I am not sure what you are asking for? You want them to say "don't use Schlage" in their videos? Or show how to use a lock that they don't recommend using?
That is fairly normal for most things I think. With most hubs it is fairly normal to add a few devices, and need to reboot. Or you should be doing that at least. Even with Windows you have to repeatedly reboot upon initial setup or upon adding new drivers and devices.
As Neonturbo has mentioned, many of us have been on journey's with Shlage.
I'm now in a very, very good place with my BE469ZP and Hubitat, they have been rock solid, but I also made sure I have multiple repeaters between my hub and doors, I don't use lock code encryption, and I let my mesh settle for a good 4 days.
They've now been running solid for over a year, and even replacing one defective from Schlage (battery issue) is working great,
) is not public, so no community member will be able to modify it, nor will you be able to "customize" it.
