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, 34 added, 0 removed)
- 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
- image-20220714155901-1.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:Main.Through MQTT to upload data.WebHome]]) 17 17 * LG02, OLG02 18 18 * LG308, DLOS8 19 19 * LPS8 ... ... @@ -20,8 +20,10 @@ 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 += 2. Firmware Change Log for MQTT feature = 27 + 28 + 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,16 @@ 29 29 * LG02_LG08-5.3.1580178039 30 30 ** Initiate version 31 31 32 -= 3. MQTT forward operating principle = 33 33 34 -= =3.1NetworkStructure ==37 += 3. MQTT forward operating principle = 35 35 39 +== 3.1 Network Structure == 40 + 41 + 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 ,44 +* **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. 45 +* **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,13 +43,15 @@ 43 43 General MQTT structure 44 44 45 45 46 -== 3.2 How sensor data is forwarded == 52 +== 3.2 How sensor data is forwarded == 47 47 54 + 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 === 58 +=== 3.2.1 Upstream === 52 52 60 + 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 55 55 ((( ... ... @@ -60,10 +60,12 @@ 60 60 61 61 ((( 62 62 Upstream path 71 + 72 + 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> 76 +(% 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 === 83 +=== 3.2.2 Downstream === 74 74 85 + 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 == 97 +== 3.3 Macro Definition == 87 87 99 + 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 === 108 +=== 3.3.1 -t topic macro === 97 97 110 + 98 98 * CHANNEL: Remote Channel ID 99 99 * CLIENTID: Client ID , Same as -i 100 100 * WRITE_API: Remote Channel Write API ... ... @@ -102,8 +102,9 @@ 102 102 * HOSTNAME: Device Hostname 103 103 104 104 105 -=== 3.3.2 -m message macro === 118 +=== 3.3.2 -m message macro === 106 106 120 + 107 107 * HOSTNAME: Device Hostname 108 108 * CHANNEL: Remote Channel ID 109 109 * DATA: Sensor Data without time stamp and rssi ... ... @@ -111,14 +111,16 @@ 111 111 * JSON: Convert META to json format. 112 112 113 113 114 -=== 3.3.3 Example for Macro === 128 +=== 3.3.3 Example for Macro === 115 115 130 + 116 116 [[image:image-20220527134251-4.png]] 117 117 118 118 MQTT Publish configure 119 119 120 -Above screen shots shows below format: 121 121 136 +**Above screen shots shows below format:** 137 + 122 122 * -t: CLIENTID/CHANNEL/data 123 123 * -m: DATA 124 124 ... ... @@ -128,13 +128,15 @@ 128 128 129 129 Sensor Data 130 130 147 + 131 131 ((( 132 132 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. 133 133 ))) 134 134 135 135 136 -== 3.4 Modify the MQTT to support more options == 153 +== 3.4 Modify the MQTT to support more options == 137 137 155 + 138 138 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: 139 139 140 140 (% class="box" %) ... ... @@ -152,9 +152,9 @@ 152 152 [-u username [-P password]] 153 153 [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]] 154 154 [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file] 155 - 156 - 157 - 173 + [~-~-ciphers ciphers] [~-~-insecure] 174 + [~-~-tls-alpn protocol] 175 + [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]] 158 158 [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]] 159 159 [~-~-proxy socks-url] 160 160 [~-~-property command identifier value] ... ... @@ -188,7 +188,7 @@ 188 188 ~-~-help : display this message. 189 189 ~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times. 190 190 ~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0. 191 -~-~-quiet : (% class="mark" %)don't print error messages.209 +~-~-quiet : (% style="color:red" %)don't print error messages. 192 192 ~-~-will-payload : payload for the client Will, which is sent by the broker in case of 193 193 unexpected disconnection. If not given and will-topic is set, a zero 194 194 length message will be sent. ... ... @@ -226,7 +226,7 @@ 226 226 227 227 (% class="box" %) 228 228 ((( 229 -# Call MQTT Publish command 247 +//# Call MQTT Publish command 230 230 \\# 1. Case with User, Password and Client ID present (e.g. Azure) 231 231 if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 232 232 case="1" ... ... @@ -253,20 +253,23 @@ 253 253 mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 254 254 \\# 0. Else - invalid parameters, just log 255 255 else 256 -case="Invalid parameters" 257 -logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." 258 -fi 274 +case="(% style="color:red" %)Invalid parameters" (%%) 275 +logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%) 276 +fi// 259 259 ))) 260 260 261 261 262 -= 4. Example to communicate to a simple MQTT server = 280 += 4. Example to communicate to a simple MQTT server = 263 263 264 -== 4.1 Overview == 282 +== 4.1 Overview == 265 265 284 + 266 266 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/]]. 267 267 268 -== 4.2 Simulate via MQTT.fx utility == 269 269 288 +== 4.2 Simulate via MQTT.fx utility == 289 + 290 + 270 270 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. 271 271 272 272 ((( ... ... @@ -273,31 +273,34 @@ 273 273 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. 274 274 ))) 275 275 276 -[[image: https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]297 +[[image:image-20220527134929-6.png]] 277 277 278 278 Connect to MQTT Broker 279 279 301 + 280 280 After connected, use publish to public some thing to MQTT server. This to simulate upsteam 281 281 282 -[[image: https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]304 +[[image:image-20220527135037-7.png]] 283 283 284 284 Upstream: Publish message to MQTT Broker 285 285 308 + 286 286 To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below: 287 287 288 -[[image: https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]311 +[[image:image-20220527135215-8.png]] 289 289 290 290 Downstream: Subscribe a topic to get downstream 291 291 292 292 293 -== 4.3 Simulate via Dragino Command Line == 316 +== 4.3 Simulate via Dragino Command Line == 294 294 318 + 295 295 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. 296 296 297 297 In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 298 298 299 299 300 -(% class="mark" %)**For Upstream**324 +(% style="color:blue" %)**For Upstream** 301 301 302 302 command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 303 303 ... ... @@ -305,63 +305,68 @@ 305 305 306 306 Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network. 307 307 308 -[[image: https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]]332 +[[image:image-20220527135310-9.png]] 309 309 310 310 mosquitto_pub 311 311 312 312 313 -(% class="mark" %)**For Downstream**337 +(% style="color:blue" %)**For Downstream** 314 314 315 315 Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 316 316 317 -[[image: https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]341 +[[image:image-20220527135440-10.png]] 318 318 319 319 mosquitto_sub 320 320 321 321 322 -== 4.4 Configure Dragino UI for MQTT connection == 346 +== 4.4 Configure Dragino UI for MQTT connection == 323 323 348 + 324 324 This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 325 325 326 326 ((( 327 -Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client**352 +Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client** 328 328 ))) 329 329 330 -[[image: https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]355 +[[image:image-20220714155901-1.png]] 331 331 332 332 go to mqtt configure menu 333 333 359 + 334 334 ((( 335 -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.361 +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. 336 336 ))) 337 337 338 -[[image: https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]]364 +[[image:image-20220527135742-11.png]] 339 339 340 340 forward to MQTT 341 341 342 342 343 -=== 4.4.1 Configure the MQTT Client for Upstream === 369 +=== 4.4.1 Configure the MQTT Client for Upstream === 344 344 345 -Below screenshot is same as the publish command: 346 346 372 +**Below screenshot is same as the publish command:** 373 + 347 347 (% class="box" %) 348 348 ((( 349 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 376 +**mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 350 350 ~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 351 351 ~/~/CLIENTID: dragino-1b7060 352 352 ~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 353 -~/~/DATA: The data stores in /var/iot/channels/ 380 +~/~/DATA: The data stores in /var/iot/channels/** 354 354 ))) 355 355 356 -[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]] 357 357 384 +[[image:image-20220527135828-12.png]] 385 + 358 358 MQTT Publish configure 359 359 360 360 361 -[[image: https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]]389 +[[image:image-20220527135929-13.png]] 362 362 363 363 MQTT Channel settings 364 364 393 + 365 365 ((( 366 366 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: 367 367 ))) ... ... @@ -380,13 +380,14 @@ 380 380 Below is a simulation to put this data to active the MQTT publish. 381 381 ))) 382 382 383 -[[image: https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]412 +[[image:image-20220527140023-14.png]] 384 384 385 385 MQTT Publish 386 386 387 387 388 -=== 4.4.2 Configure the MQTT Client for Downstream === 417 +=== 4.4.2 Configure the MQTT Client for Downstream === 389 389 419 + 390 390 Below screen shot equal to this subscribe command: 391 391 392 392 (% class="box" %) ... ... @@ -394,7 +394,7 @@ 394 394 mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 395 395 ))) 396 396 397 -[[image: https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]427 +[[image:image-20220527140100-15.png]] 398 398 399 399 MQTT Subscribe 400 400 ... ... @@ -403,7 +403,7 @@ 403 403 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: 404 404 ))) 405 405 406 -[[image: https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]436 +[[image:image-20220527140148-16.png]] 407 407 408 408 LoRa Broadcast parameters. 409 409 ... ... @@ -410,17 +410,21 @@ 410 410 411 411 And below is the subscribe simulation: 412 412 413 -[[image: https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]443 +[[image:image-20220527140238-17.png]] 414 414 415 415 downstream simulation 416 416 417 417 418 -== 4.5 Add LoRa support to communicate with remote sensor == 448 +== 4.5 Add LoRa support to communicate with remote sensor == 419 419 450 + 420 420 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. 421 421 422 -=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 423 423 454 + 455 +=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 456 + 457 + 424 424 ((( 425 425 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. 426 426 ))) ... ... @@ -431,6 +431,8 @@ 431 431 432 432 ((( 433 433 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. 468 + 469 + 434 434 ))) 435 435 436 436 ((( ... ... @@ -441,7 +441,7 @@ 441 441 * Downstream: Listening broadcast message from gateway, and print it in console. 442 442 * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below: 443 443 444 -[[image: https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]]480 +[[image:image-20220527140354-18.png]] 445 445 446 446 LoRa Parameter should match 447 447 ... ... @@ -448,35 +448,39 @@ 448 448 449 449 Below is the test result after the Arduino Sketch is running. 450 450 451 -[[image: https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]]487 +[[image:image-20220527140459-19.png]] 452 452 453 453 Upstream Data Flow 454 454 455 -[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]] 456 456 492 +[[image:image-20220527140542-20.png]] 493 + 457 457 Downstream Data Flow 458 458 459 459 460 -=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 497 +=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 461 461 499 + 462 462 ((( 463 -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.501 +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. 464 464 ))) 465 465 466 466 ((( 467 -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. 468 -(% class="mark" %)**Video Instruction**(%%):[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 505 +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. 506 + 507 + 508 +(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 469 469 ))) 470 470 471 471 ((( 472 -**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: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. 473 473 ))) 474 474 475 475 ((( 476 -**Step 2**: Make sure your Radio settings match the End Node settings. 516 +(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings. 477 477 ))) 478 478 479 -[[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]] 480 480 481 481 Use Same Frequency Band as End Node 482 482 ... ... @@ -483,86 +483,80 @@ 483 483 484 484 ((( 485 485 ((( 486 -**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: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. 487 487 ))) 488 488 ))) 489 489 490 -[[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]] 491 491 492 -Publish mush use META as data format for LG308 493 493 533 +(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server. 494 494 495 - **Step 4**: Map theDevice Address to RemoteID in MQTT server.535 +[[image:image-20220613190635-2.png]] 496 496 497 -[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]] 498 498 499 - MapDevAddrtoremoteID538 +(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server 500 500 540 +[[image:image-20220527141843-24.png]] 501 501 502 -**Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server 503 503 504 -[[image: https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]543 +[[image:image-20220527141933-25.png]] 505 505 506 -Upstream Process 507 - 508 -[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]] 509 - 510 510 Choose ASCII Format 511 511 512 -[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]] 513 513 548 +[[image:image-20220527142028-26.png]] 549 + 514 514 LHT65 Decoder 515 515 516 516 517 -**Step 6: Set up subscribe:** Subscribe a topci for downstream. 553 +(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream. 518 518 519 -[[image: https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]555 +[[image:image-20220613191426-5.png]] 520 520 521 -Subscribe to a topic 522 522 558 +(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 523 523 524 - **Step 7**: Downstream: Save the change, we can see the loginfo via "sytemlog", End Nodeand MQTT Server.560 +[[image:image-20220527142239-28.png]] 525 525 526 -[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]] 527 527 528 -Downstream Flow563 +=== 4.5.3 MQTT Downstream format === 529 529 530 -(% 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]]** 531 531 566 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**" 532 532 533 -= 5. Example For Different MQTT Servers = 568 +(% class="box infomessage" %) 569 +((( 570 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"** 571 +))) 534 534 535 -(% style="width:731.222px" %) 536 -|=(% style="width: 270px;" %)((( 537 -[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]] 573 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**" 538 538 539 -== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] == 575 +(% class="box infomessage" %) 576 +((( 577 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"** 578 +))) 540 540 580 +Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]] 541 541 542 -[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]] 543 -)))|=(% style="width: 242px;" %)((( 544 -[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]] 582 +[[image:image-20220613192816-6.png||height="440" width="1056"]] 545 545 546 546 547 - ==[[乐联网平台>>url:https://www.lewei50.com/]]==585 +(% 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"]]** 548 548 549 549 550 -[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]] 551 -)))|=(% style="width: 214px;" %)((( 552 -[[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 +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]] 553 553 554 -== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] == 555 555 591 += 5. How to Debug = 556 556 557 -[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]] 558 -))) 559 559 560 -= 6.How toDebug=594 +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. 561 561 562 -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. 563 563 564 -= 7. How to ask for Support =597 += 6. How to ask for Support = 565 565 599 + 566 566 If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info: 567 567 568 568 * Detail of your LoRaWAN end node.
- image-20220527134929-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +61.6 KB - Content
- image-20220527135037-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +65.1 KB - Content
- image-20220527135215-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +125.6 KB - Content
- image-20220527135310-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +87.9 KB - Content
- image-20220527135440-10.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.5 KB - Content
- image-20220527135742-11.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +18.2 KB - Content
- image-20220527135828-12.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +35.1 KB - Content
- image-20220527135929-13.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.0 KB - Content
- image-20220527140023-14.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +182.2 KB - Content
- image-20220527140100-15.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +8.2 KB - Content
- image-20220527140148-16.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +34.0 KB - Content
- image-20220527140238-17.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.3 KB - Content
- image-20220527140354-18.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +62.7 KB - Content
- image-20220527140459-19.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +151.0 KB - Content
- image-20220527140542-20.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +165.4 KB - Content
- image-20220527141235-21.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +83.3 KB - Content
- image-20220527141450-22.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.5 KB - Content
- image-20220527141727-23.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.6 KB - Content
- image-20220527141843-24.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +164.3 KB - Content
- image-20220527141933-25.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +100.1 KB - Content
- image-20220527142028-26.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +95.2 KB - Content
- image-20220527142115-27.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +9.3 KB - Content
- image-20220527142239-28.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +181.1 KB - Content
- image-20220527142638-29.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +62.3 KB - Content
- image-20220527142706-30.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.1 KB - Content
- image-20220527142733-31.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +10.3 KB - Content
- image-20220527142820-32.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +155.6 KB - Content
- image-20220613190254-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.7 KB - Content
- image-20220613190635-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +44.1 KB - Content
- image-20220613191154-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +56.1 KB - Content
- image-20220613191345-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.4 KB - Content
- image-20220613191426-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.8 KB - Content
- image-20220613192816-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +22.1 KB - Content
- image-20220714155901-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +75.2 KB - Content