We've seen that the HTTP POST protocol is very convenient to connect our LoRaWAN server to the IoT 1
platform. 2
It works for the uplink stream and also to send downlink messages. 3
Now let's stop for a few second and try to analyze the HTTP POST behavior. 4
First, let's imagine that we want to connect another IoT platform. 5
In that case, we need to go on the LoRaWAN server and to configure a new server that needs to be 6
connected. 7
It was not very complicated because we just had to provide the URL endpoint, but still we have to do 8
it. 9
Secondly, when we created this integration on the LoRaWAN server we defined which event had to be sent. 10
In our case, we decided to send all uplink data. 11
If your application needs more information, let's say the join accept frames, or acknowledgment, 12
then we need to go back on the server to configure it. 13
Again, it's not complicated, but still you have to do it. 14
The third point is that if for some reason your IoT platform is disconnected for a few seconds, then 15
the HTTP request will not reach your endpoint. 16
There is a good chance that your data will be definitely lost. 17
And finally, in some situation, the HTTP client can think that the request has not been received, 18
whereas the endpoint had received the message. 19
That could lead to duplicate messages on the IoT platform. 20
However, the HTTP POST method is widely used, so we absolutely not consider it's a bad way to connect 21
the LoRaWAN server with the IoT platform. 22
But we'll see now, 23
another way to connect them. 24
It's actually a new protocol that we are going to explain. 25
It supports duplicate messages, the disconnection. 26
I will also be a lightweight protocol in order to deal with thousands of potential connection at the 27
same time. 28
This protocol is called MQTT. 29
It's going to be the topic of the next video.