Changes for page MQTT Forward Instruction

Last modified by Kilight Cao on 2024/08/31 16:26

From version < 1.2 >

edited by Xiaoling
on 2022/05/12 15:37

To version < 1.4 >

edited by Xiaoling
on 2022/05/12 15:47

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -1,8 +1,13 @@
--= INTRODUCTION =
++Contents：
++{{toc/}}
++
++
++= 1. Introduction =
++
  Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
--== Support Devices ==
++== 1.1 Support Devices ==
  This MQTT forward instruction is for below devices:
@@ -15,10 +15,8 @@
  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
--\\
++= 2. Firmware Change Log for MQTT feature =
--= Firmware Change Log for MQTT feature =
--
  This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
  * LG02_LG08-5.3.1580178039
@@ -25,12 +25,10 @@
  ** Initiate version
--\\
++= 3. MQTT forward operating principle =
--= MQTT forward operating principle =
++== 3.1 Network Structure ==
--== Network Structure ==
--
  Below shows the network structure for MQTT forwarding.
  * 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.
@@ -40,11 +40,11 @@
  General MQTT structure
--== How sensor data is forwarded ==
++== 3.2 How sensor data is forwarded ==
  In this MQTT forward feature, the key point is how the gateway process the sensor data.
--=== Upstream ===
++=== 3.2.1 Upstream ===
  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,7 +56,7 @@
  Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>
--=== Downstream ===
++=== 3.2.2 Downstream ===
  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.
@@ -67,13 +67,13 @@
  Downstream path
--== Macro Definition ==
++== 3.3 Macro Definition ==
  The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
  Currently the -t (topic) and -m (message) support Macros.
--=== -t topic macro ===
++=== 3.3.1 -t topic macro ===
  * CHANNEL: Remote Channel ID
  * CLIENTID: Client ID , Same as -i
@@ -81,7 +81,7 @@
  * USERNAME: User ID (-u)
  * HOSTNAME: Device Hostname
--=== -m message macro ===
++=== 3.3.2 -m message macro ===
  * HOSTNAME: Device Hostname
  * CHANNEL: Remote Channel ID
@@ -89,7 +89,7 @@
  * META: Completely sensor data with time stamp and rssi
  * JSON: Convert META to json format.
--=== Example for Macro ===
++=== 3.3.3 Example for Macro ===
  [[~[~[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_9.png]]
@@ -109,11 +109,8 @@
  According to above macro. Gateway will publish field1=22.0&field2=49.0 to topic: dragino-1b7060/78901/data, where 78901 is the remote channel for this node ID.
--\\
++== 3.4 Modify the MQTT to support more options ==
--
--== Modify the MQTT to support more options ==
--
  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:
  {{{root@dragino-1ec39c:~# mosquitto_pub --help
@@ -240,13 +240,13 @@
  fi}}}
--= Example to communicate to a simple MQTT server =
++= 4. Example to communicate to a simple MQTT server =
--== Overview ==
++== 4.1 Overview ==
  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/]].
--== Simulate via MQTT.fx utility ==
++== 4.2 Simulate via MQTT.fx utility ==
  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.
@@ -269,7 +269,7 @@
  Downstream: Subscribe a topic to get downstream
--== Simulate via Dragino Command Line ==
++== 4.3 Simulate via Dragino Command Line ==
  For first try of MQTT connection, simulate via command line is recommend, there are many servers / connection type for MQTT. They are using different connection parameters. Simulating the connection via command line will help us rapidly connect to server and debug.
@@ -297,7 +297,7 @@
  mosquitto_sub
--== Configure Dragino UI for MQTT connection ==
++== 4.4 Configure Dragino UI for MQTT connection ==
  This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
@@ -313,7 +313,7 @@
  forward to MQTT
--=== Configure the MQTT Client for Upstream ===
++=== 4.4.1 Configure the MQTT Client for Upstream ===
  Below screenshot is same as the publish command:
@@ -347,7 +347,7 @@
  MQTT Publish
--=== Configure the MQTT Client for Downstream ===
++=== 4.4.2 Configure the MQTT Client for Downstream ===
  Below screen shot equal to this subscribe command:
@@ -375,11 +375,11 @@
  \\
--== Add LoRa support to communicate with remote sensor ==
++== 4.5 Add LoRa support to communicate with remote sensor ==
  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.
--=== Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
++=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
  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.
@@ -409,7 +409,7 @@
  Downstream Data Flow
--=== Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
++=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
  Since firmware LG02_LG08~-~-build-v5.3.1585192026-20200326-1109, Dragino LoRaWAN gateways support the communication to LoRaWAN 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.
@@ -472,7 +472,7 @@
  Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node#Downstream]]
--= Example For Different MQTT Servers =
++= 5. Example For Different MQTT Servers =
  |=(((
  [[~[~[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png~|~|alt="ThingSpeak1.png" height="98" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:ThingSpeak1.png]]
@@ -498,11 +498,11 @@
  )))
--= How to Debug =
++= 6. How to Debug =
  User can login the gateway's console and run **logread -f**. It will shows the output when there is packet arrive.User can see if it is correct.
--= How to ask for Support =
++= 7. How to ask for Support =
  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:

Changes for page MQTT Forward Instruction

Summary

Details

Applications

Navigation