I just checked, and that’s the firmware mine has apparently always been on so you should be good.
I dont believe lock firmware will break the integration. The integration talks to the allegion cloud api, not the actual lock. (Which means they could choose to brick it the way myQ did…)
I am having issues getting my encode initially setup, its an encode wifi BE489WB2
The lock is always “unavailable” in HA, although I am able to interact with the lock without issue from the Schlage Home app. Strangely, the firmware version shown in HA doesn’t match what the schlage app reports. When I set up the lock, I get no debug logs. After a bit, I start to see this repeated:
2023-11-03 07:10:41.038 DEBUG (MainThread) [homeassistant.components.schlage] Finished fetching schlage (p****@gmail.com) data in 1.652 seconds (success: True)
HA 2023.11.0
I opened this GH issue as well: Schlage lock always unavailable · Issue #103197 · home-assistant/core · GitHub
Anyone have any suggestions?
I just installed a Schlage Encode lock, set it up through the Schlage app, and added the Schlage integration to Home Assistant without any issue.
The problem that I am experiencing is that locking or unlocking the lock from Home Assistant takes several seconds, sometimes even more than 30 seconds. Has anybody experienced this issue? Or knows how to fix it?
I have two Encode Plus locks both working fine from HomeKit and the Schlage app. I installed the official integration and entered my username/password and it reported connecting successfully but neither lock shows up as a device or entity. What am I missing?
Encode Plus is different to the Encode Wifi, maybe ask in this thread.
Schlage Encode Plus - Hardware - Home Assistant Community (home-assistant.io)
Hello,
I currently have Encode Plus set up through Schlage App, to keep it on Wifi
I’ve setup Apple HomeKey through Homekit. Everything works fine
My one question is, when using Home assistant with the Schlage Integration that now exists…The door lock or unlocks right away. Very responsive. But it take 10 or 15 seconds for the entity to update. So anotherwords, if I’m not home and lock my door be cause I forgot, I’ll have to sit there for a few and wait to see if the button updates to locked
Is this just a currently limitation of the schlage app that will hopefully get better with updates?
other than that all works great. No matter/thread apple hubs etc. Blue tooth is every bit as fast as matter for the HomeKey function… Don’t let apple people fool you lol Batter just takes a bigger hit being on wifi
I’m happy to start a new thread for this, but this seems like the right place. I’ve searched extensively, but haven’t found a reference or guide for being able to modify user codes on the Schlage Encode. I have a short term rental, and I’d like to be able to add and remove codes automatically based upon calendar entries. Any breadcrumbs? I’m aware of the security implications, but I’m guessing it’s more secure than simply using the same code for 300 guests 
@dknowles2 I saw that pyschlage supports user codes. Any chance that you could update the core component to have some service calls for getting and setting codes? The ZWave_JS component does this for zwave locks and this makes it possible to program such locks.
I’m working with someone setting up some short term rentals and they got these locks before I could suggest something else and now I’m trying to figure out how to cleanly program / deprogram codes for them!
Anyone else seeing poor battery life with the Encode locks? I installed some about a 18 months ago and they seemed to get around 6 months of battery life. Lately they seem to be getting considerably less. Makes me wonder if HA polling is involved. As in, waking up the locks too often and draining battery life.
Wow, 6 months! How’d you acheive that? I get almost exactly 90 days. I’d think that the physical opening/closing the lock would be way more of a drain than HA could put on it. Also, since you can always access this remotely from the app (not HA) does it ever really sleep?
In my experience, low WiFi signal is the worst culprit. Buy a cheap repeater and place it near the door.
This is what Claude.AI told me:
A few things account for most of it, roughly in order of how often they’re the culprit:
Mechanical drag. By far the most underrated cause. If the deadbolt rubs the strike plate or the door has sagged/swollen, the motor draws far more current per cycle and sometimes retries. Test it: throw the bolt with the door open, then closed. If closed feels even slightly harder, you’re burning battery on every lock. Enlarging the strike hole or shimming the hinges often doubles battery life.
Wrong battery chemistry. Schlage specifically calls for non-rechargeable alkaline (Duracell/Energizer) and advises against lithium and rechargeables. Lithium AAs sit at ~1.7V and hold a flat curve, so the lock’s voltage-based gauge misreads them and they fall off a cliff with no warning. Bargain-brand alkalines also underperform badly under the high-current pulses a bolt motor demands.
Cold. Alkaline capacity drops sharply below freezing — you can lose a third or more of usable capacity on an exterior door in a mountain winter. A set installed in fall dying in January is often this rather than a defect.
Radio conditions. On Wi-Fi models (Encode/Encode Plus) a marginal signal at the door is the single biggest drain: the radio transmits at higher power and retries constantly. On Z-Wave (BE469), the equivalent problem is a weak mesh — no repeater within reliable range means retransmissions, and legacy S0 security roughly triples the message count versus S2.
Aggressive polling. If your hub or automation platform is querying lock state on a short interval rather than relying on the lock’s own status reports, you’re waking the radio constantly. Stretching a 30-second poll to 5–10 minutes, or switching to event-driven updates, makes a visible difference.
I gave up on using WiFi on these things ages ago. Using Bluetooth with an appropriate gateway like an Apple HomePod / TV, and they’ll easily last over a year. We had one last nearly 1.5 years with regular use.
That being said, the bolt action is so buttery smooth, you almost feel like the locking mechanism isn’t actually working.
I went the other direction. I had zwave models in multiple Airbnb’s that I own, and I got tired of messing with the Vera hubs that I was using (this was before I got into HA, so I didn’t have HA or a RPi). So I went to WiFi and hust change the batteries more often, but a simpler setup
Are all of yours the deadbolts? All of mine are the handle set kind, no deadbolts.
Yes dead bolts.
The best smart lock based on your answers | Schlage Encode
Yeah, this kind of monitoring will absolutely kill the battery much faster.