Skip to content

MQTT in Enture

MQTT is a lightweight publish/subscribe protocol commonly used by IIoT sensors, edge gateways, and embedded devices. The Enture MQTT connector subscribes to configured topics on an MQTT broker and ingests incoming payloads.

How Enture uses MQTT

  • An MQTT Device represents a single publisher, identified by the topic it publishes to and an identifier/identifier value pair that distinguishes this device's messages when several devices share the same topic.
  • MQTT Parameters map individual fields within the incoming payload to trackable data points in Enture, each identified by its own identifier (the field name/path within the message).

Once configured, the Enture edge device connected to your facility subscribes to the topic and extracts the mapped values from incoming messages, streaming them to the platform.

Typical setup workflow

  1. Add an MQTT Device — assign it to a workspace and set its topic and identifier — see Adding an MQTT Device.
  2. Add MQTT Parameters — for each value in the message payload you want to monitor, add a parameter with its identifier — see Adding MQTT Parameters.

Data flows automatically once the edge device picks up the configuration (within approximately 30 seconds).

Publishing data out to a third-party broker

Separately from ingesting data with an MQTT Device, Enture can also publish parameter values and machine statuses out to an external MQTT broker — for any parameter, regardless of which protocol it was originally collected with (Modbus, OPC UA, S7, EtherNet/IP, or MQTT). This is a distinct, unrelated capability configured via Param MQTT Mapping and Machine Status MQTT Mapping — see Publishing to a Third-Party MQTT Broker.

Next steps