Show uptime as readable text

[bharvey88]

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 #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

• Updates
  • Updated the configured ESPHome version to 26.9.29.1.
  • Uptime is now provided as a text sensor, with a space separator in its formatted output, rather than as a sensor.

[coderabbitai]

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: cfda0482-09e3-4229-b4e1-eafccfa6a790

📥 Commits

Reviewing files that changed from the base of the PR and between dc8000e and 31d5c24.

📒 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 version changes from 26.8.27.1 to 26.9.29.1. The uptime entry moves from sensor to text_sensor, retaining a 60-second update interval and adding a space separator to its formatted output.

Changes

ESPHome Core configuration

Layer / File(s)	Summary
Update version and uptime configuration Integrations/ESPHome/Core.yaml	The configured ESPHome version changes. The uptime entry moves to text_sensor with a 60-second update interval and a space separator. The entry is removed from sensor.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Feature

Suggested reviewers: bunton33

Merge Risk: ⚪ Minimal · up to 31d5c

Uptime will appear as formatted text instead of a numeric sensor, so numeric-history consumers and automations may need updating as documented. The configuration matches the intended output, with no actionable merge-blocking risk identified.

Architecture Summary

Architecture risk: 🔵 Low · up to 31d5c

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 ESPHome version changes from 26.8.27.1 to 26.9.29.1.
• observed — Modified behavior in Integrations/ESPHome/Core.yaml: The uptime sensor entry, including its 60-second update interval, is removed from the sensor component.
• observed — Modified behavior in Integrations/ESPHome/Core.yaml: The uptime sensor is added to text_sensor with a 60-second update interval and a space separator for its 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 sensor.
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

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the uptime text,
A space now joins each time.
The version hops to newer ground,
The sensor finds its line.
Five paws tap the config file,
Then nibble clover fine.}

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