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

The sensor is displayed with a decimal part that should not be there #333

Open
man55 opened this issue Feb 22, 2024 · 3 comments · May be fixed by #336
Open

The sensor is displayed with a decimal part that should not be there #333

man55 opened this issue Feb 22, 2024 · 3 comments · May be fixed by #336

Comments

@man55
Copy link

man55 commented Feb 22, 2024

I have sensors that are specified to display as an integer.
In the standard HOME card they are displayed correctly as an integer.
But when I use the lovelace-multiple-entity-row, these sensors are displayed with a decimal place, which is very annoying.
I tried changing regional settings, but it has no effect.

type: entities
entities:
 .....
      - entity: sensor.xxxxxxxx_fanrpm_combine
        name: fanrpm
        styles:
          width: 74px
          text-align: center
Screenshot 2024-02-22 183250 Screenshot 2024-02-22 183224 Screenshot 2024-02-22 183217
@ildar170975
Copy link

Why not using a documented native formatting option?
https://github.com/benct/lovelace-multiple-entity-row?tab=readme-ov-file#formatting

@man55
Copy link
Author

man55 commented Feb 23, 2024

Thanks, it worked.

Only now I need to add several dozen extra lines to the code :((.
And so I don’t understand why by default the mod can’t use the format that is defined in the sensor, why add a decimal to it?

@ildar170975
Copy link

And some other users do not understand why to reduce an initial accuracy of sensors in frontend globally.
Like me: there is NONE of sensors in my setup with changed accuracy; if I do not need some extra digits in a particular card - I change this in this particular card.

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

Successfully merging a pull request may close this issue.

2 participants