Skip to Content

Changes for page MQTT Forward Instruction

Last modified by Xiaoling on 2025/07/31 16:59
From version 1.11
edited by Xiaoling
on 2022/05/12 16:11
Change comment: There is no comment for this version
To version 58.1
edited by Xiaoling
on 2025/07/31 16:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,423 +1,98 @@
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
20 20  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
20 +* LG308N, DLOS8N, LPS8N
21 +* LPS8V2
21 21  
23 +The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands.
22 22  
23 -= 2. Firmware Change Log for MQTT feature =
25 +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]]**
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 -)))
28 28  
29 -* LG02_LG08-5.3.1580178039
30 -** Initiate version
28 += 2.  Example to communicate to a simple MQTT server =
31 31  
30 +== 2.1  Overview ==
32 32  
33 -= 3. MQTT forward operating principle =
34 34  
35 -== 3.1 Network Structure ==
33 +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/]].
36 36  
37 -Below shows the network structure for MQTT forwarding.
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,
36 +== 2.2  Simulate via MQTT.fx utility ==
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"]]
43 43  
44 -General MQTT structure
39 +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.
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 56  (((
57 -The data flow works as below diagram.
42 +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.
58 58  )))
59 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]]
45 +[[image:image-20220527134929-6.png]]
61 61  
62 -(((
63 -Upstream path
64 -)))
47 +Connect to MQTT Broker
65 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 69  
70 -(((
71 -
72 -)))
50 +After connected, use publish to public some thing to MQTT server. This to simulate upsteam
73 73  
74 -=== 3.2.2 Downstream ===
52 +[[image:image-20220527135037-7.png]]
75 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.
54 +Upstream: Publish message to MQTT Broker
77 77  
78 -(((
79 -Below are the data flow for downstream.
80 -)))
81 81  
82 -[[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png||height="368" width="600"]]
57 +To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
83 83  
84 -Downstream path
59 +[[image:image-20220527135215-8.png]]
85 85  
61 +Downstream: Subscribe a topic to get downstream
86 86  
87 -== 3.3 Macro Definition ==
88 88  
89 -The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
64 += 3. Add LoRa support to communicate with remote sensor =
90 90  
91 -(((
92 -Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros.
93 -)))
94 94  
95 -=== 3.3.1 -t topic macro ===
67 +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 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 102  
103 -=== 3.3.2 -m message macro ===
70 +== 3.1  Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ==
104 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 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 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.
74 +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 130  )))
131 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 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.
78 +The example Sketch for LoRa Shield +Arduino is here: **[[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]**
220 220  )))
221 221  
222 -
223 -and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:
224 -
225 -(% class="box" %)
226 226  (((
227 -# Call MQTT Publish command
82 +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.
83 +
228 228  
229 -# 1. Case with User, Password and Client ID present  (e.g. Azure)
230 -if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
231 -case="1" 
232 -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"
233 -
234 -# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
235 -elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
236 -case="2" 
237 -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"
238 -
239 -# 3. Case with no User, Certificate or ClientID present
240 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
241 -case="3" 
242 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
243 -
244 -# 4. Case with no User, Certificate, but with ClientID present
245 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
246 -case="4" 
247 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
248 -
249 -# 5. Case with User and ClientID present, but no Password and no Certificate present
250 -elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
251 -case="5" 
252 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
253 -
254 -# 6. Case with User and Password present, but no ClientID and no Certificate present
255 -elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
256 -case="6" 
257 -mosquitto_pub $D -h $server -p $port -q $pub_qos  -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
258 -
259 -# 0. Else - invalid parameters, just log
260 -else
261 -case="Invalid parameters" 
262 -logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
263 -fi
264 264  )))
265 265  
266 -
267 -= 4. Example to communicate to a simple MQTT server =
268 -
269 -== 4.1 Overview ==
270 -
271 -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/]].
272 -
273 -== 4.2 Simulate via MQTT.fx utility ==
274 -
275 -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.
276 -
277 -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.
278 -
279 -[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]
280 -
281 -Connect to MQTT Broker
282 -
283 -After connected, use publish to public some thing to MQTT server. This to simulate upsteam
284 -
285 -[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]
286 -
287 -Upstream: Publish message to MQTT Broker
288 -
289 -To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
290 -
291 -[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]
292 -
293 -Downstream: Subscribe a topic to get downstream
294 -
295 -
296 -== 4.3 Simulate via Dragino Command Line ==
297 -
298 -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.
299 -
300 -In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
301 -
302 -
303 -For Upstream
304 -
305 -command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
306 -
307 -Example: mosquitto_pub -h 192.168.199.148 -p 1883 -t /channel/6543 -m temp=36
308 -
309 -Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
310 -
311 -[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]]
312 -
313 -mosquitto_pub
314 -
315 -
316 -For Downstream
317 -
318 -Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
319 -
320 -[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]
321 -
322 -mosquitto_sub
323 -
324 -
325 -== 4.4 Configure Dragino UI for MQTT connection ==
326 -
327 -This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
328 -
329 -Go to Dragino Menu ~-~-> MQTT Client
330 -
331 -[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]
332 -
333 -go to mqtt configure menu
334 -
335 -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.
336 -
337 -[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]]
338 -
339 -forward to MQTT
340 -
341 -
342 -=== 4.4.1 Configure the MQTT Client for Upstream ===
343 -
344 -Below screenshot is same as the publish command:
345 -
346 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
347 -//where the CLIENTID, CHANNEL & DATA are macro. represent for
348 -//CLIENTID: dragino-1b7060
349 -//CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
350 -//DATA: The data stores in /var/iot/channels/
351 -}}}
352 -
353 -[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
354 -
355 -MQTT Publish configure
356 -
357 -[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]]
358 -
359 -MQTT Channel settings
360 -
361 -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:
362 -
363 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
364 -}}}
365 -
366 -to MQTT broker.
367 -
368 -
369 -Below is a simulation to put this data to active the MQTT publish.
370 -
371 -[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]
372 -
373 -MQTT Publish
374 -
375 -
376 -=== 4.4.2 Configure the MQTT Client for Downstream ===
377 -
378 -Below screen shot equal to this subscribe command:
379 -
380 -{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
381 -}}}
382 -
383 -[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]
384 -
385 -MQTT Subscribe
386 -
387 -
388 -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:
389 -
390 -[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]
391 -
392 -LoRa Broadcast parameters.
393 -
394 -
395 -And below is the subscribe simulation:
396 -
397 -[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]
398 -
399 -downstream simulation
400 -
401 -
402 -== 4.5 Add LoRa support to communicate with remote sensor ==
403 -
404 -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.
405 -
406 -=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
407 -
408 -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 -
410 -The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]
411 -
412 -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.
413 -
87 +(((
414 414  What does the Arduino Sketch do? The Arduino Sketch will:
89 +)))
415 415  
416 416  * 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).
417 417  * Downstream: Listening broadcast message from gateway, and print it in console.
418 418  * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
419 419  
420 -[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]]
95 +[[image:image-20220527140354-18.png]]
421 421  
422 422  LoRa Parameter should match
423 423  
... ... @@ -424,113 +424,137 @@
424 424  
425 425  Below is the test result after the Arduino Sketch is running.
426 426  
427 -[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]]
102 +[[image:image-20220527140459-19.png]]
428 428  
429 429  Upstream Data Flow
430 430  
431 -[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]]
432 432  
107 +[[image:image-20220527140542-20.png]]
108 +
433 433  Downstream Data Flow
434 434  
435 435  
436 -=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
112 +== 3.2  Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8/LG308N/LPS8N/DLOS8N ==
437 437  
438 -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.
439 439  
440 -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.
115 +(((
116 +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.
117 +)))
441 441  
119 +(((
120 +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.
442 442  
443 443  
444 -Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
445 -
123 +(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
124 +)))
446 446  
447 -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.
126 +(((
127 +(% 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.
128 +)))
448 448  
449 -Step 2: Make sure your Radio settings match the End Node settings.
130 +(((
131 +(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
132 +)))
450 450  
451 -[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]]
134 +[[image:image-20220527141235-21.png]]
452 452  
453 453  Use Same Frequency Band as End Node
454 454  
455 455  
456 -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
139 +(((
140 +(((
141 +(% 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.
142 +)))
143 +)))
457 457  
458 -[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]]
145 +[[image:image-20220613191345-4.png]]
459 459  
460 -Publish mush use META as data format for LG308
461 461  
148 +(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
462 462  
463 -Step 4: Map the Device Address to Remote ID in MQTT server.
150 +[[image:image-20220613190635-2.png]]
464 464  
465 -[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]]
466 466  
467 -Map Dev Addr to remote ID
153 +(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
468 468  
155 +[[image:image-20220527141843-24.png]]
469 469  
470 -Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
471 471  
472 -[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]
158 +[[image:image-20220527141933-25.png]]
473 473  
474 -Upstream Process
475 -
476 -[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]]
477 -
478 478  Choose ASCII Format
479 479  
480 -[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]]
481 481  
163 +[[image:image-20220527142028-26.png]]
164 +
482 482  LHT65 Decoder
483 483  
484 -Step 6: Set up subscribe: Subscribe a topci for downstream.
485 485  
486 -[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]
168 +(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
487 487  
488 -Subscribe to a topic
170 +[[image:image-20220613191426-5.png]]
489 489  
490 490  
491 -Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
173 +(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
492 492  
493 -[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]]
175 +[[image:image-20220527142239-28.png]]
494 494  
495 -Downstream Flow
496 496  
497 -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]]
498 498  
179 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
499 499  
500 -= 5. Example For Different MQTT Servers =
181 +(% class="box infomessage" %)
182 +(((
183 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**
184 +)))
501 501  
502 -(% style="width:731.222px" %)
503 -|=(% style="width: 270px;" %)(((
504 -[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]]
186 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
505 505  
506 -== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==
188 +(% class="box infomessage" %)
189 +(((
190 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"**
191 +)))
507 507  
193 +(% 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"]]**
508 508  
509 -[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]
510 -)))|=(% style="width: 242px;" %)(((
511 -[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]]
195 +Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
512 512  
513 -== [[乐联网平台>>url:https://www.lewei50.com/]] ==
197 +[[image:image-20220613192816-6.png||height="440" width="1056"]]
514 514  
515 515  
200 +== 3.3  Use LoRaWAN Protocol for communication ~-~- For LPS8V2 ==
516 516  
202 +(((
203 +
517 517  
518 -[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
519 -)))|=(% style="width: 214px;" %)(((
520 -[[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png||alt="AWS-IOT.png" height="112" width="183"]]
205 +(% 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
206 +)))
521 521  
522 -== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==
208 +(((
209 +(% style="color:blue" %)**Step 2**(%%): Make sure your node data is normal on the built-in server
523 523  
211 +Click "**Event**" on the node device interface on chirpstack, and then click "**+up**" to view the detailed data information of the node device
524 524  
525 -[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
213 +[[image:image-20240831160038-1.png||height="680" width="1321"]]
526 526  )))
527 527  
528 -= 6. How to Debug =
529 529  
530 -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.
217 +(% style="color:blue" %)**Step 3**(%%): Set up MQTT Forworder.
531 531  
532 -= 7. How to ask for Support =
219 +[[image:image-20240831162021-2.png||height="684" width="1191"]]
533 533  
221 +
222 +(% style="color:blue" %)**Step 4:** (%%)Check result
223 +
224 +Users can check the data through the MQTT server, or use the MQtt.fx tool.
225 +
226 +[[image:image-20240831162254-3.png||height="661" width="1284"]]
227 +
228 +[[image:image-20240831162454-4.png]]
229 +
230 += 4.  How to ask for Support =
231 +
232 +
534 534  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
535 535  
536 536  * 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
image-20240831162454-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +57.6 KB
Content