Skip to Content

Changes for page MQTT Forward Instruction

Last modified by Kilight Cao on 2024/08/31 16:26
From version 57.1
edited by Kilight Cao
on 2024/08/31 16:26
Change comment: There is no comment for this version
To version 7.6
edited by Xiaoling
on 2022/05/27 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
Content
... ... @@ -1,238 +1,566 @@
1 -**~ Table of Contents：**
1 +**~ Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -= 1.  Introduction =
6 += 1. Introduction =
7 7  
8 -
9 9  Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
10 10  
11 11  
12 -== 1.1  Support Devices ==
11 +== 1.1 Support Devices ==
13 13  
14 -
15 15  This MQTT forward instruction is for below devices:
16 16  
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]])
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>>url:https://wiki.dragino.com/index.php/Through_MQTT_to_upload_data]])
18 18  * LG02, OLG02
19 -* LG308, DLOS8, LPS8, LIG16
18 +* LG308, DLOS8
19 +* LPS8
20 +* LIG16
20 20  * 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
23 23  
24 -The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands.
23 += 2. Firmware Change Log for MQTT feature =
25 25  
26 -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]]**
25 +(((
26 +This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
27 +)))
27 27  
29 +* LG02_LG08-5.3.1580178039
30 +** Initiate version
28 28  
29 -= 2.  Example to communicate to a simple MQTT server =
32 += 3. MQTT forward operating principle =
30 30  
31 -== 2.1  Overview ==
34 +== 3.1 Network Structure ==
32 32  
36 +Below shows the network structure for MQTT forwarding.
33 33  
34 -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/]].
38 +* 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.
39 +* 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,
35 35  
41 +[[image:image-20220527133547-1.png]]
36 36  
37 -== 2.2  Simulate via MQTT.fx utility ==
43 +General MQTT structure
38 38  
39 39  
40 -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.
46 +== 3.2 How sensor data is forwarded ==
41 41  
48 +In this MQTT forward feature, the key point is how the gateway process the sensor data.
49 +
50 +
51 +=== 3.2.1 Upstream ===
52 +
53 +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.
54 +
42 42  (((
43 -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.
56 +The data flow works as below diagram.
44 44  )))
45 45  
46 -[[image:image-20220527134929-6.png]]
59 +[[image:image-20220527134000-2.png]]
47 47  
48 -Connect to MQTT Broker
61 +(((
62 +Upstream path
63 +)))
49 49  
65 +(((
66 +Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>
67 +)))
50 50  
51 -After connected, use publish to public some thing to MQTT server. This to simulate upsteam
69 +(((
70 +
71 +)))
52 52  
53 -[[image:image-20220527135037-7.png]]
73 +=== 3.2.2 Downstream ===
54 54  
55 -Upstream: Publish message to MQTT Broker
75 +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.
56 56  
77 +(((
78 +Below are the data flow for downstream.
79 +)))
57 57  
58 -To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
81 +[[image:image-20220527134038-3.png]]
59 59  
60 -[[image:image-20220527135215-8.png]]
83 +Downstream path
61 61  
62 -Downstream: Subscribe a topic to get downstream
63 63  
86 +== 3.3 Macro Definition ==
64 64  
88 +The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
65 65  
66 -= 3. Add LoRa support to communicate with remote sensor =
90 +(((
91 +Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros.
67 67  
93 +
94 +)))
68 68  
69 -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.
96 +=== 3.3.1 -t topic macro ===
70 70  
98 +* CHANNEL: Remote Channel ID
99 +* CLIENTID: Client ID , Same as -i
100 +* WRITE_API: Remote Channel Write API
101 +* USERNAME: User ID (-u)
102 +* HOSTNAME: Device Hostname
71 71  
104 +=== 3.3.2 -m message macro ===
72 72  
73 -== 3.1  Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ==
106 +* HOSTNAME: Device Hostname
107 +* CHANNEL: Remote Channel ID
108 +* DATA: Sensor Data without time stamp and rssi
109 +* META: Completely sensor data with time stamp and rssi
110 +* JSON: Convert META to json format.
74 74  
112 +=== 3.3.3 Example for Macro ===
75 75  
114 +[[image:image-20220527134251-4.png]]
115 +
116 +MQTT Publish configure
117 +
118 +Above screen shots shows below format:
119 +
120 +* -t: CLIENTID/CHANNEL/data
121 +* -m: DATA
122 +
123 +When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:
124 +
125 +[[image:image-20220527134332-5.png]]
126 +
127 +Sensor Data
128 +
76 76  (((
77 -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.
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.
78 78  )))
79 79  
133 +
134 +== 3.4 Modify the MQTT to support more options ==
135 +
136 +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:
137 +
138 +(% class="box" %)
80 80  (((
81 -The example Sketch for LoRa Shield +Arduino is here: **[[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]**
140 +root@dragino-1ec39c:~~# mosquitto_pub ~-~-help
141 +mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
142 +mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
143 +\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
144 + {-f file | -l | -n | -m message}
145 + [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]
146 + [-A bind_address]
147 + [-i id] [-I id_prefix]
148 + [-d] [~-~-quiet]
149 + [-M max_inflight]
150 + [-u username [-P password]]
151 + [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
152 + [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file]
153 + [~-~-ciphers ciphers] [~-~-insecure]
154 + [~-~-tls-alpn protocol]
155 + [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
156 + [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
157 + [~-~-proxy socks-url]
158 + [~-~-property command identifier value]
159 + [-D command identifier value]
160 + mosquitto_pub ~-~-help
161 +\\-A : bind the outgoing socket to this host/ip address. Use to control which interface
162 + the client communicates over.
163 +-d : enable debug messages.
164 +-D : Define MQTT v5 properties. See the documentation for more details.
165 +-f : send the contents of a file as the message.
166 +-h : mqtt host to connect to. Defaults to localhost.
167 +-i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id.
168 +-I : define the client id as id_prefix appended with the process id. Useful for when the
169 + broker is using the clientid_prefixes option.
170 +-k : keep alive in seconds for this client. Defaults to 60.
171 +-L : specify user, password, hostname, port and topic as a URL in the form:
172 + mqtt(s):~/~/[username[:password]@]host[:port]/topic
173 +-l : read messages from stdin, sending a separate message for each line.
174 +-m : message payload to send.
175 +-M : the maximum inflight messages for QoS 1/2..
176 +-n : send a null (zero length) message.
177 +-p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS.
178 +-P : provide a password
179 +-q : quality of service level to use for all messages. Defaults to 0.
180 +-r : message should be retained.
181 +-s : read message from stdin, sending the entire input as a message.
182 +-t : mqtt topic to publish to.
183 +-u : provide a username
184 +-V : specify the version of the MQTT protocol to use when connecting.
185 + Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311.
186 +~-~-help : display this message.
187 +~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
188 +~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.
189 +~-~-quiet : (% style="color:red" %)don't print error messages.
190 +~-~-will-payload : payload for the client Will, which is sent by the broker in case of
191 + unexpected disconnection. If not given and will-topic is set, a zero
192 + length message will be sent.
193 +~-~-will-qos : QoS level for the client Will.
194 +~-~-will-retain : if given, make the client Will retained.
195 +~-~-will-topic : the topic on which to publish the client Will.
196 +~-~-cafile : path to a file containing trusted CA certificates to enable encrypted
197 + communication.
198 +~-~-capath : path to a directory containing trusted CA certificates to enable encrypted
199 + communication.
200 +~-~-cert : client certificate for authentication, if required by server.
201 +~-~-key : client private key for authentication, if required by server.
202 +~-~-keyform : keyfile type, can be either "pem" or "engine".
203 +~-~-ciphers : openssl compatible list of TLS ciphers to support.
204 +~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1.
205 + Defaults to tlsv1.2 if available.
206 +~-~-insecure : do not check that the server certificate hostname matches the remote
207 + hostname. Using this option means that you cannot be sure that the
208 + remote host is the server you wish to connect to and so is insecure.
209 + Do not use this option in a production environment.
210 +~-~-tls-engine : If set, enables the use of a TLS engine device.
211 +~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.
212 +~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.
213 +~-~-psk-identity : client identity string for TLS-PSK mode.
214 +~-~-proxy : SOCKS5 proxy URL of the form:
215 + socks5h:~/~/[username[:password]@]hostname[:port]
216 + Only "none" and "username" authentication is supported.
217 +\\See https:~/~/mosquitto.org/ for more information.
82 82  )))
83 83  
220 +
84 84  (((
85 -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.
222 +and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:
223 +)))
86 86  
87 -
225 +(% class="box" %)
226 +(((
227 +//# Call MQTT Publish command
228 +\\# 1. Case with User, Password and Client ID present  (e.g. Azure)
229 +if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
230 +case="1" 
231 +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"
232 +\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
233 +elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
234 +case="2" 
235 +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"
236 +\\# 3. Case with no User, Certificate or ClientID present
237 +elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
238 +case="3" 
239 +mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
240 +\\# 4. Case with no User, Certificate, but with ClientID present
241 +elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
242 +case="4" 
243 +mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
244 +\\# 5. Case with User and ClientID present, but no Password and no Certificate present
245 +elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
246 +case="5" 
247 +mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
248 +\\# 6. Case with User and Password present, but no ClientID and no Certificate present
249 +elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
250 +case="6" 
251 +mosquitto_pub $D -h $server -p $port -q $pub_qos  -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
252 +\\# 0. Else - invalid parameters, just log
253 +else
254 +case="(% style="color:red" %)Invalid parameters" (%%)
255 +logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%)
256 +fi//
88 88  )))
89 89  
259 +
260 += 4. Example to communicate to a simple MQTT server =
261 +
262 +== 4.1 Overview ==
263 +
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 +
266 +== 4.2 Simulate via MQTT.fx utility ==
267 +
268 +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 +
90 90  (((
91 -What does the Arduino Sketch do? The Arduino Sketch will:
271 +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.
92 92  )))
93 93  
94 -* Upstream: Keep sending a LoRa Message every minutes with this payload : <4567>tem=xx&hum=yy (Where xx and yy are temperature and humidity value generated randomly).
95 -* Downstream: Listening broadcast message from gateway, and print it in console.
96 -* The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
274 +[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]
97 97  
98 -[[image:image-20220527140354-18.png]]
276 +Connect to MQTT Broker
99 99  
100 -LoRa Parameter should match
278 +After connected, use publish to public some thing to MQTT server. This to simulate upsteam
101 101  
280 +[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]
102 102  
103 -Below is the test result after the Arduino Sketch is running.
282 +Upstream: Publish message to MQTT Broker
104 104  
105 -[[image:image-20220527140459-19.png]]
284 +To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
106 106  
107 -Upstream Data Flow
286 +[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]
108 108  
288 +Downstream: Subscribe a topic to get downstream
109 109  
110 -[[image:image-20220527140542-20.png]]
111 111  
112 -Downstream Data Flow
291 +== 4.3 Simulate via Dragino Command Line ==
113 113  
293 +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.
114 114  
115 -== 3.2  Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8/LG308N/LPS8N/DLOS8N ==
295 +In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
116 116  
117 117  
118 -(((
119 -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.
120 -)))
298 +(% class="mark" %)**For Upstream**
121 121  
122 -(((
123 -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.
300 +command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
124 124  
302 +Example: mosquitto_pub -h 192.168.199.148 -p 1883 -t /channel/6543 -m temp=36
125 125  
126 -(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
304 +Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
305 +
306 +[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]]
307 +
308 +mosquitto_pub
309 +
310 +
311 +(% class="mark" %)**For Downstream**
312 +
313 +Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
314 +
315 +[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]
316 +
317 +mosquitto_sub
318 +
319 +
320 +== 4.4 Configure Dragino UI for MQTT connection ==
321 +
322 +This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
323 +
324 +(((
325 +Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client**
127 127  )))
128 128  
328 +[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]
329 +
330 +go to mqtt configure menu
331 +
129 129  (((
130 -(% 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.
333 +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.
131 131  )))
132 132  
336 +[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]]
337 +
338 +forward to MQTT
339 +
340 +
341 +=== 4.4.1 Configure the MQTT Client for Upstream ===
342 +
343 +Below screenshot is same as the publish command:
344 +
345 +(% class="box" %)
133 133  (((
134 -(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
347 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
348 +~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
349 +~/~/CLIENTID: dragino-1b7060
350 +~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
351 +~/~/DATA: The data stores in /var/iot/channels/
135 135  )))
136 136  
137 -[[image:image-20220527141235-21.png]]
354 +[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
138 138  
139 -Use Same Frequency Band as End Node
356 +MQTT Publish configure
140 140  
141 141  
359 +[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]]
360 +
361 +MQTT Channel settings
362 +
142 142  (((
364 +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:
365 +)))
366 +
367 +(% class="box" %)
143 143  (((
144 -(% 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.
369 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
145 145  )))
371 +
372 +(((
373 +to MQTT broker.
146 146  )))
147 147  
148 -[[image:image-20220613191345-4.png]]
149 149  
377 +(((
378 +Below is a simulation to put this data to active the MQTT publish.
379 +)))
150 150  
151 -(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
381 +[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]
152 152  
153 -[[image:image-20220613190635-2.png]]
383 +MQTT Publish
154 154  
155 155  
156 -(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
386 +=== 4.4.2 Configure the MQTT Client for Downstream ===
157 157  
158 -[[image:image-20220527141843-24.png]]
388 +Below screen shot equal to this subscribe command:
159 159  
390 +(% class="box" %)
391 +(((
392 +mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
393 +)))
160 160  
161 -[[image:image-20220527141933-25.png]]
395 +[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]
162 162  
163 -Choose ASCII Format
397 +MQTT Subscribe
164 164  
165 165  
166 -[[image:image-20220527142028-26.png]]
400 +(((
401 +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:
402 +)))
167 167  
168 -LHT65 Decoder
404 +[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]
169 169  
406 +LoRa Broadcast parameters.
170 170  
171 -(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
172 172  
173 -[[image:image-20220613191426-5.png]]
409 +And below is the subscribe simulation:
174 174  
411 +[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]
175 175  
176 -(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
413 +downstream simulation
177 177  
178 -[[image:image-20220527142239-28.png]]
179 179  
416 +== 4.5 Add LoRa support to communicate with remote sensor ==
180 180  
418 +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.
181 181  
182 -mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
420 +=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
183 183  
184 -(% class="box infomessage" %)
185 185  (((
186 -**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**
423 +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.
187 187  )))
188 188  
189 -mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
426 +(((
427 +The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]
428 +)))
190 190  
191 -(% class="box infomessage" %)
192 192  (((
193 -**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"**
431 +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.
194 194  )))
195 195  
196 -(% 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"]]**
434 +(((
435 +What does the Arduino Sketch do? The Arduino Sketch will:
436 +)))
197 197  
198 -Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
438 +* Upstream: Keep sending a LoRa Message every minutes with this payload : <4567>tem=xx&hum=yy (Where xx and yy are temperature and humidity value generated randomly).
439 +* Downstream: Listening broadcast message from gateway, and print it in console.
440 +* The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
199 199  
200 -[[image:image-20220613192816-6.png||height="440" width="1056"]]
442 +[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]]
201 201  
444 +LoRa Parameter should match
202 202  
203 -== 3.3  Use LoRaWAN Protocol for communication ~-~- For LPS8V2 ==
204 204  
447 +Below is the test result after the Arduino Sketch is running.
448 +
449 +[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]]
450 +
451 +Upstream Data Flow
452 +
453 +[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]]
454 +
455 +Downstream Data Flow
456 +
457 +
458 +=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
459 +
205 205  (((
206 -
461 +Since firmware (% class="mark" %)**LG02_LG08~-~-build-v5.3.1585192026-20200326-1109,**(%%) Dragino LoRaWAN gateways support the communication to LoRaWAN (% class="mark" %)**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.
462 +)))
207 207  
208 -(% style="color:blue" %)**Step 1**(%%): Refer **[[Register Node to Chirpstack>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H2.1A0RegisterNode]]** and **[[Register Gateway to Chirpstack>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0SemtechUDPforChirpStackv4]]**to know How do register node devices and gateways to the built-in chirpstack server
464 +(((
465 +When use test this feature, please use the version higher then : (% class="mark" %)**LG02_LG08~-~-build-v5.4.1593400722-20200629-1120**(%%), in this version, the upload format is changed and readable, which is easier for integration.
466 +(% class="mark" %)**Video Instruction**(%%):[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
209 209  )))
210 210  
211 211  (((
212 -(% style="color:blue" %)**Step 2**(%%): Make sure your node data is normal on the built-in server
470 +**Step 1**: Refer [[Communicate with ABP End Node>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node]] to know how to set up LG308 to work with LoRaWAN End node.
471 +)))
213 213  
214 -Click "**Event**" on the node device interface on chirpstack, and then click "**+up**" to view the detailed data information of the node device
473 +(((
474 +**Step 2**: Make sure your Radio settings match the End Node settings.
475 +)))
215 215  
216 -[[image:image-20240831160038-1.png||height="680" width="1321"]]
477 +[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]]
478 +
479 +Use Same Frequency Band as End Node
480 +
481 +
482 +(((
483 +(((
484 +**Step 3**: Set up publish format and MQTT channel. The LG308 will store the Data from End node in HEX format in the file. And we need to config the format to META
217 217  )))
486 +)))
218 218  
488 +[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]]
219 219  
220 -(% style="color:blue" %)**Step 3**(%%): Set up MQTT Forworder.
490 +Publish mush use META as data format for LG308
221 221  
222 -[[image:image-20240831162021-2.png||height="684" width="1191"]]
223 223  
493 +**Step 4**: Map the Device Address to Remote ID in MQTT server.
224 224  
225 -(% style="color:blue" %)**Step 4:** (%%)Check result
495 +[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]]
226 226  
227 -Users can check the data through the MQTT server, or use the MQtt.fx tool.
497 +Map Dev Addr to remote ID
228 228  
229 -[[image:image-20240831162254-3.png||height="661" width="1284"]]
230 230  
231 -[[image:image-20240831162454-4.png]]
500 +**Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
232 232  
233 -= 4.  How to ask for Support =
502 +[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]
234 234  
504 +Upstream Process
235 235  
506 +[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]]
507 +
508 +Choose ASCII Format
509 +
510 +[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]]
511 +
512 +LHT65 Decoder
513 +
514 +
515 +**Step 6: Set up subscribe:** Subscribe a topci for downstream.
516 +
517 +[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]
518 +
519 +Subscribe to a topic
520 +
521 +
522 +**Step 7**: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
523 +
524 +[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]]
525 +
526 +Downstream Flow
527 +
528 +(% class="mark" %)**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]]**
529 +
530 +
531 += 5. Example For Different MQTT Servers =
532 +
533 +(% style="width:731.222px" %)
534 +|=(% style="width: 270px;" %)(((
535 +[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]]
536 +
537 +== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==
538 +
539 +
540 +[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]
541 +)))|=(% style="width: 242px;" %)(((
542 +[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]]
543 +
544 +
545 +== [[乐联网平台>>url:https://www.lewei50.com/]] ==
546 +
547 +
548 +[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
549 +)))|=(% style="width: 214px;" %)(((
550 +[[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png||alt="AWS-IOT.png" height="112" width="183"]]
551 +
552 +== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==
553 +
554 +
555 +[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
556 +)))
557 +
558 += 6. How to Debug =
559 +
560 +User can login the gateway's console and run (% class="mark" %)**logread -f**(%%). It will shows the output when there is packet arrive.User can see if it is correct.
561 +
562 += 7. How to ask for Support =
563 +
236 236  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
237 237  
238 238  * Detail of your LoRaWAN end node.
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
image-20220527140542-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -165.4 KB
Content
image-20220527141235-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.3 KB
Content
image-20220527141450-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.5 KB
Content
image-20220527141727-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.6 KB
Content
image-20220527141843-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -164.3 KB
Content
image-20220527141933-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -100.1 KB
Content
image-20220527142028-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -95.2 KB
Content
image-20220527142115-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.3 KB
Content
image-20220527142239-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.1 KB
Content
image-20220527142638-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.3 KB
Content
image-20220527142706-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.1 KB
Content
image-20220527142733-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -10.3 KB
Content
image-20220527142820-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -155.6 KB
Content
image-20220613190254-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220613190635-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -44.1 KB
Content
image-20220613191154-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -56.1 KB
Content
image-20220613191345-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.4 KB
Content
image-20220613191426-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.8 KB
Content
image-20220613192816-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -22.1 KB
Content
image-20220714155901-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -75.2 KB
Content
image-20240831160038-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -151.6 KB
Content
image-20240831162021-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -64.5 KB
Content
image-20240831162254-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -91.9 KB
Content
image-20240831162454-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -57.6 KB
Content