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, 0 added, 14 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
Details
- Page properties
-
- Content
-
... ... @@ -101,6 +101,7 @@ 101 101 * USERNAME: User ID (-u) 102 102 * HOSTNAME: Device Hostname 103 103 104 + 104 104 === 3.3.2 -m message macro === 105 105 106 106 * HOSTNAME: Device Hostname ... ... @@ -109,6 +109,7 @@ 109 109 * META: Completely sensor data with time stamp and rssi 110 110 * JSON: Convert META to json format. 111 111 113 + 112 112 === 3.3.3 Example for Macro === 113 113 114 114 [[image:image-20220527134251-4.png]] ... ... @@ -122,12 +122,12 @@ 122 122 123 123 When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below: 124 124 125 -[[image:image -20220527134332-5.png]]127 +[[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]] 126 126 127 127 Sensor Data 128 128 129 129 ((( 130 -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.132 +According to above macro. Gateway will publish (% class="mark" %)**field1=22.0&field2=49.0**(%%) to topic: (% class="mark" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID. 131 131 ))) 132 132 133 133 ... ... @@ -186,7 +186,7 @@ 186 186 ~-~-help : display this message. 187 187 ~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times. 188 188 ~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0. 189 -~-~-quiet : (% style="color:red" %)don't print error messages.191 +~-~-quiet : (% class="mark" %)don't print error messages. 190 190 ~-~-will-payload : payload for the client Will, which is sent by the broker in case of 191 191 unexpected disconnection. If not given and will-topic is set, a zero 192 192 length message will be sent. ... ... @@ -224,7 +224,7 @@ 224 224 225 225 (% class="box" %) 226 226 ((( 227 - //# Call MQTT Publish command229 +# Call MQTT Publish command 228 228 \\# 1. Case with User, Password and Client ID present (e.g. Azure) 229 229 if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then 230 230 case="1" ... ... @@ -251,9 +251,9 @@ 251 251 mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data" 252 252 \\# 0. Else - invalid parameters, just log 253 253 else 254 -case=" (% style="color:red" %)Invalid parameters"(%%)255 -logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%)256 -fi //256 +case="Invalid parameters" 257 +logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called." 258 +fi 257 257 ))) 258 258 259 259 ... ... @@ -263,7 +263,6 @@ 263 263 264 264 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/]]. 265 265 266 - 267 267 == 4.2 Simulate via MQTT.fx utility == 268 268 269 269 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. ... ... @@ -272,21 +272,19 @@ 272 272 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. 273 273 ))) 274 274 275 -[[image:image -20220527134929-6.png]]276 +[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]] 276 276 277 277 Connect to MQTT Broker 278 278 279 - 280 280 After connected, use publish to public some thing to MQTT server. This to simulate upsteam 281 281 282 -[[image:image -20220527135037-7.png]]282 +[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]] 283 283 284 284 Upstream: Publish message to MQTT Broker 285 285 286 - 287 287 To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below: 288 288 289 -[[image:image -20220527135215-8.png]]288 +[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]] 290 290 291 291 Downstream: Subscribe a topic to get downstream 292 292 ... ... @@ -298,7 +298,7 @@ 298 298 In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection. 299 299 300 300 301 -(% style="color:#4f81bd" %)**For Upstream**300 +(% class="mark" %)**For Upstream** 302 302 303 303 command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]] 304 304 ... ... @@ -306,16 +306,16 @@ 306 306 307 307 Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network. 308 308 309 -[[image:image -20220527135310-9.png]]308 +[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]] 310 310 311 311 mosquitto_pub 312 312 313 313 314 -(% style="color:#4f81bd" %)**For Downstream**313 +(% class="mark" %)**For Downstream** 315 315 316 316 Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic. 317 317 318 -[[image:image -20220527135440-10.png]]317 +[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]] 319 319 320 320 mosquitto_sub 321 321 ... ... @@ -325,7 +325,7 @@ 325 325 This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection. 326 326 327 327 ((( 328 -Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client**327 +Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client** 329 329 ))) 330 330 331 331 [[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]] ... ... @@ -333,10 +333,10 @@ 333 333 go to mqtt configure menu 334 334 335 335 ((( 336 -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.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. 337 337 ))) 338 338 339 -[[image:image -20220527135742-11.png]]338 +[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]] 340 340 341 341 forward to MQTT 342 342 ... ... @@ -354,16 +354,15 @@ 354 354 ~/~/DATA: The data stores in /var/iot/channels/ 355 355 ))) 356 356 357 -[[image:image -20220527135828-12.png]]356 +[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]] 358 358 359 359 MQTT Publish configure 360 360 361 361 362 -[[image:image -20220527135929-13.png]]361 +[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]] 363 363 364 364 MQTT Channel settings 365 365 366 - 367 367 ((( 368 368 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: 369 369 ))) ... ... @@ -382,7 +382,7 @@ 382 382 Below is a simulation to put this data to active the MQTT publish. 383 383 ))) 384 384 385 -[[image:image -20220527140023-14.png]]383 +[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]] 386 386 387 387 MQTT Publish 388 388 ... ... @@ -396,7 +396,7 @@ 396 396 mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 397 397 ))) 398 398 399 -[[image:image -20220527140100-15.png]]397 +[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]] 400 400 401 401 MQTT Subscribe 402 402 ... ... @@ -405,7 +405,7 @@ 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: 406 406 ))) 407 407 408 -[[image:image -20220527140148-16.png]]406 +[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]] 409 409 410 410 LoRa Broadcast parameters. 411 411 ... ... @@ -412,7 +412,7 @@ 412 412 413 413 And below is the subscribe simulation: 414 414 415 -[[image:image -20220527140238-17.png]]413 +[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]] 416 416 417 417 downstream simulation 418 418 ... ... @@ -421,7 +421,6 @@ 421 421 422 422 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. 423 423 424 - 425 425 === 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 === 426 426 427 427 (((
- image-20220527134929-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -61.6 KB - Content
- image-20220527135037-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -65.1 KB - Content
- image-20220527135215-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -125.6 KB - Content
- image-20220527135310-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -87.9 KB - Content
- image-20220527135440-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.5 KB - Content
- image-20220527135742-11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -18.2 KB - Content
- image-20220527135828-12.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -35.1 KB - Content
- image-20220527135929-13.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.0 KB - Content
- image-20220527140023-14.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -182.2 KB - Content
- image-20220527140100-15.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.2 KB - Content
- image-20220527140148-16.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.0 KB - Content
- image-20220527140238-17.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.3 KB - Content
- image-20220527140354-18.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -62.7 KB - Content
- image-20220527140459-19.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -151.0 KB - Content