HiveMQ Blog — MQTT in depth
HiveMQ's technical blog: MQTT features, Sparkplug, broker operations, and IIoT architecture at scale.
Search
Search articles, calculators, worksheets, learning paths, glossary terms and the external index. Filter by resource type or topic, with or without a keyword.
Industrial MQTT gateway checklist for a brownfield plant
The decisions that matter before an MQTT edge gateway leaves the lab: protocol drivers, buffering, namespaces, quality, security, and ownership.
MQTT QoS, retained messages, and sessions, explained
The three MQTT features that decide whether your telemetry is lossy, stale, or exactly-once — and when each setting is correct.
MQTT: the standard for IoT messaging
The MQTT organization homepage: protocol resources, version history, and links to brokers, clients, and the OASIS standard.
QoS (MQTT)
MQTT delivery guarantees: 0, 1, or 2. — MQTT quality of service: QoS 0 (at most once), QoS 1 (at least once, may duplicate), QoS 2 (exactly once). Negotiated per hop and capped by the subscription — publishing high to a low-QoS subscriber still delivers at most once.
Retained MQTT message
The latest retained application message stored by a broker for a topic and delivered to matching new subscribers under MQTT rules. — A retained value is not a history archive and does not prove that its source remains connected or fresh. Include source time and stale behavior in…
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
Lightweight pub/sub transport for telemetry and events. — A lightweight publish/subscribe messaging protocol (OASIS standard): clients publish to topic strings on a broker, subscribers receive matching messages. Features QoS levels, retained messages, persistent sessions, and Las…
OPC UA, MQTT, and Sparkplug B: how they fit together
Three technologies that get compared as rivals but usually work as layers. What each one owns, and how to stop choosing between them.
MQTT
MQTT messaging for telemetry, UNS architectures, and device connectivity.
Eclipse Sparkplug — specification and resources
The Eclipse Sparkplug project: specification, TCK, compatible products, and working-group resources for MQTT-based OT interoperability.
Industrial data connectivity: from register to consumer
Build a trustworthy data path through Modbus, OPC UA, MQTT, Sparkplug and historian storage, with explicit identity and quality.
OptoBlog — edge & IIoT practices
Opto 22's OptoBlog: edge devices, Node-RED, MQTT/Sparkplug, and practical IIoT project writeups.
Sparkplug B in one page
The topic namespace, birth certificates, and state awareness that turn MQTT from a transport into a plug-and-play OT data fabric.
Topic namespace
Governed MQTT topic hierarchy. — The governed topic hierarchy of an MQTT deployment or UNS — naming conventions, schema rules, and lifecycle management that keep one broker understandable at enterprise scale.
Edge gateway patterns for brownfield connectivity
Protocol conversion, buffering, and context at the edge — the four gateway patterns that connect legacy equipment to modern platforms.
Industrial data contract
An owned agreement about a signal’s identity, datatype, units, timestamps, quality and consumer behavior. — Transport protocols move data; the contract makes its meaning and failure handling explicit. Include schema revision and migration rules, plus behavior for stale, duplicate…
Industrial data contract template
A CSV signal contract for asset identity, source, datatype, units, timestamp, quality, stale behavior and schema revision.
Source timestamp
The time associated with sampling or producing a value at its source. — Source time differs from gateway receipt, broker delivery and archive insertion. Preserve the distinction and define clock synchronization, time representation and stale thresholds. Republishing a cached read…
The unified namespace, explained
One broker, one topic tree, every producer and consumer decoupled. What a UNS is, what it demands, and where it goes wrong.
Kepware
Multi-protocol connectivity server, now part of Velotic. — Industrial connectivity software exposing hundreds of device and PLC protocols through OPC UA, MQTT, and other northbound interfaces. Originally by PTC, now part of Velotic alongside Proficy and ThingWorx.
Kepware industrial connectivity (Velotic)
Kepware (now part of Velotic): industrial connectivity software exposing hundreds of device protocols via OPC UA, MQTT, and more.
OPC UA PubSub
OPC UA's scalable publish/subscribe communication model. — OPC UA Publish-Subscribe: a connection-oriented or connectionless OPC UA communication model for one-to-many and many-to-many distribution. UDP with UADP or MQTT/AMQP mappings can serve different scale, routing, and timin…
Sparkplug B
MQTT namespace + payload + state spec for OT. — The Eclipse specification turning MQTT into a plug-and-play OT fabric: a fixed topic namespace (group/message-type/edge-node/device), protobuf payloads, and birth/death session semantics giving state awareness without polling.
Sparkplug B
Sparkplug B: MQTT namespace and payload spec for plug-and-play IIoT.
Store and forward
Buffering through outages, replaying on recovery. — Buffering data locally through connectivity outages and replaying it in order on recovery. Implemented in edge gateways, MQTT persistent sessions, and historian collectors; sized by the longest plausible outage.
Unified namespace
One broker hierarchy as the enterprise integration point. — Unified namespace: an architecture with a single MQTT broker hierarchy as the enterprise integration point — producers publish once, consumers subscribe independently. Requires governed topics (usually Sparkplug for OT)…
27 results.