Skip to Content

Changes for page MQTT Forward Instruction

Last modified by Xiaoling on 2025/07/31 16:59
From version 1.18
edited by Xiaoling
on 2022/05/12 16:19
Change comment: There is no comment for this version
To version 55.1
edited by Kilight Cao
on 2024/08/31 16:22
Change comment: Uploaded new attachment "image-20240831162254-3.png", version {1}

Summary

Details

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