Bring back Display Precision override or offer a UI-based alternative

[Majed-BX]

🧩 Problem Summary
After updating to Home Assistant Core 2025.6.0, the "Display precision" setting in the UI no longer affects how values are displayed for many entities — especially those with a device_class or a suggested_display_precision.
This appears to be an intentional design change where the frontend now prioritizes internal logic over the user-defined setting.

❗ Why this is a real problem
This change breaks the expected behavior of the UI and negatively affects user trust:

• Users expect "Display precision" to control the number of decimal places shown — but now it’s silently ignored.
• The only way to show something like 15.13 instead of 15.13975 is to create a Template Sensor.
• This adds unnecessary complexity, especially for non-technical users who rely on the UI and avoid YAML altogether.

🎯 What the developers intended
Based on release notes and blog posts, the goal seems to be unified formatting across the system using fallback values derived from device_class or suggested_display_precision.

While that may sound like a smart backend optimization, it removes visible control from the user — and makes the UI feel misleading when an option does nothing.

💡 What should be done?
✅ Option 1 (Recommended): Restore full functionality to the "Display precision" setting in the UI, making it override any internal or fallback precision.
This is the preferred solution because:

The default value can still be the full precision (as determined internally), but the user should be allowed to reduce the precision via the UI — without having to create a template sensor.
This matters especially for non-expert users who see such workarounds as unnecessary complexity that harms their experience and gives them a negative impression of the platform.

❌ Option 2: Remove the "Display precision" setting entirely and clearly document the reasoning.
This is not a good option, unless it’s paired with a simple and user-friendly alternative.

Real improvements don’t come from removing features — they come from making them easier to use.
No user should have to rely on YAML or templates just to round off a number display.

✅ Summary:
Either restore the "Display precision" setting and make it functional again (with default values showing full internal precision),
or remove it and provide a simpler alternative — without forcing users into YAML.

[karwosts]

Can you give examples of which entities are newly ignoring display precision, and where in release notes / blog posts it was described that this was intentional?

I don't recall seeing anywhere that this was intentionally degraded.

[Majed-BX]

https://developers.home-assistant.io/blog/2025/05/26/sensor-default-display-precision/

[karwosts]

That's a custom card in your screenshot, we have no control over how entities are displayed in custom cards.

Open an issue with the cards developer and ask them to respect the display precision.

[Majed-BX]

You're right that the card shown in the screenshot is a custom card. However, as described in the official developer blog post, the actual change was deeper:

• Sensors now return the raw unrounded value, and the automatic rounding that used to happen during unit conversion has been removed.
• Custom cards like button-card previously relied on the state, which was pre-rounded and ready for display.
• But now, since state contains the raw value, any custom card that doesn't explicitly apply display_precision will end up showing full-precision floats like 15.1397597184 instead of 15.14.

This effectively means that all custom cards need to be updated or redesigned to read and respect display_precision — otherwise they’ll ignore user settings and display raw, noisy values.

But let’s be realistic:
There are many custom cards in the ecosystem, and updating them all will take time — some may never be updated at all.

Wouldn’t it be more practical to keep the display_precision behavior as it was before, and simply ensure that the default value shown is the full raw precision?

That way:

• Users who want fewer decimals can still adjust it easily from the UI.
• Custom and official cards alike can display values correctly using state, without requiring extra logic.

This strikes a balance between developer consistency and user experience — without adding unnecessary complexity for either side.

[karwosts]

I haven't fully ingested what that change means, but it wasn't even a frontend change, it was a core change, so there's nothing can be done in this frontend repository about it.

Core changed entity state to always contain the full precision. If you want to discuss implications, maybe you can mention it in the monthly release thread, get some more opinions.

It's a pretty well established HA policy that custom cards are not considered when decisions are made for HA architecture. We are developing for core HA, custom cards can adapt or not, but they don't influence architectural direction. 🤷

I'm doubtful anyone will be interested in reverting changes because of custom cards.

[Majed-BX]

Thank you for the clarification and for your quick response — I really appreciate it.

Your explanation makes perfect sense. I now understand that this was a core-level change, and that custom cards are not part of the architectural decision-making process.

That answers my concern, and I’ll adapt accordingly.
Thanks again — I'll go ahead and close the discussion.