Installation

Prerequisites

• Ignition 8.3.0 or higher (Gateway)
• No prerequisite Ignition modules — MQTT Dev has no module dependencies
• A reachable MQTT broker (for example Eclipse Mosquitto)
• Network access from the Gateway to your broker's port(s)

Paid module with a trial

MQTT Dev is a paid module and runs on a 2-hour trial until licensed. See License and Trial below.

Download

Download MQTT Dev Module

Installation Steps

1. Log in to your Ignition Gateway web interface
2. Navigate to Platform > System > Modules
3. Click Install or Upgrade a Module
4. Select the MQTT-Dev.modl file
5. Review and accept the license agreement
6. The module installs and registers the MQTT Dev broker configuration section and the system.mqtt.* scripting functions

Verification

After installation:

1. Verify the module appears in the modules list with Running status
2. Navigate to Connections > MQTT Dev > Brokers and confirm the broker configuration page loads
3. Open the Designer and confirm an MQTT Dev section appears in the Project Browser

Network Requirements

The Gateway must be able to reach your MQTT broker. Ports depend on the transport scheme you use:

Transport	Scheme	Typical Port
TCP (plain)	tcp://	1883
TCP over TLS	ssl://	8883
WebSocket	ws://	broker-dependent (commonly 8080 / 9001)
WebSocket over TLS	wss://	broker-dependent (commonly 8443)

TLS has no dedicated configuration fields

ssl:// and wss:// URIs are accepted, but the module provides no TLS/keystore/CA configuration surface. TLS relies on the Paho client and the JVM's default trust store and settings. If your broker uses a certificate that is not trusted by the Gateway JVM's default trust store, the connection will fail.

License and Trial

MQTT Dev runs on a 2-hour trial until licensed. See Overview → Licensing for what happens when the trial expires.

Supported Brokers

The module uses a standard MQTT 3.1.1 client (Eclipse Paho v3), so it works with any MQTT 3.1.1-compliant broker reachable over tcp://, ssl://, ws://, or wss://. Eclipse Mosquitto is a common choice for testing.

Troubleshooting

Issue	Solution
Module not appearing	Restart the Ignition Gateway and check Gateway logs
Broker will not connect	Verify the server URI scheme/port and that the broker is reachable from the Gateway
Broker connects then drops	Check whether the trial has expired; reset trial or apply a license
TLS (ssl:///wss://) fails	Ensure the broker certificate is trusted by the Gateway JVM's default trust store