MQTT is a lightweight publish-subscribe mode messaging protocol designed for IoT applications in low-bandwidth and unstable network environments. MQTT is based on the publish/subscribe paradigm and works on the TCP/IP protocol family. MQTT protocol is lightweight, simple, open and easy to implement， which makes it suitable for a wide range of applications.
MQTT is based on the client-server communication mode. MQTT server is called as MQTT Broker. Currently, there are many MQTT Brokers in the industry, whose advantages and disadvantages and functional differences will not be discussed in this article. Taking the most popular MQTT broker - EMQX in the open source community as an example, this article uses the public Broker
broker.emqx.io provided by EMQ , and uses a simple example of connecting Broker, publishing and processing messages by client to summarizes the usage and examples of MQTT client libraries under different programming languages and platforms.
The selected MQTT client libraries are as follows:
- Eclipse Paho C and Eclipse Paho Embedded C
- Eclipse Paho Java Client
- Eclipse Paho MQTT Go client
- emqtt : Erlang mqtt client library provided by EMQ
- MQTT.js Web & Node.js Platform MQTT Client
- Eclipse Paho Python
Sample application introduction
The action of the MQTT client throughout its lifecycle can be summarized as: establishing a connection, subscribing to a topic, receiving and processing a message, publishing a message to a specified topic, unsubscribing, and disconnecting.
The standard client library shows the corresponding method in each link. The meaning of the method parameters required by different libraries in the same link is roughly the same. The specific parameters to be selected and the functional features to be enabled need the user to have a deep understanding of the MQTT protocol features and to be determined in combination with the actual application scenarios.
This paper takes a client connecting, publishing and processing messages as an example to show the parameters to be used in each link:
- Establish a connection：
- Specify the MQTT Broker basic information access address and port
- Specify whether the transfer type is TCP or MQTT over WebSocket
- If TLS is enabled, it is required to select the protocol version with the corresponding certificate.
- If Broker has enabled authentication, the client needs to carry the corresponding MQTT Username Password information
- Configure client parameters such as keepalive duration, clean session callback retention flag, MQTT protocol version,will message (LWT), etc.
- Subscribe to the topic : After the connection is successfully established, the topic can be subscribed to when the topic information is specified.
- Specify topic filter Topic, support for the use of the topic wildcards
# during subscribing
- Specify QoS, Qos 0 1 2 is optional according to the implementation of the client library and the broker. Note that some brokers and cloud service providers do not support some QoS levels. For example, AWS IoT, Alibaba Cloud IoT Suite, and Azure IoT Hub do not support QoS 2 Level message
- Subscribing to topics may fail due to network issues or Broker ACL rule restrictions
- Receive messages and process:
- Generally, the processing function is specified at the time of connection. The processing method is slightly different depending on the network programming model of the client library and the platform.
- Publishing a message: Publish a message to a specified topic
- Specify the target topic. Note that the topic cannot contain the wildcard
#, which may lead to message publishing failure and client disconnection (depending on the implementation of broker and Client Library)
- Specify the message QoS level. There are also different QoS levels supported by different brokers and platforms. For example, if Azure IoT Hub publishes a message of QoS 2, it will disconnect the client
- Specify the message body content, whose size cannot exceed the maximum message size set by the broker
- Specify message Retain flag
- Specify the target topic
- Proactively disconnect with issuing a Will Message (LWT)
Eclipse Paho C and Eclipse Paho Embedded C
Both Eclipse Paho C and Eclipse Paho Embedded C are client libraries under the Eclipse Paho project, which are full-featured MQTT clients written in ANSI C. Eclipse Paho Embedded C can be used on desktop operating systems, but mainly for Embedded environments such as mbed，Arduino and FreeRTOS .
The client has two kinds of APIs, synchronous and asynchronous, which start with mqttclient and mqttasync respectively:
- The Synchronization API is designed to be simpler and more useful, and some calls will block until the operation is complete, making programming easier.
- There is only one call block
API-waitForCompletion in the asynchronous API, and the result is notified through the callback, which is more suitable for the environment of the non-main thread.
For detailed download and usage instructions of the two libraries, please go to the project home page to view. This article uses Eclipse Paho C to provide the sample code directly as follows:
Eclipse Paho Java Client
Eclipse Paho Java Client is an MQTT client library written in Java that can be used with JVM or other Java compatible platforms such as Android.
The Eclipse Paho Java Client provides the MqttAsyncClient and MqttClient as asynchronous and synchronization APIs.
Install via Maven:
The connection sample code is as follows:
Callback message processing class OnMessageCallback.java
Eclipse Paho MQTT Go client
Eclipse Paho MQTT Go Client is the Go language client library for the Eclipse Paho project, which can connect to the MQTT Broker to publish messages, subscribe to topics and receive published messages and support a completely asynchronous mode of operation.
The connection sample code is as follows:
emqtt : Erlang MQTT client library provided by EMQ
emqtt is a client library officially provided by EMQ of the open source MQTT Broker EMQX, which is applicable for the Erlang language.
The Erlang ecosystem has several MQTT Broker implementations, such as RabbitMQ, VerenMQ, EMQX, etc. that support MQTT through plugins. However, there is almost no room for choice in the MQTT client library. emqtt in the Erlang client library included in the MQTT community is the best choice .
Emqtt is implemented entirely by Erlang and completely supports the MQTT v3.1.1 and MQTT v5.0 protocol. It also supports SSL single and two-way authentication and WebSocket connection. Another MQTT benchmarking tool emqtt_bench is built based on this client library.
emqtt is used as follows:
MQTT.js Web & Node.js platform MQTT client
-g global installation can be done with a command line, and it can be integrated into the project for callback.
- Browser environment: MQTT over WebSocket (including custom browser environment such as WeChat applet, Alipay applet)
- Node.js environment: MQTT, MQTT over WebSocket
In addition to a few different connection parameters in different environments, other APIs are the same.
Install with NPM:
Install with CDN (browser):
Eclipse Paho Python
Eclipse Paho Python is the Python language client library under the Eclipse Paho project, which can connect to the MQTT Broker to publish messages, subscribe to topics and receive Published message.
Install with the PyPi package management tool:
This is the introduction of MQTT protocol, MQTT client library usage process and common MQTT clients. Readers are welcome to learn MQTT and develop projects through EMQX.