Set zwave_js voltage sensor suggested precision

[MartinHjelmare]

Breaking change

Set suggested precision to 0 decimals for voltage sensors with native unit in V. This will uniform the display precision of voltage sensors where there otherwise seems to be a variety of precision reported from different devices.

If you want to change the precision you can do that in the sensor options in the GUI or with a template sensor.

Proposed change

• Set suggested precision to 0 decimals for voltage sensors with native unit in V. I don't own any sensors that report in mV so I haven't changed that sensor.

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 Ruff (ruff format 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/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!

Code owner commands

Code owners of zwave_js 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 zwave_js Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[raman325]

why are we going with 0? Are we looking for the least common denominator so that they all match? I would expect that by default users would want more precision than that, but maybe that is just me

[MartinHjelmare]

I was only considering AC voltage where my assumption was that you don't care if the voltage is fluctuating less then a Volt in household applications. The voltage for my Aeotec smartplug connected to a wall socket fluctuates between 215 and 228 V, normally.

For DC voltage you probably want 2 decimals, but I don't have a single Z-Wave sensor that measures that so I assumed it isn't very common. Battery level sensors are common but they all measure percent.

[raman325]

I was only considering AC voltage where my assumption was that you don't care if the voltage is fluctuating less then a Volt in household applications. The voltage for my Aeotec smartplug connected to a wall socket fluctuates between 215 and 228 V, normally.

For DC voltage you probably want 2 decimals, but I don't have a single Z-Wave sensor that measures that so I assumed it isn't very common. Battery level sensors are common but they all measure percent.

makes sense and I don't think there is a structured way to know if a multilevel sensor is AC or DC so I guess this default makes sense