Uptime badge showing date instead of relative time

[tyjtyj]

Checklist

• [x ] I have updated to the latest available Home Assistant version.
• [x ] I have cleared the cache of my browser.
• [x ] I have tried a different browser to see if it is related to my browser.

The problem

Uptime badge showing timestamp instead of relative time.

Expected behavior

Uptime badge show time relative like xxx ago.

Steps to reproduce

add uptime as badge

Environment

• Home Assistant release with the issue:
• Last working Home Assistant release (if known): 0.18.4
• Browser and browser version: Chrome latest
• Operating system: Win 10, android

State of relevant entities

- platform: uptime
  name: 'Hass Uptime'

Problem-relevant configuration

Javascript errors shown in your browser console/inspector

Additional information

[spacegaier]

Did it previously show something other than the timestamp? Given that there is not much space in a badge, basically everything we put int here will get ellipsis during rendering. So I am not sure if an uptime sensor as badge makes really sense to begin with.

If the uptime sensor is used as an entity row, then we show the relative time instead.

[tyjtyj]

It shows 0.1 days(unit measurements: day. But this setting has been removed.

[spacegaier]

Was that setting on the sensor or on the frontend badge YAML? Could you also select other units? If you were to choose hours the values would get a lot longer.

[tyjtyj]

On yaml 0.18.5

- platform: uptime
  name: 'Hass Uptime'
  unit_of_measurement: days

As part of breakfix in version 2020.12.1, unit of measurement has been removed. The sensor is now timestamp.

This is how it look like in version 2020.12.1

This is version 0.18.5

[coolguymatt]

The same thing happens with the entity card (but works fine with the entities card). It also happens for any sensor with device class timestamp.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.