Skip to content

Show uptime as readable text - #72

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

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
    • Uptime is now displayed as a text sensor with a space separator; the sensor-domain uptime entity has been removed.

@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: c6f9abb5-866d-4152-a357-943a8aa7b4de

📥 Commits

Reviewing files that changed from the base of the PR and between 4983129 and 3d93b26.

📒 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 configuration updates the firmware version from 26.8.27.1 to 26.9.29.1. It removes the uptime sensor and adds an uptime text sensor with a 60-second update interval and a space separator.

Changes

ESPHome uptime reporting

Layer / File(s) Summary
Firmware version and uptime entity
Integrations/ESPHome/Core.yaml
The firmware version changes to 26.9.29.1. The 60-second uptime sensor is removed and replaced with a text sensor configured with a 60-second update interval and a space separator.

Priority: ⬇️ Low

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

Change: Feature

Suggested reviewers: bunton33

Merge Risk: ⚪ Minimal · up to 3d93b

Uptime will appear as readable text instead of numeric seconds, so automations and history or statistics relying on the former numeric entity may need adjustment. The update call remains supported, and no actionable merge risk is established.

Security Architecture Review

Security architecture risk: 🔵 Low · up to 3d93b

The uptime change is an intentional breaking change for numeric consumers. The reviewed configuration does not show a new access or secret-handling risk, but deployment and rollback behavior remain unverified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

  • inferred — The demonstrated change affects the device’s reported uptime and its Home Assistant consumers. The available evidence does not quantify deployed devices or establish a wider authority change.

Trust Boundaries and Controls

  • inferred — No attacker-controlled input, new credential or authorization transition, or privileged sink is established by the reviewed changed ranges; this does not verify the security of the broader deployment path.
🚥 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 value with readable text.
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,
The text sensor reports in time.
A space joins words, the version’s new,
The config keeps its cadence true.
Hop by hop, the changes land.

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

@bharvey88 bharvey88 closed this Oct 2, 2026
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