Changes for page MQTT Forward Instruction
Last modified by Kilight Cao on 2024/08/31 16:26
Change comment:
Uploaded new attachment "image-20240831160038-1.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Kilight - Content
-
... ... @@ -9,311 +9,35 @@ 9 9 Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse. 10 10 11 11 12 - 13 13 == 1.1 Support Devices == 14 14 15 15 16 16 This MQTT forward instruction is for below devices: 17 17 18 -* Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 19 -* 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 +* 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]]) 20 20 * LG02, OLG02 21 -* LG308, DLOS8 22 -* LPS8 23 -* LIG16 19 +* LG308, DLOS8, LPS8, LIG16 24 24 * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support) 21 +* LG308N, DLOS8N, LPS8N 22 +* LPS8V2 25 25 26 26 25 +The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands. 27 27 27 +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]]** 28 28 29 -= 2. Firmware Change Log for MQTT feature = 30 30 30 += 2. Example to communicate to a simple MQTT server = 31 31 32 -((( 33 -This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware. 34 -))) 32 +== 2.1 Overview == 35 35 36 -* LG02_LG08-5.3.1580178039 37 -** Initiate version 38 38 39 - 40 - 41 - 42 -= 3. MQTT forward operating principle = 43 - 44 - 45 -== 3.1 Network Structure == 46 - 47 - 48 -Below shows the network structure for MQTT forwarding. 49 - 50 -* **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. 51 -* **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. 52 - 53 - 54 - 55 -[[image:image-20220527133547-1.png]] 56 - 57 -General MQTT structure 58 - 59 - 60 - 61 -== 3.2 How sensor data is forwarded == 62 - 63 - 64 -In this MQTT forward feature, the key point is how the gateway process the sensor data. 65 - 66 - 67 - 68 -=== 3.2.1 Upstream === 69 - 70 - 71 -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. 72 - 73 -((( 74 -The data flow works as below diagram. 75 - 76 - 77 -))) 78 - 79 -[[image:image-20220527134000-2.png]] 80 - 81 -((( 82 -Upstream path 83 - 84 - 85 -))) 86 - 87 -((( 88 -(% 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>** 89 -))) 90 - 91 -((( 92 - 93 - 94 - 95 -))) 96 - 97 -=== 3.2.2 Downstream === 98 - 99 - 100 -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. 101 - 102 -((( 103 -Below are the data flow for downstream. 104 - 105 - 106 -))) 107 - 108 -[[image:image-20220527134038-3.png]] 109 - 110 -Downstream path 111 - 112 - 113 - 114 -== 3.3 Macro Definition == 115 - 116 - 117 -The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish. 118 - 119 -((( 120 -Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros. 121 - 122 - 123 - 124 -))) 125 - 126 -=== 3.3.1 -t topic macro === 127 - 128 - 129 -* CHANNEL: Remote Channel ID 130 -* CLIENTID: Client ID , Same as -i 131 -* WRITE_API: Remote Channel Write API 132 -* USERNAME: User ID (-u) 133 -* HOSTNAME: Device Hostname 134 - 135 - 136 - 137 - 138 -=== 3.3.2 -m message macro === 139 - 140 - 141 -* HOSTNAME: Device Hostname 142 -* CHANNEL: Remote Channel ID 143 -* DATA: Sensor Data without time stamp and rssi 144 -* META: Completely sensor data with time stamp and rssi 145 -* JSON: Convert META to json format. 146 - 147 - 148 - 149 - 150 -=== 3.3.3 Example for Macro === 151 - 152 - 153 -[[image:image-20220527134251-4.png]] 154 - 155 -MQTT Publish configure 156 - 157 - 158 -**Above screen shots shows below format:** 159 - 160 -* -t: CLIENTID/CHANNEL/data 161 -* -m: DATA 162 - 163 -When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below: 164 - 165 -[[image:image-20220527134332-5.png]] 166 - 167 -Sensor Data 168 - 169 - 170 -((( 171 -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. 172 -))) 173 - 174 - 175 - 176 -== 3.4 Modify the MQTT to support more options == 177 - 178 - 179 -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: 180 - 181 -(% class="box" %) 182 -((( 183 -root@dragino-1ec39c:~~# mosquitto_pub ~-~-help 184 -mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit. 185 -mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4. 186 -\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL} 187 - {-f file | -l | -n | -m message} 188 - [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time] 189 - [-A bind_address] 190 - [-i id] [-I id_prefix] 191 - [-d] [~-~-quiet] 192 - [-M max_inflight] 193 - [-u username [-P password]] 194 - [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]] 195 - [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file] 196 - [~-~-ciphers ciphers] [~-~-insecure] 197 - [~-~-tls-alpn protocol] 198 - [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]] 199 - [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]] 200 - [~-~-proxy socks-url] 201 - [~-~-property command identifier value] 202 - [-D command identifier value] 203 - mosquitto_pub ~-~-help 204 -\\-A : bind the outgoing socket to this host/ip address. Use to control which interface 205 - the client communicates over. 206 --d : enable debug messages. 207 --D : Define MQTT v5 properties. See the documentation for more details. 208 --f : send the contents of a file as the message. 209 --h : mqtt host to connect to. Defaults to localhost. 210 --i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id. 211 --I : define the client id as id_prefix appended with the process id. Useful for when the 212 - broker is using the clientid_prefixes option. 213 --k : keep alive in seconds for this client. Defaults to 60. 214 --L : specify user, password, hostname, port and topic as a URL in the form: 215 - mqtt(s):~/~/[username[:password]@]host[:port]/topic 216 --l : read messages from stdin, sending a separate message for each line. 217 --m : message payload to send. 218 --M : the maximum inflight messages for QoS 1/2.. 219 --n : send a null (zero length) message. 220 --p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS. 221 --P : provide a password 222 --q : quality of service level to use for all messages. Defaults to 0. 223 --r : message should be retained. 224 --s : read message from stdin, sending the entire input as a message. 225 --t : mqtt topic to publish to. 226 --u : provide a username 227 --V : specify the version of the MQTT protocol to use when connecting. 228 - Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311. 229 -~-~-help : display this message. 230 -~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times. 231 -~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0. 232 -~-~-quiet : (% style="color:red" %)don't print error messages. 233 -~-~-will-payload : payload for the client Will, which is sent by the broker in case of 234 - unexpected disconnection. If not given and will-topic is set, a zero 235 - length message will be sent. 236 -~-~-will-qos : QoS level for the client Will. 237 -~-~-will-retain : if given, make the client Will retained. 238 -~-~-will-topic : the topic on which to publish the client Will. 239 -~-~-cafile : path to a file containing trusted CA certificates to enable encrypted 240 - communication. 241 -~-~-capath : path to a directory containing trusted CA certificates to enable encrypted 242 - communication. 243 -~-~-cert : client certificate for authentication, if required by server. 244 -~-~-key : client private key for authentication, if required by server. 245 -~-~-keyform : keyfile type, can be either "pem" or "engine". 246 -~-~-ciphers : openssl compatible list of TLS ciphers to support. 247 -~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1. 248 - Defaults to tlsv1.2 if available. 249 -~-~-insecure : do not check that the server certificate hostname matches the remote 250 - hostname. Using this option means that you cannot be sure that the 251 - remote host is the server you wish to connect to and so is insecure. 252 - Do not use this option in a production environment. 253 -~-~-tls-engine : If set, enables the use of a TLS engine device. 254 -~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine. 255 -~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode. 256 -~-~-psk-identity : client identity string for TLS-PSK mode. 257 -~-~-proxy : SOCKS5 proxy URL of the form: 258 - socks5h:~/~/[username[:password]@]hostname[:port] 259 - Only "none" and "username" authentication is supported. 260 -\\See https:~/~/mosquitto.org/ for more information. 261 -))) 262 - 263 - 264 -((( 265 -and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines: 266 -))) 267 - 268 -(% class="box" %) 269 -((( 270 -//# Call MQTT Publish command 271 -\\# 1. Case with User, Password and Client ID present (e.g. Azure) 272 -if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 273 -case="1" 274 -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" 275 -\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS) 276 -elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then 277 -case="2" 278 -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" 279 -\\# 3. Case with no User, Certificate or ClientID present 280 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then 281 -case="3" 282 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data" 283 -\\# 4. Case with no User, Certificate, but with ClientID present 284 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then 285 -case="4" 286 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data" 287 -\\# 5. Case with User and ClientID present, but no Password and no Certificate present 288 -elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 289 -case="5" 290 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data" 291 -\\# 6. Case with User and Password present, but no ClientID and no Certificate present 292 -elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then 293 -case="6" 294 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 295 -\\# 0. Else - invalid parameters, just log 296 -else 297 -case="(% style="color:red" %)Invalid parameters" (%%) 298 -logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%) 299 -fi// 300 -))) 301 - 302 - 303 - 304 -= 4. Example to communicate to a simple MQTT server = 305 - 306 - 307 -== 4.1 Overview == 308 - 309 - 310 310 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/]]. 311 311 312 312 38 +== 2.2 Simulate via MQTT.fx utility == 313 313 314 -== 4.2 Simulate via MQTT.fx utility == 315 315 316 - 317 317 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. 318 318 319 319 ((( ... ... @@ -340,163 +340,26 @@ 340 340 341 341 342 342 343 -= =4.3SimulateviaDraginoCommandLine ==67 += 3. Add LoRa support to communicate with remote sensor = 344 344 345 345 346 -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. 347 - 348 -In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 349 - 350 - 351 -(% style="color:blue" %)**For Upstream** 352 - 353 -command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 354 - 355 -Example: mosquitto_pub -h 192.168.199.148 -p 1883 -t /channel/6543 -m temp=36 356 - 357 -Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network. 358 - 359 -[[image:image-20220527135310-9.png]] 360 - 361 -mosquitto_pub 362 - 363 - 364 - 365 -(% style="color:blue" %)**For Downstream** 366 - 367 -Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 368 - 369 -[[image:image-20220527135440-10.png]] 370 - 371 -mosquitto_sub 372 - 373 - 374 - 375 -== 4.4 Configure Dragino UI for MQTT connection == 376 - 377 - 378 -This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 379 - 380 -((( 381 -Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client** 382 -))) 383 - 384 -[[image:image-20220714155901-1.png]] 385 - 386 -go to mqtt configure menu 387 - 388 - 389 -((( 390 -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. 391 -))) 392 - 393 -[[image:image-20220527135742-11.png]] 394 - 395 -forward to MQTT 396 - 397 - 398 - 399 -=== 4.4.1 Configure the MQTT Client for Upstream === 400 - 401 - 402 -**Below screenshot is same as the publish command:** 403 - 404 -(% class="box" %) 405 -((( 406 -**mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 407 -~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 408 -~/~/CLIENTID: dragino-1b7060 409 -~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 410 -~/~/DATA: The data stores in /var/iot/channels/** 411 -))) 412 - 413 - 414 -[[image:image-20220527135828-12.png]] 415 - 416 -MQTT Publish configure 417 - 418 - 419 - 420 -[[image:image-20220527135929-13.png]] 421 - 422 -MQTT Channel settings 423 - 424 - 425 -((( 426 -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: 427 -))) 428 - 429 -(% class="box" %) 430 -((( 431 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 432 -))) 433 - 434 -((( 435 -to MQTT broker. 436 -))) 437 - 438 - 439 -((( 440 -Below is a simulation to put this data to active the MQTT publish. 441 -))) 442 - 443 -[[image:image-20220527140023-14.png]] 444 - 445 -MQTT Publish 446 - 447 - 448 - 449 -=== 4.4.2 Configure the MQTT Client for Downstream === 450 - 451 - 452 -Below screen shot equal to this subscribe command: 453 - 454 -(% class="box" %) 455 -((( 456 -mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 457 -))) 458 - 459 -[[image:image-20220527140100-15.png]] 460 - 461 -MQTT Subscribe 462 - 463 - 464 -((( 465 -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: 466 -))) 467 - 468 -[[image:image-20220527140148-16.png]] 469 - 470 -LoRa Broadcast parameters. 471 - 472 - 473 -And below is the subscribe simulation: 474 - 475 -[[image:image-20220527140238-17.png]] 476 - 477 -downstream simulation 478 - 479 - 480 -== 4.5 Add LoRa support to communicate with remote sensor == 481 - 482 - 483 483 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. 484 484 485 485 486 486 487 -== =4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===74 +== 3.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 == 488 488 489 489 490 490 ((( 491 -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. 78 +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. 492 492 ))) 493 493 494 494 ((( 495 -The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]] 82 +The example Sketch for LoRa Shield +Arduino is here: **[[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]** 496 496 ))) 497 497 498 498 ((( 499 -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. 86 +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. 500 500 501 501 502 502 ))) ... ... @@ -509,14 +509,11 @@ 509 509 * Downstream: Listening broadcast message from gateway, and print it in console. 510 510 * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below: 511 511 512 - 513 - 514 514 [[image:image-20220527140354-18.png]] 515 515 516 516 LoRa Parameter should match 517 517 518 518 519 - 520 520 Below is the test result after the Arduino Sketch is running. 521 521 522 522 [[image:image-20220527140459-19.png]] ... ... @@ -524,16 +524,14 @@ 524 524 Upstream Data Flow 525 525 526 526 527 - 528 528 [[image:image-20220527140542-20.png]] 529 529 530 530 Downstream Data Flow 531 531 532 532 116 +== 3.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8/LG308N/LPS8N/DLOS8N == 533 533 534 -=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 === 535 535 536 - 537 537 ((( 538 538 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. 539 539 ))) ... ... @@ -567,38 +567,31 @@ 567 567 [[image:image-20220613191345-4.png]] 568 568 569 569 570 - 571 571 (% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server. 572 572 573 573 [[image:image-20220613190635-2.png]] 574 574 575 575 576 - 577 577 (% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server 578 578 579 579 [[image:image-20220527141843-24.png]] 580 580 581 581 582 - 583 - 584 584 [[image:image-20220527141933-25.png]] 585 585 586 586 Choose ASCII Format 587 587 588 588 589 - 590 590 [[image:image-20220527142028-26.png]] 591 591 592 592 LHT65 Decoder 593 593 594 594 595 - 596 596 (% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream. 597 597 598 598 [[image:image-20220613191426-5.png]] 599 599 600 600 601 - 602 602 (% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server. 603 603 604 604 [[image:image-20220527142239-28.png]] ... ... @@ -605,9 +605,6 @@ 605 605 606 606 607 607 608 -=== 4.5.3 MQTT Downstream format === 609 - 610 - 611 611 mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**" 612 612 613 613 (% class="box infomessage" %) ... ... @@ -622,28 +622,21 @@ 622 622 **mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"** 623 623 ))) 624 624 197 +(% 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"]]** 198 + 625 625 Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]] 626 626 627 627 [[image:image-20220613192816-6.png||height="440" width="1056"]] 628 628 629 629 630 - (% style="color:red"%)**Notice: Thetext usefor Downstreammust meet therequirement from [[LG308 DownstreamPayload>>Communicate with ABP EndNodewithout LoRaWAN NetworkServer ---LG308||anchor="H2.2Downstream"]]**204 +== 3.3 Use LoRaWAN Protocol for communication ~-~- For LPS8V2 == 631 631 632 632 633 -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]] 634 634 635 635 209 += 4. How to ask for Support = 636 636 637 -= 5. How to Debug = 638 638 639 - 640 -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. 641 - 642 - 643 - 644 -= 6. How to ask for Support = 645 - 646 - 647 647 If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info: 648 648 649 649 * Detail of your LoRaWAN end node.
- image-20240831160038-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +151.6 KB - Content