[docs] Rename "add-on" to "app" in getting started guide#6713
Conversation
Home Assistant 2026.2 renamed "add-ons" to "apps". Update user-facing text in the getting started with Home Assistant guide to reflect the new terminology.
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
✅ Files skipped from review due to trivial changes (8)
WalkthroughDocumentation text across multiple guides and component pages was updated to replace references to "Home Assistant add-on"/"Add-on Store" with "Home Assistant app"/"App Store", and the getting started guide's installation and SSH notes were adjusted to reference the ESPHome Device Builder app and the SSH app. ChangesApp Installation Documentation
🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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. Comment |
|
Hi @jesserockz , PTAL. I've been writing an ESPHome getting started series for Waveshare boards and ran into this — Home Assistant renamed "add-ons" to "apps" back in 2026.2, but the ESPHome docs haven't caught up yet. It'd be great to get the terminology in sync. Happy to expand the scope to cover the other files listed above if that helps. Thanks! |
Description
Home Assistant 2026.2 renamed "add-ons" to "apps". This PR updates user-facing text in the getting started with Home Assistant guide to reflect the new terminology.
Changes in
src/content/docs/guides/getting_started_hassio.mdx:Technical identifiers (variable names, external URLs, Docker container names) are left unchanged.
Note
The following files also contain "add-on" references that may need similar updates. Should these be included in this PR or handled separately?
src/content/docs/index.mdxsrc/content/docs/components/mdns.mdxsrc/content/docs/components/font.mdxsrc/content/docs/components/ota/http_request.mdxsrc/content/docs/guides/getting_started_command_line.mdxsrc/content/docs/guides/faq.mdxsrc/content/docs/guides/migrate_espurna.mdxsrc/content/docs/guides/migrate_sonoff_tasmota.mdxsrc/content/docs/guides/migrate_espeasy.mdxNote:
atm90e26.mdxandatm90e32.mdxuse "add-on" to refer to hardware expansion boards, not Home Assistant add-ons — these should remain as-is.Related issue (if applicable): N/A
Pull request in esphome with YAML changes (if applicable):
Checklist
I am merging into
nextbecause this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
currentbecause this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/src/content/docs/components/index.mdxwhen creating new documents for new components or cookbook.