Skip to content

Show uptime as readable text - #116

Open
bharvey88 wants to merge 1 commit into
betafrom
readable-uptime
Open

bharvey88 wants to merge 1 commit into
betafrom
readable-uptime

Conversation

@bharvey88

@bharvey88 bharvey88 commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Version: 26.9.29.1

What does this implement/fix?

Replaces the numeric Uptime sensor with ESPHome's built-in uptime text sensor, so Home Assistant shows uptime as 3d 4h 12m instead of a raw count of seconds. Thanks to @kernelpanic85 for the idea in ApolloAutomation/R_PRO-1#72.

  • Uptime is now a text entity. Its history graph and long-term statistics stop, and any automation or template that treats uptime as a number needs updating.
  • Home Assistant sees it as a new entity. The old numeric Uptime entity will show as unavailable and can be deleted.
  • The ID stays sys_uptime, so component.update: sys_uptime in the report scripts still works.
  • At the 60s update interval ESPHome leaves seconds off, so uptime under a minute reads 0m. Battery devices that sleep right after reporting will usually show 0m.

Types of changes

  • Bugfix (fixed change that fixes an issue)
  • New feature (thanks!)
  • Breaking change (repair/feature that breaks existing functionality)
  • Dependency Update - Does not publish
  • Other - Does not publish
  • Website of github readme file update - Does not publish
  • Github workflows - Does not publish

Checklist / Checklijst:

  • The code change has been tested and works locally
  • The code change has not yet been tested

If user-visible functionality or configuration variables are added/modified:

  • Added/updated documentation for the web page

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Improvements
    • Updated the ESPHome integration package to version 26.9.29.1.
    • Uptime is now presented as a text value, with spaces in its formatted output, instead of as a numeric sensor. This changes how uptime appears in compatible dashboards and automations.

@bharvey88 bharvey88 added the breaking-change Breaking change label Sep 29, 2026
@coderabbitai

coderabbitai Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: c2529792-4cab-47ed-b188-378f69b23338

📥 Commits

Reviewing files that changed from the base of the PR and between e6d4cf1 and 92decda.

📒 Files selected for processing (1)
  • Integrations/ESPHome/Core.yaml

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.


Walkthrough

The ESPHome package version changes from 26.8.27.1 to 26.9.29.1. The uptime sensor moves from sensor to text_sensor and uses a space separator for formatted output.

Changes

ESPHome configuration

Layer / File(s) Summary
Update uptime sensor declaration
Integrations/ESPHome/Core.yaml
The uptime sensor moves to text_sensor, retains a 60-second update interval, and uses a space separator. The ESPHome package version changes to 26.9.29.1.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Feature

Suggested reviewers: bunton33

Merge Risk: ⚪ Minimal · up to 92dec

Uptime becomes formatted text, so numeric Home Assistant automations and history/statistics require migration as disclosed. No concrete in-repository compatibility issue was found, leaving no known issue that blocks merging.

Architecture Summary

Architecture risk: 🔵 Low · up to 92dec

The change affects 1 system.

Changed systems: Integrations

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — Integrations (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in Integrations/ESPHome/Core.yaml: The package version changes from 26.8.27.1 to 26.9.29.1.
  • observed — Modified behavior in Integrations/ESPHome/Core.yaml: The uptime sensor declaration is removed from the sensor section; it previously exposed uptime with a 60-second update interval.
  • observed — Modified behavior in Integrations/ESPHome/Core.yaml: The uptime sensor is added under text_sensor with a 60-second update interval and a space separator for formatted output.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: displaying uptime as readable text instead of a numeric value.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

I’m a rabbit, ears held high,
I watch the uptime text go by.
A space now joins each time it shows,
The package gets an update dose.
I hop through YAML, neat and bright,
Then nibble clover through the night.

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking-change Breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant