[Solved] Release 2.3.0.119 - Schlage locks completely dead to Hubitat

🛎️ Get Help Devices
1

Release 2.3.0.118 broke a couple devices, a LIFX white bulb and a couple random switches - Release 2.3.0.119 fixed that last night (whew).

This morning neither of my Schlage locks will respond to my Hubitat. Completely ignored. Reviewing the release notes I saw no mention of breaking changes around Schlage devices (yes, I know they're cranky, but they'd been working flawlessly for the last several releases.)

2

Did you try the the remove from battery and re-connect yet. When ever mine stop responding that usually gets them back.

It could be something in the release but I have 4 Schlage's and mine all seem to still be working.

3 Likes
3

Platform updates don’t intentionally break devices that used to be compatible.

Are these z-wave locks?

2 Likes
4

My Schlage works fine after the update. Maybe more information about the model of the Schlage lock and what hub you are using, could be helpful.

3 Likes
5

Well, I'm glad to know multiple other users are having no issues - that's hopeful. Seems odd that it's both of them and Troubleshooting 101 always starts with "what changed?"

These are the BE469's. One is a couple years old, the other is a few months old. I had initial issues with the newer one, ended up with it living on my Vera for a short while. Then a recent release of Hubitat addressed Schlage specifically and I moved the newer one back over - and they both perform flawlessly.

I've rebooted the Hub (C7) just so it has a clean restart. Testing the older lock, it now unlocked immediately but took several minutes to lock again. Testing the newer one, totally unresponsive until I did the battery unplug/replug and now all good (including a backlog of notifications flowing in.)

Thanks all - your ideas were very helpful!

6

Just tested my Schlage BE468/9 (can't remember which one it is!) and it's working fine - unlocked/locked immediately on command from device page, and the auto lock automation I have set up was working fine yeseterday after I updated to .119

1 Like
7

Take a look at your Z-wave details page - make sure you don't have any Z-Wave devices that have routing missing (last column in the table).

3 Likes
8

Pulling the batteries and putting them back combined with rebooting the hub did the trick. 24 hours of success since.

Thanks again, all!

2 Likes
9

That worked for my FE599 too. It had stopped taking to the hub but, when I checked the logs, that happened a couple of days before I did the software upgrade. Usually it just requires a battery change.

1 Like