Publish

yaml

type: "io.kestra.plugin.mqtt.Publish"

Produce message in a MQTT topic

Examples

yaml

id: mqtt_publish
namespace: company.team

tasks:
  - id: publish
    type: io.kestra.plugin.mqtt.Publish
    server: tcp://localhost:1883
    clientId: kestraProducer
    topic: kestra/sensors/cpu
    serdeType: JSON
    retain: true
    from:
      type: "sensors"
      value: 1.23

yaml

    id: mqtt_publish
    namespace: company.team

    tasks:
      - id: publish
        type: io.kestra.plugin.mqtt.Publish
        server: ssl://localhost:8883
        clientId: kestraProducer
        topic: kestra/sensors/cpu
        crt: /home/path/to/ca.crt
        serdeType: JSON
        retain: true
        from:
          type: "sensors"
          value: 1.23

Properties

`clientId`

Type: string
Dynamic: ✔️
Required: ✔️

A client identifier that is unique on the server being connected to

A client identifier clientId must be specified and be less that 65535 characters. It must be unique across all clients connecting to the same server. The clientId is used by the server to store data related to the client, hence it is important that the clientId remain the same when connecting to a server if durable subscriptions or reliable messaging are required. As the client identifier is used by the server to identify a client when it reconnects, the client must use the same identifier between connections if durable subscriptions or reliable delivery of messages is required.

`from`

Type:
- string
- array
- object
Dynamic: ✔️
Required: ✔️

Source of message send

Can be an internal storage uri, a map or a list.

`qos`

Type: integer
Dynamic: ❌
Required: ✔️
Default: 1

Sets the quality of service for this message.

Quality of Service 0: indicates that a message should be delivered at most once (zero or one times). The message will not be persisted to disk, and will not be acknowledged across the network. This QoS is the fastest, but should only be used for messages which are not valuable - note that if the server cannot process the message (for example, there is an authorization problem). Also known as "fire and forget".

Quality of Service 1: indicates that a message should be delivered at least once (one or more times). The message can only be delivered safely if it can be persisted, so the application must supply a means of persistence using MqttConnectOptions. If a persistence mechanism is not specified, the message will not be delivered in the event of a client failure. The message will be acknowledged across the network.
Quality of Service 2: indicates that a message should be delivered once. The message will be persisted to disk, and will be subject to a two-phase acknowledgement across the network. The message can only be delivered safely if it can be persisted, so the application must supply a means of persistence using MqttConnectOptions. If a persistence mechanism is not specified, the message will not be delivered in the event of a client failure. If persistence is not configured, QoS 1 and 2 messages will still be delivered in the event of a network or server problem as the client will hold state in memory. If the MQTT client is shutdown or fails and persistence is not configured then delivery of QoS 1 and 2 messages can not be maintained as client-side state will be lost.

`retain`

Type: boolean
Dynamic: ❌
Required: ✔️
Default: false

**Whether or not the publish message should be retained by the messaging engine. **

Sending a message with retained set to true and with an empty byte array as the payload e.g. null will clear the retained message from the server.

`serdeType`

Type: string
Dynamic: ❌
Required: ✔️
Possible Values:
- STRING
- JSON
- BYTES

Serializer / Deserializer used for the payload

`server`

Type: string
Dynamic: ✔️
Required: ✔️

The address of the server to connect to, specified as a URI

The serverURI parameter is typically used with the the clientId parameter to form a key. The key is used to store and reference messages while they are being delivered. The address of the server to connect to is specified as a URI. Two types of connection are supported tcp:// for a TCP connection and ssl:// for a TCP connection secured by SSL/TLS. For example:

tcp://localhost:1883
ssl://localhost:8883 If the port is not specified, it will default to 1883 for tcp://" URIs, and 8883 for ssl:// URIs.

`topic`

Type: string
Dynamic: ✔️
Required: ✔️

Topic where to send message

`version`

Type: string
Dynamic: ❌
Required: ✔️
Default: V5
Possible Values:
- V3
- V5

The MQTT version to use.

`authMethod`

Type: string
Dynamic: ✔️
Required: ❌

The Authentication Method.

Only available if version = V5 If set, this value contains the name of the authentication method to be used for extended authentication. If null, extended authentication is not performed.

`connectionTimeout`

Type: string
Dynamic: ❌
Required: ❌
Format: duration

The connection timeout.

This value defines the maximum time interval the client will wait for the network connection to the MQTT server to be established. The default timeout is 30 seconds. A value of 0 disables timeout processing meaning the client will wait until the network connection is made successfully or fails.