Non-direct neighbor routing nodes fails
Hi,
I am trying to recalculate my mesh routing tables using the Network Heal tool in the Zipabox web UI. The main purpose is to get better communication with a POPP schuko dimmer module in my garage. It used to work fine, but now it's offline most of the time. I suspect that it happened after the last time I tried a network heal...
When I start a network heal, most of my mains powered devices are handled ok within a few minutes. There is one exception which is the POPP device in question. It is listed as "Other routing nodes" which is the same category as the battery powered Aeon multisensors, which I suspect do not route at all.
Is anyone familiar with the output in the attached screenshot? Should I suspect that the POPP dimmer is out of reach since it's neighbor update failed, or is it not recognized as a routing device at all? Would it be better to move it close to another device while performing the network heal and then move it back to its proper location?
Any tips are helpful since I can't find any documentation about the network heal feature.
Cheers,
Mattias
The same question
Replies have been locked on this page!