Skip to content

Add known limitations section to ESPHome #38618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 18, 2025
Merged

Add known limitations section to ESPHome #38618

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3a5ae94
Add known limitations section to ESPHome
bdraco Apr 18, 2025
69131c5
Merge branch 'current' into bdraco-patch-15
bdraco Apr 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions source/_integrations/esphome.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,3 +135,9 @@ The entity will be named `Temperature` and will default to having an entity_id o
data:
homeassistant.components.esphome: debug
```

## Known Limitations

Each ESPHome device must have a **unique name**. This name is important for mDNS announcements, ensuring that the device can be properly discovered, quickly reconnected when it comes online or wakes from deep sleep (for devices that support deep sleep), and correctly linked to the [**ESPHome Device Builder Add-on**](https://my.home-assistant.io/redirect/supervisor_addon/?addon=5c53de3b_esphome&repository_url=https%3A%2F%2Fgithub.com%2Fesphome%2Fhome-assistant-addon). It's also crucial for **DHCP discovery** if mDNS is not available.

Using duplicate names can lead to connection issues, failed discovery, and unexpected behavior with both the integration and the add-on.