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, 5 removed)
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,7 +306,7 @@ 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
- image-20220527134332-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.7 KB - Content
- 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