MQTT

---

CONNECTIVITY PORTFOLIO | What is MQTT?

What is MQTT?

MQTT, or Message Queuing Telemetry Transport, is a lightweight publish (send a message) – subscribe (wait for a message) protocol.

Publishing means that data is uploaded to a well-defined place (called topic) on a central server (called message-broker). Subscribing means that data is downloaded from a topic of the message broker, once it was published there. MQTT hence is an event-driven communication protocol, notifying a subscriber once a data message has arrived on its topic.

What is MQTT used for?

MQTT was designed to be used on networks that have low-bandwidth, high-latency and could be unreliable. Since it was designed with these constraints in mind, it’s perfectly suitable for sending data between devices and is very common in the IoT world.

It is supported by major IoT cloud providers, such as Azure, AWS, Google, but also by players specialized in industrial use cases, e.g. Adamos, Mindsphere, Bosch IoT, to name a few. 

MQTT implementation with Cybus

MQTT is the main protocol of the Connectware data interface. Connectware supports MQTT 3.1, MQTT 3.1.1 and MQTT 5. Although data can be provided to or retrieved from the Connectware using most of the supported protocols, MQTT remains the preferred protocol for data exchange with external applications. The advantages mentioned above make MQTT an ideal option for most IoT use cases.

The Connectware MQTT message-broker always runs as a component of the Connectware itself and is started automatically. Data access to remote users (i.e. “to the Internet”) can be granted by locally allowing specific users to read or write on specific topics.