device class duration sensors are using wrong unit_of_measurement about dreame-vacuum HOT 3 CLOSED

I did some tests with changing the unit_of_measurement - and noticed, that it's looking better when it is like it is right now.
Changing the "hr" to "h" as given in the specs, would change how the Entities List will display the value...

Unfortunately, with the current Setup, the unit of measurement will not be translated, which is looking a bit weired in a translated UI...

:-(

from dreame-vacuum.

I've searched a bit deeper... and one thing isn't quite clear to me:

why does the integration use different units here?

I think, it would make sense to implement some calculation logic like:

if value > 24 hrs --> use days
else use hrs.

this is what's given in the core/const.py

TIME_MILLISECONDS: Final = "ms"
"""Deprecated: please use UnitOfTime.MILLISECONDS."""
TIME_SECONDS: Final = "s"
"""Deprecated: please use UnitOfTime.SECONDS."""
TIME_MINUTES: Final = "min"
"""Deprecated: please use UnitOfTime.MINUTES."""
TIME_HOURS: Final = "h"
"""Deprecated: please use UnitOfTime.HOURS."""
TIME_DAYS: Final = "d"
"""Deprecated: please use UnitOfTime.DAYS."""
TIME_WEEKS: Final = "w"
"""Deprecated: please use UnitOfTime.WEEKS."""
TIME_MONTHS: Final = "m"
"""Deprecated: please use UnitOfTime.MONTHS."""
TIME_YEARS: Final = "y"
"""Deprecated: please use UnitOfTime.YEARS."""

So - I think it should be possible to calculate the values not only for days and hours, but for weeks or years...
Or does the robot provide the values in days and hours?

After changing the Unit_of_measurement from "days" to "d" and "hr" to "h"
I am getting this

before:

from dreame-vacuum.

I did some tests with changing the unit_of_measurement - and noticed, that it's looking better when it is like it is right now.

I did think the same thing and thats why this is implemented this way.

why does the integration use different units here?

All of the values directly read from the device and some values implemeted as days instead of hours on the device itself for keeping it under 16bit integer (65535). Your suggestion will result losing presicion of the values returning in hours from the device.

from dreame-vacuum.