Add WS command sensor/numeric_device_classes

[emontnemery]

Proposed change

Add WS command sensor/numeric_device_classes

Needed by frontend PR home-assistant/frontend#18099

Background

If either of the following is true, frontend should plot a graph for sensor history:

• A sensor has a unit of measurement which is not None
• A sensor has a state class which is not None
• A sensor has a device_class which is numeric

The third check is enabled by the command added in this PR

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)
• Deprecation (breaking change to happen in the future)
• 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
• I have followed the perfect PR recommendations
• 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.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (sensor) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of sensor can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign sensor Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[jbouwh]

Nice,
Thnx @emontnemery 👍

[edenhaus]

Should we add developer docs for this new WS endpoint?

[emontnemery]

Should we add developer docs for this new WS endpoint?

I don't think it's needed, we don't document the WS API. Or is the existing sensor API documented?

[edenhaus]

Should we add developer docs for this new WS endpoint?

I don't think it's needed, we don't document the WS API. Or is the existing sensor API documented?

The websocket api is only partly documented and the WS sensor endpoint is not documented. So it's fine for me

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[MartinHjelmare]

Please link the frontend PR that will use this command.

[frenck]

Frontend PR is awaiting backend, backend is awaiting frontend 😄