MQTT Device trigger
The mqtt device trigger platform uses an MQTT message payload to generate device trigger events.
An MQTT device trigger is a better option than a binary sensor for buttons, remote controls etc.
Configuration
MQTT device triggers are only supported through MQTT discovery, manual setup through configuration.yamlconfiguration.yaml 文件是 Home Assistant 的主要配置文件。它列出了要加载的集成及其特定配置。在某些情况下,需要直接在 configuration.yaml 文件中手动编辑配置。大多数集成可以在 UI 中配置。 [Learn more] is not supported.
The discovery topic needs to be: <discovery_prefix>/device_automation/[<node_id>/]<object_id>/config. Note that only one trigger may be defined per unique discovery topic. Also note that the combination of type and subtype should be unique for a device.
Configuration Variables
Must be device_automation. Only allowed and required in MQTT auto discovery device messages.
The maximum QoS level to be used when receiving and publishing messages.
The type of the trigger, e.g. button_short_press. Entries supported by the frontend: button_short_press, button_short_release, button_long_press, button_long_release, button_double_press, button_triple_press, button_quadruple_press, button_quintuple_press. If set to an unsupported value, will render as subtype type, e.g. button_1 spammed with type set to spammed and subtype set to button_1
The subtype of the trigger, e.g. button_1. Entries supported by the frontend: turn_on, turn_off, button_1, button_2, button_3, button_4, button_5, button_6. If set to an unsupported value, will render as subtype type, e.g. left_button pressed with type set to button_short_press and subtype set to left_button
Information about the device this device trigger is a part of to tie it into the device registry. 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://, https:// or an internal homeassistant:// URL.
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.
Example
This shows a complete example of defining a remote control type device with two triggers: “left arrow click” and “right arrow click”.
Note that it is not necessary to provide the full device information in each message, but the identifying information, identifier in the example, must be the same.
Left arrow click configuration
-
Discovery topic:
homeassistant/device_automation/0x90fd9ffffedf1266/action_arrow_left_click/config -
Discovery payload:
{ "automation_type": "trigger", "type": "action", "subtype": "arrow_left_click", "payload": "arrow_left_click", "topic": "zigbee2mqtt/0x90fd9ffffedf1266/action", "device": { "identifiers": [ "zigbee2mqtt_0x90fd9ffffedf1266" ], "name": "0x90fd9ffffedf1266", "sw_version": "Zigbee2MQTT 1.14.0", "model": "TRADFRI remote control (E1524/E1810)", "manufacturer": "IKEA" } } -
Trigger topic:
zigbee2mqtt/0x90fd9ffffedf1266/action -
Trigger payload:
arrow_left_click
Right arrow click configuration
-
Discovery topic:
homeassistant/device_automation/0x90fd9ffffedf1266/action_arrow_right_click/config -
Discovery payload:
{ "automation_type": "trigger", "type": "action", "subtype": "arrow_right_click", "payload": "arrow_right_click", "topic": "zigbee2mqtt/0x90fd9ffffedf1266/action", "device": { "identifiers": [ "zigbee2mqtt_0x90fd9ffffedf1266" ] } } -
Trigger topic:
zigbee2mqtt/0x90fd9ffffedf1266/action -
Trigger payload:
arrow_right_click