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)
Details
- Page properties
-
- Content
-
... ... @@ -338,7 +338,9 @@ 338 338 339 339 go to mqtt configure menu 340 340 341 -Select Forward to MQTT server. 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. 341 +((( 342 +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. 343 +))) 342 342 343 343 [[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]] 344 344 ... ... @@ -349,27 +349,36 @@ 349 349 350 350 Below screenshot is same as the publish command: 351 351 352 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 353 -//where the CLIENTID, CHANNEL & DATA are macro. represent for 354 -//CLIENTID: dragino-1b7060 355 -//CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 356 -//DATA: The data stores in /var/iot/channels/ 357 -}}} 354 +(% class="box" %) 355 +((( 356 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA 357 +~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for 358 +~/~/CLIENTID: dragino-1b7060 359 +~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456 360 +~/~/DATA: The data stores in /var/iot/channels/ 361 +))) 358 358 359 359 [[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]] 360 360 361 361 MQTT Publish configure 362 362 367 + 363 363 [[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]] 364 364 365 365 MQTT Channel settings 366 366 372 +((( 367 367 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: 374 +))) 368 368 369 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 370 -}}} 376 +(% class="box" %) 377 +((( 378 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46 379 +))) 371 371 381 +((( 372 372 to MQTT broker. 383 +))) 373 373 374 374 375 375 Below is a simulation to put this data to active the MQTT publish. ... ... @@ -383,8 +383,10 @@ 383 383 384 384 Below screen shot equal to this subscribe command: 385 385 386 -{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 387 -}}} 397 +(% class="box" %) 398 +((( 399 +mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command. 400 +))) 388 388 389 389 [[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]] 390 390 ... ... @@ -391,7 +391,9 @@ 391 391 MQTT Subscribe 392 392 393 393 407 +((( 394 394 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: 409 +))) 395 395 396 396 [[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]] 397 397