MQTT Client

If your service is equipped with MQTT Broker Server, you can use the MQTT Client type to connect to your server and publish the data.

Specific configuration

Name	Description	Valid values
mqtt_dist_client_id	MQTT Client ID	Any string
mqtt_dist_transport	Transport type used to connect to server	tcp or websockets
mqtt_dist_tls	Should TLS be used to connect?	true or false
mqtt_dist_json_datastream_topic	Topic used for sending telemetry messages	Any string
mqtt_dist_publish_qos_default	QoS parameter of messages sent from the client	Any integer number

Example specific configuration

Following is an example of configuration JSON

{
  "mqtt_dist_client_id": "dronetag_0001",
  "mqtt_dist_transport": "tcp",
  "mqtt_dist_tls": false,
  "mqtt_dist_json_datastream_topic": "dronetag/telemetry/{msgtype}",
  "mqtt_dist_publish_qos_default": 0
}

Using {msgtype} in topic name

If you use Dronetag DUMP format and you'd like to send different types of messages to different topics, you can use the {msgtype} placeholder in the topic name. It will be replaced with the actual message type before sending. For example, if the message type is "UA telemetry", the topic dronetag/telemetry/{msgtype} will become dronetag/telemetry/tele-ua.

Available message types are:

• tele-ua - UA telemetry messages
• tele-operator - Operator telemetry messages
• tele-system - System telemetry messages
• operation-update - Operation update messages

Refer to the 'Understanding DUMP' page for more information about the message types.

Configuration recommendations

• Usually a valid Target Port is required to be set.