Is there any documentation about how this should work? If I choose a device and the node to test on is controller I get a rating of 0/10. The device works though.
I can’t speak for OP but I see something weird on my end depending on what type of device I check which kinda determines if I get 0/10 or 10/10 ratings…
Here is a zen23 light switch, getting 0/10:
it’s not doing too badly, and going from the controller to the node has 0/10 failures, but it also tests from the switch to the node and gets 10/10 failures.
A nearby Zen73 gets 9/10 but looks largely the same as the Zen23, except no return trips are tested.
I’m not sure if this is different reported capabilities of the Zen23 vs Zen73 and if it’s something I could remedy myself, but maybe this is what OP is seeing as well. Just wanted to point out an odd scenario where things could be seemingly okay but still have ‘bad’ health.
Similar experience. This is for a device (Smart Switch 6) just 2 meters from to the controller.
Did anybody get their head around this report?
bringing this thread back from the dead, sorry! Having the same issues myself. Wondering if anyone found a resolution?
Here is my setup
Home assistant > Aeotec Z-Stick 7 Plus > Schlage Connect zwave deadbolt lock.
The lock is 8 feet away from the Z-Stick. The lock works, but the health check is very concerning to me. I too get 0/10 ratings with very large max latency numbers.
Any news regarding this? Same issue here…
So the health check looks as 6 different metrics and assigns a score of 0-10 to each metric. Your lowest score becomes your overall score which is what is displayed in the rating column. On the health check window everything is color coded so red is bad, orange is okay and green is good. The reason why you probably got a 0/10 is because of your latency. Locks are FliRs devices which means they wake up every second to check if there is a message waiting for them. Even though you might get a 0/10 this is the normal behavior for those types of devices so I wouldn’t be concerned.