Ignition Module

MQTT Module for Ignition

MQTT module for Ignition SCADA. Connect to any MQTT broker, subscribe to topics, publish messages, and react to incoming data through gateway scripting.

Download Module Documentation

The Problem

Without This Module

MQTT is the backbone of IIoT messaging, but wiring Ignition to external brokers usually means custom OPC bridges, third-party middleware, or fragile scripting hacks. Managing subscriptions, reconnections, and message handling by hand is error-prone.

No native MQTT client inside the Ignition Gateway
External bridges and middleware add cost and complexity
Manual reconnection and subscription handling is fragile
No clean way to route broker messages into gateway logic

The Solution

With This Module

The MQTT module embeds a full MQTT client inside the Ignition Gateway. Configure broker connections from the web UI, subscribe to any topic with wildcards, and route incoming messages to gateway scripts. Publishing to a topic is a single scripting call.

Full MQTT client running directly in the Gateway
Broker connections configured from the web interface
Incoming messages routed straight to gateway scripts
Publish to any topic with a single scripting call

Why Use the MQTT Module?

Native MQTT connectivity designed for Ignition SCADA

Zero Middleware

Connect Ignition straight to your broker. No OPC bridges, no external gateways, no extra servers to maintain.

Any Broker

Works with Mosquitto, HiveMQ, EMQX, AWS IoT, Azure IoT Hub, and any MQTT 3.1.1 broker.

Secure by Design

TLS/SSL transport with username/password or certificate authentication keeps your messaging protected.

Key Features

A complete MQTT client built into the Ignition Gateway

Broker Connection Management

Configure and monitor broker connections directly from the Gateway web UI.

Set host, port, client ID, credentials, keep-alive, and clean-session options per connection.

Topic Subscriptions

Subscribe to any topic, including single-level (+) and multi-level (#) wildcards.

Each subscription defines its QoS level and the gateway script that handles incoming messages.

Message Handler Scripting

Run gateway scripts whenever a message arrives on a subscribed topic.

The handler receives topic, payload, and QoS, letting you parse JSON, write tags, or trigger logic.

Publish from Scripting

Publish messages to any topic with a single scripting call.

The publish function supports payload, QoS level, and the retained flag for stateful topics.

Secure Connections

Encrypted broker connections with authentication built in.

TLS/SSL transport with username/password or certificate-based security, configured per connection.

Automatic Reconnection

Resilient connections that recover automatically from network drops.

Configurable reconnect intervals keep subscriptions alive without manual intervention.

How It Works

Get MQTT connectivity running in three simple steps

Install the Module

Download the .modl file and install it on your Ignition Gateway. No external middleware required.

Connect Your Broker

Add a broker connection from the Gateway web UI, with optional TLS and authentication.

Subscribe and Publish

Subscribe to topics, handle incoming messages with gateway scripts, and publish back to any topic.

Technical Specifications

Built for seamless integration with your Ignition platform

CompatibilityIgnition 8.3+

Module TypeGateway + Designer Module

MQTT ClientEclipse Paho 1.2.5

ProtocolMQTT 3.1 / 3.1.1

SecurityTLS/SSL, Username/Password

LicenseCommercial

What's Included

Everything you need for MQTT connectivity

Full MQTT client in the Ignition Gateway
Unlimited broker connections
Topic subscriptions with wildcard support
Message handler gateway scripting
Publish to any topic from scripting
TLS/SSL secure connections

License Typecommercial

Versionv1.0.0

Frequently Asked Questions

Common questions about the MQTT Module for Ignition

Any broker that speaks MQTT 3.1 or 3.1.1: Mosquitto, HiveMQ, EMQX, VerneMQ, AWS IoT Core, Azure IoT Hub, and more. The module uses the Eclipse Paho client for broad compatibility.

Yes. Broker connections can be secured with TLS/SSL, using username and password or certificate-based authentication. Security settings are configured per connection.

Each subscription is bound to a gateway message-handler script that receives the topic, payload, and QoS whenever a message arrives. From there you can parse the data, write tags, or run any gateway logic.

Yes. The module exposes a scripting function to publish to any topic with a chosen QoS level and an optional retained flag, so your gateway logic can push data back to the broker.

The module requires Ignition 8.3.0 or later and runs on the Gateway and Designer scopes.