Advice on Zwave range and repeaters

#1

I have a number of inovelli switches and dimmers all capable of repeating. In fact they are the only zwave repeaters i have. I am trying to add one in my barn. I included it in my garage beside an existing switch which is the closest to the barn on an outside wall about 30feet from the barn door where the new switch will be.

I temporarily placed it just outside the door of the garage switch and ran a zwave repair, everything went great and i could control it. BUT if i then move the new switch the rest of the way to the barn i lose it.

So I ran another zwave repair while at the barn door and it does not pick it up. Any pointers, is the inovelli in the garage not repeating as it should? its a clear 25-30ft shot (outside door to outside door). I even ran a zwave repair half way between the garage and barn and nothing.

#2

is this the z-wave or z-wave plus model? The plus has longer range and might just get you there.

#3

All of them are PLUS versions

#4 
sys:12019-02-10 02:31:30.146 pm infoFinished Z-Wave Network Repair

dev:1432019-02-10 02:31:24.661 pm infoMaster Bath Motion: Detected motion
dev:1432019-02-10 02:31:24.620 pm infoMaster Bath Motion: Illuminance is 466 lux
sys:12019-02-10 02:29:54.655 pm traceZ-Wave Node 19: Repair setting SUC route
sys:12019-02-10 02:29:54.481 pm traceZ-Wave Node 19: Repair setting SUC route
sys:12019-02-10 02:29:54.368 pm traceZ-Wave Node 19: Repair setting SUC route
sys:12019-02-10 02:29:54.284 pm traceZ-Wave Node 19: Repair setting SUC route
dev:1432019-02-10 02:29:52.009 pm infoMaster Bath Motion: Reset to motion inactive after 61 seconds
sys:12019-02-10 02:29:50.143 pm traceZ-Wave Node 19: Repair pinging
sys:12019-02-10 02:29:50.141 pm traceZ-Wave Node 19: Repair starting
sys:12019-02-10 02:29:44.849 pm traceZ-Wave Node 17: Repair is done.
dev:1392019-02-10 02:29:44.848 pm debug'zw device: 11, command: 8503, payload: 01 05 00 01 ' parsed to null
dev:1392019-02-10 02:29:44.843 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:29:44.838 pm traceZ-Wave Node 17: Repair is requesting node neighbor info
sys:12019-02-10 02:29:44.837 pm traceZ-Wave Node 17: Repair is adding return route
sys:12019-02-10 02:29:44.835 pm traceZ-Wave Node 17: Repair is deleting routes
sys:12019-02-10 02:29:44.431 pm traceZ-Wave Node 17: Repair is requesting device associations
dev:1522019-02-10 02:29:42.106 pm infoLaundry Room Door is inactive
sys:12019-02-10 02:29:38.742 pm traceZ-Wave Node 17: Repair is updating neighbors
sys:12019-02-10 02:29:35.209 pm traceZ-Wave Node 17: Repair setting SUC route
sys:12019-02-10 02:29:35.139 pm traceZ-Wave Node 17: Repair pinging
sys:12019-02-10 02:29:35.137 pm traceZ-Wave Node 17: Repair starting
dev:1522019-02-10 02:29:32.141 pm infoLaundry Room Door is [x:18,y:6,z:-1053]
dev:1332019-02-10 02:29:29.838 pm debug'zw device: 10, command: 8503, payload: 01 05 00 01 ' parsed to null
dev:1332019-02-10 02:29:29.833 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:29:29.820 pm traceZ-Wave Node 16: Repair is done.
sys:12019-02-10 02:29:29.811 pm traceZ-Wave Node 16: Repair is requesting node neighbor info
sys:12019-02-10 02:29:29.810 pm traceZ-Wave Node 16: Repair is adding return route
sys:12019-02-10 02:29:29.808 pm traceZ-Wave Node 16: Repair is deleting routes
sys:12019-02-10 02:29:29.222 pm traceZ-Wave Node 16: Repair is requesting device associations
dev:322019-02-10 02:29:26.031 pm debugcondition: 1003 | condition text: Partly cloudy | condition factor: 0.8 | lux: 4956
dev:322019-02-10 02:29:26.029 pm debugbetween noon and sunset
sys:12019-02-10 02:29:18.717 pm traceZ-Wave Node 16: Repair is updating neighbors
sys:12019-02-10 02:29:10.229 pm traceZ-Wave Node 16: Repair setting SUC route
sys:12019-02-10 02:29:10.136 pm traceZ-Wave Node 16: Repair pinging
sys:12019-02-10 02:29:10.134 pm traceZ-Wave Node 16: Repair starting
sys:12019-02-10 02:29:04.787 pm traceZ-Wave Node 15: Repair is done.
dev:1322019-02-10 02:29:04.782 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:29:04.721 pm traceZ-Wave Node 15: Repair is requesting node neighbor info
sys:12019-02-10 02:29:04.719 pm traceZ-Wave Node 15: Repair is adding return route
sys:12019-02-10 02:29:04.717 pm traceZ-Wave Node 15: Repair is deleting routes
sys:12019-02-10 02:29:04.361 pm traceZ-Wave Node 15: Repair is requesting device associations
sys:12019-02-10 02:28:58.754 pm traceZ-Wave Node 15: Repair is updating neighbors
sys:12019-02-10 02:28:55.206 pm traceZ-Wave Node 15: Repair setting SUC route
sys:12019-02-10 02:28:55.133 pm traceZ-Wave Node 15: Repair pinging
sys:12019-02-10 02:28:55.131 pm traceZ-Wave Node 15: Repair starting
dev:1432019-02-10 02:28:51.012 pm infoMaster Bath Motion: Detected motion
dev:1432019-02-10 02:28:50.964 pm infoMaster Bath Motion: Illuminance is 500 lux
dev:1312019-02-10 02:28:47.451 pm debug'zw device: 0E, command: 8503, payload: 01 05 00 01 ' parsed to null
dev:1312019-02-10 02:28:47.445 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:28:47.425 pm traceZ-Wave Node 14: Repair is done.
sys:12019-02-10 02:28:47.417 pm traceZ-Wave Node 14: Repair is requesting node neighbor info
sys:12019-02-10 02:28:47.415 pm traceZ-Wave Node 14: Repair is adding return route
sys:12019-02-10 02:28:47.409 pm traceZ-Wave Node 14: Repair is deleting routes
sys:12019-02-10 02:28:47.367 pm traceZ-Wave Node 14: Repair is requesting device associations
sys:12019-02-10 02:28:45.510 pm traceZ-Wave Node 14: Repair is updating neighbors
sys:12019-02-10 02:28:45.151 pm traceZ-Wave Node 14: Repair setting SUC route
sys:12019-02-10 02:28:45.129 pm traceZ-Wave Node 14: Repair pinging
sys:12019-02-10 02:28:45.127 pm traceZ-Wave Node 14: Repair starting
dev:592019-02-10 02:28:38.400 pm debug'zw device: 0D, command: 8503, payload: 01 05 00 01 ' parsed to null
sys:12019-02-10 02:28:38.398 pm traceZ-Wave Node 13: Repair is done.
dev:592019-02-10 02:28:38.394 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:28:38.384 pm traceZ-Wave Node 13: Repair is requesting node neighbor info
sys:12019-02-10 02:28:38.382 pm traceZ-Wave Node 13: Repair is adding return route
sys:12019-02-10 02:28:38.377 pm traceZ-Wave Node 13: Repair is deleting routes
sys:12019-02-10 02:28:37.312 pm traceZ-Wave Node 13: Repair is requesting device associations
dev:1432019-02-10 02:28:33.582 pm infoMaster Bath Motion: Reset to motion inactive after 61 seconds
sys:12019-02-10 02:28:26.251 pm traceZ-Wave Node 13: Repair is updating neighbors
sys:12019-02-10 02:28:15.239 pm traceZ-Wave Node 13: Repair setting SUC route
sys:12019-02-10 02:28:15.125 pm traceZ-Wave Node 13: Repair pinging
sys:12019-02-10 02:28:15.123 pm traceZ-Wave Node 13: Repair starting
dev:582019-02-10 02:28:08.138 pm debug'zw device: 0C, command: 8503, payload: 01 05 00 01 ' parsed to null
dev:582019-02-10 02:28:08.130 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:28:08.126 pm traceZ-Wave Node 12: Repair is done.
sys:12019-02-10 02:28:08.117 pm traceZ-Wave Node 12: Repair is requesting node neighbor info
sys:12019-02-10 02:28:08.115 pm traceZ-Wave Node 12: Repair is adding return route
sys:12019-02-10 02:28:08.113 pm traceZ-Wave Node 12: Repair is deleting routes
sys:12019-02-10 02:28:07.047 pm traceZ-Wave Node 12: Repair is requesting device associations
sys:12019-02-10 02:27:53.948 pm traceZ-Wave Node 12: Repair is updating neighbors
sys:12019-02-10 02:27:50.233 pm traceZ-Wave Node 12: Repair setting SUC route
sys:12019-02-10 02:27:50.120 pm traceZ-Wave Node 12: Repair pinging
sys:12019-02-10 02:27:50.117 pm traceZ-Wave Node 12: Repair starting
dev:312019-02-10 02:27:45.603 pm debug'zw device: 0B, command: 8503, payload: 01 05 00 01 ' parsed to null
sys:12019-02-10 02:27:45.599 pm traceZ-Wave Node 11: Repair is done.
dev:312019-02-10 02:27:45.596 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:27:45.583 pm traceZ-Wave Node 11: Repair is requesting node neighbor info
sys:12019-02-10 02:27:45.580 pm traceZ-Wave Node 11: Repair is adding return route
sys:12019-02-10 02:27:45.577 pm traceZ-Wave Node 11: Repair is deleting routes
sys:12019-02-10 02:27:44.869 pm traceZ-Wave Node 11: Repair is requesting device associations
sys:12019-02-10 02:27:39.182 pm traceZ-Wave Node 11: Repair is updating neighbors
dev:1432019-02-10 02:27:32.591 pm infoMaster Bath Motion: Illuminance is 494 lux
dev:1432019-02-10 02:27:32.561 pm infoMaster Bath Motion: Detected motion
sys:12019-02-10 02:27:30.209 pm traceZ-Wave Node 11: Repair setting SUC route
sys:12019-02-10 02:27:30.116 pm traceZ-Wave Node 11: Repair pinging
sys:12019-02-10 02:27:30.114 pm traceZ-Wave Node 11: Repair starting
dev:272019-02-10 02:27:25.134 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:27:25.132 pm traceZ-Wave Node 10: Repair is done.
sys:12019-02-10 02:27:25.122 pm traceZ-Wave Node 10: Repair is requesting node neighbor info
sys:12019-02-10 02:27:25.120 pm traceZ-Wave Node 10: Repair is adding return route
sys:12019-02-10 02:27:25.115 pm traceZ-Wave Node 10: Repair is deleting routes
sys:12019-02-10 02:27:24.712 pm traceZ-Wave Node 10: Repair is requesting device associations
sys:12019-02-10 02:27:18.873 pm traceZ-Wave Node 10: Repair is updating neighbors
sys:12019-02-10 02:27:15.186 pm traceZ-Wave Node 10: Repair setting SUC route
sys:12019-02-10 02:27:15.113 pm traceZ-Wave Node 10: Repair pinging
sys:12019-02-10 02:27:15.111 pm traceZ-Wave Node 10: Repair starting
sys:12019-02-10 02:27:06.955 pm traceZ-Wave Node 6: Repair is done.
dev:232019-02-10 02:27:06.951 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:27:06.945 pm traceZ-Wave Node 6: Repair is requesting node neighbor info
sys:12019-02-10 02:27:06.944 pm traceZ-Wave Node 6: Repair is adding return route
sys:12019-02-10 02:27:06.942 pm traceZ-Wave Node 6: Repair is deleting routes
dev:1432019-02-10 02:27:06.777 pm infoMaster Bath Motion: Reset to motion inactive after 61 seconds
sys:12019-02-10 02:27:06.648 pm traceZ-Wave Node 6: Repair is requesting device associations
sys:12019-02-10 02:27:02.224 pm traceZ-Wave Node 6: Repair is updating neighbors
sys:12019-02-10 02:27:00.178 pm traceZ-Wave Node 6: Repair setting SUC route
sys:12019-02-10 02:27:00.109 pm traceZ-Wave Node 6: Repair pinging
sys:12019-02-10 02:27:00.108 pm traceZ-Wave Node 6: Repair starting
sys:12019-02-10 02:26:55.572 pm traceZ-Wave Node 4: Repair is done.
dev:202019-02-10 02:26:55.569 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:26:55.558 pm traceZ-Wave Node 4: Repair is requesting node neighbor info
sys:12019-02-10 02:26:55.555 pm traceZ-Wave Node 4: Repair is adding return route
sys:12019-02-10 02:26:55.552 pm traceZ-Wave Node 4: Repair is deleting routes
sys:12019-02-10 02:26:55.369 pm traceZ-Wave Node 4: Repair is requesting device associations
sys:12019-02-10 02:26:51.876 pm traceZ-Wave Node 4: Repair is updating neighbors
sys:12019-02-10 02:26:50.158 pm traceZ-Wave Node 4: Repair setting SUC route
sys:12019-02-10 02:26:50.108 pm traceZ-Wave Node 4: Repair pinging
sys:12019-02-10 02:26:50.106 pm traceZ-Wave Node 4: Repair starting
sys:12019-02-10 02:26:41.563 pm traceZ-Wave Node 3: Repair is done.
dev:192019-02-10 02:26:41.558 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:26:41.552 pm traceZ-Wave Node 3: Repair is requesting node neighbor info
sys:12019-02-10 02:26:41.550 pm traceZ-Wave Node 3: Repair is adding return route
sys:12019-02-10 02:26:41.549 pm traceZ-Wave Node 3: Repair is deleting routes
sys:12019-02-10 02:26:41.245 pm traceZ-Wave Node 3: Repair is requesting device associations
sys:12019-02-10 02:26:37.134 pm traceZ-Wave Node 3: Repair is updating neighbors
sys:12019-02-10 02:26:35.178 pm traceZ-Wave Node 3: Repair setting SUC route
sys:12019-02-10 02:26:35.105 pm traceZ-Wave Node 3: Repair pinging
sys:12019-02-10 02:26:35.103 pm traceZ-Wave Node 3: Repair starting
sys:12019-02-10 02:26:26.595 pm traceZ-Wave Node 2: Repair is done.
dev:52019-02-10 02:26:26.588 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:26:26.579 pm traceZ-Wave Node 2: Repair is requesting node neighbor info
sys:12019-02-10 02:26:26.576 pm traceZ-Wave Node 2: Repair is adding return route
sys:12019-02-10 02:26:26.573 pm traceZ-Wave Node 2: Repair is deleting routes
sys:12019-02-10 02:26:26.376 pm traceZ-Wave Node 2: Repair is requesting device associations
sys:12019-02-10 02:26:22.435 pm traceZ-Wave Node 2: Repair is updating neighbors
sys:12019-02-10 02:26:20.150 pm traceZ-Wave Node 2: Repair setting SUC route
sys:12019-02-10 02:26:20.102 pm traceZ-Wave Node 2: Repair pinging
sys:12019-02-10 02:26:20.099 pm traceZ-Wave Node 2: Repair starting
sys:12019-02-10 02:26:20.028 pm infoStarting Z-Wave Network Repair

#5

Node 10 is the garage switch closest to the barn and node 19 is the new switch

This is from the "good" repair when it was close to the inovelli switch (but outside)

sys:12019-02-10 02:14:38.003 pm debugZ-Wave Node 19:  Repair is done.

dev:1542019-02-10 02:14:37.996 pm debugAssociations for Group 2: []
sys:12019-02-10 02:14:37.989 pm debugZ-Wave Node 19: Repair is requesting node neighbor info
sys:12019-02-10 02:14:37.989 pm debugZ-Wave Node 19: Repair is adding return route
sys:12019-02-10 02:14:37.988 pm debugZ-Wave Node 19: Repair is deleting routes
dev:1542019-02-10 02:14:37.778 pm debugAssociations for Group 1: [01]
sys:12019-02-10 02:14:36.988 pm debugZ-Wave Node 19: Repair is requesting device associations
sys:12019-02-10 02:14:32.268 pm debugZ-Wave Node 19: Repair is updating neighbors
sys:12019-02-10 02:14:29.671 pm debugZ-Wave Node 19: Repair setting SUC route
sys:12019-02-10 02:14:29.572 pm debugZ-Wave Node 19: Repair pinging
sys:12019-02-10 02:14:29.571 pm debugZ-Wave Node 19: Repair starting

#6

19 never finishes the repair probably because it can't talk to it. What type of siding or what on the outside of the walls?

#7

Wood stud and vinyl siding

#8

assuming plastic and not metal switch boxes?

Otherwise I wouldn't think that distance is too much...but obviously.

#9

Both boxes are metal but I dont have them in the boxes, the garage switch is protruding out of the box about 5 inches in mid air supported by the wires and the new switch I have hooked to a cord until I can get it to connect to the garage switch

Is there any way to tell if they are repeating? Other than trial and error and keep doing repairs until they see one another?

#10

If you did the mesh repair while they are next to each other that should be fine. Next step would be just to walk further and further away on your cord until it stops responding to an event (like on/off) that will get you an idea of distance. If that metal box is between you and line of sight to that dangling switch...It will still be an issue. At least this will give you some idea of what kind of distance you are getting.

#11

It did not take much distance to lose it, like 10ft. That seems low even with a wall and metal box?

Unless it chose to connect to another switch further away in my porch? But i guess there is now way to tell?

#13

I did this test and got 10 feet before i lost it.

#14

It's going to connect to the closest...if it did connect to something else...you would still be able to talk to it. The fact that it didn't mean's it's losing it. What happens if you extend the wires on the one in the house a bit to get further away from the metal box. I'll bet that helps. 10' is not very far.

#15

Ive read that zwave can do a max of 4 hops , possibly the garage switch is the 4th and cannot be a repeater for the barn so the barn is connecting to another farther away or even all the way back to the hub

#16

I guess i could verify that it is using the garage switch as a repeater by turning the power off for the garage switch and see if the new barn switch still operates?

#17

It definately is using the garage switch as a repeater since it loses connectivity when i kill power to the garage switch. So i guess the range for the inovelli switch as a repeater is just very weak

#18

It's probably easiest way is to get an outdoor plug for repeater and using it for controlling devices outdoor at the same time. Quite decent price with this one.

#19

I do have an outside receptacle just outside that garage mandoor so i could give that a try. Im in canada so that one is a bit pricy. I think Zooz has one too

#20

Just an fyi I do have a zigbee outlet out in the barn and it is connecting fine! I guess zigbee trumps zwave in my scenario, i have great luck with zigbee devices here including xiaomi

#21

Yeah, I am using mostly zigbee devices for my detached garage as well. Added 2 xbee pro recently and it's so much better.