Changes for page MQTT Forward Instruction

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

Summary

Details

Page properties
Content
... ... @@ -134,136 +134,128 @@
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 -(% class="box" %)
138 -(((
139 -root@dragino-1ec39c:~~# mosquitto_pub ~-~-help
137 +{{{root@dragino-1ec39c:~# mosquitto_pub --help
140 140  mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
141 141  mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
142 -
140 + 
143 143  Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
144 144   {-f file | -l | -n | -m message}
145 - [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]
143 + [-c] [-k keepalive] [-q qos] [-r] [--repeat N] [--repeat-delay time]
146 146   [-A bind_address]
147 147   [-i id] [-I id_prefix]
148 - [-d] [~-~-quiet]
146 + [-d] [--quiet]
149 149   [-M max_inflight]
150 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]
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]
159 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
158 + mosquitto_pub --help
159 + 
160 + -A : bind the outgoing socket to this host/ip address. Use to control which interface
163 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
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
170 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.
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.
186 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
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
192 192   unexpected disconnection. If not given and will-topic is set, a zero
193 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
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
198 198   communication.
199 -~-~-capath : path to a directory containing trusted CA certificates to enable encrypted
197 + --capath : path to a directory containing trusted CA certificates to enable encrypted
200 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.
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.
206 206   Defaults to tlsv1.2 if available.
207 -~-~-insecure : do not check that the server certificate hostname matches the remote
205 + --insecure : do not check that the server certificate hostname matches the remote
208 208   hostname. Using this option means that you cannot be sure that the
209 209   remote host is the server you wish to connect to and so is insecure.
210 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]
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]
217 217   Only "none" and "username" authentication is supported.
218 -
219 -See https:~/~/mosquitto.org/ for more information.
220 -)))
216 + 
217 +See https://mosquitto.org/ for more information.}}}
221 221  
222 222  
223 -(((
224 224  and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:
225 -)))
226 226  
227 -(% class="box" %)
228 -(((
229 -# Call MQTT Publish command
230 -
231 -# 1. Case with User, Password and Client ID present  (e.g. Azure)
222 +{{{# Call MQTT Publish command
223 + 
224 +# 1. Case with User, Password and Client ID present (e.g. Azure)
232 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 -
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 + 
236 236  # 2. Case with Certificate, Key and ClientID present (e.g. AWS)
237 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 -
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 + 
241 241  # 3. Case with no User, Certificate or ClientID present
242 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 -
236 + case="3"
237 + mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
238 + 
246 246  # 4. Case with no User, Certificate, but with ClientID present
247 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 -
241 + case="4"
242 + mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
243 + 
251 251  # 5. Case with User and ClientID present, but no Password and no Certificate present
252 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 -
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 + 
256 256  # 6. Case with User and Password present, but no ClientID and no Certificate present
257 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 -
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 + 
261 261  # 0. Else - invalid parameters, just log
262 262  else
263 -case="Invalid parameters" 
264 -logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
265 -fi
266 -)))
256 + case="Invalid parameters"
257 + logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
258 +fi}}}
267 267  
268 268  
269 269  = 4. Example to communicate to a simple MQTT server =
... ... @@ -276,23 +276,21 @@
276 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 -(((
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 -)))
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"]]
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]]
284 284  
285 285  Connect to MQTT Broker
286 286  
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"]]
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]]
290 290  
291 291  Upstream: Publish message to MQTT Broker
292 292  
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"]]
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]]
296 296  
297 297  Downstream: Subscribe a topic to get downstream
298 298  
... ... @@ -304,7 +304,7 @@
304 304  In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
305 305  
306 306  
307 -(% class="mark" %)**For Upstream**
297 +For Upstream
308 308  
309 309  command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
310 310  
... ... @@ -312,80 +312,65 @@
312 312  
313 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"]]
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]]
316 316  
317 317  mosquitto_pub
318 318  
319 319  
320 -(% class="mark" %)**For Downstream**
310 +For Downstream
321 321  
322 322  Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
323 323  
324 -[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]
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]]
325 325  
326 326  mosquitto_sub
327 327  
328 -
329 329  == 4.4 Configure Dragino UI for MQTT connection ==
330 330  
331 331  This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
332 332  
333 -(((
334 -Go to (% class="mark" %)**Dragino Menu ~-~-> MQTT Client**
335 -)))
322 +Go to Dragino Menu ~-~-> MQTT Client
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"]]
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]]
338 338  
339 339  go to mqtt configure menu
340 340  
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.
343 -)))
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.
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"]]
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]]
346 346  
347 347  forward to MQTT
348 348  
349 -
350 350  === 4.4.1 Configure the MQTT Client for Upstream ===
351 351  
352 352  Below screenshot is same as the publish command:
353 353  
354 -(% class="box" %)
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 -)))
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 +}}}
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"]]
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]]
364 364  
365 365  MQTT Publish configure
366 366  
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]]
367 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 370  MQTT Channel settings
371 371  
372 -(((
373 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:
374 -)))
375 375  
376 -(% class="box" %)
377 -(((
378 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
379 -)))
355 +{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
356 +}}}
380 380  
381 -(((
382 382  to MQTT broker.
383 -)))
384 384  
385 385  
386 386  Below is a simulation to put this data to active the MQTT publish.
387 387  
388 -[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]
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]]
389 389  
390 390  MQTT Publish
391 391  
... ... @@ -397,7 +397,7 @@
397 397  {{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
398 398  }}}
399 399  
400 -[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]
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]]
401 401  
402 402  MQTT Subscribe
403 403  
... ... @@ -404,7 +404,7 @@
404 404  
405 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 406  
407 -[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]
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]]
408 408  
409 409  LoRa Broadcast parameters.
410 410  
... ... @@ -411,11 +411,12 @@
411 411  
412 412  And below is the subscribe simulation:
413 413  
414 -[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]
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]]
415 415  
416 416  downstream simulation
417 417  
418 418  
394 +
419 419  == 4.5 Add LoRa support to communicate with remote sensor ==
420 420  
421 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.
... ... @@ -434,7 +434,7 @@
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"]]
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]]
438 438  
439 439  LoRa Parameter should match
440 440  
... ... @@ -441,11 +441,11 @@
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"]]
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]]
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"]]
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]]
449 449  
450 450  Downstream Data Flow
451 451  
... ... @@ -465,7 +465,7 @@
465 465  
466 466  Step 2: Make sure your Radio settings match the End Node settings.
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"]]
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]]
469 469  
470 470  Use Same Frequency Band as End Node
471 471  
... ... @@ -472,7 +472,7 @@
472 472  
473 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
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"]]
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]]
476 476  
477 477  Publish mush use META as data format for LG308
478 478  
... ... @@ -479,7 +479,7 @@
479 479  
480 480  Step 4: Map the Device Address to Remote ID in MQTT server.
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"]]
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]]
483 483  
484 484  Map Dev Addr to remote ID
485 485  
... ... @@ -486,21 +486,21 @@
486 486  
487 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"]]
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]]
490 490  
491 491  Upstream Process
492 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"]]
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]]
494 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"]]
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]]
498 498  
499 499  LHT65 Decoder
500 500  
501 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"]]
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]]
504 504  
505 505  Subscribe to a topic
506 506  
... ... @@ -507,7 +507,7 @@
507 507  
508 508  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"]]
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]]
511 511  
512 512  Downstream Flow
513 513  
... ... @@ -516,36 +516,32 @@
516 516  
517 517  = 5. Example For Different MQTT Servers =
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"]]
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]]
522 522  
523 -== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==
498 +=== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ===
524 524  
525 525  
526 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"]]
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]]
529 529  
530 -(% class="wikigeneratedid" %)
531 -== ==
505 +=== [[乐联网平台>>url:https://www.lewei50.com/]] ===
532 532  
533 -== [[乐联网平台>>url:https://www.lewei50.com/]] ==
534 534  
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]]
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"]]
512 +=== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ===
539 539  
540 -== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==
541 541  
542 -
543 543  [[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
544 544  )))
545 545  
546 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.
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.
549 549  
550 550  = 7. How to ask for Support =
551 551  

Applications

Navigation

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