Duration-class badges do not respect unit of measurement

[mateuszdrab]

Checklist

• I have updated to the latest available Home Assistant version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

In 2024.8, a badge for a sensor with the configuration below displays '103 minutes'

Changing unit of measurement from min to millisecond reflects immediately on the card.

Describe the behavior you expected

In 2024.9, the preference for unit of measurement is ignored and the value displayed is '1:43:0'
Changing unit of measurement from min to millisecond does not reflect on the card.

Steps to reproduce the issue

Downgrade to 2024.8.

What version of Home Assistant Core has the issue?

core-2024.9.0

What was the last working version of Home Assistant Core?

core-2024.8.3

In which browser are you experiencing the issue with?

Edge

Which operating system are you using to run this browser?

Mac OS/Windows/Android

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[karwosts]

This is a side effect of removing #21755

We don't have a good solution for customizing duration formatting at this time.

[mateuszdrab]

Thanks for clarifying.

It's strange because the actual state of the entity shows as minutes, I'd hope it would just show that.

Is the output of the states in Dev Tools is already formatted?

[karwosts]

Developer-tools/states is always the raw state from the backend, that will be a number like 0.111.

In frontend device_class: duration sensors are in many places then reformatted as human readable HH:MM:SS format for display. It is the latter that generally there is no specific control for, and display_precision does not affect this.

[timdream]

This regression has caused Ping integration entities to display ping round trip time in seconds even though "unit of measurements" is set to "ms".

[N3rdix]

Just observed the same and makes some entities more or less unusable when using "d" as unit of measurement... Interesting enough that the configuration dialog respects the unit of measurement correctly (in my example 99).
Hopefully there can be a fix.

[mateuszdrab]

Just observed the same and makes some entities more or less unusable when using "d" as unit of measurement... Interesting enough that the configuration dialog respects the unit of measurement correctly (in my example 99).
Hopefully there can be a fix.

Agreed, it's a strange experience since the units are now inconsistent in various locations.