In the last video, we saw a first method to request messages received under the LoRaWAN server. 1
This method is interesting because it's very simple. 2
Whenever we need to get the uplink message, then we just ask for it. 3
But if we analyze it closer, we can see a few drawbacks. 4
The first drawback is that we only worked on the uplink stream. 5
There is no possibility to send a downlink message to the LoRaWAN server with this kind of request. 6
Why? 7
Simply because no LoRaWAN server has implemented the possibility to ask to the user, the downlink message to 8
send to the device. 9
It doesn't really matter because we'll see other methods to do so. 10
But we have to keep in mind that with HTTP GET request, we can only get the uplink message from the 11
server, but we can't send downlink message to it. 12
The second drawback is that for the uplink stream, we spend our time requesting data that potentially 13
doesn't exist. 14
We request data without knowing if it has been received. 15
So, for example, if a sensor is sending, let's say a few times a day, then we'll have to make periodic 16
requests with a high chance of receiving empty responses. 17
That's definitely not efficient because it increases unnecessarily the network load. 18
So if this HTTP GET request is so bad, then you could ask why does it exist? 19
Actually, if for some reasons on our IoT platform, we've had a problem during a certain time, then 20
we will be very happy to know that these data are still on the LoRaWAN server for a few hours and 21
we can get them with the HTTP GET request. 22
So what can we do to improve the data transmission between the LoRaWAN server and the IoT platform? 23
From the IoT platform side, instead of asking for data. 24
Then, it would be a much better idea to receive them whenever they are available. 25
It's possible and very simple. 26
We just need to reorganize the client and server rules. 27
And now the client Pushes the message to the server. 28
It's possible because the request is not a GET request anymore, but a POST request. 29
That's what we're going to explain in the next video.