Get desktop application:
View/edit binary Protocol Buffers messages
legacy, for older peers, newer ones should use CLIMATE_PRESET_AWAY in preset
Message sent at the beginning of each connection to authenticate the client Can only be sent by the client and only at the beginning of the connection
The password to log in with
Confirmation of successful connection. After this the connection is available for all traffic. Can only be sent by the server and only at the beginning of the connection
legacy: command has been removed in 1.13 clients/servers must still send/accept it until the next protocol change
(message has no fields)
The name of the node, given by "App.set_name()"
The mac address of the device. For example "AC:BC:32:89:0E:A9"
A string describing the ESPHome version. For example "1.10.0"
A string describing the date of compilation, this is generated by the compiler and therefore may not be in the same format all the time. If the user isn't using ESPHome, this will also not be set.
The model of the board. For example NodeMCU
The esphome project details if set
Request to close the connection. Can be sent by both the client and server
(message has no fields)
(message has no fields)
==================== IMPORT TIME ====================
(message has no fields)
Message sent at the beginning of each connection Can only be sent by the client and only at the beginning of the connection
Description of client (like User Agent) For example "Home Assistant" Not strictly necessary to send but nice for debugging purposes.
Confirmation of successful connection request. Can only be sent by the server and only at the beginning of the connection
The version of the API to use. The _client_ (for example Home Assistant) needs to check for compatibility and if necessary adopt to an older API. Major is for breaking changes in the base protocol - a mismatch will lead to immediate disconnect_client_ Minor is for breaking changes in individual messages - a mismatch will lead to a warning message
A string identifying the server (ESP); like client info this may be empty and only exists for debugging/logging purposes. For example "ESPHome v1.10.0 on ESP8266"
(message has no fields)
(message has no fields)
(message has no fields)
==================== IMPORT HOME ASSISTANT STATES ==================== 1. Client sends SubscribeHomeAssistantStatesRequest 2. Server responds with zero or more SubscribeHomeAssistantStateResponse (async) 3. Client sends HomeAssistantStateResponse for state changes.
(message has no fields)
==================== HOMEASSISTANT.SERVICE ====================
(message has no fields)
(message has no fields)
If the binary sensor does not have a valid state yet. Equivalent to `!obj->has_state()` - inverse logic to make state packets smaller
Used in:
values same as mode for readability
Used in: , ,
==================== CLIMATE ====================
Used in: , ,
Used in: , ,
For older peers, equal to preset == CLIMATE_PRESET_AWAY
Used in: , ,
Used in:
legacy: state has been removed in 1.13 clients/servers must still send/accept it until the next protocol change
Used in:
ESPHome 1.14 (api v1.3) make int a signed value
Used in: ,
Used in: ,
Used in:
Used in:
Used in:
==================== BINARY SENSOR ====================
==================== CAMERA ====================
for older peer versions - in new system this is if CLIMATE_PRESET_AWAY exists is supported_presets
==================== COVER ====================
(message has no fields)
==================== FAN ====================
==================== LIGHT ====================
Used in:
==================== SWITCH ====================
==================== TEXT SENSOR ====================
==================== SUBSCRIBE LOGS ====================
Used in: ,
==================== SENSOR ====================
Used in:
If the sensor does not have a valid state yet. Equivalent to `!obj->has_state()` - inverse logic to make state packets smaller
==================== USER-DEFINES SERVICES ====================
Used in:
If the text sensor does not have a valid state yet. Equivalent to `!obj->has_state()` - inverse logic to make state packets smaller
Used as response type in: APIConnection.camera_image, APIConnection.climate_command, APIConnection.cover_command, APIConnection.execute_service, APIConnection.fan_command, APIConnection.light_command, APIConnection.list_entities, APIConnection.subscribe_home_assistant_states, APIConnection.subscribe_homeassistant_services, APIConnection.subscribe_logs, APIConnection.subscribe_states, APIConnection.switch_command
(message has no fields)