Add inclusion state to zwave_js/network_status WS API cmd

[raman325]

Proposed change

In order to resolve #61855 the frontend needs to know the current inclusion state when opening the configuration page.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @home-assistant/z-wave, mind taking a look at this pull request as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[MartinHjelmare]

Looks good!

[MartinHjelmare]

For future readers, the value is an IntEnum:
https://github.com/home-assistant-libs/zwave-js-server-python/blob/47124d7670cfbff7f5edc0f002579efa67dc1eb2/zwave_js_server/const/__init__.py#L269-L277

[raman325]

should I explicitly use controller.inclusion_state.value to make it more clear?

[MartinHjelmare]

I don't think it matters. It will be converted to a number by the json serializer before the websocket consumer gets it. It's the possible values that may be interesting and those aren't shown anyway by the code here.

[MartinHjelmare]

CC @bramkragten

[MartinHjelmare]

We'd like the frontend, if inclusion/exclusion is in progress, show a cancel action instead of the add/remove action.

[MartinHjelmare]

Converting to draft until frontend team approves.

[raman325]

One other frontend quirk I noticed when I started looking into this is that we check for the connecting status in a bunch of conditionals (example https://github.com/home-assistant/frontend/blob/dev/src/panels/config/integrations/integration-panels/zwave_js/zwave_js-config-dashboard.ts#L116)

But the property that's being read can only ever be connected or disconnected (https://github.com/home-assistant/core/blob/dev/homeassistant/components/zwave_js/api.py#L370) so I don't think this code is working unless I am missing something.

[MartinHjelmare]

Frontend PR is merged.