Mesh Network Reconfiguration not requesting/updating some device's neighbor list.

[max121234 0]

Hello All,

 

When i'm running the 'Mesh Network Reconfiguration' on my HC2 it skips certain devices. Basically it only requests and updates the Fibaro Dimmers in my house. Other Fibaro devices (such as Double Switch 2 and Universal Sensors) and other brand devices do not seem to have the command sent to them and therefore do not respond with a neighbour list (By the way i'm getting this information from the command line at the top of the HC2 webpage) Even if I do it per device, not whole network, i doesn't do it. You can see it do the dimmers, but nothing else. 

 

The reason i'm doing this at all is that a Double Switch 2 i have in my garage has recently stopped working on the network. It's fine when I bring it closer to the HC2 but not when in it's desired location. I've reset the device, disconnected/reconnected it from the HC2 and still only work when close to the HC2. But has previously work fine in its desired location. Which leads me to think it was using other nodes to connect to the HC2, but for some reason the mesh has changed, hence the need to 'Mesh Network Reconfiguration'. Annoying i can't get the device to perform a range test, i get the violet light, release and tap the B button, then nothing. 

 

Any help would be dearly appreciated.

 

 

[petergebruers 1,268]

It happens. Even when everything is fine. But your network probaply isn't running smoothly.

 

Please read this topic, it is long, but it is very comprehensive and based on experience and knowledge gathered over years. Stop wasting your time with anything else.

 

 

[alex88 71]

4 minutes ago, petergebruers said:

It happens. Even when everything is fine. But your network probaply isn't running smoothly.

 

Please read this topic, it is long, but it is very comprehensive and based on experience and knowledge gathered over years. Stop wasting your time with anything else.

 

 

 

Absolutely agree with @petergebruers.

 

Before I made the changes specified in the above post I had situations where many if not most of my devices failed the mesh network reconfigure. 

 

The last time I ran a complete mesh network rebuild, which BTW I never plan to do again ie I am only rebuilding it on a device by device basis as required, I didn't recall seeing any failures.

 

 

[max121234 0]

Thanks for pointing me in the right direction, much apreciated.

[max121234 0]

So i got this problem fixed, it turns out the SW2 was faulty. Using the z-range analyzer is showed theSW2 had only a 14% signal, even when close to the controller. Put a new one in and it works fine. 

 

However, i still never managed to get all my devices to update the neighbour list. There are still 3 that will not update, 2 x TKB switches and another SW2, even though they all work absolutely fine and show 95%-99% connection in the z-range analyzer.

[cag014 731]

2 hours ago, max121234 said:

So i got this problem fixed, it turns out the SW2 was faulty. Using the z-range analyzer is showed theSW2 had only a 14% signal, even when close to the controller. Put a new one in and it works fine.

However, i still never managed to get all my devices to update the neighbour list. There are still 3 that will not update, 2 x TKB switches and another SW2, even though they all work absolutely fine and show 95%-99% connection in the z-range analyzer.

First of all I glad to hear that Z-wave range analyzer "somehow" helps to indicate/identify a problem.

There is an issue with mesh reconfiguration (Fibaro team aware about it and work  on that) on some devices (especially with non-Fibaro devices). But if you have 95%-99%, it means device can "see" enough neighbors to make stable communication. Hope on next stable release mesh reconfiguration will be fixed.