Improve duration formatting

[piitaya]

Proposed change

• Merge format_duration.ts and duration.ts files
• Use duration formatting in entity card to be consistent with other cards
• memoize formatDurationLong
• Fix media_duration formatting (bug introduced with Use explicit duration format for state formatting #23017)

Entity card example

Partial fix for #21346 (graph tooltip is not part of this PR as it requires more work)
Partial fix for #20533 (time default formatting is not part of this PR)

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[ntompson]

Handling of durations seems to have gone backwards since this update. For example:

I don't have pre-upgrade screenshots, but I'm pretty sure these were formatted more reasonably (hours, minutes and so on).

[piitaya]

The old format was hh:mm:ss and didn't use the unit of measurement.

With the new update, the unit of measurement is taken into account. You can choose the unit using the entity settings. What integration are you using? May be it needs a update to provide the right unit by default.

[ntompson]

Ok great! I didn’t realise that would work. These examples come from ESPHome projects I’ve built myself; they are configured as durations in seconds in ESPHome config. But your method works nicely, so thanks

[craibo]

Good day

Can we please get this reverted.

The unit of measure is what the base value is provided in.

For activity sensors where the duration can range between seconds to minutes to hours to days for the same entity value, you cannot hard set the unit of measure.

The dynamic formatting which handled these scenarios was very beneficial in these cases.

A different approach is required here please.

Thank you

Bug ref #23338

[craibo]

Good day @piitaya, @bramkragten

After further discussion on #23338 would it be possible to by default use the previous functionality that automatically formatted the value in a human readable way.
Then the users can decide to use your unit of measure enhancement to override this and force the unit of measure to be used for display?

Also the unit of measure selection field is not showing for me to select on the latest version.

Thank you

[jouster1974]

I'm seeing some issues with the new formatting in an integration that previously worked fine with activity lengths being shown in hours, minutes and seconds..whereas now it just shows in seconds.

Please see my further info from my previously logged bug below

Since 2024.12, the time duration seems to have changed to only seconds...and it no longer appears to be possible to change this after a core change, so its no longer possible to show duration in hours, minutes and seconds

For clarity, no further core updates have reverted this issue and from this thread it appears this has been done by design