Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I have just updated sunsynk add on, and am now getting 2 or 3 decimal places for all values. #247

Closed
f1wade opened this issue Feb 22, 2024 · 5 comments

Comments

@f1wade
Copy link
Contributor

f1wade commented Feb 22, 2024

I have just updated sunsynk add on, and am now getting 2 or 3 decimal places for all values.

Is there a way I can change this default to be 0 decimal places, like it use to be?

I posted the below in discussions, but haven't seen any response.
and looking around the definitions, I can't see anything that suggests this has changed in there, unless its changed more internal to the add-on.

any help greatly appreciated?

Originally posted by @f1wade in #242

@RhysMcW
Copy link
Contributor

RhysMcW commented Feb 22, 2024

you can set the display precision on each sensor in HA in it's settings (hopefully the image below comes out)
image

@f1wade
Copy link
Contributor Author

f1wade commented Feb 22, 2024

@RhysMcW that works for the dashboards, but not for markdown.

I don't understand why they where all showing whole numbers mostly and occationally 1 decimal place before the update I did to both HA os, core and sunsynk the other day, moving up about 6 months of updates, so not sure exactly what change has triggered this.

@kellerza
Copy link
Owner

Probably a change on Home Assistant side as there are several changes in this area

https://developers.home-assistant.io/blog/2023/02/08/sensor_presentation_rounding/

maybe you can set suggested precision for mqtt sensors (or in the mqtt discovery payload)

@kellerza
Copy link
Owner

Is 1 decimal place a good enough suggestion for most sensors?

Hoping this will make a difference - 0cbfd61

@f1wade
Copy link
Contributor Author

f1wade commented Feb 29, 2024

Is 1 decimal place a good enough suggestion for most sensors?

Hoping this will make a difference - 0cbfd61

Maybe, on next release I'll try it.
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants