Industrial MQTT topic design: names, payloads and data contracts
Design a stable telemetry namespace with identity, timestamps, units, quality and schema ownership before connecting dashboards and consumers.
MQTT messaging for telemetry, UNS architectures, and device connectivity.
Learning paths & worksheets: Industrial data connectivity: from register to consumer · Industrial data contract template
Design a stable telemetry namespace with identity, timestamps, units, quality and schema ownership before connecting dashboards and consumers.
The decisions that matter before an MQTT edge gateway leaves the lab: protocol drivers, buffering, namespaces, quality, security, and ownership.
One broker, one topic tree, every producer and consumer decoupled. What a UNS is, what it demands, and where it goes wrong.
The topic namespace, birth certificates, and state awareness that turn MQTT from a transport into a plug-and-play OT data fabric.
Three technologies that get compared as rivals but usually work as layers. What each one owns, and how to stop choosing between them.
The three MQTT features that decide whether your telemetry is lossy, stale, or exactly-once — and when each setting is correct.
Protocol conversion, buffering, and context at the edge — the four gateway patterns that connect legacy equipment to modern platforms.
The MQTT organization homepage: protocol resources, version history, and links to brokers, clients, and the OASIS standard.
The Eclipse Sparkplug project: specification, TCK, compatible products, and working-group resources for MQTT-based OT interoperability.
HiveMQ's technical blog: MQTT features, Sparkplug, broker operations, and IIoT architecture at scale.
Opto 22's OptoBlog: edge devices, Node-RED, MQTT/Sparkplug, and practical IIoT project writeups.
Industrial IoT / IIoT · Sparkplug B · OPC UA · Edge Computing · Factory Software · Industrial Networking