Improve Z-Wave heal network feedback

MartinHjelmare commented 1 year ago

Checklist

[X] I have updated to the latest available Home Assistant version.
[X] I have cleared the cache of my browser.
[X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

This issue is the result of a meeting about current issues that blocks Home Assistant from becoming Z-Wave certified.

The heal network command, reached from the Z-Wave config panel, only shows a general progress indicator without further information.

Describe the behavior you expected

The heal network command needs better UI feedback. We want to see the progress of the heal command among the devices in the network.

The progress of the network heal, is available from the backend with the zwave_js/subscribe_heal_network_progress websocket command. The returned data is an object with the node id of the nodes and a string with the node heal status.

{
    "event": "heal network progress",
    "heal_node_status": {
        "2": "pending",
        "3": "done",
        "4": "failed",
        "6": "skipped"
    }
}

For more information about the command, see:

https://zwave-js.github.io/node-zwave-js/#/api/controller?id=beginhealingnetwork

Steps to reproduce the issue

Go to the config panel of the Z-Wave integration.
Press Heal Network.
Press Start Healing.
See lack of detailed progress indicator as the heal progresses. ...

What version of Home Assistant Core has the issue?

core-2023.7.0.dev0

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Google Chrome Version 114.0.5735.133

Which operating system are you using to run this browser?

Ubuntu 20.04

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

Tested in Firefox 111.0.1 and Google Chrome Version 114.0.5735.133.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 9 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 6 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 3 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

home-assistant / frontend