If it was something we decided to add it would be a per user (like the language in the profile setting that would be set per device, as its set in the local storage)

(language is a user setting, it is sent to the backend)

If it's common for your language, couldn't you do this based on languages?

think the point I'm making is, the separator might be common in computer lingo, but in many if not most other media isn't used by default. Hence an option to at least Not use it would be most obvious?

whether this can be done based on languages is not up to me, Zack and probably Bram would know best how to. I guess the language setting now changes it from 1.234,56 (Dutch) to 1,234.56 (English), so both using the separator. Again, to change that would need an option, for both.

There's a button for that:
image

at first glance that is what I believe too indeed, but as you can see it shows a decimal dot between 7 and 8.

even figured tot to be the thousand indicator or so, but all number entities still show a decimal.

Maybe I am completely missing the point, but as far as I can see we have no way in the number settings to disable that decimal globally

Geen (none) should be 123456789 and not 1234567.89

Ok I thought this was just about the thousands seperator... why would you remove the decimal seperator? Then you can't even differentiate fifteen versus one-and-a-half, it totally obfuscates the result.

I see now that None doesn't use your localized decimal seperator though, so yeah maybe that's not what you wanted.

of all of the number entities I'd like to show decimals on a fraction of those

all of my energy/power sensors can be in whole numbers for what I care. as would brightness stuff .

Probably some volume levels that are in 0 to 1 scale need decimals, so Id set that on those individually

timing might need some thought, depending on the scale being seconds or minutes/hours

temperature might be the most interesting class for decimals, but I set those to show but 1, as no sensor is actually that precise to begin with....

guess what this boils down to is when do we need to clutter the views with imprecise decimals

Then you can't even differentiate fifteen versus one-and-a-half, it totally obfuscates the result.

I dont understand why you'd say that. 15 would show as 15, one-and-half would show as 2 probably, depending on your rules of rounding. the device class would make that either a great loss (in which case one would override the global setting to show 1 decimal), or completely sufficient (power/energy/brightness, even temperature...)

I guess I got confused, at first you were talking about removing the thousands seperator with the laundry/lumens example, and then at some point this became about rounding decimals.

Tbh, you’re probably right about the confusion....
I did show the correct decimal setting in the opening post but next continued with a separator....

separator is indeed settled.
Decimal not as far as I am concerned