Changes for page MQTT Forward Instruction
Last modified by Kilight Cao on 2024/08/31 16:26
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 35 added, 0 removed)
- image-20220527134251-4.png
- image-20220527134332-5.png
- image-20220527134929-6.png
- image-20220527135037-7.png
- image-20220527135215-8.png
- image-20220527135310-9.png
- image-20220527135440-10.png
- image-20220527135742-11.png
- image-20220527135828-12.png
- image-20220527135929-13.png
- image-20220527140023-14.png
- image-20220527140100-15.png
- image-20220527140148-16.png
- image-20220527140238-17.png
- image-20220527140354-18.png
- image-20220527140459-19.png
- image-20220527140542-20.png
- image-20220527141235-21.png
- image-20220527141450-22.png
- image-20220527141727-23.png
- image-20220527141843-24.png
- image-20220527141933-25.png
- image-20220527142028-26.png
- image-20220527142115-27.png
- image-20220527142239-28.png
- image-20220527142638-29.png
- image-20220527142706-30.png
- image-20220527142733-31.png
- image-20220527142820-32.png
- image-20220613190254-1.png
- image-20220613190635-2.png
- image-20220613191154-3.png
- image-20220613191345-4.png
- image-20220613191426-5.png
- image-20220613192816-6.png
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,16 +83,20 @@ 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 ((( 91 91 Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros. 106 + 107 + 92 92 ))) 93 93 94 -=== 3.3.1 -t topic macro === 110 +=== 3.3.1 -t topic macro === 95 95 112 + 96 96 * CHANNEL: Remote Channel ID 97 97 * CLIENTID: Client ID , Same as -i 98 98 * WRITE_API: Remote Channel Write API ... ... @@ -99,8 +99,12 @@ 99 99 * USERNAME: User ID (-u) 100 100 * HOSTNAME: Device Hostname 101 101 102 -=== 3.3.2 -m message macro === 103 103 120 + 121 + 122 +=== 3.3.2 -m message macro === 123 + 124 + 104 104 * HOSTNAME: Device Hostname 105 105 * CHANNEL: Remote Channel ID 106 106 * DATA: Sensor Data without time stamp and rssi ... ... @@ -107,30 +107,38 @@ 107 107 * META: Completely sensor data with time stamp and rssi 108 108 * JSON: Convert META to json format. 109 109 110 -=== 3.3.3 Example for Macro === 111 111 112 -[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]] 113 113 133 + 134 +=== 3.3.3 Example for Macro === 135 + 136 + 137 +[[image:image-20220527134251-4.png]] 138 + 114 114 MQTT Publish configure 115 115 116 -Above screen shots shows below format: 117 117 142 +**Above screen shots shows below format:** 143 + 118 118 * -t: CLIENTID/CHANNEL/data 119 119 * -m: DATA 120 120 121 121 When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below: 122 122 123 -[[image: https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]]149 +[[image:image-20220527134332-5.png]] 124 124 125 125 Sensor Data 126 126 153 + 127 127 ((( 128 -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.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 129 ))) 130 130 131 131 132 -== 3.4 Modify the MQTT to support more options == 133 133 160 +== 3.4 Modify the MQTT to support more options == 161 + 162 + 134 134 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: 135 135 136 136 (% class="box" %) ... ... @@ -148,9 +148,9 @@ 148 148 [-u username [-P password]] 149 149 [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]] 150 150 [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file] 151 - 152 - 153 - 180 + [~-~-ciphers ciphers] [~-~-insecure] 181 + [~-~-tls-alpn protocol] 182 + [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]] 154 154 [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]] 155 155 [~-~-proxy socks-url] 156 156 [~-~-property command identifier value] ... ... @@ -184,7 +184,7 @@ 184 184 ~-~-help : display this message. 185 185 ~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times. 186 186 ~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0. 187 -~-~-quiet : (% class="mark" %)don't print error messages.216 +~-~-quiet : (% style="color:red" %)don't print error messages. 188 188 ~-~-will-payload : payload for the client Will, which is sent by the broker in case of 189 189 unexpected disconnection. If not given and will-topic is set, a zero 190 190 length message will be sent. ... ... @@ -222,7 +222,7 @@ 222 222 223 223 (% class="box" %) 224 224 ((( 225 -# Call MQTT Publish command 254 +//# Call MQTT Publish command 226 226 \\# 1. Case with User, Password and Client ID present (e.g. Azure) 227 227 if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 228 228 case="1" ... ... @@ -249,20 +249,25 @@ 249 249 mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 250 250 \\# 0. Else - invalid parameters, just log 251 251 else 252 -case="Invalid parameters" 253 -logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." 254 -fi 281 +case="(% style="color:red" %)Invalid parameters" (%%) 282 +logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%) 283 +fi// 255 255 ))) 256 256 257 257 258 -= 4. Example to communicate to a simple MQTT server = 259 259 260 -= =4.1Overview==288 += 4. Example to communicate to a simple MQTT server = 261 261 290 + 291 +== 4.1 Overview == 292 + 293 + 262 262 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/]]. 263 263 264 -== 4.2 Simulate via MQTT.fx utility == 265 265 297 +== 4.2 Simulate via MQTT.fx utility == 298 + 299 + 266 266 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. 267 267 268 268 ((( ... ... @@ -269,31 +269,34 @@ 269 269 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. 270 270 ))) 271 271 272 -[[image: https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]306 +[[image:image-20220527134929-6.png]] 273 273 274 274 Connect to MQTT Broker 275 275 310 + 276 276 After connected, use publish to public some thing to MQTT server. This to simulate upsteam 277 277 278 -[[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]] 279 279 280 280 Upstream: Publish message to MQTT Broker 281 281 317 + 282 282 To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below: 283 283 284 -[[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]] 285 285 286 286 Downstream: Subscribe a topic to get downstream 287 287 288 288 289 -== 4.3 Simulate via Dragino Command Line == 290 290 326 +== 4.3 Simulate via Dragino Command Line == 327 + 291 291 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. 292 292 293 293 In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 294 294 295 295 296 -(% class="mark" %)**For Upstream**333 +(% style="color:blue" %)**For Upstream** 297 297 298 298 command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 299 299 ... ... @@ -301,16 +301,17 @@ 301 301 302 302 Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network. 303 303 304 -[[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]] 305 305 306 306 mosquitto_pub 307 307 308 308 309 -(% class="mark" %)**For Downstream** 310 310 347 +(% style="color:blue" %)**For Downstream** 348 + 311 311 Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 312 312 313 -[[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]] 314 314 315 315 mosquitto_sub 316 316 ... ... @@ -320,7 +320,7 @@ 320 320 This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 321 321 322 322 ((( 323 -Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client**361 +Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client** 324 324 ))) 325 325 326 326 [[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]] ... ... @@ -327,11 +327,12 @@ 327 327 328 328 go to mqtt configure menu 329 329 368 + 330 330 ((( 331 -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. 332 332 ))) 333 333 334 -[[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]] 335 335 336 336 forward to MQTT 337 337 ... ... @@ -349,15 +349,16 @@ 349 349 ~/~/DATA: The data stores in /var/iot/channels/ 350 350 ))) 351 351 352 -[[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]] 353 353 354 354 MQTT Publish configure 355 355 356 356 357 -[[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]] 358 358 359 359 MQTT Channel settings 360 360 400 + 361 361 ((( 362 362 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: 363 363 ))) ... ... @@ -376,7 +376,7 @@ 376 376 Below is a simulation to put this data to active the MQTT publish. 377 377 ))) 378 378 379 -[[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]] 380 380 381 381 MQTT Publish 382 382 ... ... @@ -390,7 +390,7 @@ 390 390 mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 391 391 ))) 392 392 393 -[[image: https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]433 +[[image:image-20220527140100-15.png]] 394 394 395 395 MQTT Subscribe 396 396 ... ... @@ -399,7 +399,7 @@ 399 399 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: 400 400 ))) 401 401 402 -[[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]] 403 403 404 404 LoRa Broadcast parameters. 405 405 ... ... @@ -406,7 +406,7 @@ 406 406 407 407 And below is the subscribe simulation: 408 408 409 -[[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]] 410 410 411 411 downstream simulation 412 412 ... ... @@ -415,6 +415,7 @@ 415 415 416 416 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. 417 417 458 + 418 418 === 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 419 419 420 420 ((( ... ... @@ -437,19 +437,22 @@ 437 437 * Downstream: Listening broadcast message from gateway, and print it in console. 438 438 * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below: 439 439 440 -[[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]] 441 441 442 442 LoRa Parameter should match 443 443 444 444 486 + 445 445 Below is the test result after the Arduino Sketch is running. 446 446 447 -[[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]] 448 448 449 449 Upstream Data Flow 450 450 451 -[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]] 452 452 494 + 495 +[[image:image-20220527140542-20.png]] 496 + 453 453 Downstream Data Flow 454 454 455 455 ... ... @@ -456,23 +456,23 @@ 456 456 === 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 457 457 458 458 ((( 459 -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. 460 460 ))) 461 461 462 462 ((( 463 -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.464 -(% 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]] 465 465 ))) 466 466 467 467 ((( 468 -**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. 469 469 ))) 470 470 471 471 ((( 472 -**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. 473 473 ))) 474 474 475 -[[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]] 476 476 477 477 Use Same Frequency Band as End Node 478 478 ... ... @@ -479,86 +479,83 @@ 479 479 480 480 ((( 481 481 ((( 482 -**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 META526 +(% 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. 483 483 ))) 484 484 ))) 485 485 486 -[[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]] 487 487 488 -Publish mush use META as data format for LG308 489 489 490 490 491 -**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. 492 492 493 -[[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]] 494 494 495 -Map Dev Addr to remote ID 496 496 497 497 498 -**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 499 499 500 -[[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]] 501 501 502 -Upstream Process 503 503 504 -[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]] 505 505 546 + 547 +[[image:image-20220527141933-25.png]] 548 + 506 506 Choose ASCII Format 507 507 508 -[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]] 509 509 510 -LHT65 Decoder 511 511 553 +[[image:image-20220527142028-26.png]] 512 512 513 - **Step6:Set up subscribe:** Subscribe a topci fordownstream.555 +LHT65 Decoder 514 514 515 -[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]] 516 516 517 -Subscribe to a topic 518 518 559 +(% style="color:#4f81bd" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream. 519 519 520 - **Step 7**: Downstream: Save the change, we can see the loginfo via "sytemlog", End Nodeand MQTT Server.561 +[[image:image-20220613191426-5.png]] 521 521 522 -[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]] 523 523 524 -Downstream Flow 525 525 526 -(% class="mark" %)**Notice:Thetext use forDownstreammust meettherequirementfrom [[LG308 DownstreamPayload>>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. 527 527 567 +[[image:image-20220527142239-28.png]] 528 528 529 -= 5. Example For Different MQTT Servers = 530 530 531 -(% style="width:731.222px" %) 532 -|=(% style="width: 270px;" %)((( 533 -[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]] 534 534 535 -== [[ThingSpeakServer>>url:http://www.thingspeak.com/]]==571 +=== MQTT Downstream format === 536 536 537 537 538 -[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]] 539 -)))|=(% style="width: 242px;" %)((( 540 -[[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**" 541 541 576 +(% class="box infomessage" %) 577 +((( 578 +mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello" 579 +))) 542 542 543 - == [[乐联网平台>>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**" 544 544 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 +))) 545 545 546 -[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]] 547 -)))|=(% style="width: 214px;" %)((( 548 -[[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]] 549 549 550 - ==[[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]]==590 +[[image:image-20220613192816-6.png||height="440" width="1056"]] 551 551 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"]]** 552 552 553 -[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]] 554 -))) 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]] 555 555 556 -= 6. How to Debug =596 += 5. How to Debug = 557 557 558 -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. 559 559 560 -= 7. How to ask for Support = 561 561 601 += 6. How to ask for Support = 602 + 562 562 If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info: 563 563 564 564 * Detail of your LoRaWAN end node.
- 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