MQTT destination
Navigation: Configuration > IoT > Destinations > MQTT destination
The MQTT destination page configures one or more MQTT broker connections to which the device forwards collected IoT measurement data. Each destination defines a broker URI, authentication credentials, a topic path, and a client ID. The device supports persistent buffering so that data is not lost during temporary connection outages. Multiple MQTT destinations can be configured to send data to different brokers simultaneously.

Settings
- MQTT persistence
- Enables persistent buffering of MQTT messages. On devices, 100 MB are allocated for the persistent buffer. Messages are stored locally when the broker connection is unavailable and transmitted once connectivity is restored.
- MQTT topic
- The MQTT topic string that identifies the data stream on the MQTT broker.
- Server URI
- The broker connection URI in the format
tcp://[hostname|IP]:portorssl://hostname:port. - Client ID
- The MQTT client ID that identifies this data source on the broker.
- Login
- The username for authentication with the MQTT broker. Leave empty if username/password authentication is not required.
- Password
- The corresponding password for the MQTT broker. Leave empty if not required.
- CA certificate
- The Certificate Authority certificate used to verify the broker's TLS certificate when using an
ssl://connection.
Security
Use TLS (ssl://) connections to protect measurement data in transit. Provide a CA certificate to verify the broker identity. Use unique client IDs and strong credentials for each device to prevent unauthorized data injection.