Conversation
🤖 Generated with [Claude Code](https://claude.com/claude-code)
|
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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review. WalkthroughThe ESPHome package version changes from ChangesESPHome configuration
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~5 minutes Change: Feature Suggested reviewers: Merge Risk: ⚪ Minimal · up to 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 SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. I’m a rabbit, ears held high, Comment |
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 12minstead of a raw count of seconds. Thanks to @kernelpanic85 for the idea in ApolloAutomation/R_PRO-1#72.sys_uptime, socomponent.update: sys_uptimein the report scripts still works.0m. Battery devices that sleep right after reporting will usually show0m.Types of changes
Checklist / Checklijst:
If user-visible functionality or configuration variables are added/modified:
🤖 Generated with Claude Code
Summary by CodeRabbit