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