Skip to content
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

[uptime] Add new timestamp type for uptime sensor #7029

Merged
merged 2 commits into from
Jul 2, 2024
Merged

Conversation

jesserockz
Copy link
Member

@jesserockz jesserockz commented Jul 1, 2024

What does this implement/fix?

This adds a new type field to the uptime sensor platform that allows a new type of timestamp which requires a time source to be configured and will send the timestamp of the boot once the time is syncronised for the first time. This gets the current timestamp of the sync and takes away the current boot millis() to get the timestamp of the boot.

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Other

Related issue or feature (if applicable): fixes

Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#4014

Test Environment

  • ESP32
  • ESP32 IDF
  • ESP8266
  • RP2040
  • BK72xx
  • RTL87xx

Example entry for config.yaml:

# Example config.yaml

Checklist:

  • The code change is tested and works locally.
  • Tests have been added to verify that the new code works (under tests/ folder).

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

@kbx81 kbx81 merged commit d8f0dce into dev Jul 2, 2024
26 of 27 checks passed
@kbx81 kbx81 deleted the jesserockz-2024-267 branch July 2, 2024 02:29
@github-actions github-actions bot locked and limited conversation to collaborators Jul 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants