MQTT protocol is a Machine to Machine (M2M) protocol widely used in IoT (Internet of things).
The MQTT protocol is a message based protocol, extremely light-weight and for this reason, it is adopted in IoT. Almost all IoT platforms support MQTT to send and receive data from smart objects.
This tutorial provides an in-depth MQTT tutorial covering:
- how MQTT works
- the MQTT messages
- how to use it in IoT projects
- MQTT security aspects
- how to configure Mosquitto MQTT to handle the MQTT protocol
There are several implementations for different IoT boards like Arduino, Raspberry, ESP32, ESP8266 and so on.
There are other IoT protocols used to implement IoT projects but MQTT is one of the most efficient.
MQTT Protocol Technical description
The MQTT IoT protocol was developed around 1999. The main goal of this protocol was to create a protocol very efficient from the bandwidth point of view. Moreover, it is a very power-saving protocol. For all these reasons, it is suitable for IoT.
This uses the publish-subscribe paradigm in contrast to HTTP based on the request/response paradigm. It uses binary messages to exchange information with low overhead. It is very simple to implement and it is open. All these aspects contribute to its large adoption in IoT. Another interesting aspect is the fact that the MQTT protocol uses TCP stack as a transmission substrate.
The role of the MQTT Broker and MQTT Client
As said before, the MQTT protocol implements a publish-subscribe paradigm. This paradigm decouples a client that publishes a message (“publisher”) to other clients that receive the message (“subscribers”). Moreover, MQTT is an asynchronous protocol, which means that it does not block the client while it waits for the message.
In contrast to the HTTP protocol, that is a mainly asynchronous protocol. Another interesting property of MQTT protocol is that it does not require that the client (“subscriber”) and the publisher are connected at the same time.
The key component in MQTT is the MQTT broker. The main task of MQTT broker is dispatching messages to the MQTT clients (“subscribers”). In other words, the MQTT broker receives messages from the publisher and dispatches these messages to the subscribers.
The MQTT topic
While it dispatches messages, the MQTT broker uses the topic to filter the MQTT clients that will receive the message. The topic is a string and it is possible to combine the topics creating topic levels.
A topic is a virtual channel that connects a publisher to its subscribers. MQTT broker manages this topic. Through this virtual channel, the publisher is decoupled from the subscribers and the MQTT clients (publishers or subscribers) do not have to know each other to exchange data. This makes this protocol highly scalable without a direct dependency from the message producer (“publisher”) and the message consumer (“subscriber”).
The schema below describes the MQTT architecture:
As you may already know there are other IoT protocols that you can use in an IoT as CoAP, HTTP, and so on. If you don’t know other IoT protocols you could give a look at my article.
How to use Cayenne IoT ESP8266 + MQTT
ESP32 MQTT client: Publish and Subscribe
ESP8266 MQTT Client: Publish and Subscribe with Node-RED Dashboard
How to build an Arduino MQTT client
Raspberry Pi IoT: Sensors, InfluxDB, MQTT and Grafana
How to use MQTT protocol with Mosquitto
Now we have an overview of MQTT and it is time to know how to use it using a real example. There are several implementations of MQTT, in this example, we will use Mosquitto, an implementation developed by Eclipse. The first step is installing the MQTT broker. We will install it on Raspberry PI. To install it, we have to add the repository that holds the application, so that we can download it. Before adding the repository it is necessary to add the key to verify that the download package is valid. Let us connect to Raspberry PI using ssh or a remote desktop connection. Now in the terminal, we have to write:
Now, it is time to import the key:
sudo apt-key add mosquitto-repo.gpg.key
Finally, let us add the fil .list:
sudo wget http://repo.mosquitto.org/debian/mosquitto-wheezy.list
Now, that the repository link is configured properly, we can install Mosquitto on Raspberry PI.
apt-get install mosquitto
The MQTT server (aka MQTT broker) is installed on Raspberry Pi. This server is our MQTT broker as specified above. Now we need to install the client, or in other words, the publisher and the subscriber. In this example, we will install the client and server on the same Raspberry but you can install it on a different pc/server or IoT board.
apt-get install mosquitto-clients
How to send an MQTT Message
We have installed and configured the client and the server, now we can register a subscriber to a specific topic and wait for an incoming message from a publisher. To register a subscriber we will use this command:
As you can notice, our subscriber is waiting for a message. In this example, we used a topic called swa_news. Now we will send a message using an MQTT publisher that uses the same topic swa_news.
In the example, the MQTT publisher sends “Hello Protocol” message. On the subscriber side, we get the message:
An important aspect to note is that the MQTT is a plain protocol so the message is clear and everyone can read it.
How to use MQTT on Android smartphone
In this last example, we will use an Android MQTT client so that the same message we sent is received by the Android MQTT client. This video shows how to configure an Android MQTT client.
What does MQTT security mean?
Another important aspect is how to implement MQTT security. In more detail, we will describe how to implement MQTT security using the Mosquitto MQTT broker.
In this context, it is important to talk about MQTT security and it is crucial to know how to securing MQTT protocol and how to protect the information. In the next paragraphs, we will analyze the steps we have to follow to secure MQTT using Raspberry Pi as an MQTT broker.
By its nature, MQTT is a plain protocol that is all the information exchanged is in plain-text format. In other words, everyone could access to this message and read the payload. This could not be a problem if MQTT client and MQTT broker exchange not sensible information. Anyway, they are several use cases where we want to keep the information private and guarantee that it can not be read or modified during the transmitting process. In this case, there are several approaches we can use to face the MQTT security problem:
- Create a VPN between the clients and the server
- Use MQTT over SSL/TSL that encrypts and secure the information between the MQTT clients and MQTT broker
We will focus our attention on how to create an MQTT over SSL. To make MQTT a secure protocol we have to follow these steps:
- Create a private key (CA Key)
- Generate a certificate using the private key (CA cert)
- Create a certificate for Mosquitto MQTT server with the key
The final step is configuring Mosquitto MQTT so that it uses these certificates.
MQTT Security: Securing Mosquitto MQTT server
The first step in this process is creating a private key. Connect to the Raspberry Pi using ssh or a remote desktop as you prefer and open a command terminal. Before starting, it is important you check if OpenSSL is installed in your Raspberry Pi, otherwise, you have to download from here.
Before creating the private key, you should create a directory where you store all the certificates you will create. In the terminal write:
openssl genrsa -out mosq-ca.key 2048
Using this command, we are creating a 2048 bit called
mosq-ca.key. The result is shown in the picture below:
The next step is creating a X509 certificate that uses the private key generated in the previous step. Open the terminal again and in the same directory you used to store the private key write:
openssl req -new -x509 -days365 -key mosq-ca.key -out mosq-ca.crt
In this step, you have to provide different information before creating the certificate as shown in the picture below:
Creating the MQTT server certificate
Once the private key and the certificate are ready, we can move on and create the MQTT server certificate and private key:
openssl genrsa -out mosq-serv.key 2048
Then the server certificate. During this step, we have to create a CSR (Certificate Signing Request). You have to send this certificate to the Certification authority that after verifying the author identity returns a certificate. In this tutorial, we will use a self-sign certificate:
openssl req -new -key mosq-serv.key -out mosq-serv.csr
As you can notice we have used the private key generated in the step before. Finally, we can create the certificate to use in our MQTT Mosquitto Server:
openssl x509 -req -in mosq-serv.csr -CA mosq-ca.crt
-CAkey mosq-ca.key -CAcreateserial
-out mosq-serv.crt -days 365 -sha256
All done! We have completed the steps necessary to secure our MQTT server. You can verify your certificate writing:
openssl x509 -in mosq-serv.crt -noout -text
Now you should see the certificate.
How to configure MQTT Mosquitto Server to secure MQTT
Once the certificates are ready, we have to configure the MQTT Mosquitto server so that it can use these certificates. The certificates we have to use are:
mosquitto.conf file that holds all the configuration parameters and add the following lines:
where the path /home/pi/ssl-cert-mosq is the path where you stored your certificate. Moreover, we change the default Mosquitto MQTT port to 8883.
Now you have to stop and restart Mosquitto MQTT so that it can read the new configuration file:[plain]sudo service mosquitto stop/start[/plain]
That’s all. Now our MQTT protocol is secure and encrypted. The last step is testing the configuration and the MQTT server.
MQTT Security testing Mosquitto over SSL/TSL
In this step, we will verify if the connection is correctly configured. To this purpose, we use MQTT.fx a java based MQTT client. After you installed it, we have to create a new profile providing all the information as shown in the picture below:
Notice that we have enabled the SSL/TSL configuration providing the mosq-ca.crt creating during the previous steps. I wrote another tutorial describing how to use secure MQTT protocol. Amazon AWS uses secure MQTT to exchange data with the devices. If you want to know more about how to use secure MQTT protocol you can read how to connect ESP32 to AWS IoT.
Finally, we can connect to the MQTT Mosquitto server:
clicking on connect. You will notice that the MQTT client will establish the connection to the MQTT broker as you can check in the log tab.
Now it is time to test if our client gets the message. Select the subscribe menu and subscribe to the MQTT client to a topic (choosing a topic name).
On the Raspberry Pi side lets us send a message on the same channel:
mosquitto_pub -p 8883 -t "test" -cafile mosq-ca.crt -m "Hello MQTT" -d -h 192.168.1.8
The result is shown in the picture below:
On the subscriber side we have:
As you can notice, we received the message sent by the publisher.
If you like to see the MQTT protocol in action, please check this article describing how to build an MQTT system using Raspberry, Grafana, and InfluxDB.
At the end of this post, you know how to publish a message using MQTT protocol and to handle MQTT security configure Mosquitto MQTT over SSL/TSL. It is really important to know the MQTT protocol because it is widely used in IoT. Through this tutorial, we have covered some security aspects related to the MQTT. Finally, we have installed an MQTT broker, Mosquitto, that you can use for your next IoT project.