Changes for page MQTT Forward Instruction

Last modified by Xiaoling on 2025/07/31 16:59

From version 48.1
edited by Kilight Cao
on 2022/07/28 17:55
Change comment: There is no comment for this version
To version 2.1
edited by Xiaoling
on 2022/05/12 16:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
Content
... ... @@ -1,21 +1,18 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -= 1.  Introduction =
6 += 1. Introduction =
7 7  
8 -
9 9  Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
10 10  
10 +== 1.1 Support Devices ==
11 11  
12 -== 1.1  Support Devices ==
13 -
14 -
15 15  This MQTT forward instruction is for below devices:
16 16  
17 17  * Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
18 -* LG01N, OLG01N ((% style="color:red" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>doc:Through MQTT to upload data.WebHome]])
15 +* LG01N, OLG01N ((% class="mark" %)**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]])
19 19  * LG02, OLG02
20 20  * LG308, DLOS8
21 21  * LPS8
... ... @@ -23,9 +23,8 @@
23 23  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
24 24  
25 25  
26 -= 2.  Firmware Change Log for MQTT feature =
23 += 2. Firmware Change Log for MQTT feature =
27 27  
28 -
29 29  (((
30 30  This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
31 31  )))
... ... @@ -34,50 +34,41 @@
34 34  ** Initiate version
35 35  
36 36  
37 -= 3.  MQTT forward operating principle =
33 += 3. MQTT forward operating principle =
38 38  
35 +== 3.1 Network Structure ==
39 39  
40 -== 3.1  Network Structure ==
41 -
42 -
43 43  Below shows the network structure for MQTT forwarding.
44 44  
45 -* **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.
46 -* **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 +* 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.
40 +* 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,
47 47  
48 -[[image:image-20220527133547-1.png]]
42 +[[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png||height="348" width="600"]]
49 49  
50 50  General MQTT structure
51 51  
52 52  
47 +== 3.2 How sensor data is forwarded ==
53 53  
54 -== 3.2  How sensor data is forwarded ==
55 -
56 -
57 57  In this MQTT forward feature, the key point is how the gateway process the sensor data.
58 58  
59 59  
60 -=== 3.2.1  Upstream ===
52 +=== 3.2.1 Upstream ===
61 61  
62 -
63 63  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.
64 64  
65 65  (((
66 66  The data flow works as below diagram.
67 -
68 -
69 69  )))
70 70  
71 -[[image:image-20220527134000-2.png]]
60 +[[~[~[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]]
72 72  
73 73  (((
74 74  Upstream path
75 -
76 -
77 77  )))
78 78  
79 79  (((
80 -(% style="color:red" %)**Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>**
67 +Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>
81 81  )))
82 82  
83 83  (((
... ... @@ -84,9 +84,8 @@
84 84  
85 85  )))
86 86  
87 -=== 3.2.2  Downstream ===
74 +=== 3.2.2 Downstream ===
88 88  
89 -
90 90  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.
91 91  
92 92  (((
... ... @@ -93,27 +93,21 @@
93 93  Below are the data flow for downstream.
94 94  )))
95 95  
96 -[[image:image-20220527134038-3.png]]
82 +[[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png||height="368" width="600"]]
97 97  
98 98  Downstream path
99 99  
100 100  
87 +== 3.3 Macro Definition ==
101 101  
102 -== 3.3  Macro Definition ==
103 -
104 -
105 105  The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
106 106  
107 107  (((
108 -Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros.
109 -
110 -
111 -
92 +Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros.
112 112  )))
113 113  
114 -=== 3.3.1  -t topic macro ===
95 +=== 3.3.1 -t topic macro ===
115 115  
116 -
117 117  * CHANNEL: Remote Channel ID
118 118  * CLIENTID: Client ID , Same as -i
119 119  * WRITE_API: Remote Channel Write API
... ... @@ -120,10 +120,8 @@
120 120  * USERNAME: User ID (-u)
121 121  * HOSTNAME: Device Hostname
122 122  
103 +=== 3.3.2 -m message macro ===
123 123  
124 -=== 3.3.2  -m message macro ===
125 -
126 -
127 127  * HOSTNAME: Device Hostname
128 128  * CHANNEL: Remote Channel ID
129 129  * DATA: Sensor Data without time stamp and rssi
... ... @@ -130,36 +130,30 @@
130 130  * META: Completely sensor data with time stamp and rssi
131 131  * JSON: Convert META to json format.
132 132  
111 +=== 3.3.3 Example for Macro ===
133 133  
134 -=== 3.3.3  Example for Macro ===
113 +[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
135 135  
136 -
137 -[[image:image-20220527134251-4.png]]
138 -
139 139  MQTT Publish configure
140 140  
117 +Above screen shots shows below format:
141 141  
142 -**Above screen shots shows below format:**
143 -
144 144  * -t: CLIENTID/CHANNEL/data
145 145  * -m: DATA
146 146  
147 147  When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:
148 148  
149 -[[image:image-20220527134332-5.png]]
124 +[[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]]
150 150  
151 151  Sensor Data
152 152  
153 -
154 154  (((
155 -According to above macro. Gateway will publish (% style="color:#4f81bd" %)**field1=22.0&field2=49.0**(%%) to topic: (% style="color:#4f81bd" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID.
129 +According to above macro. Gateway will publish (% class="mark" %)**field1=22.0&field2=49.0**(%%) to topic: (% class="mark" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID.
156 156  )))
157 157  
158 158  
133 +== 3.4 Modify the MQTT to support more options ==
159 159  
160 -== 3.4  Modify the MQTT to support more options ==
161 -
162 -
163 163  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:
164 164  
165 165  (% class="box" %)
... ... @@ -167,7 +167,8 @@
167 167  root@dragino-1ec39c:~~# mosquitto_pub ~-~-help
168 168  mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
169 169  mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
170 -\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
142 +
143 +Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
171 171   {-f file | -l | -n | -m message}
172 172   [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]
173 173   [-A bind_address]
... ... @@ -177,15 +177,16 @@
177 177   [-u username [-P password]]
178 178   [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
179 179   [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file]
180 - [~-~-ciphers ciphers] [~-~-insecure]
181 - [~-~-tls-alpn protocol]
182 - [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
153 + [~-~-ciphers ciphers] [~-~-insecure]
154 + [~-~-tls-alpn protocol]
155 + [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
183 183   [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
184 184   [~-~-proxy socks-url]
185 185   [~-~-property command identifier value]
186 186   [-D command identifier value]
187 187   mosquitto_pub ~-~-help
188 -\\-A : bind the outgoing socket to this host/ip address. Use to control which interface
161 +
162 +-A : bind the outgoing socket to this host/ip address. Use to control which interface
189 189   the client communicates over.
190 190  -d : enable debug messages.
191 191  -D : Define MQTT v5 properties. See the documentation for more details.
... ... @@ -213,7 +213,7 @@
213 213  ~-~-help : display this message.
214 214  ~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
215 215  ~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.
216 -~-~-quiet : (% style="color:red" %)don't print error messages.
190 +~-~-quiet : (% class="mark" %)don't print error messages.
217 217  ~-~-will-payload : payload for the client Will, which is sent by the broker in case of
218 218   unexpected disconnection. If not given and will-topic is set, a zero
219 219   length message will be sent.
... ... @@ -241,7 +241,8 @@
241 241  ~-~-proxy : SOCKS5 proxy URL of the form:
242 242   socks5h:~/~/[username[:password]@]hostname[:port]
243 243   Only "none" and "username" authentication is supported.
244 -\\See https:~/~/mosquitto.org/ for more information.
218 +
219 +See https:~/~/mosquitto.org/ for more information.
245 245  )))
246 246  
247 247  
... ... @@ -251,52 +251,54 @@
251 251  
252 252  (% class="box" %)
253 253  (((
254 -//# Call MQTT Publish command
255 -\\# 1. Case with User, Password and Client ID present  (e.g. Azure)
229 +# Call MQTT Publish command
230 +
231 +# 1. Case with User, Password and Client ID present  (e.g. Azure)
256 256  if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
257 257  case="1" 
258 258  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"
259 -\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
235 +
236 +# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
260 260  elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
261 261  case="2" 
262 262  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"
263 -\\# 3. Case with no User, Certificate or ClientID present
240 +
241 +# 3. Case with no User, Certificate or ClientID present
264 264  elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
265 265  case="3" 
266 266  mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
267 -\\# 4. Case with no User, Certificate, but with ClientID present
245 +
246 +# 4. Case with no User, Certificate, but with ClientID present
268 268  elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
269 269  case="4" 
270 270  mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
271 -\\# 5. Case with User and ClientID present, but no Password and no Certificate present
250 +
251 +# 5. Case with User and ClientID present, but no Password and no Certificate present
272 272  elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
273 273  case="5" 
274 274  mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
275 -\\# 6. Case with User and Password present, but no ClientID and no Certificate present
255 +
256 +# 6. Case with User and Password present, but no ClientID and no Certificate present
276 276  elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
277 277  case="6" 
278 278  mosquitto_pub $D -h $server -p $port -q $pub_qos  -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
279 -\\# 0. Else - invalid parameters, just log
260 +
261 +# 0. Else - invalid parameters, just log
280 280  else
281 -case="(% style="color:red" %)Invalid parameters" (%%)
282 -logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%)
283 -fi//
263 +case="Invalid parameters" 
264 +logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
265 +fi
284 284  )))
285 285  
286 286  
269 += 4. Example to communicate to a simple MQTT server =
287 287  
288 -= 4.  Example to communicate to a simple MQTT server =
271 +== 4.1 Overview ==
289 289  
290 -
291 -== 4.1  Overview ==
292 -
293 -
294 294  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/]].
295 295  
275 +== 4.2 Simulate via MQTT.fx utility ==
296 296  
297 -== 4.2  Simulate via MQTT.fx utility ==
298 -
299 -
300 300  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.
301 301  
302 302  (((
... ... @@ -303,35 +303,31 @@
303 303  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.
304 304  )))
305 305  
306 -[[image:image-20220527134929-6.png]]
283 +[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]
307 307  
308 308  Connect to MQTT Broker
309 309  
310 -
311 311  After connected, use publish to public some thing to MQTT server. This to simulate upsteam
312 312  
313 -[[image:image-20220527135037-7.png]]
289 +[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]
314 314  
315 315  Upstream: Publish message to MQTT Broker
316 316  
317 -
318 318  To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
319 319  
320 -[[image:image-20220527135215-8.png]]
295 +[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]
321 321  
322 322  Downstream: Subscribe a topic to get downstream
323 323  
324 324  
300 +== 4.3 Simulate via Dragino Command Line ==
325 325  
326 -== 4.3  Simulate via Dragino Command Line ==
327 -
328 -
329 329  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.
330 330  
331 331  In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
332 332  
333 333  
334 -(% style="color:blue" %)**For Upstream**
307 +(% class="mark" %)**For Upstream**
335 335  
336 336  command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
337 337  
... ... @@ -339,72 +339,63 @@
339 339  
340 340  Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
341 341  
342 -[[image:image-20220527135310-9.png]]
315 +[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]]
343 343  
344 344  mosquitto_pub
345 345  
346 346  
320 +(% class="mark" %)**For Downstream**
347 347  
348 -(% style="color:blue" %)**For Downstream**
349 -
350 350  Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
351 351  
352 -[[image:image-20220527135440-10.png]]
324 +[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]
353 353  
354 354  mosquitto_sub
355 355  
356 356  
329 +== 4.4 Configure Dragino UI for MQTT connection ==
357 357  
358 -== 4.4  Configure Dragino UI for MQTT connection ==
359 -
360 -
361 361  This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
362 362  
363 363  (((
364 -Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client**
334 +Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client**
365 365  )))
366 366  
367 -[[image:image-20220714155901-1.png]]
337 +[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]
368 368  
369 369  go to mqtt configure menu
370 370  
371 -
372 372  (((
373 -Select (% style="color:#4f81bd" %)**Forward to MQTT server**. (% style="color:red" %)**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.
342 +Select **Forward to MQTT server**. (% class="mark" %)**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.
374 374  )))
375 375  
376 -[[image:image-20220527135742-11.png]]
345 +[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]]
377 377  
378 378  forward to MQTT
379 379  
380 380  
350 +=== 4.4.1 Configure the MQTT Client for Upstream ===
381 381  
382 -=== 4.4.1  Configure the MQTT Client for Upstream ===
352 +Below screenshot is same as the publish command:
383 383  
384 -
385 -**Below screenshot is same as the publish command:**
386 -
387 387  (% class="box" %)
388 388  (((
389 -**mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
356 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
390 390  ~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
391 391  ~/~/CLIENTID: dragino-1b7060
392 392  ~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
393 -~/~/DATA: The data stores in /var/iot/channels/**
360 +~/~/DATA: The data stores in /var/iot/channels/
394 394  )))
395 395  
363 +[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
396 396  
397 -[[image:image-20220527135828-12.png]]
398 -
399 399  MQTT Publish configure
400 400  
401 401  
368 +[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]]
402 402  
403 -[[image:image-20220527135929-13.png]]
404 -
405 405  MQTT Channel settings
406 406  
407 -
408 408  (((
409 409  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:
410 410  )))
... ... @@ -423,15 +423,13 @@
423 423  Below is a simulation to put this data to active the MQTT publish.
424 424  )))
425 425  
426 -[[image:image-20220527140023-14.png]]
390 +[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]
427 427  
428 428  MQTT Publish
429 429  
430 430  
395 +=== 4.4.2 Configure the MQTT Client for Downstream ===
431 431  
432 -=== 4.4.2  Configure the MQTT Client for Downstream ===
433 -
434 -
435 435  Below screen shot equal to this subscribe command:
436 436  
437 437  (% class="box" %)
... ... @@ -439,7 +439,7 @@
439 439  mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
440 440  )))
441 441  
442 -[[image:image-20220527140100-15.png]]
404 +[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]
443 443  
444 444  MQTT Subscribe
445 445  
... ... @@ -448,7 +448,7 @@
448 448  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:
449 449  )))
450 450  
451 -[[image:image-20220527140148-16.png]]
413 +[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]
452 452  
453 453  LoRa Broadcast parameters.
454 454  
... ... @@ -455,20 +455,17 @@
455 455  
456 456  And below is the subscribe simulation:
457 457  
458 -[[image:image-20220527140238-17.png]]
420 +[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]
459 459  
460 460  downstream simulation
461 461  
462 462  
463 -== 4.5  Add LoRa support to communicate with remote sensor ==
425 +== 4.5 Add LoRa support to communicate with remote sensor ==
464 464  
465 -
466 466  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.
467 467  
429 +=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
468 468  
469 -=== 4.5.1  Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
470 -
471 -
472 472  (((
473 473  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.
474 474  )))
... ... @@ -479,8 +479,6 @@
479 479  
480 480  (((
481 481  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.
482 -
483 -
484 484  )))
485 485  
486 486  (((
... ... @@ -491,138 +491,127 @@
491 491  * Downstream: Listening broadcast message from gateway, and print it in console.
492 492  * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
493 493  
494 -[[image:image-20220527140354-18.png]]
451 +[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]]
495 495  
496 496  LoRa Parameter should match
497 497  
498 498  
499 -
500 500  Below is the test result after the Arduino Sketch is running.
501 501  
502 -[[image:image-20220527140459-19.png]]
458 +[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]]
503 503  
504 504  Upstream Data Flow
505 505  
462 +[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]]
506 506  
507 -
508 -[[image:image-20220527140542-20.png]]
509 -
510 510  Downstream Data Flow
511 511  
512 512  
467 +=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
513 513  
514 -=== 4.5.2  Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
515 -
516 -
517 517  (((
518 -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.
470 +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.
519 519  )))
520 520  
521 521  (((
522 -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.
523 -
524 -
525 -(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
474 +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.
475 +Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
526 526  )))
527 527  
528 528  (((
529 -(% 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.
479 +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.
530 530  )))
531 531  
532 532  (((
533 -(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
483 +Step 2: Make sure your Radio settings match the End Node settings.
534 534  )))
535 535  
536 -[[image:image-20220527141235-21.png]]
486 +[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]]
537 537  
538 538  Use Same Frequency Band as End Node
539 539  
540 540  
541 541  (((
542 -(((
543 -(% 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.
492 +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
544 544  )))
545 -)))
546 546  
547 -[[image:image-20220613191345-4.png]]
495 +[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]]
548 548  
497 +Publish mush use META as data format for LG308
549 549  
550 550  
551 -(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
500 +Step 4: Map the Device Address to Remote ID in MQTT server.
552 552  
553 -[[image:image-20220613190635-2.png]]
502 +[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]]
554 554  
504 +Map Dev Addr to remote ID
555 555  
556 556  
557 -(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
507 +Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
558 558  
559 -[[image:image-20220527141843-24.png]]
509 +[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]
560 560  
511 +Upstream Process
561 561  
513 +[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]]
562 562  
563 -
564 -[[image:image-20220527141933-25.png]]
565 -
566 566  Choose ASCII Format
567 567  
517 +[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]]
568 568  
569 -
570 -[[image:image-20220527142028-26.png]]
571 -
572 572  LHT65 Decoder
573 573  
521 +Step 6: Set up subscribe: Subscribe a topci for downstream.
574 574  
523 +[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]
575 575  
576 -(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
525 +Subscribe to a topic
577 577  
578 -[[image:image-20220613191426-5.png]]
579 579  
528 +Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
580 580  
530 +[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]]
581 581  
582 -(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
532 +Downstream Flow
583 583  
584 -[[image:image-20220527142239-28.png]]
534 +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]]
585 585  
586 586  
537 += 5. Example For Different MQTT Servers =
587 587  
588 -=== 4.5.3 MQTT Downstream format ===
539 +(% style="width:731.222px" %)
540 +|=(% style="width: 270px;" %)(((
541 +[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]]
589 589  
543 +== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==
590 590  
591 -mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
592 592  
593 -(% class="box infomessage" %)
594 -(((
595 -**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**
596 -)))
546 +[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]
547 +)))|=(% style="width: 242px;" %)(((
548 +[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]]
597 597  
598 -mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
550 +(% class="wikigeneratedid" %)
551 +== ==
599 599  
600 -(% class="box infomessage" %)
601 -(((
602 -**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"**
603 -)))
553 +== [[乐联网平台>>url:https://www.lewei50.com/]] ==
604 604  
605 -Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
606 606  
607 -[[image:image-20220613192816-6.png||height="440" width="1056"]]
556 +[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
557 +)))|=(% style="width: 214px;" %)(((
558 +[[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png||alt="AWS-IOT.png" height="112" width="183"]]
608 608  
560 +== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==
609 609  
610 -(% 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"]]**
611 611  
563 +[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
564 +)))
612 612  
613 -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]]
566 += 6. How to Debug =
614 614  
568 +User can login the gateway's console and run (% class="mark" %)**logread -f**(%%). It will shows the output when there is packet arrive.User can see if it is correct.
615 615  
570 += 7. How to ask for Support =
616 616  
617 -= 5.  How to Debug =
618 -
619 -
620 -User can login the gateway's console and run (% style="color:#4f81bd" %)**logread -f**(%%). It will shows the output when there is packet arrive.User can see if it is correct.
621 -
622 -
623 -= 6.  How to ask for Support =
624 -
625 -
626 626  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
627 627  
628 628  * Detail of your LoRaWAN end node.
image-20220527133547-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -199.3 KB
Content
image-20220527134000-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -115.8 KB
Content
image-20220527134038-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -94.2 KB
Content
image-20220527134251-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20220527134332-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.7 KB
Content
image-20220527134929-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -61.6 KB
Content
image-20220527135037-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.1 KB
Content
image-20220527135215-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -125.6 KB
Content
image-20220527135310-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -87.9 KB
Content
image-20220527135440-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 KB
Content
image-20220527135742-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -18.2 KB
Content
image-20220527135828-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20220527135929-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.0 KB
Content
image-20220527140023-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.2 KB
Content
image-20220527140100-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.2 KB
Content
image-20220527140148-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.0 KB
Content
image-20220527140238-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.3 KB
Content
image-20220527140354-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.7 KB
Content
image-20220527140459-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -151.0 KB
Content
image-20220527140542-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -165.4 KB
Content
image-20220527141235-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.3 KB
Content
image-20220527141450-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.5 KB
Content
image-20220527141727-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.6 KB
Content
image-20220527141843-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -164.3 KB
Content
image-20220527141933-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -100.1 KB
Content
image-20220527142028-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -95.2 KB
Content
image-20220527142115-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.3 KB
Content
image-20220527142239-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.1 KB
Content
image-20220527142638-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.3 KB
Content
image-20220527142706-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.1 KB
Content
image-20220527142733-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -10.3 KB
Content
image-20220527142820-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -155.6 KB
Content
image-20220613190254-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220613190635-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -44.1 KB
Content
image-20220613191154-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -56.1 KB
Content
image-20220613191345-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.4 KB
Content
image-20220613191426-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.8 KB
Content
image-20220613192816-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -22.1 KB
Content
image-20220714155901-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -75.2 KB
Content