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