I'm in Zwave hell

What is the best way to completely start over?

I have Aeotec Range Extenders that don't seem to be working. I've got Inovelli Red Light Dimmers which won't pair. I just need to start over, but... man does that mean I have to COMPLETELY start over?

Can you gave us more info should as Hub Version and whether you have did and exclusion or factory resets on the sensors that you are trying to use. I have not had any issues with the Inovelli Red Dimmers other than not exclusion them before I move them from another hub or excluded them after I receive them from Inovelli. I don't think that you will have to start over Two day ago I moved some Red Dimmer and Red Switch from Inovelli from a C-5 Hub to a C-7 and like I said only issue was not excluded correctly.

1 Like

I have a C7 with the latest firmware. I think that some of my issues stem from the Aeotec Range Extender 7. I can't seem to get it off or on. I think that I factory reset it. I have no idea about S2 stuff. I do remember that pairing them was... weird.

The Red Dimmers are 1.47

What I would do is to excluded and then add it back with out the S2 and see how it works. All you need to do is uncheck all the boxes. I had to wait about a hour or so and some of my sensors starting working. I still hadn't figure that out yet? You can also do the same for the red dimmer?

1 Like

I hate pairing on the C7. Shut down from the settings menu, once hub is off, pull the plug for 1 minute(FROM THE WALL-NOT THE HUB- CONNECTOR IS WEAK)
restart and your device will pair. I've only done this like 10 times, it's maddening

1 Like

Thanks I forgot about that.

The Aeotec Range Extender 7 are giving a lot of people headaches from what I've seen in the forum.

The red series inovelli seem to need a power cycle before exclude/include will work properly. pull the air gap at the bottom for 30 seconds.

1 Like

This not at all nessecary. I don’t have a ton of Z-Wave devices, but didn’t have to power cycle the hub for joining z-wave devices on two different C-7 hubs. Power cycle of the devices is commonly a fix, not the hub.

2 Likes

OK -- so with a LOT of power cycling of stuff and ripping out the Extenders I'm having better luck.

I've added more devices and am trying a zwave repair (with the extenders in a drawer).

You don’t need to repair Plus devices and shouldn’t unless there’s a non-plus device on the network.

Running repairs are just going to make an all Z-Wave Plus network unnecessarily busy and devices will seem slow or unresponsive.

1 Like

Well here is my experience...

If you have Z-Wave Plus devices and Z-Wave Non-Plus devices, the Plus devices don't seem to like to talk to Non-Plus devices. The Non-Plus devices don't seem to talk to or route through the Plus devices. Each type of device, Plus or Non-Plus, seem to only want to communicate with their own kind. If you are trying to add a Plus-Extender to extend the range of Non-Plus devices, it just doesn't seem to work.

As far as Including new devices. Non-Plus devices generally can't be Included if they are being routed through other Non-Plus devices. You need to put your Non-Plus devices right next to the Hub and Include them, and then move them to their final location. If you are trying to include a Plus device, it must route completely to the Hub using only Plus devices. It is generally better to also move these devices right next to the Hub and Include them, and then move them to their final location.

Same issue here. Aeotec 7 extender and causes issues with zwave mesh. I added them to my c7 without security and they both stop working after couple hours.
I look them up uder zwave devices and they dont show any connection/bandwidth status.

So i removed them both and ran zwave repair now my mesh is working fine.

For what it’s worth when I bot my C7 I purchased three ring S2 extenders on @bcopeland early recommendations. Nothing else I’d paired in S2 except my door lock but I do have only zwave plus devices.

Originally I was quite disappointed that NOTHING was routing through my extenders. More than a week later a couple devices were using them. Weeks later I now have over a dozen devices using them. I just ordered two more yesterday because the back upstairs corner of my house is being finicky and I’m hoping they will help me out.

3 Likes

Thank you for posting this. More people need to see this and understand that Z-Wave Plus decides its own routes over time. The problem is people have these old experiences with Z-Wave non-Plus devices and the way the two should be handled is not the same. Applying old knowledge to new devices just makes people chase their tails and click Repair constantly when it's not needed. Patience and time is what is needed with these newer generation of devices.

5 Likes

Yes! What you said! Also that the hubs "concept" of neighbors (devices that are id'd as good routes to go through) and our real world experience can be completely different things. The devices themselves don't physically know that they exist right next to other devices rather they have a table of initial good routes that get set during an include and are then adjusted over time due to various algorithms. That is my current albeit limited understanding of the situation.

I also have noticed that some devices for whatever reason get stuck with bad routes that persist over reboots and time. The only way to resolve those seems to be an exclude/include.

3 Likes

I would also update the firmware for aeotec range extender 7 firmware update 1.03 which seem to fix a lot of my issues with C7 with S2

Isn't it 1.3? Mine shows 1.3
image

So I think that means it is on the latest firmware... it's just displaying oddly. I get the same with the Zooz firmware reporting..

I just paired earlier with security and updated to the latest firmware but it's not showing at all..

I believe that’s a bug (feature) of the built-in Aeotec RE7 built-in driver, because mine report like yours do, @erktrek, on the built-in driver. Denny Page’s (@dennypage) RE7 driver reports firmware level, as also does the “Device” driver.

1 Like

Yep can confirm @dennypage's driver reports firmware just fine (as "1.3")

Thank you!