MQTT Generic (Gen 1)

Enter a name for the connector

Yes

IP Address or Server FQDN of MQTT broker (Must be reachable from the Edge system)

Yes

MQTT broker port

Yes

Unique client identity. If left blank, a default value is auto-generated.

No

Enter the username

No

Enter the user password

No

The Quality of Service (QoS) level represents an understanding between the message sender and receiver, outlining the assurance of message delivery for a particular message. Simultaneously publishing multiple messages can enhance throughput, but opting for higher values may increase the risk of message loss, even when QoS is set to 1. Please note that the actual QoS options available may vary based on the server configuration.

Yes

It refers to the number of messages that can be simultaneously published or sent in parallel. It is a measure of how many messages can be transmitted at the same time. As an example, in Mosquitto, you have the following settings:

Yes

Default topic for publishing

No

It refers to the specific topic where the last will message will be published.

No

It is the information or message that will be sent to the specified topic when the client disconnects unexpectedly or goes offline without sending a proper "goodbye" message.

No

A payload type (raw string or base64 encoded bytes) for Last Will and Testament feature of MQTT

No

A QoS value for Last Will and Testament feature of MQTT

No

If enabled, the broker will store the LWT message, and any new subscribers to the LWT topic will immediately receive this retained LWT message.

No

Set a limit on the number of outbound messages per second. If sending data to a server that has restrictions on the rate of incoming messages, this ensures that no messages are lost.

No

If enabled, messages in the outbound queue are stored on disk. If there are interruptions in connection or power loss, messages will be retained and eventually sent when the connection is restored.

No

Select the sequence of data transfer: FIFO or LIFO. Selecting FIFO (First In First Out) will send the earliest message first. Selecting LIFO (Last In First Out) will send the latest message first.