Skip to content

Show uptime as readable text - #50

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

  • Bug Fixes
    • Improved uptime display formatting with a space separator. The uptime value continues to update every 60 seconds.

@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: 57c71c5b-28e7-459b-b32e-dee9d7cdc501

📥 Commits

Reviewing files that changed from the base of the PR and between 9ff544d and d02530a.

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

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


Walkthrough

The ESPHome firmware version changes from 26.8.27.1 to 26.9.29.1. The uptime entry moves from sensor to text_sensor, retains its 60-second update interval and sys_uptime ID, and adds a space separator.

Changes

ESPHome Configuration

Layer / File(s) Summary
Firmware version and uptime configuration
Integrations/ESPHome/Core.yaml
The firmware version changes. The uptime entry moves to text_sensor and uses a space separator. Its 60-second update interval and sys_uptime ID remain. The ESPHome uptime sensor is removed.

Priority: ⬇️ Low

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

Change: Feature

Suggested reviewers: bunton33

Merge Risk: ⚪ Minimal · up to d0253

Uptime will be exposed as readable text instead of numeric seconds; consumers relying on numeric history or automation need to adapt, as documented. No unresolved merge-blocking issue remains.

Architecture Summary

Architecture risk: 🔵 Low · up to d0253

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 configured firmware version changes from 26.8.27.1 to 26.9.29.1.
  • observed — Modified behavior in Integrations/ESPHome/Core.yaml: The uptime sensor is removed from the sensor configuration; its 60-second update interval and sys_uptime ID are retained in the new text_sensor entry.
  • observed — Modified behavior in Integrations/ESPHome/Core.yaml: A 60-second uptime entry is added to text_sensor using sys_uptime, with a space as the formatted-output separator.
🚥 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: replacing the numeric uptime sensor with readable text output.
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

A rabbit checks the uptime line,
A space now marks the time,
The firmware number hops ahead,
The sensor finds a text home,
All set beneath the moon.

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

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