8000 Non compliant uptime sensor · Issue #40004 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Non compliant uptime sensor #40004

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
chemelli74 opened this issue Sep 12, 2020 · 4 comments · Fixed by #43623
Closed

Non compliant uptime sensor #40004

chemelli74 opened this issue Sep 12, 2020 · 4 comments · Fixed by #43623

Comments

@chemelli74
Copy link
Contributor

The problem

As found during another integration development, the uptime sensor of HA stores an absolute value and not a timestamp as core rules require.

Environment

  • Home Assistant Core release with the issue: 0.114.4
  • Last working Home Assistant Core release (if known):
  • Operating environment (OS/Container/Supervised/Core): Docker
  • Integration causing this issue: uptime
  • Link to integration documentation on our website: https://www.home-assistant.io/integrations/uptime/

Traceback/Error logs

-

Additional information

image

@probot-home-assistant
Copy link

uptime documentation
uptime source
(message by IssueLinks)

@frenck
Copy link
Member
frenck commented Sep 14, 2020

Yes, this is a leftover from the old day.

@AlecRust
Copy link
AlecRust commented Dec 14, 2020

This now isn't really "time since the last Home Assistant restart" despite what docs says, it's "date of last boot".

Don't we already have "date of last boot" at system_monitor.last_boot? I now don't see the purpose of Uptime integration, the relative time only shows in the Lovelace output the sensor is just a timestamp.

@frenck
Copy link
Member
frenck commented Dec 15, 2020

@AlecRust If you have a new issue, please create a new issue. Thanks 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
0