[SOLVED] Node heal fails during UPDATE_NEIGHBORS

[robmac (R Macdonald)]

@robbert

The new node, while functioning, hasn’t reported its neighbors (yet), according to OH / Habmin

This is not relevant to any routing. It is simply a report of neighbours discovered by a heal. It is in many ways a confusing thing. The actual route used could not be listed on here and it would be no issues.

@robbert

As for the old node that is removed: I have another edge device that, again according to Habmin, still has the removed node in its neighbor list and is likely to have a stale return route (that may currently not be utilized) to the controller via this removed node.

This may be possible. If this is a recent device, after a few attempts that tried to use the bad route the last working route and next working route in the return routes in this node would self heal. The controller routing table will already be corrected as the node was removed from the cotroller.

@robbert

It’s often advised on this forum and elsewhere to perform a heal after network changes, to optimize the mesh. Also, the nightly heal being enabled in the default configuration seems to suggest that’s it’s a good idea to regularly heal.

It certainly is sensible to heal after a network change but it is not always required. One thing to consider when deciding if you want to run heal regularly is to understand it is in no way an optimization process. Often after a heal the network takes a few days or weeks to settle and become optimal again. The best that can be said about heal is that it sets a working baseline position not that it sets the best possible position.

@robbert

So, my primary reason for wanting to heal these devices is having a healthy network and optimizing the mesh, deleting any stale return routes (that may not be used now, but could be used in the future).

That is a fair point and if you want to run heal I can only refer you to the workaround I use to heal and that is to remove the USB and use the PC Controller Program from silicon labs. I have posted how to use this for this purpose. Just after I posted this Chris came through saying he had made a tweak to the heal in the binding so this workaround may no longer be needed. Many thanks Chris. As always great work.

@robbert

Additionally, there is a secondary reason : I still would like to fix my ZWave network map as laid out in this topic. The general advice for fixing the map seems to heal your network/all your nodes.

Don’t you agree these are valid reasons?

The last reason not at all.

That diagram is of no help in understanding the routing in use in your network whatsoever. It is a picture of a historic moment in time of what nodes had what neighbours under very abnormal conditions. i.e. when using -6db signal to communicate. For this reason it will never show you the full potential of routing nor the route and if heal is not working is never updated. Even if you heal using PC Controller program it will remain broken but your network routing table held in your controller will be fine.

To see the actual routing table follow my instructions here

[SOLVED] Z-Wave unreliable in 2.5.0.M4

I’ve updated to the 2.5.1 snapshot linked in another thread and heal is still destroying my network causing me to have to restart my openHABIAN pi to bring all the nodes back online. You can see that my network needs to update the neighbors because the last 20 or so devices I’ve added haven’t correctly mapped their network. Heal doesn’t seem to be working on individual nodes, either. [image]

This is the view read from the controller in PC Controller Program. Even thi sis limited as it gives no information on the quality of communication.

If you want that then a network health check would be worth running

Z Wave Routing Basics

There is a lot of misunderstanding about z-wave routing. This is a very simplified bitesize description that avoids explanation of how the routes are established and managed, how preferences are defined and the types of attempts at communication that are made to get a command or acknowledgement through. It deals with the simple and ideal source route example. All of the clever things z-wave does to get the message through will be described in a later post. [image] Unlike routing in networks…