I have no way to test but srwhite's driver workaround for the FE599 may work for this lock too.
jkudave, thank you. I am in the market for a Garage Door Lock, so perhaps I will go Zigbee for that. I can't say that I had issues with the Schlage with the Wink because I only had two robots setup. Not much to go by there. It seemed to work well, and the times it did not, I thought it was related to Internet/Cloud rule analysis.
I would also recommend zigbee, it just works.
To get the z-wave lock working, it needs to be paired in secure mode. Does it say secure mode in the device info? I found I needed to bring the hub near to the lock to get it to pair in secure mode.
Update - Things work now.
Steps Taken
Around the corner, 2 ft and 2 ft, there is another 2 gang box. I turned off power (which included the GE smart dimmer by the door that would not pair). I removed my Wink Relay and installed two GE devices (smart switch/smart dimmer). Those paired just fine. After that I went to my dimmer by the door. I started exclusion and it did not count down from 30, it immediately said it excluded Unknown.
2019-04-02 12:13:12.517 pm infoUnknown Z-Wave device excluded. (yes, my log is still running)
I then requested to pair Z-Wave. It found the dimmer and it worked just fine.
So I tested my lock and it still did not log any events.
I opened the battery cover, unplugged the power, manually locked and unlocked the lock, I pressed the Schlage button above the keypad, and powered it back up, I saw the battery % in the log.
I manually locked the door, unlocked it. Pressed the Schlage, entered my code.
dev:1332019-04-02 12:36:26.711 pm infoFront Door was unlocked by Charlie[6:6]
dev:1332019-04-02 12:36:18.140 pm infoFront Door was locked via keypad[6:5]
dev:1332019-04-02 12:36:15.046 pm infoFront Door battery is 76%
dev:1332019-04-02 12:36:13.326 pm infoFront Door was manually unlocked [physical][6:2]
dev:1332019-04-02 12:36:10.867 pm infoFront Door was manually locked [physical][6:1]
dev:1332019-04-02 12:36:05.727 pm infoFront Door battery is 78%
I left, returned, entered code. Checked and it was in the log. I was able to unlock and lock the device from the Hubitat GUI Device menu.
So everything seems to be working now. Now to build some automations.
Thank you for the replies. Things to consider next time.
This sounds like 'Beaming'... that beaming wasn't working, now it is.
Beaming was 'invented' to extend battery life on Locks. Battery devices sleep, which is the exact opposite of a lock that's supposed to be ready when you are.
My Wink hub died, so now I'm a Hubitat guy. Most everything was easy enough to transfer. My Schlage BE469 was another story. I'm on my third day of beating on it and finally figured it out, I think. I kept running Zwave exclude, but it would never leave the Wink network. I tried all of the suggestions that I could find here, no luck.
Finally I thought, maybe 2 feet is not close enough after all, so I duct taped the Hubitat to the lock.
It excluded on the first try, then it included on the first try!
I hope this works for you.
2 Likes
Just to add my experience. I moved from iris to ST then to hubitat with them. I to had issues with them, but I discovered that if I just disconnect the battery and wait 5 seconds pressing the schlage button, releasing the button and plugging the batteries back in (Not a factory reset). and right away do an exclude process, it would exclude immediately , then right after run the discover process, it would work. I had one lock that kept acting up (The closest to the hub) and that process fixed it. I have one lock that is about 150ft away from the hub through several walls and it has no issue if I use the method above. I just grabed my phone and walked around to the locks setting. using my phone to switch modes back and forth. It worked like a charm.
I am able to get my Schlage Connect lock to work. Took some time as I moved from Vera to Hubitat. I had to factory reset, unpair and pair a few times. But now it is added and I can control it(lock/unlock).
My problem are:
- That the state of the lock is never updated. I never see if unlocked or locked.
a) Because I can not see state, I can not create rule like to auto lock - Dashboard does not look right. I shows up at "?". I can click it, it ask am I sure then will lock it. If locked, it will do nothing. From Device menu, not dashboard I can lock and unlock.
Any suggestions, change settings or something?
The BE469 is my first major Hubitat woe. I got the locked paired fine, controlled by Alexa, and Rule Machine etc. on April 11th.
The one thing that never worked is battery updates. Anyway, the batteries died yesterday, and in the process my codes were lost from the lock - it reset to factory codes. When I put new batteries in, it was controlled right away by HE, and I could re-enter the old codes using HE just fine.
I wish battery updates worked. Also, when I had this paired to Wink, batteries dying never caused the lock to reset.
Finally, batteries lasted 3-6 months with Wink - not 2 weeks. I suspect that for some reason, secure z-wave is not being beamed by z-wave devices I have right next to the front door lock (a GE z-wave binary switch, and a Leviton z-wave outlet). Or that z-wave routing is not setup correctly.
I bought an Aeon labs repeater to hopefully fix this issue and I will rebuild the z-wave network tonight.
I found just how sensitive this lock can be. I have a Zwave Plus Leviton switched plug (that moves with my 3D printer around the house). It was right above it the floor above and the lock worked fine. I moved it about 15 ft away the other day, and the lock hasnt reported back since.
I have an older Zwave switch next to the lock (literally 8" away) but I am guessing it isnt repeating anything since the lock is not working right now on the network. I am replacing the switch with a GE Zwave Plus switch next week to hopefully get stuff working again down by the lock.
Previously I had a Wink hub located directly above the switch the floor above, so that seemed to work for it. Then again, it seems the Wink system had a stronger hub signal in general than the Hubitat hub, which isnt a big deal, just something I noticed.
Is anyone else having difficulty with BE469 locks after upgrading to HE Software 2.0.9.126?
My locks had finally started to work relatively well over the past few days. I made some rule changes so only one lock tries to unlock at a time every 10 seconds which seemed to help.
However, tonight I upgrade my HE to version 2.0.9.126. Now, I can't lock/unlock any locks via HE. I also can't get Lock Manager to transfer new codes to the locks. Is anyone else experiencing anything similar?
I have a BE469 but I'm having no issues at all with either the rules I have setup, using Lock Code Manager or locking/unlocking the door using Hubitat after the update. I tested out a few new rules too using RM 3.0 and having no issues so far. Lock Manager probably isn't working since you cannot lock/unlock in HE, may want to try new batteries first to see if that helps since this lock seems to stop all of a sudden for me every 3-6 months until I change the batteries out.
Sadly if that doesn't help, it may need reset and paired again. Seems like there's numerous ppl having issues with this lock, I will have to say I seem to be one of the lucky ones and have no issues at all on HE besides when the battery dies but had a ton of issues on Smartthings.
1 Like
I have this lock and was able to pair it. I am able to see the locked state and can lock/unlock it.
However, I have a rule that is supposed to function from 8:30 PM to 9 AM that will determine if it is locked and lock it if it is false.
It is correctly identifying the lock state but it isn't locking the door. I believe this was working in 2.08 but it hasn't been working recently. If I go out and check the lock around 9 PM, it is is unlocked and the lock state is unlocked - so it should lock for me.
I am able to use the dashboard and/or device page to lock it but now what I notice that is different is that when I go to lock/unlock it from the dashboard, I get popup that says "Are you sure?". If I click yes, it locks.
I wonder if this is something that it would be waiting on in rule and so it doesn't lock? Anyone see this behavior as well? It was originally created with Rule machine (2.5).
This has always been there and done this for over the past month when Dashboards 2.0 came out ---> . Confirmation prompt
I have noticed if you have a rule that fires multiple actions, create a separate one for the locks as these locks are very temperamental with communications.
Strange. I don't remember seeing that until I updated a few days ago.
This is the only device and action I have on this rule - to check if it's locked and lock it if is false.
Hi, anyone having issues with the lock no longer communicating with Hubitat unless you reboot the lock by disconnecting and reconnecting the batteries in the lock BE469. Restarting the hub doesn’t do anything to fix it once the lock is frozen.
It’s weird, it’ll work fine for a while and then one day it’ll just stop communicating. It never did that with Wink so I wonder if it’s a driver issue causing it to lock up (pun).
Batteries are fresh.
Many others have reported this issue in the past. It used to happen to me as well but one of the firmware updates (don't remember which) seemed to clear this issue up for me. What firmware are you running on your hub?
Thanks, I’m using the latest one for the Hub 2.1.2.123
Even with 2.1.3.120, I’m still having to unplug and replug the batteries in the lock about once a day because it just stops responding. It’s one of the more frustrating things moving always from Wink. I’m even considering using the Wink again just for the lock since it was one of the things Wink did well.
Are there any outstanding issues the team is working on with the drivers for this?
