MQTT Transport Adaptor¶

Discovery¶

Delivery (explicit selection). If the MQTT integration's config entry exists and no mqtt delivery is defined, an mqtt delivery is generated automatically — but since a topic has no automatic mapping to a recipient or entity, it only fires when selected explicitly (data: {data: {delivery: [mqtt]}} or a scenario), not by default. MQTT devices that already expose themselves as notify entities are covered automatically by the notify_entity transport's own default delivery instead.

Whilst MQTT Notify Entities can be used for many cases, and the Supernotify generic can be used to send a payload to mqtt.publish, the specific MQTT integration can be easier to use.

• Payloads can be defined in YAML rather than escaped JSON, and will be JSONified if needed on delivery
• The action doesn't need to be specified, and the config will validate that a topic has been provided.

Example¶

- action: supernotify.notify
  data:
    message: ""
    delivery:
        mqtt:
            target: notify/queue/1
            data:
                payload:
                  warning:
                    duration: 30
                    mode: emergency
                    level: low

The topic can also be supplied as a target instead of data.topic - useful for selecting the topic per scenario or recipient rather than hard-coding it into the delivery. If both are given, target takes precedence. Multiple targets publish the same payload to each topic in turn.

- action: supernotify.notify
  data:
    message: "this will be the MQTT payload"
    target: topic:notify/queue/1

Reference¶

Home Assistant¶

• MQTT Integration
  • Open Issues