How can I limit the display value of a sensor?

[snook (Ryan Snook)]

Hello, pretty new to Home Assistant. I would like to know how to limit my temperature displays to 1 or 2 decimal places. Thank you.

cards:
  - entity: climate.entryway_thermostat
    name: Thermostat
    type: thermostat
  - cards:
      - entity: sensor.bedroom_temperature
        name: Bedroom
        type: sensor
      - entity: sensor.hue_motion_sensor_1_temperature
        name: Kitchen
        type: sensor
    type: vertical-stack
type: horizontal-stack

[tom_l]

You limit it in the integration definition not the Lovelace card.

[Markus99 (Mark)]

I believe you have to create a new template sensor to format to your liking (if you’re unable to format (per @tom_l’s comment above) in the integration itself.

Remove temperature gauge decimal places

I’m quite new to Home assistant, so this may be a relatively easy questions. How do I remove the to decimal places from the end of the temperature gauge I have on the overview page? [Screenshot%20from%202019-08-25%2018-15-07] I would like it to just display 74 F I am using a Hue motion sensor (sensor.entry_motion_sensor_temperature) Thanks!

[tom_l]

That will usually work but the correct way is shown by Phil here:

How to round the result of adjusted temperature

This usually works, but in some cases you can still get a lot of digits after the decimal point due to float precision. It’s generally better to do this: {{ '%0.2f'|format(states('sensor.varasto2_osram_temp')|float + 0.7) }}

[snook (Ryan Snook)]

Thank you, don’t know why search fu was unable to find those previous threads.

[Bart_Huitsing]

I experience this template workaround as non-intuitive.

A sensor stands for data, a card/badge stands for representation of that data to the end-user. I don’t want to limit the digits in the integration as you then lose accuracy.

The process is non-intuitive, as I must create a new (forked) sensor with the only purpose to represent the value on a card in lovelace. This gives me a bad user experience. For my solar panels, I now need to have two template sensors: one for the badge (zero digits) and one for a sensor card (1 digit). This means extra data in your database/list with all sorts of “postfix sensors” (e.g. sensor.solaredge_current_power, sensor.solaredge_current_power_0digits and sensor.solaredge_current_power_1digit). You could consider as database pollution, but at least increased maintenance of your data.
I don’t want to ignore that there are other use cases that justify the creation of a template sensor, but to my opinion it should be an option on the card to simply limit the number of digits.

It now works, but hope that in the future it would be possible to enhance this.

[tom_l]

It is a feature that has been requested. You can vote for it here:

Formatting numbers in Lovelace

It would be nice to be able to format the numbers that Lovelace displays in various ways. Primarily the formatting would use the comma to delineate powers-of-a-thousand and use the period or full-stop to indicate the decimal point or, as in some places, the reverse where the comma and period swap duties. I thought additionally it might be nice to be able to format the numbers in scientific notation. However, this seems less useful in the normal workings of the average HA install. I’m not a progr…

[parautenbach (Pieter Rautenbach)]

Since March this is available via the UI: sensor display precision.