Changes for page MQTT Forward Instruction

Last modified by Kilight Cao on 2024/08/31 16:26
<
From version < 1.8 >
edited by Xiaoling
on 2022/05/12 15:57
To version < 2.3 >
edited by Xiaoling
on 2022/05/12 16:33
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -19,7 +19,6 @@
19 19  * LIG16
20 20  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
21 21  
22 -
23 23  = 2. Firmware Change Log for MQTT feature =
24 24  
25 25  (((
... ... @@ -29,7 +29,6 @@
29 29  * LG02_LG08-5.3.1580178039
30 30  ** Initiate version
31 31  
32 -
33 33  = 3. MQTT forward operating principle =
34 34  
35 35  == 3.1 Network Structure ==
... ... @@ -134,128 +134,126 @@
134 134  
135 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 136  
137 -{{{root@dragino-1ec39c:~# mosquitto_pub --help
135 +(% class="box" %)
136 +(((
137 +root@dragino-1ec39c:~~# mosquitto_pub ~-~-help
138 138  mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
139 139  mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
140 - 
141 -Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
140 +\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
142 142   {-f file | -l | -n | -m message}
143 - [-c] [-k keepalive] [-q qos] [-r] [--repeat N] [--repeat-delay time]
142 + [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]
144 144   [-A bind_address]
145 145   [-i id] [-I id_prefix]
146 - [-d] [--quiet]
145 + [-d] [~-~-quiet]
147 147   [-M max_inflight]
148 148   [-u username [-P password]]
149 - [--will-topic [--will-payload payload] [--will-qos qos] [--will-retain]]
150 - [{--cafile file | --capath dir} [--cert file] [--key file]
151 - [--ciphers ciphers] [--insecure]
152 - [--tls-alpn protocol]
153 - [--tls-engine engine] [--keyform keyform] [--tls-engine-kpass-sha1]]
154 - [--psk hex-key --psk-identity identity [--ciphers ciphers]]
155 - [--proxy socks-url]
156 - [--property command identifier value]
148 + [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
149 + [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file]
150 + [~-~-ciphers ciphers] [~-~-insecure]
151 + [~-~-tls-alpn protocol]
152 + [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
153 + [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
154 + [~-~-proxy socks-url]
155 + [~-~-property command identifier value]
157 157   [-D command identifier value]
158 - mosquitto_pub --help
159 - 
160 - -A : bind the outgoing socket to this host/ip address. Use to control which interface
157 + mosquitto_pub ~-~-help
158 +\\-A : bind the outgoing socket to this host/ip address. Use to control which interface
161 161   the client communicates over.
162 - -d : enable debug messages.
163 - -D : Define MQTT v5 properties. See the documentation for more details.
164 - -f : send the contents of a file as the message.
165 - -h : mqtt host to connect to. Defaults to localhost.
166 - -i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id.
167 - -I : define the client id as id_prefix appended with the process id. Useful for when the
160 +-d : enable debug messages.
161 +-D : Define MQTT v5 properties. See the documentation for more details.
162 +-f : send the contents of a file as the message.
163 +-h : mqtt host to connect to. Defaults to localhost.
164 +-i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id.
165 +-I : define the client id as id_prefix appended with the process id. Useful for when the
168 168   broker is using the clientid_prefixes option.
169 - -k : keep alive in seconds for this client. Defaults to 60.
170 - -L : specify user, password, hostname, port and topic as a URL in the form:
171 - mqtt(s)://[username[:password]@]host[:port]/topic
172 - -l : read messages from stdin, sending a separate message for each line.
173 - -m : message payload to send.
174 - -M : the maximum inflight messages for QoS 1/2..
175 - -n : send a null (zero length) message.
176 - -p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS.
177 - -P : provide a password
178 - -q : quality of service level to use for all messages. Defaults to 0.
179 - -r : message should be retained.
180 - -s : read message from stdin, sending the entire input as a message.
181 - -t : mqtt topic to publish to.
182 - -u : provide a username
183 - -V : specify the version of the MQTT protocol to use when connecting.
167 +-k : keep alive in seconds for this client. Defaults to 60.
168 +-L : specify user, password, hostname, port and topic as a URL in the form:
169 + mqtt(s):~/~/[username[:password]@]host[:port]/topic
170 +-l : read messages from stdin, sending a separate message for each line.
171 +-m : message payload to send.
172 +-M : the maximum inflight messages for QoS 1/2..
173 +-n : send a null (zero length) message.
174 +-p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS.
175 +-P : provide a password
176 +-q : quality of service level to use for all messages. Defaults to 0.
177 +-r : message should be retained.
178 +-s : read message from stdin, sending the entire input as a message.
179 +-t : mqtt topic to publish to.
180 +-u : provide a username
181 +-V : specify the version of the MQTT protocol to use when connecting.
184 184   Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311.
185 - --help : display this message.
186 - --repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
187 - --repeat-delay : if using --repeat, wait time seconds between publishes. Defaults to 0.
188 - --quiet : don't print error messages.
189 - --will-payload : payload for the client Will, which is sent by the broker in case of
183 +~-~-help : display this message.
184 +~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
185 +~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.
186 +~-~-quiet : (% class="mark" %)don't print error messages.
187 +~-~-will-payload : payload for the client Will, which is sent by the broker in case of
190 190   unexpected disconnection. If not given and will-topic is set, a zero
191 191   length message will be sent.
192 - --will-qos : QoS level for the client Will.
193 - --will-retain : if given, make the client Will retained.
194 - --will-topic : the topic on which to publish the client Will.
195 - --cafile : path to a file containing trusted CA certificates to enable encrypted
190 +~-~-will-qos : QoS level for the client Will.
191 +~-~-will-retain : if given, make the client Will retained.
192 +~-~-will-topic : the topic on which to publish the client Will.
193 +~-~-cafile : path to a file containing trusted CA certificates to enable encrypted
196 196   communication.
197 - --capath : path to a directory containing trusted CA certificates to enable encrypted
195 +~-~-capath : path to a directory containing trusted CA certificates to enable encrypted
198 198   communication.
199 - --cert : client certificate for authentication, if required by server.
200 - --key : client private key for authentication, if required by server.
201 - --keyform : keyfile type, can be either "pem" or "engine".
202 - --ciphers : openssl compatible list of TLS ciphers to support.
203 - --tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1.
197 +~-~-cert : client certificate for authentication, if required by server.
198 +~-~-key : client private key for authentication, if required by server.
199 +~-~-keyform : keyfile type, can be either "pem" or "engine".
200 +~-~-ciphers : openssl compatible list of TLS ciphers to support.
201 +~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1.
204 204   Defaults to tlsv1.2 if available.
205 - --insecure : do not check that the server certificate hostname matches the remote
203 +~-~-insecure : do not check that the server certificate hostname matches the remote
206 206   hostname. Using this option means that you cannot be sure that the
207 207   remote host is the server you wish to connect to and so is insecure.
208 208   Do not use this option in a production environment.
209 - --tls-engine : If set, enables the use of a TLS engine device.
210 - --tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.
211 - --psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.
212 - --psk-identity : client identity string for TLS-PSK mode.
213 - --proxy : SOCKS5 proxy URL of the form:
214 - socks5h://[username[:password]@]hostname[:port]
207 +~-~-tls-engine : If set, enables the use of a TLS engine device.
208 +~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.
209 +~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.
210 +~-~-psk-identity : client identity string for TLS-PSK mode.
211 +~-~-proxy : SOCKS5 proxy URL of the form:
212 + socks5h:~/~/[username[:password]@]hostname[:port]
215 215   Only "none" and "username" authentication is supported.
216 - 
217 -See https://mosquitto.org/ for more information.}}}
214 +\\See https:~/~/mosquitto.org/ for more information.
215 +)))
218 218  
219 219  
218 +(((
220 220  and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:
220 +)))
221 221  
222 -{{{# Call MQTT Publish command
223 - 
224 -# 1. Case with User, Password and Client ID present (e.g. Azure)
222 +(% class="box" %)
223 +(((
224 +# Call MQTT Publish command
225 +\\# 1. Case with User, Password and Client ID present  (e.g. Azure)
225 225  if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
226 - case="1"
227 - 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"
228 - 
229 -# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
227 +case="1" 
228 +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"
229 +\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
230 230  elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
231 - case="2"
232 - 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"
233 - 
234 -# 3. Case with no User, Certificate or ClientID present
231 +case="2" 
232 +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"
233 +\\# 3. Case with no User, Certificate or ClientID present
235 235  elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
236 - case="3"
237 - mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
238 - 
239 -# 4. Case with no User, Certificate, but with ClientID present
235 +case="3" 
236 +mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
237 +\\# 4. Case with no User, Certificate, but with ClientID present
240 240  elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
241 - case="4"
242 - mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
243 - 
244 -# 5. Case with User and ClientID present, but no Password and no Certificate present
239 +case="4" 
240 +mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
241 +\\# 5. Case with User and ClientID present, but no Password and no Certificate present
245 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 - 
249 -# 6. Case with User and Password present, but no ClientID and no Certificate present
243 +case="5" 
244 +mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
245 +\\# 6. Case with User and Password present, but no ClientID and no Certificate present
250 250  elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
251 - case="6"
252 - mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
253 - 
254 -# 0. Else - invalid parameters, just log
247 +case="6" 
248 +mosquitto_pub $D -h $server -p $port -q $pub_qos  -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
249 +\\# 0. Else - invalid parameters, just log
255 255  else
256 - case="Invalid parameters"
257 - logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
258 -fi}}}
251 +case="Invalid parameters" 
252 +logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
253 +fi
254 +)))
259 259  
260 260  
261 261  = 4. Example to communicate to a simple MQTT server =
... ... @@ -268,21 +268,23 @@
268 268  
269 269  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.
270 270  
267 +(((
271 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.
269 +)))
272 272  
273 -[[~[~[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png~|~|height="201" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_4.png]]
271 +[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]
274 274  
275 275  Connect to MQTT Broker
276 276  
277 277  After connected, use publish to public some thing to MQTT server. This to simulate upsteam
278 278  
279 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png~|~|height="149" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_5.png]]
277 +[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]
280 280  
281 281  Upstream: Publish message to MQTT Broker
282 282  
283 283  To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
284 284  
285 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png~|~|height="279" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_6.png]]
283 +[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]
286 286  
287 287  Downstream: Subscribe a topic to get downstream
288 288  
... ... @@ -294,7 +294,7 @@
294 294  In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
295 295  
296 296  
297 -For Upstream
295 +(% class="mark" %)**For Upstream**
298 298  
299 299  command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
300 300  
... ... @@ -302,65 +302,82 @@
302 302  
303 303  Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
304 304  
305 -[[~[~[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png~|~|height="188" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_6.png]]
303 +[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]]
306 306  
307 307  mosquitto_pub
308 308  
309 309  
310 -For Downstream
308 +(% class="mark" %)**For Downstream**
311 311  
312 312  Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
313 313  
314 -[[~[~[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png~|~|height="267" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_7.png]]
312 +[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]
315 315  
316 316  mosquitto_sub
317 317  
316 +
318 318  == 4.4 Configure Dragino UI for MQTT connection ==
319 319  
320 320  This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
321 321  
322 -Go to Dragino Menu ~-~-> MQTT Client
321 +(((
322 +Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client**
323 +)))
323 323  
324 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png~|~|height="249" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_8.png]]
325 +[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]
325 325  
326 326  go to mqtt configure menu
327 327  
328 -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.
329 +(((
330 +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.
331 +)))
329 329  
330 -[[~[~[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png~|~|height="240" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Commands_8.png]]
333 +[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]]
331 331  
332 332  forward to MQTT
333 333  
337 +
334 334  === 4.4.1 Configure the MQTT Client for Upstream ===
335 335  
336 336  Below screenshot is same as the publish command:
337 337  
338 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
339 -//where the CLIENTID, CHANNEL & DATA are macro. represent for
340 -//CLIENTID: dragino-1b7060
341 -//CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
342 -//DATA: The data stores in /var/iot/channels/
343 -}}}
342 +(% class="box" %)
343 +(((
344 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
345 +~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
346 +~/~/CLIENTID: dragino-1b7060
347 +~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
348 +~/~/DATA: The data stores in /var/iot/channels/
349 +)))
344 344  
345 -[[~[~[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_9.png]]
351 +[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
346 346  
347 347  MQTT Publish configure
348 348  
349 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png~|~|height="544" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_10.png]]
350 350  
356 +[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]]
357 +
351 351  MQTT Channel settings
352 352  
360 +(((
353 353  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 +)))
354 354  
355 -{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
356 -}}}
364 +(% class="box" %)
365 +(((
366 +mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
367 +)))
357 357  
369 +(((
358 358  to MQTT broker.
371 +)))
359 359  
360 360  
374 +(((
361 361  Below is a simulation to put this data to active the MQTT publish.
376 +)))
362 362  
363 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png~|~|height="308" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_11.png]]
378 +[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]
364 364  
365 365  MQTT Publish
366 366  
... ... @@ -369,17 +369,21 @@
369 369  
370 370  Below screen shot equal to this subscribe command:
371 371  
372 -{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
373 -}}}
387 +(% class="box" %)
388 +(((
389 +mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
390 +)))
374 374  
375 -[[~[~[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png~|~|height="173" width="579"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_12.png]]
392 +[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]
376 376  
377 377  MQTT Subscribe
378 378  
379 379  
397 +(((
380 380  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:
399 +)))
381 381  
382 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png~|~|height="300" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_13.png]]
401 +[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]
383 383  
384 384  LoRa Broadcast parameters.
385 385  
... ... @@ -386,12 +386,11 @@
386 386  
387 387  And below is the subscribe simulation:
388 388  
389 -[[~[~[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png~|~|height="255" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_14.png]]
408 +[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]
390 390  
391 391  downstream simulation
392 392  
393 393  
394 -
395 395  == 4.5 Add LoRa support to communicate with remote sensor ==
396 396  
397 397  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.
... ... @@ -398,19 +398,27 @@
398 398  
399 399  === 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
400 400  
419 +(((
401 401  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.
421 +)))
402 402  
423 +(((
403 403  The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]
425 +)))
404 404  
427 +(((
405 405  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.
429 +)))
406 406  
431 +(((
407 407  What does the Arduino Sketch do? The Arduino Sketch will:
433 +)))
408 408  
409 409  * 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).
410 410  * Downstream: Listening broadcast message from gateway, and print it in console.
411 411  * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
412 412  
413 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png~|~|height="197" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_17.png]]
439 +[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]]
414 414  
415 415  LoRa Parameter should match
416 416  
... ... @@ -417,11 +417,11 @@
417 417  
418 418  Below is the test result after the Arduino Sketch is running.
419 419  
420 -[[~[~[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png~|~|height="319" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_18.png]]
446 +[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]]
421 421  
422 422  Upstream Data Flow
423 423  
424 -[[~[~[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png~|~|height="309" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Command_19.png]]
450 +[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]]
425 425  
426 426  Downstream Data Flow
427 427  
... ... @@ -428,62 +428,69 @@
428 428  
429 429  === 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
430 430  
431 -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.
457 +(((
458 +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.
459 +)))
432 432  
433 -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.
461 +(((
462 +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.
463 +(% class="mark" %)**Video Instruction**(%%):[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
464 +)))
434 434  
466 +(((
467 +**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.
468 +)))
435 435  
470 +(((
471 +**Step 2**: Make sure your Radio settings match the End Node settings.
472 +)))
436 436  
437 -Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
438 -
474 +[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]]
439 439  
440 -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.
441 -
442 -Step 2: Make sure your Radio settings match the End Node settings.
443 -
444 -[[~[~[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png~|~|height="387" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_5.png]]
445 -
446 446  Use Same Frequency Band as End Node
447 447  
448 448  
449 -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
479 +(((
480 +**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
481 +)))
450 450  
451 -[[~[~[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png~|~|height="385" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_3.png]]
483 +[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]]
452 452  
453 453  Publish mush use META as data format for LG308
454 454  
455 455  
456 -Step 4: Map the Device Address to Remote ID in MQTT server.
488 +**Step 4**: Map the Device Address to Remote ID in MQTT server.
457 457  
458 -[[~[~[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png~|~|height="335" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_4.png]]
490 +[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]]
459 459  
460 460  Map Dev Addr to remote ID
461 461  
462 462  
463 -Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
495 +**Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
464 464  
465 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png~|~|height="279" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6.png]]
497 +[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]
466 466  
467 467  Upstream Process
468 468  
469 -[[~[~[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png~|~|height="246" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6_1.png]]
501 +[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]]
470 470  
471 471  Choose ASCII Format
472 472  
473 -[[~[~[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png~|~|height="248" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_6_2.png]]
505 +[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]]
474 474  
475 475  LHT65 Decoder
476 476  
477 -Step 6: Set up subscribe: Subscribe a topci for downstream.
478 478  
479 -[[~[~[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png~|~|height="176" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_7.png]]
510 +**Step 6: Set up subscribe:** Subscribe a topci for downstream.
480 480  
512 +[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]
513 +
481 481  Subscribe to a topic
482 482  
483 483  
484 -Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
517 +**Step 7**: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
485 485  
486 -[[~[~[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png~|~|height="298" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:LG308_MQTT_8.png]]
519 +[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]]
487 487  
488 488  Downstream Flow
489 489  
... ... @@ -492,32 +492,35 @@
492 492  
493 493  = 5. Example For Different MQTT Servers =
494 494  
495 -|=(((
496 -[[~[~[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png~|~|alt="ThingSpeak1.png" height="98" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:ThingSpeak1.png]]
528 +(% style="width:731.222px" %)
529 +|=(% style="width: 270px;" %)(((
530 +[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]]
497 497  
498 -=== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ===
532 +== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==
499 499  
500 500  
501 501  [[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]
502 -)))|=(((
503 -[[~[~[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png~|~|alt="Lewei50.png" height="58" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:Lewei50.png]]
536 +)))|=(% style="width: 242px;" %)(((
537 +[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]]
504 504  
505 -=== [[乐联网平台>>url:https://www.lewei50.com/]] ===
539 +== ==
506 506  
541 +== [[乐联网平台>>url:https://www.lewei50.com/]] ==
507 507  
508 -[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
509 -)))|=(((
510 -[[~[~[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png~|~|alt="AWS-IOT.png" height="122" width="200"~]~]>>url:https://wiki.dragino.com/index.php/File:AWS-IOT.png]]
511 511  
512 -=== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ===
544 +[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
545 +)))|=(% style="width: 214px;" %)(((
546 +[[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png||alt="AWS-IOT.png" height="112" width="183"]]
513 513  
548 +== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==
514 514  
550 +
515 515  [[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
516 516  )))
517 517  
518 518  = 6. How to Debug =
519 519  
520 -User can login the gateway's console and run **logread -f**. It will shows the output when there is packet arrive.User can see if it is correct.
556 +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.
521 521  
522 522  = 7. How to ask for Support =
523 523  

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0