Upstream/esphome-docs
1
0
Fork 0
mirror of https://github.com/esphome/esphome-docs.git synced 2024-12-23 16:58:11 +01:00
Code Issues Projects Releases Wiki Activity

Update api.rst (#3319)

Browse Source 
mention ioBroker as additional SmartHome system able to communicate by Native API
This commit is contained in:
Rafal Drozda 2023-11-01 18:36:22 +01:00 committed by GitHub
parent aba2f3afd5
commit ac11455611
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
components/api.rst
View File

@ -7,7 +7,7 @@ Native API Component
:keywords: Native API, ESPHome, Home Assistant
The ESPHome native API is used to communicate with clients directly, with a highly-optimized
network protocol. Currently, only the ESPHome tool and Home Assistant use this native API.
network protocol. Currently, only the ESPHome tool, Home Assistant and ioBroker use this native API.
After adding an ``api:`` line to your ESPHome configuration you can go to the Home Assistant
web interface and navigate to the "Integrations" screen in the "Configuration" panel. Then wait
@ -330,7 +330,7 @@ Advantages over MQTT
--------------------
The ESPHome native API has many advantages over using MQTT for communication with Home
Automation software (currently only Home Assistant). But MQTT is a great protocol and will
Automation software (currently only Home Assistant and ioBroker). But MQTT is a great protocol and will
never be removed. Features of native API (vs. MQTT):
- **Much more efficient:** ESPHome encodes all messages in a highly optimized format with