Schlage BE468 Compatibility

mattw · March 10, 2018, 10:31pm

I’m trying to move over a Schlage BE468 from SmartThings. Unfortunately I’m having some issues with getting it paired. In Discover Devices it’s detected and initialized/included and I’m able to set a name, but the pairing never completes on the lock. It continues flashing and eventually times out with an error. No commands work and status’ are never received. It shows up in Z-Wave devices as alive. The status check on the lock says it’s not paired.

I thought it might be a distance issue with the lock not receiving the configuration so I got a long ethernet cord and set up the hub less than a foot away. Tried the process again and had the same issue. Tried to pair it back to SmartThings and worked no problem.

I confirmed there’s no issues with the exclusion from SmartThings or not being in inclusion mode while trying to join to Hubitat.

Seems like there’s some differences even within models. keltymd1 was able to get a slightly different BE469 paired in this thread. @coreylista had the same model with a different fingerprint which seems like the same issue I’m having. @coreylista do you know if the fix made it into any of the previous updates?

Thanks!

NoWon · March 12, 2018, 10:40am

I have two BE469 and had no problems switching them to Hubitat.
just to be clear to remove the lock from SmartThings

while SmartThings was in Zwave exclusion mode
you did press the schlage word on the outside of the door and
then typed in the programming code from the sticker on the back of the manual followed by a zero

correct?

After unpairing from SmartThings I also removed the battery connector and then put it back.

Then did steps 2 and 3 while Hubitat was in pairing mode

I didn’t do a full factory reset and I didn’t have to move my hub closer it was upstairs

you could also try doing a zwave repair and then reboot the hub

mattw · March 12, 2018, 2:59pm

Good to know, seems like the BE469 models have been working,

Yep, the first time I didn’t disconnect/reconnect the battery to check the pairing status LED in the back cover since it showed the green checkmark after exclusion. The second time I decided to check every step and after pairing back to SmartThings, I verified the LED flashed when connecting power. Then excluded from SmartThings, verified it didn’t flash. Included to Hubitat, which timed out again during inclusion and doesn’t flash when disconnecting/reconnecting power. I also tried to let it sit on the Discover Devices page after it initialized until it timed out. It doesn’t seem like there’s a factory reset function. The closest thing I found was to reset all lock codes, which I tried as well.

Thanks, I’ll try the Z-Wave repair tonight and see if that has any affect. Unfortunately I have a feeling something needs to be modified on Hubitat’s side though.

mattw · March 13, 2018, 12:55am

I tried the process of including it again and had the same result. I also tried Z-Wave repair without any success. On another note, ST platform is down right now so I can’t add the lock back to ST, ha!

I had live logging open during the whole process and saw no logs that had anything to do with the lock. There’s no Z-Wave log either so I really can’t gather any further debug data.

Here’s some info from pairing:

Manufacturer:003BProduct Name:Generic Z-Wave LockModel Number:Unknown Part NumberdeviceTypeId:16
deviceType: 25417
inClusters: 0x22,0x72,0x7A,0x98,0x86
deviceId: 20548
manufacturer: 59

Hopefully Hubitat support can help me track down the issue or have a fix in sight. I’m not in any rush to get it moved over since it’s working fine on ST for now (once the platform is back up) but I’d like to avoid issues like this

coreylista · March 13, 2018, 1:05am

I apologize for not getting to this today. It will be first on my list to work on tomorrow.

mattw · March 13, 2018, 1:09am

No problem, thanks Corey!

EdwardN · March 13, 2018, 2:47am

Don’t wait too long. Some guy on the ST forums got locked out of his own house by the smartthings outage because his car was in the shop and he didn’t grab the presence sensors out of it to open his garage.

ritchierich · March 13, 2018, 2:54am

I cannot even imagine that situation. Crazy

mattw · March 13, 2018, 3:02am

I did see that post in the other thread. Luckily the unlock codes still work and if all else fails, the ol’ trusty physcial key I think we all know to have a backup in place, but that is really unfortunate timing.

cuboy29 · March 13, 2018, 3:05am

Too much automation is never a good thing. All my locks have code and them pesky physical keys.

coreylista · March 13, 2018, 8:50pm

I was able to replicate the issue today and it should be fixed with the next firmware update. Apologies for the issue!

mattw · March 13, 2018, 10:14pm

Nice! Looking forward to the next update! Thanks for taking time to replicate it and get a fix in queue

mattw · March 15, 2018, 11:40pm

@coreylista I just updated to 703 and was able to pair the lock! I got the red x on the first few tries but eventually was recognized and paired successfully. Thanks again for getting this into the update!

gtamberlane · March 21, 2018, 6:01pm

Long time ST user and new Hubitat owner. I’ve migrated (almost) everything over to Hubitat and I am proud to say all my lights, thermostats, etc. are working well. I paired my ST hub as a secondary controller to provide home control via the ST app (so my wife doesn’t need to change a thing on her end - this also allows me to use the ZWN 7 Button Controller without porting the code as well as Z Wave thermostats of which I have a few).

However, I cannot seem to pair my Schlage Connect Door Lock (model: BE469NX, firmware: MAIN_7.1). Many, many Hubitat pairing attempts, factory resets, etc. - all end with the lock declining the pairing by flashing a red X.

I’ve also tried including via ST (which worked before my transition), but now that ST is a secondary hub I get strange behavior. Occasionally ST will discover the lock, though the lock had flashed a red X during pairing. When this occurs ST cannot control the lock and I get an error message in the app saying something like “the node has failed the security handshake… if you cannot control, you may need to remove and re-add the node”.

I have also tried using an Aeotec Z Wave stick I happened to have lying around, paired as a secondary hub and plugged into my laptop. Using the Zensys tool to pair the lock, I always get a green checkmark on the lock to indicate successful programming and the lock shows up in Hubitat as dead and shows in ST with the same error message as above - still unable to control.

Currently on Hubitat version 1.0.3.705 and looking for any help from the bright minds in this community.

mattw · March 21, 2018, 6:23pm

How far away is the lock from the hub? During any of the pairing attempts with Hubitat, does it detect the lock and show up on the Discover Devices page? If so, it could be an issue with it exchanging the security key and needs to be closer so it’s within “whisper distance” (from what I’ve read).

When I did get my lock paired sucessfully, an additional entry in the device data was added:

zwaveSecurePairingComplete: true

It’s possible it’s a different variation of the BE469 or different a firmware version. The first thing to try to rule out would be distance by moving the hub closer.

gtamberlane · March 21, 2018, 7:02pm

@mattw thanks for the suggestion and what to look out for. It’s painful trying to pair this at all - it seems that Hubitat will discover the lock once for every 15 minutes of attempts. Of the two times in the last 30 minutes the lock was actually discovered - one time Hubitat froze and the lock never even showed up in the zwave node list; the second time, I checked the device data and no zwaveSecurePairingComplete entry was found.
I will probably try at various times today and tomorrow to see if it comes up, but as of yet no luck.

As for distance, Hubitat is currently resting against the lock - i don’t think i can get it any closer than that.

gtamberlane · March 21, 2018, 8:19pm

I hate to say this, but I tried the close contact pairing with ST and it worked. Since it’s a secondary hub my lock now shows up and works in Hubitat.

I don’t know if it’s a hardware or software issue, but certainly something for the Hubitat team to look into. Adding things to the network is kind of a critical piece to the home automation puzzle and should work at least as good as the platform we are trying to move away from.

Thanks again for your suggestions @mattw

cjrad63 · March 21, 2018, 9:00pm

I was having problems getting a Schlage BE469 to pair. I read somewhere that bluetooth could interfere with Zwave. When I turned Bluetooth off on my phone, I was able to get the lock paired. Not sure if it was luck or turning off bluetooth, but I got it to pair

gtamberlane · March 23, 2018, 2:42am

Well, I was getting terrible reliability with the locks added via ST so I decided to reset the zwave network and start with the locks from a clean implementation.

Lo and behold, my locks pair perfectly every time. My guess is that having secondary controllers in the network somehow interferes with the pairing of certain devices.

Now everything works… almost.
I have rule set up to turn off a switch when my lock is locked which works fine. The reverse, however, does not. I can verify the rule is setup properly as it will fire when I press the refresh action on the lock. However, checking the logs, Hubitat does not seem to receive an “unlocked” value change when the lock is unlocked.

There is an entry that says the lock was unlocked using code 1, but no state change. I could write a custom device code that does it I suppose or just port one from ST, but wondering if this is odd behavior with the default Zwave Lock device code.

EdwardN · March 23, 2018, 3:34am

That sounds like a bug.