Skip to content

Add supported devices and updating data section to ESPHome #38613

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 10 commits into from
Apr 18, 2025
Merged

Add supported devices and updating data section to ESPHome #38613

Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
0cfbdd8
Add supported devices to ESPHome
bdraco Apr 18, 2025
70bdcdd
Update source/_integrations/esphome.markdown
bdraco Apr 18, 2025
929f64f
Update source/_integrations/esphome.markdown
bdraco Apr 18, 2025
1564c15
Update esphome.markdown
bdraco Apr 18, 2025
b9e48e9
Update esphome.markdown
bdraco Apr 18, 2025
dc886aa
Update esphome.markdown
bdraco Apr 18, 2025
2fbf3a5
Update source/_integrations/esphome.markdown
bdraco Apr 18, 2025
8bbeb14
Update source/_integrations/esphome.markdown
bdraco Apr 18, 2025
0a07357
Merge branch 'current' into bdraco-patch-10
bdraco Apr 18, 2025
753c354
Update source/_integrations/esphome.markdown
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
14 changes: 14 additions & 0 deletions source/_integrations/esphome.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,20 @@ This integration follows the standard integration removal process; no extra step

{% include integrations/remove_device_service.md %}

## Supported devices

The ESPHome integration works with devices that run ESPHome firmware and expose their functionality through the [native ESPHome API](https://esphome.io/components/api.html). This API is designed for tight, efficient integration with Home Assistant, enabling ESPHome devices to push updates directly to Home Assistant in **near real time**.

## Updating data

Rather than polling for sensor values or device states, Home Assistant maintains a persistent connection to each ESPHome device using the native API. This allows state changes—such as a temperature sensor update, a button press, or a binary sensor trigger—to be sent immediately as they happen, reducing latency and improving responsiveness in automations.

### Additional Technical Details
- **Efficient Communication Protocol**: ESPHome uses a lightweight, bi-directional protocol over TCP, optimized for microcontrollers. This protocol is implemented in [aioesphomeapi](https://github.com/esphome/aioesphomeapi), the async Python library used by Home Assistant to handle real-time communication with ESPHome devices. It enables low-latency updates and near instant command execution.
- **Automatic Reconnection**: Home Assistant maintains a persistent connection to each ESPHome device and will automatically attempt to reconnect if the connection is lost. This includes support for "sleepy" or battery-powered devices that periodically wake from deep sleep. When such a device comes online, Home Assistant quickly re-establishes the connection—especially when **mDNS** (Multicast DNS) is available—allowing the device to be discovered and connected without requiring static IPs or manual configuration.

This real-time behavior enables fast, reactive automations and a smooth user experience compared to traditional polling-based integrations.

## Home Assistant actions

ESPHome devices can perform actions to any [Home Assistant action](https://esphome.io/components/api.html#homeassistant-service-action). This functionality is not enabled by default for newly configured device, but can be turned on the options flow on a per device basis.
Expand Down