Skip to Content

Changes for page MQTT Forward Instruction

Last modified by Kilight Cao on 2024/08/31 16:26
From version 9.1
edited by Xiaoling
on 2022/05/27 13:50
Change comment: Uploaded new attachment "image-20220527135037-7.png", version {1}
To version 45.1
edited by Xiaoling
on 2022/07/14 15:59
Change comment: Uploaded new attachment "image-20220714155901-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,19 +1,21 @@
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 10  
11 -== 1.1 Support Devices ==
12 +== 1.1  Support Devices ==
12 12  
14 +
13 13  This MQTT forward instruction is for below devices:
14 14  
15 15  * Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
16 -* LG01N, OLG01N ((% style="color:red" %)**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]])
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]])
17 17  * LG02, OLG02
18 18  * LG308, DLOS8
19 19  * LPS8
... ... @@ -20,8 +20,11 @@
20 20  * LIG16
21 21  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
22 22  
23 -= 2. Firmware Change Log for MQTT feature =
24 24  
26 +
27 += 2.  Firmware Change Log for MQTT feature =
28 +
29 +
25 25  (((
26 26  This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
27 27  )))
... ... @@ -29,14 +29,18 @@
29 29  * LG02_LG08-5.3.1580178039
30 30  ** Initiate version
31 31  
32 -= 3. MQTT forward operating principle =
33 33  
34 -== 3.1 Network Structure ==
35 35  
39 += 3.  MQTT forward operating principle =
40 +
41 +
42 +== 3.1  Network Structure ==
43 +
44 +
36 36  Below shows the network structure for MQTT forwarding.
37 37  
38 -* 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.
39 -* 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 +* **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.
48 +* **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,
40 40  
41 41  [[image:image-20220527133547-1.png]]
42 42  
... ... @@ -43,12 +43,13 @@
43 43  General MQTT structure
44 44  
45 45  
46 -== 3.2 How sensor data is forwarded ==
55 +== 3.2  How sensor data is forwarded ==
47 47  
57 +
48 48  In this MQTT forward feature, the key point is how the gateway process the sensor data.
49 49  
50 50  
51 -=== 3.2.1 Upstream ===
61 +=== 3.2.1  Upstream ===
52 52  
53 53  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.
54 54  
... ... @@ -60,10 +60,12 @@
60 60  
61 61  (((
62 62  Upstream path
73 +
74 +
63 63  )))
64 64  
65 65  (((
66 -Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>
78 +(% 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 67  )))
68 68  
69 69  (((
... ... @@ -70,8 +70,9 @@
70 70  
71 71  )))
72 72  
73 -=== 3.2.2 Downstream ===
85 +=== 3.2.2  Downstream ===
74 74  
87 +
75 75  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.
76 76  
77 77  (((
... ... @@ -83,8 +83,9 @@
83 83  Downstream path
84 84  
85 85  
86 -== 3.3 Macro Definition ==
99 +== 3.3  Macro Definition ==
87 87  
101 +
88 88  The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
89 89  
90 90  (((
... ... @@ -93,8 +93,9 @@
93 93  
94 94  )))
95 95  
96 -=== 3.3.1 -t topic macro ===
110 +=== 3.3.1  -t topic macro ===
97 97  
112 +
98 98  * CHANNEL: Remote Channel ID
99 99  * CLIENTID: Client ID , Same as -i
100 100  * WRITE_API: Remote Channel Write API
... ... @@ -101,8 +101,12 @@
101 101  * USERNAME: User ID (-u)
102 102  * HOSTNAME: Device Hostname
103 103  
104 -=== 3.3.2 -m message macro ===
105 105  
120 +
121 +
122 +=== 3.3.2  -m message macro ===
123 +
124 +
106 106  * HOSTNAME: Device Hostname
107 107  * CHANNEL: Remote Channel ID
108 108  * DATA: Sensor Data without time stamp and rssi
... ... @@ -109,14 +109,19 @@
109 109  * META: Completely sensor data with time stamp and rssi
110 110  * JSON: Convert META to json format.
111 111  
112 -=== 3.3.3 Example for Macro ===
113 113  
132 +
133 +
134 +=== 3.3.3  Example for Macro ===
135 +
136 +
114 114  [[image:image-20220527134251-4.png]]
115 115  
116 116  MQTT Publish configure
117 117  
118 -Above screen shots shows below format:
119 119  
142 +**Above screen shots shows below format:**
143 +
120 120  * -t: CLIENTID/CHANNEL/data
121 121  * -m: DATA
122 122  
... ... @@ -126,13 +126,16 @@
126 126  
127 127  Sensor Data
128 128  
153 +
129 129  (((
130 130  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.
131 131  )))
132 132  
133 133  
134 -== 3.4 Modify the MQTT to support more options ==
135 135  
160 +== 3.4  Modify the MQTT to support more options ==
161 +
162 +
136 136  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:
137 137  
138 138  (% class="box" %)
... ... @@ -150,9 +150,9 @@
150 150   [-u username [-P password]]
151 151   [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
152 152   [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file]
153 - [~-~-ciphers ciphers] [~-~-insecure]
154 - [~-~-tls-alpn protocol]
155 - [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
180 + [~-~-ciphers ciphers] [~-~-insecure]
181 + [~-~-tls-alpn protocol]
182 + [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
156 156   [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
157 157   [~-~-proxy socks-url]
158 158   [~-~-property command identifier value]
... ... @@ -257,15 +257,19 @@
257 257  )))
258 258  
259 259  
260 -= 4. Example to communicate to a simple MQTT server =
261 261  
262 -== 4.1 Overview ==
288 += 4.  Example to communicate to a simple MQTT server =
263 263  
290 +
291 +== 4.1  Overview ==
292 +
293 +
264 264  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/]].
265 265  
266 266  
267 -== 4.2 Simulate via MQTT.fx utility ==
297 +== 4.2  Simulate via MQTT.fx utility ==
268 268  
299 +
269 269  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.
270 270  
271 271  (((
... ... @@ -276,27 +276,30 @@
276 276  
277 277  Connect to MQTT Broker
278 278  
310 +
279 279  After connected, use publish to public some thing to MQTT server. This to simulate upsteam
280 280  
281 -[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]
313 +[[image:image-20220527135037-7.png]]
282 282  
283 283  Upstream: Publish message to MQTT Broker
284 284  
317 +
285 285  To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
286 286  
287 -[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]
320 +[[image:image-20220527135215-8.png]]
288 288  
289 289  Downstream: Subscribe a topic to get downstream
290 290  
291 291  
292 -== 4.3 Simulate via Dragino Command Line ==
293 293  
326 +== 4.3  Simulate via Dragino Command Line ==
327 +
294 294  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.
295 295  
296 296  In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
297 297  
298 298  
299 -(% class="mark" %)**For Upstream**
333 +(% style="color:blue" %)**For Upstream**
300 300  
301 301  command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
302 302  
... ... @@ -304,16 +304,17 @@
304 304  
305 305  Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
306 306  
307 -[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]]
341 +[[image:image-20220527135310-9.png]]
308 308  
309 309  mosquitto_pub
310 310  
311 311  
312 -(% class="mark" %)**For Downstream**
313 313  
347 +(% style="color:blue" %)**For Downstream**
348 +
314 314  Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
315 315  
316 -[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]
351 +[[image:image-20220527135440-10.png]]
317 317  
318 318  mosquitto_sub
319 319  
... ... @@ -323,7 +323,7 @@
323 323  This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
324 324  
325 325  (((
326 -Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client**
361 +Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client**
327 327  )))
328 328  
329 329  [[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]
... ... @@ -330,11 +330,12 @@
330 330  
331 331  go to mqtt configure menu
332 332  
368 +
333 333  (((
334 -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.
370 +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.
335 335  )))
336 336  
337 -[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]]
373 +[[image:image-20220527135742-11.png]]
338 338  
339 339  forward to MQTT
340 340  
... ... @@ -352,15 +352,16 @@
352 352  ~/~/DATA: The data stores in /var/iot/channels/
353 353  )))
354 354  
355 -[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
391 +[[image:image-20220527135828-12.png]]
356 356  
357 357  MQTT Publish configure
358 358  
359 359  
360 -[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]]
396 +[[image:image-20220527135929-13.png]]
361 361  
362 362  MQTT Channel settings
363 363  
400 +
364 364  (((
365 365  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:
366 366  )))
... ... @@ -379,7 +379,7 @@
379 379  Below is a simulation to put this data to active the MQTT publish.
380 380  )))
381 381  
382 -[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]
419 +[[image:image-20220527140023-14.png]]
383 383  
384 384  MQTT Publish
385 385  
... ... @@ -393,7 +393,7 @@
393 393  mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
394 394  )))
395 395  
396 -[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]
433 +[[image:image-20220527140100-15.png]]
397 397  
398 398  MQTT Subscribe
399 399  
... ... @@ -402,7 +402,7 @@
402 402  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:
403 403  )))
404 404  
405 -[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]
442 +[[image:image-20220527140148-16.png]]
406 406  
407 407  LoRa Broadcast parameters.
408 408  
... ... @@ -409,7 +409,7 @@
409 409  
410 410  And below is the subscribe simulation:
411 411  
412 -[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]
449 +[[image:image-20220527140238-17.png]]
413 413  
414 414  downstream simulation
415 415  
... ... @@ -418,6 +418,7 @@
418 418  
419 419  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.
420 420  
458 +
421 421  === 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
422 422  
423 423  (((
... ... @@ -440,19 +440,22 @@
440 440  * Downstream: Listening broadcast message from gateway, and print it in console.
441 441  * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
442 442  
443 -[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]]
481 +[[image:image-20220527140354-18.png]]
444 444  
445 445  LoRa Parameter should match
446 446  
447 447  
486 +
448 448  Below is the test result after the Arduino Sketch is running.
449 449  
450 -[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]]
489 +[[image:image-20220527140459-19.png]]
451 451  
452 452  Upstream Data Flow
453 453  
454 -[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]]
455 455  
494 +
495 +[[image:image-20220527140542-20.png]]
496 +
456 456  Downstream Data Flow
457 457  
458 458  
... ... @@ -459,23 +459,23 @@
459 459  === 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
460 460  
461 461  (((
462 -Since firmware (% class="mark" %)**LG02_LG08~-~-build-v5.3.1585192026-20200326-1109,**(%%) Dragino LoRaWAN gateways support the communication to LoRaWAN (% class="mark" %)**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.
503 +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.
463 463  )))
464 464  
465 465  (((
466 -When use test this feature, please use the version higher then : (% class="mark" %)**LG02_LG08~-~-build-v5.4.1593400722-20200629-1120**(%%), in this version, the upload format is changed and readable, which is easier for integration.
467 -(% class="mark" %)**Video Instruction**(%%):[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
507 +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.
508 +(% style="color:#4f81bd" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
468 468  )))
469 469  
470 470  (((
471 -**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.
512 +(% style="color:#4f81bd" %)**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.
472 472  )))
473 473  
474 474  (((
475 -**Step 2**: Make sure your Radio settings match the End Node settings.
516 +(% style="color:#4f81bd" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
476 476  )))
477 477  
478 -[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]]
519 +[[image:image-20220527141235-21.png]]
479 479  
480 480  Use Same Frequency Band as End Node
481 481  
... ... @@ -482,86 +482,83 @@
482 482  
483 483  (((
484 484  (((
485 -**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
526 +(% style="color:#4f81bd" %)**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.
486 486  )))
487 487  )))
488 488  
489 -[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]]
530 +[[image:image-20220613191345-4.png]]
490 490  
491 -Publish mush use META as data format for LG308
492 492  
493 493  
494 -**Step 4**: Map the Device Address to Remote ID in MQTT server.
534 +(% style="color:#4f81bd" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
495 495  
496 -[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]]
536 +[[image:image-20220613190635-2.png]]
497 497  
498 -Map Dev Addr to remote ID
499 499  
500 500  
501 -**Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
540 +(% style="color:#4f81bd" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
502 502  
503 -[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]
542 +[[image:image-20220527141843-24.png]]
504 504  
505 -Upstream Process
506 506  
507 -[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]]
508 508  
546 +
547 +[[image:image-20220527141933-25.png]]
548 +
509 509  Choose ASCII Format
510 510  
511 -[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]]
512 512  
513 -LHT65 Decoder
514 514  
553 +[[image:image-20220527142028-26.png]]
515 515  
516 -**Step 6: Set up subscribe:** Subscribe a topci for downstream.
555 +LHT65 Decoder
517 517  
518 -[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]
519 519  
520 -Subscribe to a topic
521 521  
559 +(% style="color:#4f81bd" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
522 522  
523 -**Step 7**: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
561 +[[image:image-20220613191426-5.png]]
524 524  
525 -[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]]
526 526  
527 -Downstream Flow
528 528  
529 -(% class="mark" %)**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]]**
565 +(% style="color:#4f81bd" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
530 530  
567 +[[image:image-20220527142239-28.png]]
531 531  
532 -= 5. Example For Different MQTT Servers =
533 533  
534 -(% style="width:731.222px" %)
535 -|=(% style="width: 270px;" %)(((
536 -[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]]
537 537  
538 -== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==
571 +=== MQTT Downstream format ===
539 539  
540 540  
541 -[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]
542 -)))|=(% style="width: 242px;" %)(((
543 -[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]]
574 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
544 544  
576 +(% class="box infomessage" %)
577 +(((
578 +mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"
579 +)))
545 545  
546 -== [[乐联网平台>>url:https://www.lewei50.com/]] ==
581 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
547 547  
583 +(% class="box infomessage" %)
584 +(((
585 +mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2 > /var/iot/push/test"
586 +)))
548 548  
549 -[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
550 -)))|=(% style="width: 214px;" %)(((
551 -[[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png||alt="AWS-IOT.png" height="112" width="183"]]
588 +Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
552 552  
553 -== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==
590 +[[image:image-20220613192816-6.png||height="440" width="1056"]]
554 554  
592 +(% 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"]]**
555 555  
556 -[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
557 -)))
594 +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]]
558 558  
559 -= 6. How to Debug =
596 += 5. How to Debug =
560 560  
561 -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.
598 +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.
562 562  
563 -= 7. How to ask for Support =
564 564  
601 += 6. How to ask for Support =
602 +
565 565  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
566 566  
567 567  * Detail of your LoRaWAN end node.
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