MQTT Connector

Stream device telemetry to external MQTT brokers for third-party integrations, custom analytics pipelines, and cross-platform IoT communication. Lightweight pub-sub messaging with configurable topics and QoS levels.

What is MQTT

MQTT (Message Queuing Telemetry Transport) is a lightweight pub-sub messaging protocol designed for constrained devices and low-bandwidth networks. It is the de facto standard for IoT device communication. The /IOTCONNECT™ MQTT connector re-publishes your device data to external MQTT brokers.

Key Features:

Lightweight Protocol: Minimal overhead (2-byte header) ideal for high-frequency telemetry streams.

Quality of Service: QoS 0 (at-most-once), QoS 1 (at-least-once), QoS 2 (exactly-once) delivery guarantees.

Topic Hierarchy: Flexible topic structure (e.g., devices/deviceId/telemetry) with wildcard subscriptions.

Retained Messages: Last-known-good value retained for new subscribers connecting later.

Universal Compatibility: Connect to any MQTT 3.1.1 or 5.0 compliant broker (Mosquitto, HiveMQ, EMQX, etc.).

How it Works

When the MQTT connector is enabled, /IOTCONNECT™ re-publishes device telemetry to your external MQTT broker:

Device sends telemetry → Data arrives at /IOTCONNECT™ via the platform’s internal MQTT.

Connector picks up → Selected data types are prepared for re-publishing.

Publishes to external broker → Data is published to your configured broker on specified topics.

External subscribers receive → Any client subscribed to those topics on your broker receives the data.

User Manual

Step 1: Navigate to Connector Settings

Go to Settings > Configuration > Live Data Streaming in the /IOTCONNECT™ portal.

Step 2: Enable MQTT

Find the MQTT connector card and toggle the switch to ON (green).

Step 3: Select Data Types

Choose which data to stream: Telemetry, Faulty, Diagnostics, Command History.

Step 4: Configure Broker Details

Provide your external MQTT broker connection details:

Broker Host: The hostname or IP of your MQTT broker.

Port: Typically 1883 (TCP) or 8883 (TLS).

Username/Password: Authentication credentials for the broker.

Topic Prefix: Base topic path for published messages.

Step 5: Save

Click Save. Telemetry begins publishing to your external MQTT broker.

Use Cases

Cross-platform Integration: Bridge telemetry to other IoT platforms (Home Assistant, ThingsBoard, etc.).

Edge Computing: Feed data to edge analytics engines running on local MQTT brokers.

Custom Pipelines: Build custom data pipelines with Node-RED, Apache Kafka, or Flink consuming MQTT.

Multi-cloud: Mirror telemetry data from one cloud to another via MQTT bridging.

Local Monitoring: Stream to local MQTT brokers for on-premise monitoring and alerting.

ⓘ NOTE

Ensure your external MQTT broker is accessible from the internet with TLS encryption enabled. Use QoS 1 for guaranteed delivery of telemetry data. Available for both AWS and Azure deployments.