IoTServa Get Started
Protocol Support

MQTT Integration

Subscribe to any broker, publish normalized data back out, and keep topics, QoS and retained state under control.

Standard
OASIS MQTT 3.1.1 (ISO/IEC 20922) and MQTT 5
Medium
TCP and TLS (port 8883), WebSocket
Topology
Publish and subscribe through a broker
Data Model
Topic strings with free-form payloads such as JSON or plain values
Six teal cables of different thicknesses converging into one small white hub, a picture of many sources joining one broker

What MQTT Is

MQTT is a lightweight publish and subscribe protocol. Devices send messages to named topics on a broker, and anything subscribed to a topic receives them. MQTT defines the transport, not the payload, so two vendors can both speak MQTT and still send incompatible data. IoTServa treats a broker as both a source and a destination, and its gateways send signed telemetry through a broker you configure.

Native Address

Topic factory/line-2/oven/temperature
JSON payload {"t":182.4}
QoS 1, retained
Broker over TLS

Node

Factory > Line 2 > Oven Temperature

182.4°C

How IoTServa Connects MQTT

Ingest from Any Broker

Subscribe with topic filters and wildcards, then map each topic and JSON path to a tag with a unit.

Signed Gateway Telemetry

Gateways send signed readings over MQTT 3.1.1 to the broker set in the cloud, so a forged message is rejected.

Publish Normalized Data

Send clean, consistently named values back out to your own broker or a cloud broker, with the QoS you choose.

TLS and Credentials

Connect over TLS with client certificates or a username and password, and keep secrets sealed rather than in project files.

Sparkplug B on the Roadmap

Plain MQTT is read today. Sparkplug B decoding is on the roadmap; until then a bridge can republish its metrics as plain topics.

Typical Jobs

  • Collecting data from third-party gateways and sensors
  • Carrying gateway telemetry to the cloud
  • Bridging two sites through one broker
  • Giving other teams a clean topic structure

Plan for These

  • Choose QoS deliberately. QoS 0 can drop messages, QoS 2 costs more than most telemetry needs.

  • Retained messages make a dashboard show stale data as if it were live unless you track message age.

  • Agree one topic naming scheme per site before devices multiply.

Learn More About MQTT

Look Up a Term in the Glossary or check devices on the Hardware Page

Works Alongside the Others

A site rarely runs a single protocol. The same project can read all eight.

MQTT Questions

Does IoTServa include an MQTT broker?

No. It connects to the broker you already run, or to one you choose, acting as an MQTT client that can both subscribe and publish, over TLS with client certificates or a username and password.

Can IoTServa publish data out as MQTT?

Yes. Every normalized Node can be published to a broker with a topic pattern and QoS you define, so other systems receive clean, consistently named values with units. Data is also available through the REST API, signed webhooks, and CSV and JSON exports.

What do MQTT QoS 0, 1 and 2 mean?

QoS 0 delivers a message at most once with no acknowledgement. QoS 1 delivers at least once, so duplicates are possible. QoS 2 delivers exactly once between each sender and receiver using a four-packet handshake (PUBLISH, PUBREC, PUBREL and PUBCOMP). Higher levels use more bandwidth and add latency, so telemetry often uses 0 or 1 and commands use 1 or 2.

Bring Your MQTT Devices. We Will Read Them.

Tell us the make and model of what is on site. We will scope a pilot against your real equipment.

WhatsApp