Is it for zwave and zwave plus only?
Mine paired as a generic zigbee lock.
Just searched and found a thread saying the built in driver is for zwave and zwave plus only. No complaints with the generic zigbee driver it seems to be working flawlessly.
That’s just not true. I had a pair of BE469NX locks (still have them, in fact, in the attic in a box) that I swapped out for my BE469ZP locks, all used the built-in driver. I swapped out the BE469NX locks when I moved everything from my C-5 hub to my C-7 hub because of battery life issues. The BE469NX only pairs as S0, which uses 3x the Z-Wave packets as S2, which the BE469ZP can use on the C-7. I am seeing much longer battery life on the BE469ZP than on the BE469NX. Looks like the BE469ZP batteries will last well over a year.
Regardless of which lock, and unrelated to the driver, I had to put beaming repeaters near the locks for reliable operation.
I will correct myself, I meant it only supports zwave AND zwave plus. Mine is zigbee as stated in my post. Sorry for the confusion.
Wait until you get into your seventies, you will be in a permanent state of confusion like me.
I don’t know whether the driver supports the Zigbee version, I don’t have any Zigbee devices.
2 Likes
Yep. And it's working great. My only point with the post for @bcopeland was that it wasn't recognized as such, hence I posted the fingerprint this gave me which paired to generic before I switched it.
Hi all -
I'm having a heck of a time getting Lock Code Manager to set any codes on my second BE469 (no issues at all with another BE469). I get a failed job every time.
I've read through this entire thread and tried a few things, including a factory reset, and I am sure to delete all factory codes before proceeding.
It looks like I'm getting a good (secure) pairing:
- zwaveSecurePairingComplete: true
- deviceId: 1129
- deviceType: 1
- manufacturer: 59
- inClusters: 0x5E,0x98,0x9F,0x55,0x6C,0x8A,0x22
Everything else seems to work with the lock in Hubitat.
Here is the log from a failed attempt. Any thoughts as to what this might be?
[error] java.lang.NullPointerException: Cannot set property '1' on null object (setCode)
[debug]setCode- 1
[debug]processJobs- Front Door.setCode(1,xxxxxx,Main Code, try:10)
[debug]processJobs- try job:[836_1:[code:xxxxxx, name:Main Code, codeState:pe, retry:9]]
[warn]processJobs- job stuck:836_1={code=xxxxxx, name=Main Code, codeState=pe, retry=9}
[info]getLockCodesFromDevices- complete
[trace]getLockCodesFromDevices- device:Front Door
[debug]getLockCodesFromDevices- lockCode:1={code=xxxxxx, name=Main Code}
[trace]getLockCodesFromDevices- device:Garage Entry Door
[info]getLockCodesFromDevices- devices:[Garage Entry Door, Front Door]
Can you set codes from the device page?
I just tried that and it looks like I'm getting the same error in the log: java.lang.NullPointerException: Cannot get property '1' on null object (parse)
EDIT: Well that happened the first time. Now what I get when I attempt to set at the device is:
[warn]encryption is: true
[warn]description logging is: true
[warn]debug logging is: true
EDIT Part Deux:
Well, I have no idea why, but going through that exercise, even though it didn't seem to be working, somehow got LCM to start working with this lock as well.
Thanks!
I had this problem, and my solution was to manually remove the codes I wanted to use for the lock, manually change it to the digit number I want to use, THEN use lock Manager.
I also learned to never use position "1" on the Schlage. Always start with 2 and higher.
By manually, you mean at the lock itself? What a pain! I'll keep that in mind if it acts up again. Thanks.
1 Like
Why? I’ve never had a problem with position “1” and LCM.
No idea, but for my BE469ZP, it threw errors if I ever tried the 1 position. Maybe now it's good, but I had to manually delete codes and then start at 2 for it to be happy with the Lock Manager.
And you are SURE that there was no code in that position? I’ve got one BE469ZP with firmware 0.11.0 and one with 0.10.9 on my C-7. Never a problem. I believe you, I just never saw it.
Good question. No idea to be honest. Could have been even though I performed a "reset all user codes" etc.
When I started out, my procedure on both locks (I migrated from Wink), was: exclude from Wink, reset locks to factory defaults, include locks on Hubitat (with hub 3 ft away), manually delete both default codes at the lock (and test that they no longer worked), use Lock Code Manager to add users and codes to the locks, one lock at a time. Didn’t work if I tried to get Lock Code Manager to add both together, didn’t work unless hub was near locks.
1 Like
...was to call @672southmain up, and say to him "Hey, what the heck, when are you going to come over and set up my locks?!?"
Best way to add and program locks ever. 
1 Like
You got hot bread and pastry ready? I’m on my way.
2 Likes
I've been playing musical chairs with my 3 locks after having one replaced under warranty and eventually found a way to consistently secure-join my locks and have them work with Lock Manager:
- Exclude the lock from the the network (Extend bolt, Schlage button, 6 digit programming code, 0) and factory reset the lock (unplug battery, hold Schlage button and plug in battery).
- Delete all existing codes manually from the lock itself (Schlage->Programming code->2->enter 4 digit factory codes twice
- TURN OFF all other Z-wave devices near the hub and lock. I unplugged/cut power to/pulled the air-gap on as many devices as possible. This was more important than bringing the hub close for me.
- Pair with hub.
- Enroll in Lock Manager and ensure user codes successfully transfer
- Turn on other Z-wave devices
I was able to secure join my locks even from 20-30 ft away.
My only issue now is my main lock has a very short battery life, but I have avoided repairing Z-wave mesh.
The lock has probably gone into high force mode, which it does if it has a hard time moving the deadbolt. Only way to get out of this mode is a factory reset, which means you will have to exclude, reset, include, set lock codes up again.
2 Likes
Just following up on discussion about Schlage Connect Deadbolt Lock. Any one using this Zigbee version (BE468GBAK)?
https://www.amazon.com/Schlage-Connect-Deadbolt-Camelot-Certified/dp/B07H3NQH53/ref=sr_1_1?dchild=1&keywords=schlage+zigbee&qid=1615269418&sr=8-1
Or this one (BE479AA)?
https://www.amazon.com/Schlage-Deadbolt-Camelot-CAM-619/dp/B00YUPDW0Q/ref=sr_1_7?dchild=1&keywords=schlage+zigbee&qid=1615269418&sr=8-7
Or this (BE468GBAK)?
https://www.amazon.com.au/gp/product/B07H3BD4LS/ref=ox_sc_act_title_1?smid=A4XRJ8S0WXSO0&psc=1
Is there default Hubitat device driver for them?
