MQTT Event
The mqtt event platform allows you to process event info from an MQTT message. Events are signals that are emitted when something happens, for example, when a user presses a physical button like a doorbell or when a button on a remote control is pressed. With the event some event attributes can be sent to become available as an attribute on the entity. MQTT events are stateless. For example, a doorbell does not have a state like being “on” or “off” but instead is momentarily pressed.
Configuration
# Example configuration.yaml entry
mqtt:
- event:
state_topic: "home/doorbell/state"
event_types:
- press
Configuration Variables
A list of MQTT topics subscribed to receive availability (online/offline) updates. Must not be used together with availability_topic.
The payload that represents the available state.
The payload that represents the unavailable state.
When availability is configured, this controls the conditions needed to set the entity to available. Valid entries are all, any, and latest. If set to all, payload_available must be received on all configured availability topics before the entity is marked as online. If set to any, payload_available must be received on at least one configured availability topic before the entity is marked as online. If set to latest, the last payload_available or payload_not_available received on any configured availability topic controls the availability.
Defines a template to extract device’s availability from the availability_topic. To determine the devices’s availability result of this template will be compared to payload_available and payload_not_available.
The MQTT topic subscribed to receive availability (online/offline) updates. Must not be used together with availability.
Information about the device this event is a part of to tie it into the device registry. Only works when unique_id is set. At least one of identifiers or connections must be present to identify the device.
A link to the webpage that can manage the configuration of this device. Can be either an HTTP or HTTPS link.
A list of connections of the device to the outside world as a list of tuples [connection_type, connection_identifier]. For example the MAC address of a network interface: "connections": [["mac", "02:5b:26:a8:dc:12"]].
A list of IDs that uniquely identify the device. For example a serial number.
The type/class of the event to set the icon in the frontend. The device_class can be null.
Flag which defines if the entity should be enabled when first added.
The category of the entity.
Defines a template to extract the JSON dictionary from messages received on the json_attributes_topic. Usage example can be found in MQTT sensor documentation.
The MQTT topic subscribed to receive a JSON dictionary payload and then set as sensor attributes. Usage example can be found in MQTT sensor documentation.
The payload that represents the available state.
The payload that represents the unavailable state.
The maximum QoS level to be used when receiving and publishing messages.
The MQTT topic subscribed to receive JSON event payloads. The JSON payload should contain the event_type element. The event type should be one of the configured event_types. Note that replayed retained messages will be discarded.
An ID that uniquely identifies this event entity. If two events have the same unique ID, Home Assistant will raise an exception.
Make sure that your topic matches exactly. some-topic/ and some-topic are different topics.
Full configuration with JSON data
The example below shows a full configuration for an event MQTT entity.
# Example configuration.yaml entry
mqtt:
- event:
state_topic: "home/doorbell/state"
event_types:
- "press"
- "hold"
availability:
- topic: "home/doorbell/available"
qos: 0
device_class: "doorbell"
The event information is extracted from a JSON formatted MQTT message.
To test, you can use the command line tool mosquitto_pub shipped with mosquitto or the mosquitto-clients package to send MQTT messages.
To set trigger the mqtt event entity manually:
mosquitto_pub -h 127.0.0.1 -t home/doorbell/available -m "online"
mosquitto_pub -h 127.0.0.1 -t home/doorbell/state -m '{"event_type": "hold"}'
Besides the required event_type element, the payload can contain additional event attributes.
These additional attribute updates will be exposed as attributes on the mqtt event entity.
The example below demonstrates how event attributes can be added to the event data.
mosquitto_pub -h 127.0.0.1 -t home/doorbell/state -m '{"event_type": "press", "duration": 0.1}'
Example: processing event data using a value template
In many cases, translation of an existing published payload is needed.
The example config below translates the payload {"Button1": {"Action": "SINGLE"}} of
the device Button1 with event type single to the required format.
An extra attribute button will be set to Button1 and be added to the entity,
but only if the Action property is set. Empty dictionaries will be ignored.
mqtt:
- event:
name: "Desk button"
state_topic: "desk/button/state"
event_types:
- single
- double
device_class: "button"
value_template: |
{ {% for key in value_json %}
{% if value_json[key].get("Action") %}
"button": "{{ key }}",
"event_type": "{{ value_json[key].Action | lower }}"
{% endif %}
{% endfor %} }