Move uptime from relative time to absolute time

[chemelli74]

Breaking change

In order to optimize stability and performance of HomeAssistant, sensors should use only absolute time values (store the date of the event) and not relative time values (seconds from event) so the db value doesn't change each seconds.
"uptime" integration is one leftover, so to adhere to HomeAssistant development rules, the sensor is now changed to a timestamp.
Please review your lovelace config to reflect the change.

Moved uptime sensor from relative time to absolute time

Proposed change

Moved uptime sensor from relative time to absolute time

Type of change

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

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes Non compliant uptime sensor #40004
• This PR is related to issue:
• Link to documentation pull request: Removed unit of measurement from config home-assistant.io#15750

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• 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

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[yuvalabou]

But how does this new sensor tells me the uptime of the system? It will only show last boot?

[frenck]

@yuvalabou because of the device class the frontend will show the relative time. As for any other use case, the time can be calculated if needed. Essentially, knowing when the last boot was, allows one to calculate it in any way one wants.

[frenck]

Could not place a comment on the specific line, but:

_LOGGER = logging.getLogger(__name__)

Is unused.

[chemelli74]

Could not place a comment on the specific line, but:

_LOGGER = logging.getLogger(__name__)

Is unused.

You are right, strange flake8 didn't notice.

Simone

[frenck]

I'm OK with this. I think I want a second opinion from @balloob on this one. Mainly because of the impact of the change.

[balloob]

Nice!