Easiest way to extend range of deadbolt

Devices & Integrations
1

To give a high level overview of my scenario, I have a ranch house. In my basement, I have a full cinder block wall running down the middle of the house in basement. The ST hub sits on the main level on 1 side of the wall. About 40 feet away is a kwikset lock that won’t work with hub. I’m thinking it’s because of that cinder block wall blocking the signal.

I thought I read in the past that deadbolts send encrypted messages and light switches and power outlets won’t relay the signal. Is there any truth to that?

I guess my question is, what’s the easiest way to get that deadbolt working? Install power outlets and light switches to extend the network? Or just get another hub down in the basement?

Any feedback is greatly appreciated.

2

Easiest answer is, any powered ZWave device will work as a network extended. If it runs on battery it will not extend the network. So if it simply isn’t reaching it, put 1 or 2 powered z wave devices between the hub and it and it should start to work.

They do sell dedicated zwave extenders, but i don’t like doing that since they only perform one function.

3

And once you add the extenders don’t forget to rebuild your z-wave network from the IDE site.

4

Thank you for the responses. I have a GE 3way switch coming and GE power outlet that will be here Wednesday. I will add those in the middle and hopefully then ST will see it and I will be able to include it.

5

@Ben, would it be possible for the Hub to automatically rebuild the network when a new zwave device is added so people don’t have to do it? The only way to do it right now is in the IDE…which means everyone will need to go to the IDE. Is it a bad thing to automatically rebuild?

6

It is possible but there are some reasons we have not done that yet. Wondering what some others think about this. @urman @duncan ?

7

Ben - you say rebuild but I assume you mean repair? I don’t see a rebuild in the IDE tools.

8

Correct. Sorry. Also should have included this:

#time

9

I’m definitely not a pro, But I would say if it doesn’t hurt by having an automatic repair done when a new device is added, then I would think that would make a lot of peoples lives easier.

As a mesh network, adding 1 or 2 devices could dramatically improve the operation of things. And if a user isn’t tech savvy then they wouldn’t know to do a repair each time they add a device.

But if it does cause issues when doing a repair then maybe come up with a screen after a device is added that informs users to do a repair to achieve the best results.

Just my thoughts.

2 Likes
10

Repairing Z-Wave network can take very long time - 20 minutes or more for large networks. That’s why it’s never done “automatically”.

11

What about scheduled or prompt? If you add a device, you could get a prompt explaining that it needs to be done. The options could be “sometime overnight, now, or I’m adding more devices so not yet”

12

What we have thought about is having a maintenance window late at night where the process may run without too many interferences. But there are technical hurdles. We can also make it easier to perform those repair procedures and advise on when to do them. #SoManyThingsToDo :slight_smile:

13

. #AintThatTheTruth #Don’tEnvyYou

I do like the idea of suggesting when they should be run.

14

I think that having a prompt to do it after installing a new device would be a good idea. I, for one, had no idea this needed to be done or how to do it. I’ve not yet looked at how to do it - but it already sounds more complicated than some of us might be up to. So, having something simple right in the ST interface would definitely be my preference.