Response Route MQTT


images/download/thumbnails/44944895/arrow_up-version-1-modificationdate-1583212123048-api-v2.png Introduction: You can find a description of this phase in section Phase 6 (Introduction).


images/download/thumbnails/44944895/image2020-3-19_16-12-49-version-1-modificationdate-1584587567025-api-v2.png

images/download/attachments/44944895/686-version-1-modificationdate-1649840533770-api-v2.png


(1) The MQTT alias. See section MQTT Connections.

(2) The topic to which the message is sent. Note: See also section File Names, File Patterns, Paths, System Constants and Variables.

(3) Die Übertragungsqualität (Quality of Service, QoS).

At most once

The lowest-cost in terms of volume of data transfer. This is suitable if you have a reliable connection between Lobster_data and the MQTT broker.

At least once

A good choice if you need to be sure every message gets through and the receiving application can tolerate receiving a message more than once.

Exactly once

Guarantees delivery exactly once, but has a relatively high cost in terms of data transfer.

System Variables


In MQTT version 5, you can use system variables of the form MQTT_<keyname> to pass user properties (key, value). See also MQTT_SYS_CONTENTTYPE and MQTT_SYS_CORRELATIONDATA.

Input Agent


See section MQTT (Input Agent) .