Fix stale README intro: add-on runs Device Builder by default#1549
Merged
bdraco merged 1 commit intoJun 18, 2026
Conversation
The Try-it intro called the dashboard an opt-in preview in both the HA add-on and ESPHome Desktop. As of ESPHome 2026.6.0 the add-on runs the Device Builder by default (the add-on section below already says so), so only Desktop remains opt-in. Reword the intro to match.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1549 +/- ##
=======================================
Coverage 99.54% 99.54%
=======================================
Files 224 224
Lines 17519 17519
=======================================
Hits 17439 17439
Misses 80 80
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
bdraco
approved these changes
Jun 18, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the README “Try it” introduction to reflect the current rollout status: the Home Assistant add-on runs Device Builder by default (no longer an opt-in preview), while ESPHome Desktop still requires explicitly selecting the backend.
Changes:
- Reword the “Try it” intro sentence to remove “opt-in preview” language for the Home Assistant add-on.
- Clarify that ESPHome Desktop uses an opt-in backend selection flow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this implement/fix?
The "Try it" intro still described the dashboard as an opt-in preview in
both the Home Assistant add-on and ESPHome Desktop. That's stale for the
add-on: as of ESPHome 2026.6.0 the add-on runs the Device Builder by
default (the "Home Assistant add-on" section just below already states this,
and the status banner is already marked stable/1.0). Only ESPHome Desktop
remains opt-in via the backend picker.
Reword the one intro sentence so it no longer calls the add-on a preview, while
keeping both paths and the "pick the path that matches how you run ESPHome
today" framing intact.
Related issue or feature (if applicable):
Types of changes
bugfixnew-featureenhancementbreaking-changerefactordocsmaintenancecidependenciesFrontend coordination
Checklist
ruff,codespell, yaml/json/python checks).tests/where applicable.components.index.json/definitions/components/*.jsonhave not been hand-edited (regenerate viascript/sync_components.pyif a sync is needed).docs/ARCHITECTURE.mdand/ordocs/API.md.Quality Report
Changes: 1 file changed, 3 insertions(+), 2 deletions(-)
Code scan: clean
Tests: failed (FAILED)
Branch hygiene: clean
Generated by Kōan