MQTT
Explore practical guides to MQTT for industrial data collection, including message delivery, broker configuration, data reliability, troubleshooting, security, and integration with time-series databases and industrial historians.
Sparkplug B vs. Plain MQTT: When Do Industrial Systems Need More Structure?
Plain MQTT is intentionally flexible. It moves a topic and an application payload between clients through a broker, but it does not say how a
TDengine Team
October 30, 2026 | MQTT
How to Design MQTT Topic Hierarchies for Industrial Equipment
An MQTT topic convention can look tidy during a pilot and become unmanageable after the second plant, a new equipment vendor, or the first external
TDengine Team
October 30, 2026 | MQTT
MQTT Timestamps: Source Time vs. Ingestion Time in Industrial Data
An MQTT message can arrive at the broker or historian long after the physical measurement occurred. If that arrival time becomes the historian timestamp, a
TDengine Team
October 29, 2026 | MQTT
MQTT Store and Forward: How to Reduce Historian Data Gaps During Network Outages
An MQTT connection can recover while a historian still has a permanent gap. The missing question is not simply whether the broker or collector reconnects.
TDengine Team
October 28, 2026 | MQTT
How to Secure MQTT Data Collection Across OT and IT Networks
MQTT can move industrial telemetry across network boundaries without giving every IT system direct access to control systems. That outcome depends on the architecture around
TDengine Team
October 28, 2026 | MQTT
MQTT Retained Messages vs. Persistent Sessions: What’s the Difference?
An industrial MQTT client reconnects after losing network access. Should it receive the latest equipment state, or every eligible message published while it was offline?
TDengine Team
October 27, 2026 | MQTT
MQTT QoS 0 vs. 1 vs. 2: Which Should You Use for Industrial Data?
For most industrial telemetry, QoS 1 is the practical starting point. It reduces the risk of losing a message on an MQTT delivery hop, but
TDengine Team
October 27, 2026 | MQTT
How to Map MQTT JSON Payloads to Historian Tables and Tags
An MQTT message is only a topic plus a payload. A useful historian record needs more: stable equipment identity, typed measurements, a trustworthy time, and
TDengine Team
October 27, 2026 | MQTT
MQTT Broker vs. Historian: Why Message Delivery Is Not Data History
An MQTT broker moves application messages between publishers and subscribers. A historian preserves time-indexed records so engineers can query, trend, aggregate, and investigate them later.
TDengine Team
October 27, 2026 | MQTT
Why Are MQTT Messages Reaching the Broker but Not the Historian?
The MQTT broker shows incoming messages. Your publisher is online, and a dashboard may even display the latest value. But the historian has no new
TDengine Team
October 27, 2026 | MQTT
