Přeskočit na hlavní obsah
3 pages combined into one document. Tip: enable Background graphics in the print dialog so note and warning boxes keep their shading.
All printable guides
Dronetag
Developers

Typy distribucí

Document
Developers — Typy distribucí
Chapters
3
Source
help.dronetag.cz/cs/print/developers/data-push/distribution-types
Dronetag s.r.o. · The online version of this document is always the authoritative one.

HTTP Webhooks

The most common distribution type uses HTTP protocol to distribute the data.
For each telemetry message, a new HTTP request is created and sent to your service's HTTP server.

Specific configuration​

Currently, only additional HTTP headers can be set using the specific configuration.

NameDescriptionValid values
target_additional_http_headersAdditional HTTP headers sent with each requestJSON object

Example specific configuration​

Following is an example of configuration JSON where custom headers are used to send a Bearer token with each request.

{
"target_additional_http_headers": {
"X-My-Custom-Id": "12345"
}
}

MQTT Client

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

Specific configuration​

NameDescriptionValid values
mqtt_dist_client_idMQTT Client IDAny string
mqtt_dist_transportTransport type used to connect to the servertcp or websockets
mqtt_dist_tlsShould TLS be used to connect?true or false
mqtt_dist_json_datastream_topicTopic used for sending telemetry messagesAny string
mqtt_dist_publish_qos_defaultQoS parameter of messages sent from the clientAny integer number
embed_metadataAdds message metadata like account_visibility or integration_client_id to payloadtrue or false

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.

TCP & UDP Sockets

This distribution type uses plain TCP or UDP socket to distribute the data.

Specific configuration​

NameDescriptionValid values
embed_metadataAdds message metadata like account_visibility or integration_client_id to payloadtrue or false

Example specific configuration​

Following is an example of configuration JSON

{
"embed_metadata": true
}

Configuration recommendations​

  • The 'Target port' must be set
  • We recommend using the AES cipher authorization type to keep the traffic secure

Source pages

Every chapter of this document is a page of the Dronetag help site. Use these addresses to reach the latest version.

  1. 1HTTP Webhookshelp.dronetag.cz/cs/developers/data-push/distribution-types/http
  2. 2MQTT Clienthelp.dronetag.cz/cs/developers/data-push/distribution-types/mqtt
  3. 3TCP & UDP Socketshelp.dronetag.cz/cs/developers/data-push/distribution-types/tcp