Table of Contents:
MQTT is a publish/subscribe model that runs over TCP/IP sockets or WebSockets. MQTT over WebSockets can be secured with SSL.
The MQTT protocol runs on TCP / IP or other network protocols and provides an ordered, lossless, bidirectional connection. Features include:
The server we use here is ThingSpeak which has an intuitive chart to show the test result for our test.The ThingSpeak IoT service now supports MQTT subscriptions to receive instant updates when ThingSpeak channel gets updated. The method here is general and can be used with other IoT servers for MQTT connection as well.
Message Queuing Telemetry Transport
working principle
Schematic diagram: uplink.In this section, we will try to program LG01 to uplink data to ThingSpeak. The data flow in this example.We have already tried ① and ② in the above simple LoRa example. Now we will try the step ③ first, after it work as expect, we will integrate these three steps together for a complete uplink example.
Schematic diagram:downlink.In this section, we will try to program LG01 to fetch download data from ThingSpeak, then broadcast this data to local LoRa network. The end node will get this message and check if they need to do something. Similar with Uplink Example, we will first try to do it in PC, then do it in Linux side, and finally integrate it with LoRa.
MQTT agreement to achieve the need: client and server There are three identities in the MQTT protocol: Publish, Broker (server), Subscribe. Among them, the publisher and the subscriber of the message are all clients, the broker is the server, and the publisher can be both the subscriber and the subscriber. MQTT transmission of information is divided into: Topic and payload in two parts Topic, can be understood as the type of message subscribers Subscribe, you will receive the theme of the message content (payload) The payload, which can be understood as the content of the message, refers to the specific content to be used by the subscribers.
To use the server, we need to register an account on ThingSpeak . Then create a channel and type the channel info. As shown below, the Channel ID is the unique ID to store our data in ThingSpeak .
Listening on the LoRa wireless channel, while there is new LoRa packet arrives, parse it and send out to IoT Server.
The LoRa End node keeps getting temperature and humidity from the sensor and sends out via LoRa periodically.
Channel ID,Write API Key
Account->My Profile,MQTT API Key
Tips: Please confirm that your LG01 version is 4.3.3.
Overview
Senosor->IOT Server
MQTT->Configure MQTT Server
MQTT->MQTT Channel
Sensor->LoRa/LoraWAN
Configure network access.Network->Internet Access
Open this Application.
Input passward(dragino).After into the console.
First, we need to make sure the LG01 has internet access. We can log in the SSH and ping an Internet address and see if it get through. As below
LG01 has built-in Linux tool mosquitto. It is a very powerful tool for http communication. We can use this tool to handle MQTT API call in LG01. Input this command and replace your keys.
Go to Server check out result.We success to use LG01 to uplink data to ThingSpeak,the mosquitto_pub command is executed in the Linux side, finally, we will have to call mosquitto_pub command with sensor data variable in Arduino side. This is through the process class in Arduino and we will show it in the final sketch.
Open this Application.
Check the settings.
input this command.
Check the result.
Open the sketch MQTT_Simple_Server.(Board:Dragino Yun + UNO or LG01/OLG01,Port:Network ports.)and upload.
Open Serial monitor.
Open Serial monitor.
First, try to run mosquitto_pub in Linux console to send a data to MQTT server.
For example: for ThingSpeak, a MQTT publish command is:
What now we need to put in the LG01 is how to combine this command.
Refer to your server to fill in.
Ex:ThingSpeak Server
According to MQTT commands: mosquitto_pub, we need to put
In the mqtt script, the upper CHANNEL will be replaced by the parameter (remote channel in IoT server). and the WRITE_API will be replaced by the settings in write api key. the DATA will be replaced by the value stored in the /var/iot/channels/LOCAL_CHANNEL file.
MQTT script will keep checking the files in /var/iot/channels/ . If it find a match Local channel, then the MQTT script will send out the data of this local channel to a remote channel according to the setting above.
User can also enable MQTT debug in the LG01 --> IoT Server settings and run logread in Linux console to see how the mqtt command is compose. below is an example:
MQTT Logread example
LG01 for 4.3.3 version,we have added watchdog feature. In order to avoid the gateway running process will get stuck. So add writing action on every times.
Enable Sensor->Micro-Controller settings
Open the sketch MQTT_Simple_Server.(Board:Dragino Yun + UNO or LG01/OLG01,Port:Network ports.)and upload.
Each time the function loops, it uses the watchdog function once.
Open SSH and check watchdog result.If the result change constantly,the feature enable successfully.
If the time doesnt's change,you can refer it to calculate for checking status.