-
-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Displaying the failedPingsController attribute #3557
Comments
I don't show them when they are undefined: zwave-js-ui/src/components/dialogs/DialogHealthCheck.vue Lines 289 to 317 in 04f1c76
I dunno sincerly why sometimes they are undefined and sometimes them are not, maybe that's an issue on driver not setting them to 0 by default. cc @AlCalzone |
Wouldn't it be more relevant to display it anyway even if it's "undefined"? We have the impression that we have 0 ping losses to the controller when in reality the information is unknown. I'm in the process of improving my network and I don't feel like I've ever seen a 0/10, I wonder if it really exists, do you have it on your side or is it just mine? |
@duylong I have a feel that when missing it's 0/10, it's just the driver maybe that doens't set it. Let me talk with @AlCalzone to see what's the best solution |
Please make a driver log of a health check where they are missing, loglevel |
I ran a Health check for debugging. OK for Controller to Node, but no trace from Node to Controller. |
Ok, so this requires a bit of explanation: When it is supported, the Currently, the only situation when |
Not all that easy O:-) I just did a test again, and indeed when minPowerlevel is 0, the failedPingsController field appears. In other cases, it is not defined.
For me it would be necessary to continue displaying node -> controller to maintain display consistency, it's complicated to understand when sometimes it is displayed, sometimes not. Additionally, is there a way to detect and display when powerlevel cc is not available? This way we are not surprised by the absence of the failedPingsController information. |
@robertsLando I think this is mostly a presentation issue. Maybe we should rework the columns to make this clearer:
|
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label |
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label |
Hi,
Is the failedPingsNode attribute displayed all the time even when it's 0 ?
I ran 2 tests on the same node and once it appeared, another time it didn't.
I don't have a custom route, and I haven't done any reconstruction in the meantime. Can you explain to me ?
The text was updated successfully, but these errors were encountered: