Schlage lock survey

🛎️ Get Help Devices
2

I'll start off.

I started with Wink 1, and had issues with my Schlage locks draining batteries (was a well known Wink bug). Moved to Wink Hub 2, and then ST and the rboy app/driver. Now to HE.

For other mesh devices, I have a mix of Zwave and Zwave plus devices. Zwave devices in range of my most troublesome lock are a Jasco/GE Zwave Plus outdoor outlet (possibly also a regular non-zwave plus one as well), a GE Zwave Plus dimmer, a couple Zooz Zen27's, 2 Aeotec Zwave Extenders, and I think that's it.

This makes me want to model out where each device is on a map of my house. lol.

Thanks!

3

There is a survey option. Click the gear icon in the Reply box and select build survey.

image
image.png711×178 5.88 KB

Was this helpful

  • Yes
  • No

0 voters

1 Like
4

Thanks. Sadly doesn't let people add options, so letting people say "I've got this device" would require modifying the poll each time. =/ But might not be a terrible option... thinks

5

My system/network has changed so much since I was on SmartThings that any comparison between then and now (on Hubitat) would be totally irrelevant.

If you are interested, you will find there was a thread (I was a participant) where we found we could save some parameters from the ST driver and then switch back to the HE driver and the experience was improved. I think srwhite may have made the discovery (my apologies if I have that wrong - this is by memory and it was a good while ago). This was last year prior to the Hubitat Team working over the common Schlage drivers. I don't believe it is really relevant to today except that it is the closest thing I can think of to what you are exploring.

6

The concern I have is more that Wink or ST drivers set some parameter in the lock that HE isn't aware of, etc. So it wouldn't matter how much Zwave changes. The additional problem is a factory reset of the lock specifically does NOT reset the zwave module in the lock. =/

An exclude should, but who knows. Schlage could be doing something dumb... =/

Anyway, just a thought. Trying to figure out what the heck we're missing regarding these locks and their behavior in HE. =/

7
8

You can use the basic z-wave tool to poll the parameters configured in the device.

2 Likes
9

Yes, I recall this thread. =/ Tried it, and still having issues. I'm trying to avoid spending several hundred on new Yale locks (my one Yale lock works amazingly well)

10

Seems to do nothing with the lock. Commands return no results. =/

11

It is in the logs not on the driver view

12

okay. will look more. that said, that wasn't really my goal of this thread... =/

13

You totally miss my point . . . again.

14

lol. no, I didn't. you're saying this is a fruitless exercise. fine. For you, this seems pointless. Then don't bother answering. I thought maybe we could find some commonality that HE doesn't have the time or manpower to explore. You know, try to help.

15

I tried my 3 Schlage Z-Wave locks on HE but had to many issues. Moved them back to ST and use HubConnect to sync them to HE.

1 Like
16

I started with a Schlage FE469NX on a Wink Hub 1 in mid-2016. It paired very easily but battery life was awful. I upgraded to a Wink Hub 2 in December 2016 and battery life actually got worse. If memory serves, the lock was running FW version 7.2 and Schlage support replaced the lock summer 2017 with a unit running FW 8.1 because of the battery life issue. Schlage didn't want the old lock back and It sat in a drawer for 6 months.

I replaced The Wink 2 Hub with an HE hub in December 2018 and paring was very difficult; odd given that I had very few z-wave devices when I added the lock to Wink compared to a much larger and stronger z-wave mesh when I added it to HE. I also paired the "defective" lock running FW 7.2 to the HE hub. I had similar pairing issues but eventually got it paired. Strangely, the battery life problem has been a non-issue with the HE hub. And both locks, once paired, have been rock solid.

1 Like
17

There was definitely an issue with Wink and the battery life on the Schlage locks. They worked with Schlage for months trying to resolve and finally did. But never said what the issue was... I believe I heard it was just polling a lot (chatty). Which... kinda sounds like the HE issue some of us have.

This is good info, thank you.

18

I just migrated from wink 2 hub took me 3 days. Very interesting I had to take my hubitat elevation to the door to get it included. Very strange I am also using aeotec 7 extenders.

1 Like
19

This sounds like it's pretty common, especially for anything that is secure pairing.

20

Started on Wink 1, then 2, now habitat. Schlage be469 locks are solid. Look at the video below, I did what it said and haven't had any issues.

5 Likes
21

If your theory were in any way plausible, this would mean that anybody who migrated from wink to st as well would likely be having the same issues. Unless the 2 were very coincidentally writing the exact same variable. And not to mention the odds of that 1 particular variable not being cleared on a factory reset...

As for a device corrupting traffic, everybody would have to be having that same device repeating the signal between the hub ad lock. It would be one hell of a coincidence.

There's a number of posts from people who feel (as do I) that the HE hub has a weak z-wave radio compared to some of these other hubs. I think it far more likely that the issue stems from there since we're dealing with a secure device.

I personally never moved my locks to HE because of all the reported issues. I kept them on ST (with rboy's DTH) and used hubconnect.

1 Like