feat(sensor): round battery voltage display to 1 decimal#270
Open
sslivins wants to merge 1 commit intobinarydev:mainfrom
Open
feat(sensor): round battery voltage display to 1 decimal#270sslivins wants to merge 1 commit intobinarydev:mainfrom
sslivins wants to merge 1 commit intobinarydev:mainfrom
Conversation
The API returns battery voltage with multiple decimals (e.g. 13.74321) which makes the dashboard look noisy. Add suggested_display_precision = 1 so HA rounds the displayed value to 1 decimal while keeping the full value in state. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tiny one-liner. The API returns battery voltage with a decimal (e.g.
13.7), but the device page in HA rounds it to a whole number, so it shows up as:Adding
suggested_display_precision = 1tells HA to render the value at 1 decimal in the UI while keeping whatever the API gives us in state for history/graphs:Last of the followups (along with #267 / #268 / #269). Take it or leave it, no worries either way.