Decimal Places display issue in 'entities list' card

[johnBoy (john R)]

I created some ‘input number helpers’, to store some wind values provided from AccuWeather.
(The values have a step setting of 0.1 - if that’s of any relevence).

There is an automation, triggered once a day, which copies the required values, all of which are shown on two dashboard, entity list displays. (Source on the left, target on the right).

This works fine, if the default units are used in the source display. In this case, km//h.
(Shown here for ‘speed day 1’ and ‘speed day 2’).

The decimal places in the source display are all set to 1dp, apart from:-

speed day 1 - is set to default
speed day 2 - is set to 1dp

Both of these show as 1dp in the copied display. (As shown here). Which is good.

But if I change the units in the ‘source’ display from, km/h to mph, the values transferred to the target list, have many decimal places, no matter what the decimal place selected. (Only 1 required).

Is this a bug, or do I need to do something to limit what is copied?

(Incidentally, hovering over a copied value produces the popup as shown, but is of no concern).

[AshaiRey]

I wonder if it could be this.
What are your locales settings?
Because 19 point 7 km/h is written with a , as decimal marker and the . Are just markers for ease the reading in parts of thousand.
Like 1.900,56

[johnBoy (john R)]

UK.
I can’t see any comma separators in these values.
There are when pressure values are displayed, when above 1000hPa.
But then, there are no decimal places involved.

I think the built in conversion is causing the extra digits. It would make sense. Dividing the original number by a scaling value, could result in this. But as the dp function is built into the entities display function as a feature, it should respect it.

Maybe?

[johnBoy (john R)]

Ok. So it might be ‘a bug’, but it’s easy enough to fix by adding ’ , rounded=True’ in the yaml.

EG.
"{{ states (‘sensor.home_wind_speed_day_4’ , rounded=True) }} "

No worries…