"Getting new neighbor list failed" on many devices

[AutoFrank 372]

Hi

If I try a mesh reconfiguration on a node/device I get the following...

Please login or register to see this code.

Its the same if I try any node

 

Has anybody seen this and have any suggestion

 

Thanks... 

 

EDIT

If I have a bad node/device - Do I mesh reconfigure it or a neighbor ?

Has anybody done a full zwave mesh reconfiguration >

 

Edited April 30, 2017 by AutoFrank

[Sankotronic 2,370]

Hi Frank,

 

I usually do mesh reconfiguration for first neighbor that is closer to the HC2 and then for the node that makes troubles. For example, I had one door/window sensor on the attic that was lately reported as dead. I first did mesh reconfiguration for the nearest wall plug and then again for both door/window sensors on attic, the one that was never reported as dead and the one lately reported dead. Of course I do this with laptop on the site since battery operated devices must be woken up during reconfiguration. After doing this it looks good for now.

[AutoFrank 372]

16 minutes ago, Sankotronic said:

Hi Frank,

 

I usually do mesh reconfiguration for first neighbor that is closer to the HC2 and then for the node that makes troubles. For example, I had one door/window sensor on the attic that was lately reported as dead. I first did mesh reconfiguration for the nearest wall plug and then again for both door/window sensors on attic, the one that was never reported as dead and the one lately reported dead. Of course I do this with laptop on the site since battery operated devices must be woken up during reconfiguration. After doing this it looks good for now.

 

@Sankotronic

Thanks,

I'm going to try a few of those this evening and see if it improves things

[AutoFrank 372]

Hi,

I just tried this on one MS6 and got the following

 

Please login or register to see this code.

Is it normal to fail and then succeed ?

 

 

Edited May 2, 2017 by AutoFrank

[petergebruers 1,268]

1 minute ago, AutoFrank said:

Hi,

I just tried this on one MS6 and got the following

 

Please login or register to see this code.

Is it normal to fail and then succeed ?

 

Yes.

No.

Yes.

 

 

I think it does that on 4.120 and 4.121, I can confirm it. I think the explanation is that they introduced a timeout. But the command sometimes takes a bit longer on networks with many nodes than with 10 so now we get this odd result. I haven't discussed it with support yet. I'm assuming it's working! The important message is the last one.