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)
Details
- Page properties
-
- Content
-
... ... @@ -19,7 +19,6 @@ 19 19 * LIG16 20 20 * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support) 21 21 22 - 23 23 = 2. Firmware Change Log for MQTT feature = 24 24 25 25 ((( ... ... @@ -29,7 +29,6 @@ 29 29 * LG02_LG08-5.3.1580178039 30 30 ** Initiate version 31 31 32 - 33 33 = 3. MQTT forward operating principle = 34 34 35 35 == 3.1 Network Structure == ... ... @@ -139,8 +139,7 @@ 139 139 root@dragino-1ec39c:~~# mosquitto_pub ~-~-help 140 140 mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit. 141 141 mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4. 142 - 143 -Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 140 +\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 144 144 {-f file | -l | -n | -m message} 145 145 [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time] 146 146 [-A bind_address] ... ... @@ -158,8 +158,7 @@ 158 158 [~-~-property command identifier value] 159 159 [-D command identifier value] 160 160 mosquitto_pub ~-~-help 161 - 162 --A : bind the outgoing socket to this host/ip address. Use to control which interface 158 +\\-A : bind the outgoing socket to this host/ip address. Use to control which interface 163 163 the client communicates over. 164 164 -d : enable debug messages. 165 165 -D : Define MQTT v5 properties. See the documentation for more details. ... ... @@ -215,8 +215,7 @@ 215 215 ~-~-proxy : SOCKS5 proxy URL of the form: 216 216 socks5h:~/~/[username[:password]@]hostname[:port] 217 217 Only "none" and "username" authentication is supported. 218 - 219 -See https:~/~/mosquitto.org/ for more information. 214 +\\See https:~/~/mosquitto.org/ for more information. 220 220 ))) 221 221 222 222 ... ... @@ -227,38 +227,31 @@ 227 227 (% class="box" %) 228 228 ((( 229 229 # Call MQTT Publish command 230 - 231 -# 1. Case with User, Password and Client ID present (e.g. Azure) 225 +\\# 1. Case with User, Password and Client ID present (e.g. Azure) 232 232 if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 233 233 case="1" 234 234 mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data" 235 - 236 -# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 229 +\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 237 237 elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then 238 238 case="2" 239 239 mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic ~-~-cert $cert ~-~-key $key $C $cafile $PUB_FLAG "$mqtt_data" 240 - 241 -# 3. Case with no User, Certificate or ClientID present 233 +\\# 3. Case with no User, Certificate or ClientID present 242 242 elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then 243 243 case="3" 244 244 mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 245 - 246 -# 4. Case with no User, Certificate, but with ClientID present 237 +\\# 4. Case with no User, Certificate, but with ClientID present 247 247 elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then 248 248 case="4" 249 249 mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 250 - 251 -# 5. Case with User and ClientID present, but no Password and no Certificate present 241 +\\# 5. Case with User and ClientID present, but no Password and no Certificate present 252 252 elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 253 253 case="5" 254 254 mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data" 255 - 256 -# 6. Case with User and Password present, but no ClientID and no Certificate present 245 +\\# 6. Case with User and Password present, but no ClientID and no Certificate present 257 257 elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then 258 258 case="6" 259 259 mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 260 - 261 -# 0. Else - invalid parameters, just log 249 +\\# 0. Else - invalid parameters, just log 262 262 else 263 263 case="Invalid parameters" 264 264 logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." ... ... @@ -383,7 +383,9 @@ 383 383 ))) 384 384 385 385 374 +((( 386 386 Below is a simulation to put this data to active the MQTT publish. 376 +))) 387 387 388 388 [[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]] 389 389 ... ... @@ -394,8 +394,10 @@ 394 394 395 395 Below screen shot equal to this subscribe command: 396 396 397 -{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 398 -}}} 387 +(% class="box" %) 388 +((( 389 +mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 390 +))) 399 399 400 400 [[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]] 401 401 ... ... @@ -402,7 +402,9 @@ 402 402 MQTT Subscribe 403 403 404 404 397 +((( 405 405 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: 399 +))) 406 406 407 407 [[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]] 408 408 ... ... @@ -422,13 +422,21 @@ 422 422 423 423 === 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 424 424 419 +((( 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. 421 +))) 426 426 423 +((( 427 427 The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]] 425 +))) 428 428 427 +((( 429 429 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. 429 +))) 430 430 431 +((( 431 431 What does the Arduino Sketch do? The Arduino Sketch will: 433 +))) 432 432 433 433 * Upstream: Keep sending a LoRa Message every minutes with this payload : <4567>tem=xx&hum=yy (Where xx and yy are temperature and humidity value generated randomly). 434 434 * Downstream: Listening broadcast message from gateway, and print it in console. ... ... @@ -452,25 +452,31 @@ 452 452 453 453 === 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 454 454 455 -Since firmware LG02_LG08~-~-build-v5.3.1585192026-20200326-1109, Dragino LoRaWAN gateways support the communication to LoRaWAN ABP end node locally without the need of LoRaWAN server. This feature allow us to integrate MQTT in the gateway to support LoRaWAN to MQTT forwarding or visa verse. 457 +((( 458 +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. 459 +))) 456 456 457 -When use test this feature, please use the version higher then : LG02_LG08~-~-build-v5.4.1593400722-20200629-1120, in this version, the upload format is changed and readable, which is easier for integration. 461 +((( 462 +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. 463 +(% class="mark" %)**Video Instruction**(%%):[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 464 +))) 458 458 466 +((( 467 +**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. 468 +))) 459 459 470 +((( 471 +**Step 2**: Make sure your Radio settings match the End Node settings. 472 +))) 460 460 461 -Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]] 462 - 463 - 464 -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. 465 - 466 -Step 2: Make sure your Radio settings match the End Node settings. 467 - 468 468 [[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]] 469 469 470 470 Use Same Frequency Band as End Node 471 471 472 472 473 -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 479 +((( 480 +**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 481 +))) 474 474 475 475 [[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]] 476 476 ... ... @@ -477,7 +477,7 @@ 477 477 Publish mush use META as data format for LG308 478 478 479 479 480 -Step 4: Map the Device Address to Remote ID in MQTT server. 488 +**Step 4**: Map the Device Address to Remote ID in MQTT server. 481 481 482 482 [[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]] 483 483 ... ... @@ -484,7 +484,7 @@ 484 484 Map Dev Addr to remote ID 485 485 486 486 487 -Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server 495 +**Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server 488 488 489 489 [[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]] 490 490 ... ... @@ -498,20 +498,21 @@ 498 498 499 499 LHT65 Decoder 500 500 501 -Step 6: Set up subscribe: Subscribe a topci for downstream. 502 502 510 +**Step 6: Set up subscribe:** Subscribe a topci for downstream. 511 + 503 503 [[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]] 504 504 505 505 Subscribe to a topic 506 506 507 507 508 -Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 517 +**Step 7**: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 509 509 510 510 [[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]] 511 511 512 512 Downstream Flow 513 513 514 -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]] 523 +(% 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]]** 515 515 516 516 517 517 = 5. Example For Different MQTT Servers = ... ... @@ -527,7 +527,6 @@ 527 527 )))|=(% style="width: 242px;" %)((( 528 528 [[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]] 529 529 530 -(% class="wikigeneratedid" %) 531 531 == == 532 532 533 533 == [[乐联网平台>>url:https://www.lewei50.com/]] ==