Skip to Content

Changes for page MQTT Forward Instruction

Last modified by Xiaoling on 2025/07/31 16:59
From version 1.5
edited by Xiaoling
on 2022/05/12 15:47
Change comment: There is no comment for this version
To version 52.1
edited by Kilight Cao
on 2024/08/31 15:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -1,397 +1,102 @@
1 -**~ Contents：**
1 +**~ Table of Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -= 1. Introduction =
6 += 1.  Introduction =
7 7  
8 +
8 8  Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
9 9  
10 -== 1.1 Support Devices ==
11 11  
12 +== 1.1  Support Devices ==
13 +
14 +
12 12  This MQTT forward instruction is for below devices:
13 13  
14 -* Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
15 -* LG01N, OLG01N (Warning: LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>url:https://wiki.dragino.com/index.php/Through_MQTT_to_upload_data]])
17 +* LG01N, OLG01N ((% style="color:red" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>doc:Main.Through MQTT to upload data.WebHome]])
16 16  * LG02, OLG02
17 -* LG308, DLOS8
18 -* LPS8
19 -* LIG16
19 +* LG308, DLOS8, LPS8, LIG16
20 20  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
21 +* LG308N, DLOS8N, LPS8N
22 +* LPS8V2
21 21  
22 22  
23 -= 2. Firmware Change Log for MQTT feature =
25 +The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands.
24 24  
25 -This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
27 +Check out this link for more mosquito-related directives **[[https:~~/~~/mosquitto.org/man/mosquitto_pub-1.html>>https://mosquitto.org/man/mosquitto_pub-1.html]]**
26 26  
27 -* LG02_LG08-5.3.1580178039
28 -** Initiate version
29 29  
30 += 2.  Example to communicate to a simple MQTT server =
30 30  
31 -= 3. MQTT forward operating principle =
32 +== 2.1  Overview ==
32 32  
33 -== 3.1 Network Structure ==
34 34  
35 -Below shows the network structure for MQTT forwarding.
35 +This section is an example to show how to set up LG01-N to communicate with a MQTT server. The MQTT server is a simple utility set up in a local PC. Note: User can set up same server via [[this instruction>>url:http://www.steves-internet-guide.com/install-mosquitto-broker/]].
36 36  
37 -* For Uplink: The sensor sends data to LoRa Gateway via LoRa wireless, The gateway will process these data and forward to remote MQTT Broker via Internet.
38 -* For Downlink: The gateway subscribe a topic in the MQTT broker, when there is update on the topic, the gateway will know and broadcast the data to Local LoRa network,
39 39  
40 -[[~[~[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png~|~|height="348" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_1.png]]
38 +== 2.2  Simulate via MQTT.fx utility ==
41 41  
42 -General MQTT structure
43 43  
44 -== 3.2 How sensor data is forwarded ==
45 -
46 -In this MQTT forward feature, the key point is how the gateway process the sensor data.
47 -
48 -=== 3.2.1 Upstream ===
49 -
50 -Assume there are two sensor nodes, their ID are Node1 ID: 6734 , Node2 ID: 7456. In the remote MQTT broker there are two topics: Topic1: /channel/765800, Topic2: /channel/367860. We can set up in the gateway to map Node1 to Topic1 and Node2 to Topic2. So when there is a sensor data from Node1, the gateway will forward the data to Topic1, when there is sensor data from Node2, the gateway will forward to Topic2.
51 -
52 -The data flow works as below diagram.
53 -
54 -[[~[~[image:https://wiki.dragino.com/images/thumb/2/2a/MQTT_Forward_2.png/600px-MQTT_Forward_2.png~|~|height="355" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_2.png]]
55 -
56 -Upstream path
57 -
58 -Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>
59 -
60 -=== 3.2.2 Downstream ===
61 -
62 -The gateway subscribes to a topic of the remote MQTT broker topic. When there is some one publish a value on this topic. The gateway will get it and broadcast to local LoRa Network.
63 -
64 -Below are the data flow for downstream.
65 -
66 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png~|~|height="368" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_3.png]]
67 -
68 -Downstream path
69 -
70 -
71 -== 3.3 Macro Definition ==
72 -
73 -The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
74 -
75 -Currently the -t (topic) and -m (message) support Macros.
76 -
77 -=== 3.3.1 -t topic macro ===
78 -
79 -* CHANNEL: Remote Channel ID
80 -* CLIENTID: Client ID , Same as -i
81 -* WRITE_API: Remote Channel Write API
82 -* USERNAME: User ID (-u)
83 -* HOSTNAME: Device Hostname
84 -
85 -=== 3.3.2 -m message macro ===
86 -
87 -* HOSTNAME: Device Hostname
88 -* CHANNEL: Remote Channel ID
89 -* DATA: Sensor Data without time stamp and rssi
90 -* META: Completely sensor data with time stamp and rssi
91 -* JSON: Convert META to json format.
92 -
93 -=== 3.3.3 Example for Macro ===
94 -
95 -[[~[~[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_9.png]]
96 -
97 -MQTT Publish configure
98 -
99 -Above screen shots shows below format:
100 -
101 -* -t: CLIENTID/CHANNEL/data
102 -* -m: DATA
103 -
104 -When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:
105 -
106 -[[~[~[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png~|~|height="325" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_20.png]]
107 -
108 -Sensor Data
109 -
110 -According to above macro. Gateway will publish field1=22.0&field2=49.0 to topic: dragino-1b7060/78901/data, where 78901 is the remote channel for this node ID.
111 -
112 -
113 -== 3.4 Modify the MQTT to support more options ==
114 -
115 -The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands. User can check the valid options by command mosquitto_pub ~-~-help. as below:
116 -
117 -{{{root@dragino-1ec39c:~# mosquitto_pub --help
118 -mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
119 -mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
120 - 
121 -Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
122 - {-f file | -l | -n | -m message}
123 - [-c] [-k keepalive] [-q qos] [-r] [--repeat N] [--repeat-delay time]
124 - [-A bind_address]
125 - [-i id] [-I id_prefix]
126 - [-d] [--quiet]
127 - [-M max_inflight]
128 - [-u username [-P password]]
129 - [--will-topic [--will-payload payload] [--will-qos qos] [--will-retain]]
130 - [{--cafile file | --capath dir} [--cert file] [--key file]
131 - [--ciphers ciphers] [--insecure]
132 - [--tls-alpn protocol]
133 - [--tls-engine engine] [--keyform keyform] [--tls-engine-kpass-sha1]]
134 - [--psk hex-key --psk-identity identity [--ciphers ciphers]]
135 - [--proxy socks-url]
136 - [--property command identifier value]
137 - [-D command identifier value]
138 - mosquitto_pub --help
139 - 
140 - -A : bind the outgoing socket to this host/ip address. Use to control which interface
141 - the client communicates over.
142 - -d : enable debug messages.
143 - -D : Define MQTT v5 properties. See the documentation for more details.
144 - -f : send the contents of a file as the message.
145 - -h : mqtt host to connect to. Defaults to localhost.
146 - -i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id.
147 - -I : define the client id as id_prefix appended with the process id. Useful for when the
148 - broker is using the clientid_prefixes option.
149 - -k : keep alive in seconds for this client. Defaults to 60.
150 - -L : specify user, password, hostname, port and topic as a URL in the form:
151 - mqtt(s)://[username[:password]@]host[:port]/topic
152 - -l : read messages from stdin, sending a separate message for each line.
153 - -m : message payload to send.
154 - -M : the maximum inflight messages for QoS 1/2..
155 - -n : send a null (zero length) message.
156 - -p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS.
157 - -P : provide a password
158 - -q : quality of service level to use for all messages. Defaults to 0.
159 - -r : message should be retained.
160 - -s : read message from stdin, sending the entire input as a message.
161 - -t : mqtt topic to publish to.
162 - -u : provide a username
163 - -V : specify the version of the MQTT protocol to use when connecting.
164 - Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311.
165 - --help : display this message.
166 - --repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
167 - --repeat-delay : if using --repeat, wait time seconds between publishes. Defaults to 0.
168 - --quiet : don't print error messages.
169 - --will-payload : payload for the client Will, which is sent by the broker in case of
170 - unexpected disconnection. If not given and will-topic is set, a zero
171 - length message will be sent.
172 - --will-qos : QoS level for the client Will.
173 - --will-retain : if given, make the client Will retained.
174 - --will-topic : the topic on which to publish the client Will.
175 - --cafile : path to a file containing trusted CA certificates to enable encrypted
176 - communication.
177 - --capath : path to a directory containing trusted CA certificates to enable encrypted
178 - communication.
179 - --cert : client certificate for authentication, if required by server.
180 - --key : client private key for authentication, if required by server.
181 - --keyform : keyfile type, can be either "pem" or "engine".
182 - --ciphers : openssl compatible list of TLS ciphers to support.
183 - --tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1.
184 - Defaults to tlsv1.2 if available.
185 - --insecure : do not check that the server certificate hostname matches the remote
186 - hostname. Using this option means that you cannot be sure that the
187 - remote host is the server you wish to connect to and so is insecure.
188 - Do not use this option in a production environment.
189 - --tls-engine : If set, enables the use of a TLS engine device.
190 - --tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.
191 - --psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.
192 - --psk-identity : client identity string for TLS-PSK mode.
193 - --proxy : SOCKS5 proxy URL of the form:
194 - socks5h://[username[:password]@]hostname[:port]
195 - Only "none" and "username" authentication is supported.
196 - 
197 -See https://mosquitto.org/ for more information.}}}
198 -
199 -
200 -and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:
201 -
202 -{{{# Call MQTT Publish command
203 - 
204 -# 1. Case with User, Password and Client ID present (e.g. Azure)
205 -if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
206 - case="1"
207 - mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data"
208 - 
209 -# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
210 -elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
211 - case="2"
212 - mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic --cert $cert --key $key $C $cafile $PUB_FLAG "$mqtt_data"
213 - 
214 -# 3. Case with no User, Certificate or ClientID present
215 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
216 - case="3"
217 - mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
218 - 
219 -# 4. Case with no User, Certificate, but with ClientID present
220 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
221 - case="4"
222 - mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
223 - 
224 -# 5. Case with User and ClientID present, but no Password and no Certificate present
225 -elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
226 - case="5"
227 - mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
228 - 
229 -# 6. Case with User and Password present, but no ClientID and no Certificate present
230 -elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
231 - case="6"
232 - mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
233 - 
234 -# 0. Else - invalid parameters, just log
235 -else
236 - case="Invalid parameters"
237 - logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
238 -fi}}}
239 -
240 -
241 -= 4. Example to communicate to a simple MQTT server =
242 -
243 -== 4.1 Overview ==
244 -
245 -This section is an example to show how to set up LG01-N to communicate with a MQTT server. The MQTT server is a simple utility set up in a local PC. Note: User can set up same server via [[this instruction>>url:http://www.steves-internet-guide.com/install-mosquitto-broker/]].
246 -
247 -== 4.2 Simulate via MQTT.fx utility ==
248 -
249 249  The [[MQTT.fx>>url:http://mqttfx.jensd.de/index.php/download]] is a MQTT client tool. We can use this to simulate a MQTT connection to our MQTT broker first to make sure the MQTT broker works. This will also help us understand how it works.
250 250  
43 +(((
251 251  In this test, the MQTT broker and MQTT.fx are installed in the same PC, so the MQTT server address in MQTT.fx should be localhost. Below shows how to connect to the server.
45 +)))
252 252  
253 -[[~[~[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png~|~|height="201" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_4.png]]
47 +[[image:image-20220527134929-6.png]]
254 254  
255 255  Connect to MQTT Broker
256 256  
51 +
257 257  After connected, use publish to public some thing to MQTT server. This to simulate upsteam
258 258  
259 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png~|~|height="149" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_5.png]]
54 +[[image:image-20220527135037-7.png]]
260 260  
261 261  Upstream: Publish message to MQTT Broker
262 262  
58 +
263 263  To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
264 264  
265 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png~|~|height="279" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_6.png]]
61 +[[image:image-20220527135215-8.png]]
266 266  
267 267  Downstream: Subscribe a topic to get downstream
268 268  
269 269  
270 -== 4.3 Simulate via Dragino Command Line ==
271 271  
272 -For first try of MQTT connection, simulate via command line is recommend, there are many servers / connection type for MQTT. They are using different connection parameters. Simulating the connection via command line will help us rapidly connect to server and debug.
67 += 3. Add LoRa support to communicate with remote sensor =
273 273  
274 -In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
275 275  
70 +In above section, we have configured the UI to support MQTT upstream and downstream. We can simulate via Linux command. In this section, we will guide how to communicate with remote LoRa End Node for upstream and downstream.
276 276  
277 -For Upstream
278 278  
279 -command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
280 280  
281 -Example: mosquitto_pub -h 192.168.199.148 -p 1883 -t /channel/6543 -m temp=36
74 +== 3.1  Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ==
282 282  
283 -Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
284 284  
285 -[[~[~[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png~|~|height="188" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_6.png]]
77 +(((
78 +We can use **[[LoRa Shield>>url:http://www.dragino.com/products/lora/item/102-lora-shield.html]]** to send LoRa Raw data to Gateway and receive data from gateway.
79 +)))
286 286  
287 -mosquitto_pub
81 +(((
82 +The example Sketch for LoRa Shield +Arduino is here: **[[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]**
83 +)))
288 288  
85 +(((
86 +And this link is the required library: **[[arduino-LoRa-master>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]**. Unzip this library and put in Arduino library location.
289 289  
290 -For Downstream
88 +
89 +)))
291 291  
292 -Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
293 -
294 -[[~[~[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png~|~|height="267" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_7.png]]
295 -
296 -mosquitto_sub
297 -
298 -== 4.4 Configure Dragino UI for MQTT connection ==
299 -
300 -This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
301 -
302 -Go to Dragino Menu ~-~-> MQTT Client
303 -
304 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png~|~|height="249" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_8.png]]
305 -
306 -go to mqtt configure menu
307 -
308 -Select Forward to MQTT server. Notice: This option is removed from the latest firmware, in the latest firmware, if user submit "SAVE & APPLY" in MQTT page, the gateway will use MQTT service.
309 -
310 -[[~[~[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png~|~|height="240" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Commands_8.png]]
311 -
312 -forward to MQTT
313 -
314 -=== 4.4.1 Configure the MQTT Client for Upstream ===
315 -
316 -Below screenshot is same as the publish command:
317 -
318 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
319 -//where the CLIENTID, CHANNEL & DATA are macro. represent for
320 -//CLIENTID: dragino-1b7060
321 -//CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
322 -//DATA: The data stores in /var/iot/channels/
323 -}}}
324 -
325 -[[~[~[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_9.png]]
326 -
327 -MQTT Publish configure
328 -
329 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png~|~|height="544" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_10.png]]
330 -
331 -MQTT Channel settings
332 -
333 -For example, if we put a data(temp=46) on the file /var/iot/channels/4567, because 4567 match the remote channel 78901. the gateway will run this command:
334 -
335 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
336 -}}}
337 -
338 -to MQTT broker.
339 -
340 -
341 -Below is a simulation to put this data to active the MQTT publish.
342 -
343 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png~|~|height="308" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_11.png]]
344 -
345 -MQTT Publish
346 -
347 -
348 -=== 4.4.2 Configure the MQTT Client for Downstream ===
349 -
350 -Below screen shot equal to this subscribe command:
351 -
352 -{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
353 -}}}
354 -
355 -[[~[~[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png~|~|height="173" width="579"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_12.png]]
356 -
357 -MQTT Subscribe
358 -
359 -
360 -When MQTT broker receive a update on this topic, the gateway will get the update and use LoRa radio to broadcast this message. The LoRa parameters used for update is:
361 -
362 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png~|~|height="300" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_13.png]]
363 -
364 -LoRa Broadcast parameters.
365 -
366 -
367 -And below is the subscribe simulation:
368 -
369 -[[~[~[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png~|~|height="255" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_14.png]]
370 -
371 -downstream simulation
372 -
373 -
374 -\\
375 -
376 -== 4.5 Add LoRa support to communicate with remote sensor ==
377 -
378 -In above section, we have configured the UI to support MQTT upstream and downstream. We can simulate via Linux command. In this section, we will guide how to communicate with remote LoRa End Node for upstream and downstream.
379 -
380 -=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
381 -
382 -We can use [[LoRa Shield>>url:http://www.dragino.com/products/lora/item/102-lora-shield.html]] to send LoRa Raw data to Gateway and receive data from gateway.
383 -
384 -The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]
385 -
386 -And this link is the required library: [[arduino-LoRa-master>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]. Unzip this library and put in Arduino library location.
387 -
91 +(((
388 388  What does the Arduino Sketch do? The Arduino Sketch will:
93 +)))
389 389  
390 390  * Upstream: Keep sending a LoRa Message every minutes with this payload : <4567>tem=xx&hum=yy (Where xx and yy are temperature and humidity value generated randomly).
391 391  * Downstream: Listening broadcast message from gateway, and print it in console.
392 392  * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
393 393  
394 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png~|~|height="197" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_17.png]]
99 +[[image:image-20220527140354-18.png]]
395 395  
396 396  LoRa Parameter should match
397 397  
... ... @@ -398,110 +398,112 @@
398 398  
399 399  Below is the test result after the Arduino Sketch is running.
400 400  
401 -[[~[~[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png~|~|height="319" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_18.png]]
106 +[[image:image-20220527140459-19.png]]
402 402  
403 403  Upstream Data Flow
404 404  
405 -[[~[~[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png~|~|height="309" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_19.png]]
406 406  
111 +[[image:image-20220527140542-20.png]]
112 +
407 407  Downstream Data Flow
408 408  
409 409  
410 -=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
116 +== 3.2  Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8/LG308N/LPS8N/DLOS8N ==
411 411  
412 -Since firmware LG02_LG08~-~-build-v5.3.1585192026-20200326-1109, Dragino LoRaWAN gateways support the communication to LoRaWAN ABP end node locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse.
413 413  
414 -When use test this feature, please use the version higher then : LG02_LG08~-~-build-v5.4.1593400722-20200629-1120, in this version, the upload format is changed and readable, which is easier for integration.
119 +(((
120 +Since firmware (% style="color:#4f81bd" %)**LG02_LG08~-~-build-v5.3.1585192026-20200326-1109,**(%%) Dragino LoRaWAN gateways support the communication to LoRaWAN (% style="color:#4f81bd" %)**ABP end node**(%%) locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse.
121 +)))
415 415  
123 +(((
124 +When use test this feature, please use the version higher then : (% style="color:#4f81bd" %)**LG02_LG08~-~-build-v5.4.1593400722-20200629-1120**(%%), in this version, the upload format is changed and readable, which is easier for integration.
416 416  
417 -\\Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
418 -
419 419  
420 -Step 1: Refer [[Communicate with ABP End Node>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]] to know how to set up LG308 to work with LoRaWAN End node.
127 +(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
128 +)))
421 421  
422 -Step 2: Make sure your Radio settings match the End Node settings.
130 +(((
131 +(% style="color:blue" %)**Step 1**(%%): Refer [[Communicate with ABP End Node>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308]] to know how to set up LG308 to work with LoRaWAN End node.
132 +)))
423 423  
424 -[[~[~[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png~|~|height="387" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_5.png]]
134 +(((
135 +(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
136 +)))
425 425  
138 +[[image:image-20220527141235-21.png]]
139 +
426 426  Use Same Frequency Band as End Node
427 427  
428 428  
429 -Step 3: Set up publish format and MQTT channel. The LG308 will store the Data from End node in HEX format in the file. And we need to config the format to META
143 +(((
144 +(((
145 +(% style="color:blue" %)**Step 3**(%%): Set up publish format and MQTT channel. The LG308 will store the Data from End node in (% style="color:#4f81bd" %)**HEX format**(%%) in the file.
146 +)))
147 +)))
430 430  
431 -[[~[~[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_3.png]]
149 +[[image:image-20220613191345-4.png]]
432 432  
433 -Publish mush use META as data format for LG308
434 434  
152 +(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
435 435  
436 -Step 4: Map the Device Address to Remote ID in MQTT server.
154 +[[image:image-20220613190635-2.png]]
437 437  
438 -[[~[~[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png~|~|height="335" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_4.png]]
439 439  
440 -Map Dev Addr to remote ID
157 +(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
441 441  
159 +[[image:image-20220527141843-24.png]]
442 442  
443 -Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
444 444  
445 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png~|~|height="279" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6.png]]
162 +[[image:image-20220527141933-25.png]]
446 446  
447 -Upstream Process
448 -
449 -[[~[~[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png~|~|height="246" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6_1.png]]
450 -
451 451  Choose ASCII Format
452 452  
453 -[[~[~[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png~|~|height="248" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6_2.png]]
454 454  
167 +[[image:image-20220527142028-26.png]]
168 +
455 455  LHT65 Decoder
456 456  
457 -Step 6: Set up subscribe: Subscribe a topci for downstream.
458 458  
459 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png~|~|height="176" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_7.png]]
172 +(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
460 460  
461 -Subscribe to a topic
174 +[[image:image-20220613191426-5.png]]
462 462  
463 463  
464 -Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
177 +(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
465 465  
466 -[[~[~[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png~|~|height="298" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_8.png]]
179 +[[image:image-20220527142239-28.png]]
467 467  
468 -Downstream Flow
469 469  
470 -Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node#Downstream]]
471 471  
183 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
472 472  
473 -= 5. Example For Different MQTT Servers =
185 +(% class="box infomessage" %)
186 +(((
187 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**
188 +)))
474 474  
475 -|=(((
476 -[[~[~[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png~|~|alt="ThingSpeak1.png" height="98" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:ThingSpeak1.png]]
190 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
477 477  
478 -=== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ===
192 +(% class="box infomessage" %)
193 +(((
194 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"**
195 +)))
479 479  
197 +(% style="color:red" %)**Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308||anchor="H2.2Downstream"]]**
480 480  
481 -[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]
482 -)))|=(((
483 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png~|~|alt="Lewei50.png" height="58" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:Lewei50.png]]
199 +Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
484 484  
485 -=== [[乐联网平台>>url:https://www.lewei50.com/]] ===
201 +[[image:image-20220613192816-6.png||height="440" width="1056"]]
486 486  
487 487  
488 -[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
489 -)))|=(((
490 -[[~[~[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png~|~|alt="AWS-IOT.png" height="122" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:AWS-IOT.png]]
204 +== 3.3 Use LoRaWAN Protocol for communication ~-~- For LPS8V2 ==
491 491  
492 -=== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ===
493 493  
494 494  
495 -[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
496 -)))
497 497  
209 += 4.  How to ask for Support =
498 498  
499 -= 6. How to Debug =
500 500  
501 -User can login the gateway's console and run **logread -f**. It will shows the output when there is packet arrive.User can see if it is correct.
502 -
503 -= 7. How to ask for Support =
504 -
505 505  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
506 506  
507 507  * Detail of your LoRaWAN end node.
image-20220527133547-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +199.3 KB
Content
image-20220527134000-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +115.8 KB
Content
image-20220527134038-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +94.2 KB
Content
image-20220527134251-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +35.1 KB
Content
image-20220527134332-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +34.7 KB
Content
image-20220527134929-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +61.6 KB
Content
image-20220527135037-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.1 KB
Content
image-20220527135215-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +125.6 KB
Content
image-20220527135310-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +87.9 KB
Content
image-20220527135440-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.5 KB
Content
image-20220527135742-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +18.2 KB
Content
image-20220527135828-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +35.1 KB
Content
image-20220527135929-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.0 KB
Content
image-20220527140023-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +182.2 KB
Content
image-20220527140100-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.2 KB
Content
image-20220527140148-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +34.0 KB
Content
image-20220527140238-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.3 KB
Content
image-20220527140354-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +62.7 KB
Content
image-20220527140459-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +151.0 KB
Content
image-20220527140542-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +165.4 KB
Content
image-20220527141235-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +83.3 KB
Content
image-20220527141450-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +46.5 KB
Content
image-20220527141727-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.6 KB
Content
image-20220527141843-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +164.3 KB
Content
image-20220527141933-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +100.1 KB
Content
image-20220527142028-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +95.2 KB
Content
image-20220527142115-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +9.3 KB
Content
image-20220527142239-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.1 KB
Content
image-20220527142638-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +62.3 KB
Content
image-20220527142706-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.1 KB
Content
image-20220527142733-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.3 KB
Content
image-20220527142820-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +155.6 KB
Content
image-20220613190254-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20220613190635-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +44.1 KB
Content
image-20220613191154-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +56.1 KB
Content
image-20220613191345-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +55.4 KB
Content
image-20220613191426-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +55.8 KB
Content
image-20220613192816-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +22.1 KB
Content
image-20220714155901-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +75.2 KB
Content