Understanding Z-Way Diagnostic Numbers

[mango]

Apologies in advance for the long post, but im hoping my questions here are useful to others wanting to learn more about the features of Z-way's diagnostic tools. I was very impressed by the Youtube presentation and just wanted some explanations on how to interpret certain values (unfortunately there isnt much information on the zway essentials book on this topic). Rather than having to pause frame the video to learn certain aspects about the tool, it would be good if the dev team can probably document this for easier reading.

The information below is based on my network with 100% powered devices, and I have questions based on the different tools available.

Delivery Statistics:
If Delivery is < 100% e.g. 80%, 90% - should that be a concern?
So green number represents fast and > 200 (black) is re-trying routes, what does 11 (lowest black number i can see)-199 represent?
If we have regular, say 1 in 10 (red) undelivered packets, is it a 'good indication' that the node is defective?

Neighbor Map:
If i have a node, that contains only 1 or 2 potential routes i.e. green (is that a good indication of a bad node?) - given its quite close to the controller. Generally my understanding is, there should be more green then red, unless its communicating from totally opposite ends of the house. Some of my nodes contain > 70% red neighbors.
Does updating the node neighbor table improve or alter the routes? or its just for visibility?
Black Dot Associations - in a small space, is it necessarily a bad thing that routing is enforced? i.e. its a Red Dotted Cell

Route Map:
Rerouted Value - Higher the better or Lower the Better? Expected value under normal/efficent operating conditions? I have a node that shows '250% Rerouted'
Explorer Frames Rate - Higher the better or Lower the Better? Expected value under normal/efficent operating conditions?
Dashed Line - Does this represent an issue between the nodes on a dashed line, or potentially rerouted paths between the nodes?

Noise Graphs:
My understanding from the video is a value between -80 and -90 is within the normal operating range. My Z-wave network is reporting a range between -90 and -50 with regular peaks and troughs. My understanding is that this is undesirable, but the only other thing i can think of that might interfere is Wifi and a Zigbee controller close by.

Transmitter Statistics:
Is there a way to dwelve into the CRC statistics to establish which nodes are getting these errors? That information does not seem to be available under Zniffer History page.
My backoff ratio is currently 2.6 i.e > 2, despite Foreign Network Impact at 99.97% and Success of Reception at 96%, and 3% in CRC error - im assuming this is related to the environment noise

[PoltoS]

Have you checked this?
https://www.youtube.com/watch?v=kW8UXYx ... EIXW8cqdN4

Delivery Statistics:
Failures are bad routes or end of the range - bad for user experience.
> 200ms (20 in the table) is also bad - rerouting

Neighbor Map:
Not a problem unless there are at least few different routes to that device

Route Map:
Rerouted Value higher is worse (unstable routes). 250% means 2.5 times routes changes on each packet (in average). Really bad!
Explorer Frames Rate higher is worse. Means device was not able to reach the controller after trying all saved routes
Dashed Line represents failures in communication - routes should not contain such hops

Noise Graphs:
Everything above -75dB is bad - you have a lot of noise. -50 is the size of typical Z-Wave packet strengh - so noise kills the RF.
WiFi and ZigBee do not really affect - different range. Check other 868 devices. Connect yout RPi to a powerbank and walk thru your house to find the source of this noise. Go toward rising noise.

Transmitter Statistics:
No, this comes from the chip demodulator.
Zniffer sees only valid packets with correct CRC.
Backoff might be due to high noise indeed.

[mango]

Thanks Polto! Much appreciate you always looking out for these posts