Skip to Content

Changes for page MQTT Forward Instruction

Last modified by Kilight Cao on 2024/08/31 16:26
From version 37.5
edited by Xiaoling
on 2022/05/31 14:41
Change comment: There is no comment for this version
To version 54.1
edited by Kilight Cao
on 2024/08/31 16:20
Change comment: Uploaded new attachment "image-20240831162021-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -1,271 +1,43 @@
1 -**~ Contents：**
1 +**~ Table of Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -= 1. Introduction =
6 += 1.  Introduction =
7 7  
8 +
8 8  Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
9 9  
10 10  
11 -== 1.1 Support Devices ==
12 +== 1.1  Support Devices ==
12 12  
14 +
13 13  This MQTT forward instruction is for below devices:
14 14  
15 -* Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
16 -* LG01N, OLG01N ((% style="color:red" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>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]])
17 17  * LG02, OLG02
18 -* LG308, DLOS8
19 -* LPS8
20 -* LIG16
19 +* LG308, DLOS8, LPS8, LIG16
21 21  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
21 +* LG308N, DLOS8N, LPS8N
22 +* LPS8V2
22 22  
23 -= 2. Firmware Change Log for MQTT feature =
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 -)))
25 +The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands.
28 28  
29 -* LG02_LG08-5.3.1580178039
30 -** Initiate version
27 +Check out this link for more mosquito-related directives **[[https:~~/~~/mosquitto.org/man/mosquitto_pub-1.html>>https://mosquitto.org/man/mosquitto_pub-1.html]]**
31 31  
32 -= 3. MQTT forward operating principle =
33 33  
34 -== 3.1 Network Structure ==
30 += 2.  Example to communicate to a simple MQTT server =
35 35  
36 -Below shows the network structure for MQTT forwarding.
32 +== 2.1  Overview ==
37 37  
38 -* For Uplink: The sensor sends data to LoRa Gateway via LoRa wireless, The gateway will process these data and forward to remote MQTT Broker via Internet.
39 -* For Downlink: The gateway subscribe a topic in the MQTT broker, when there is update on the topic, the gateway will know and broadcast the data to Local LoRa network,
40 40  
41 -[[image:image-20220527133547-1.png]]
42 -
43 -General MQTT structure
44 -
45 -
46 -== 3.2 How sensor data is forwarded ==
47 -
48 -In this MQTT forward feature, the key point is how the gateway process the sensor data.
49 -
50 -
51 -=== 3.2.1 Upstream ===
52 -
53 -Assume there are two sensor nodes, their ID are Node1 ID: 6734 , Node2 ID: 7456. In the remote MQTT broker there are two topics: Topic1: /channel/765800, Topic2: /channel/367860. We can set up in the gateway to map Node1 to Topic1 and Node2 to Topic2. So when there is a sensor data from Node1, the gateway will forward the data to Topic1, when there is sensor data from Node2, the gateway will forward to Topic2.
54 -
55 -(((
56 -The data flow works as below diagram.
57 -)))
58 -
59 -[[image:image-20220527134000-2.png]]
60 -
61 -(((
62 -Upstream path
63 -)))
64 -
65 -(((
66 -Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>
67 -)))
68 -
69 -(((
70 -
71 -)))
72 -
73 -=== 3.2.2 Downstream ===
74 -
75 -The gateway subscribes to a topic of the remote MQTT broker topic. When there is some one publish a value on this topic. The gateway will get it and broadcast to local LoRa Network.
76 -
77 -(((
78 -Below are the data flow for downstream.
79 -)))
80 -
81 -[[image:image-20220527134038-3.png]]
82 -
83 -Downstream path
84 -
85 -
86 -== 3.3 Macro Definition ==
87 -
88 -The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
89 -
90 -(((
91 -Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros.
92 -
93 -
94 -)))
95 -
96 -=== 3.3.1 -t topic macro ===
97 -
98 -* CHANNEL: Remote Channel ID
99 -* CLIENTID: Client ID , Same as -i
100 -* WRITE_API: Remote Channel Write API
101 -* USERNAME: User ID (-u)
102 -* HOSTNAME: Device Hostname
103 -
104 -=== 3.3.2 -m message macro ===
105 -
106 -* HOSTNAME: Device Hostname
107 -* CHANNEL: Remote Channel ID
108 -* DATA: Sensor Data without time stamp and rssi
109 -* META: Completely sensor data with time stamp and rssi
110 -* JSON: Convert META to json format.
111 -
112 -=== 3.3.3 Example for Macro ===
113 -
114 -[[image:image-20220527134251-4.png]]
115 -
116 -MQTT Publish configure
117 -
118 -Above screen shots shows below format:
119 -
120 -* -t: CLIENTID/CHANNEL/data
121 -* -m: DATA
122 -
123 -When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:
124 -
125 -[[image:image-20220527134332-5.png]]
126 -
127 -Sensor Data
128 -
129 -(((
130 -According to above macro. Gateway will publish (% style="color:#4f81bd" %)**field1=22.0&field2=49.0**(%%) to topic: (% style="color:#4f81bd" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID.
131 -)))
132 -
133 -
134 -== 3.4 Modify the MQTT to support more options ==
135 -
136 -The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands. User can check the valid options by command mosquitto_pub ~-~-help. as below:
137 -
138 -(% class="box" %)
139 -(((
140 -root@dragino-1ec39c:~~# mosquitto_pub ~-~-help
141 -mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
142 -mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
143 -\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
144 - {-f file | -l | -n | -m message}
145 - [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]
146 - [-A bind_address]
147 - [-i id] [-I id_prefix]
148 - [-d] [~-~-quiet]
149 - [-M max_inflight]
150 - [-u username [-P password]]
151 - [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
152 - [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file]
153 - [~-~-ciphers ciphers] [~-~-insecure]
154 - [~-~-tls-alpn protocol]
155 - [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
156 - [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
157 - [~-~-proxy socks-url]
158 - [~-~-property command identifier value]
159 - [-D command identifier value]
160 - mosquitto_pub ~-~-help
161 -\\-A : bind the outgoing socket to this host/ip address. Use to control which interface
162 - the client communicates over.
163 --d : enable debug messages.
164 --D : Define MQTT v5 properties. See the documentation for more details.
165 --f : send the contents of a file as the message.
166 --h : mqtt host to connect to. Defaults to localhost.
167 --i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id.
168 --I : define the client id as id_prefix appended with the process id. Useful for when the
169 - broker is using the clientid_prefixes option.
170 --k : keep alive in seconds for this client. Defaults to 60.
171 --L : specify user, password, hostname, port and topic as a URL in the form:
172 - mqtt(s):~/~/[username[:password]@]host[:port]/topic
173 --l : read messages from stdin, sending a separate message for each line.
174 --m : message payload to send.
175 --M : the maximum inflight messages for QoS 1/2..
176 --n : send a null (zero length) message.
177 --p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS.
178 --P : provide a password
179 --q : quality of service level to use for all messages. Defaults to 0.
180 --r : message should be retained.
181 --s : read message from stdin, sending the entire input as a message.
182 --t : mqtt topic to publish to.
183 --u : provide a username
184 --V : specify the version of the MQTT protocol to use when connecting.
185 - Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311.
186 -~-~-help : display this message.
187 -~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
188 -~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.
189 -~-~-quiet : (% style="color:red" %)don't print error messages.
190 -~-~-will-payload : payload for the client Will, which is sent by the broker in case of
191 - unexpected disconnection. If not given and will-topic is set, a zero
192 - length message will be sent.
193 -~-~-will-qos : QoS level for the client Will.
194 -~-~-will-retain : if given, make the client Will retained.
195 -~-~-will-topic : the topic on which to publish the client Will.
196 -~-~-cafile : path to a file containing trusted CA certificates to enable encrypted
197 - communication.
198 -~-~-capath : path to a directory containing trusted CA certificates to enable encrypted
199 - communication.
200 -~-~-cert : client certificate for authentication, if required by server.
201 -~-~-key : client private key for authentication, if required by server.
202 -~-~-keyform : keyfile type, can be either "pem" or "engine".
203 -~-~-ciphers : openssl compatible list of TLS ciphers to support.
204 -~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1.
205 - Defaults to tlsv1.2 if available.
206 -~-~-insecure : do not check that the server certificate hostname matches the remote
207 - hostname. Using this option means that you cannot be sure that the
208 - remote host is the server you wish to connect to and so is insecure.
209 - Do not use this option in a production environment.
210 -~-~-tls-engine : If set, enables the use of a TLS engine device.
211 -~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.
212 -~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.
213 -~-~-psk-identity : client identity string for TLS-PSK mode.
214 -~-~-proxy : SOCKS5 proxy URL of the form:
215 - socks5h:~/~/[username[:password]@]hostname[:port]
216 - Only "none" and "username" authentication is supported.
217 -\\See https:~/~/mosquitto.org/ for more information.
218 -)))
219 -
220 -
221 -(((
222 -and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:
223 -)))
224 -
225 -(% class="box" %)
226 -(((
227 -//# Call MQTT Publish command
228 -\\# 1. Case with User, Password and Client ID present  (e.g. Azure)
229 -if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
230 -case="1" 
231 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data"
232 -\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
233 -elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
234 -case="2" 
235 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic ~-~-cert $cert ~-~-key $key $C $cafile $PUB_FLAG "$mqtt_data"
236 -\\# 3. Case with no User, Certificate or ClientID present
237 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
238 -case="3" 
239 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
240 -\\# 4. Case with no User, Certificate, but with ClientID present
241 -elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
242 -case="4" 
243 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
244 -\\# 5. Case with User and ClientID present, but no Password and no Certificate present
245 -elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
246 -case="5" 
247 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
248 -\\# 6. Case with User and Password present, but no ClientID and no Certificate present
249 -elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
250 -case="6" 
251 -mosquitto_pub $D -h $server -p $port -q $pub_qos  -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
252 -\\# 0. Else - invalid parameters, just log
253 -else
254 -case="(% style="color:red" %)Invalid parameters" (%%)
255 -logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%)
256 -fi//
257 -)))
258 -
259 -
260 -= 4. Example to communicate to a simple MQTT server =
261 -
262 -== 4.1 Overview ==
263 -
264 264  This section is an example to show how to set up LG01-N to communicate with a MQTT server. The MQTT server is a simple utility set up in a local PC. Note: User can set up same server via [[this instruction>>url:http://www.steves-internet-guide.com/install-mosquitto-broker/]].
265 265  
266 266  
267 -== 4.2 Simulate via MQTT.fx utility ==
38 +== 2.2  Simulate via MQTT.fx utility ==
268 268  
40 +
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  
271 271  (((
... ... @@ -291,152 +291,32 @@
291 291  Downstream: Subscribe a topic to get downstream
292 292  
293 293  
294 -== 4.3 Simulate via Dragino Command Line ==
295 295  
296 -For first try of MQTT connection, simulate via command line is recommend, there are many servers / connection type for MQTT. They are using different connection parameters. Simulating the connection via command line will help us rapidly connect to server and debug.
67 += 3. Add LoRa support to communicate with remote sensor =
297 297  
298 -In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
299 299  
70 +In above section, we have configured the UI to support MQTT upstream and downstream. We can simulate via Linux command. In this section, we will guide how to communicate with remote LoRa End Node for upstream and downstream.
300 300  
301 -(% style="color:#4f81bd" %)**For Upstream**
302 302  
303 -command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
304 304  
305 -Example: mosquitto_pub -h 192.168.199.148 -p 1883 -t /channel/6543 -m temp=36
74 +== 3.1  Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ==
306 306  
307 -Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
308 308  
309 -[[image:image-20220527135310-9.png]]
310 -
311 -mosquitto_pub
312 -
313 -
314 -(% style="color:#4f81bd" %)**For Downstream**
315 -
316 -Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
317 -
318 -[[image:image-20220527135440-10.png]]
319 -
320 -mosquitto_sub
321 -
322 -
323 -== 4.4 Configure Dragino UI for MQTT connection ==
324 -
325 -This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
326 -
327 327  (((
328 -Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client**
78 +We can use **[[LoRa Shield>>url:http://www.dragino.com/products/lora/item/102-lora-shield.html]]** to send LoRa Raw data to Gateway and receive data from gateway.
329 329  )))
330 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 335  (((
336 -Select (% style="color:#4f81bd" %)**Forward to MQTT server**. (% style="color:red" %)**Notice**(%%): This option is removed from the latest firmware, in the latest firmware, if user submit "SAVE & APPLY" in MQTT page, the gateway will use MQTT service.
82 +The example Sketch for LoRa Shield +Arduino is here: **[[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]**
337 337  )))
338 338  
339 -[[image:image-20220527135742-11.png]]
340 -
341 -forward to MQTT
342 -
343 -
344 -=== 4.4.1 Configure the MQTT Client for Upstream ===
345 -
346 -Below screenshot is same as the publish command:
347 -
348 -(% class="box" %)
349 349  (((
350 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
351 -~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
352 -~/~/CLIENTID: dragino-1b7060
353 -~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
354 -~/~/DATA: The data stores in /var/iot/channels/
355 -)))
86 +And this link is the required library: **[[arduino-LoRa-master>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]**. Unzip this library and put in Arduino library location.
356 356  
357 -[[image:image-20220527135828-12.png]]
358 -
359 -MQTT Publish configure
360 -
361 -
362 -[[image:image-20220527135929-13.png]]
363 -
364 -MQTT Channel settings
365 -
366 -
367 -(((
368 -For example, if we put a data(temp=46) on the file /var/iot/channels/4567, because 4567 match the remote channel 78901. the gateway will run this command:
88 +
369 369  )))
370 370  
371 -(% class="box" %)
372 372  (((
373 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
374 -)))
375 -
376 -(((
377 -to MQTT broker.
378 -)))
379 -
380 -
381 -(((
382 -Below is a simulation to put this data to active the MQTT publish.
383 -)))
384 -
385 -[[image:image-20220527140023-14.png]]
386 -
387 -MQTT Publish
388 -
389 -
390 -=== 4.4.2 Configure the MQTT Client for Downstream ===
391 -
392 -Below screen shot equal to this subscribe command:
393 -
394 -(% class="box" %)
395 -(((
396 -mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
397 -)))
398 -
399 -[[image:image-20220527140100-15.png]]
400 -
401 -MQTT Subscribe
402 -
403 -
404 -(((
405 -When MQTT broker receive a update on this topic, the gateway will get the update and use LoRa radio to broadcast this message. The LoRa parameters used for update is:
406 -)))
407 -
408 -[[image:image-20220527140148-16.png]]
409 -
410 -LoRa Broadcast parameters.
411 -
412 -
413 -And below is the subscribe simulation:
414 -
415 -[[image:image-20220527140238-17.png]]
416 -
417 -downstream simulation
418 -
419 -
420 -== 4.5 Add LoRa support to communicate with remote sensor ==
421 -
422 -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.
423 -
424 -
425 -=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
426 -
427 -(((
428 -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.
429 -)))
430 -
431 -(((
432 -The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]
433 -)))
434 -
435 -(((
436 -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.
437 -)))
438 -
439 -(((
440 440  What does the Arduino Sketch do? The Arduino Sketch will:
441 441  )))
442 442  
... ... @@ -461,8 +461,9 @@
461 461  Downstream Data Flow
462 462  
463 463  
464 -=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
116 +== 3.2  Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8/LG308N/LPS8N/DLOS8N ==
465 465  
118 +
466 466  (((
467 467  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.
468 468  )))
... ... @@ -469,15 +469,17 @@
469 469  
470 470  (((
471 471  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.
472 -(% style="color:#4f81bd" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
125 +
126 +
127 +(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
473 473  )))
474 474  
475 475  (((
476 -(% style="color:#4f81bd" %)**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.
131 +(% style="color:blue" %)**Step 1**(%%): Refer [[Communicate with ABP End Node>>Communicate with ABP End Node without LoRaWAN Network Server --- LG308]] to know how to set up LG308 to work with LoRaWAN End node.
477 477  )))
478 478  
479 479  (((
480 -(% style="color:#4f81bd" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
135 +(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
481 481  )))
482 482  
483 483  [[image:image-20220527141235-21.png]]
... ... @@ -487,29 +487,23 @@
487 487  
488 488  (((
489 489  (((
490 -(% style="color:#4f81bd" %)**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. And we need to config the format to (% style="color:#4f81bd" %)**META**
145 +(% style="color:blue" %)**Step 3**(%%): Set up publish format and MQTT channel. The LG308 will store the Data from End node in (% style="color:#4f81bd" %)**HEX format**(%%) in the file.
491 491  )))
492 492  )))
493 493  
494 -[[image:image-20220527141450-22.png]]
149 +[[image:image-20220613191345-4.png]]
495 495  
496 -Publish mush use META as data format for LG308
497 497  
152 +(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
498 498  
499 -(% style="color:#4f81bd" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
154 +[[image:image-20220613190635-2.png]]
500 500  
501 -[[image:image-20220527141727-23.png]]
502 502  
503 -Map Dev Addr to remote ID
157 +(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
504 504  
505 -
506 -(% style="color:#4f81bd" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
507 -
508 508  [[image:image-20220527141843-24.png]]
509 509  
510 -Upstream Process
511 511  
512 -
513 513  [[image:image-20220527141933-25.png]]
514 514  
515 515  Choose ASCII Format
... ... @@ -520,29 +520,46 @@
520 520  LHT65 Decoder
521 521  
522 522  
523 -(% style="color:#4f81bd" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
172 +(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
524 524  
525 -[[image:image-20220527142115-27.png]]
174 +[[image:image-20220613191426-5.png]]
526 526  
527 -Subscribe to a topic
528 528  
177 +(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
529 529  
530 -(% style="color:#4f81bd" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
531 -
532 532  [[image:image-20220527142239-28.png]]
533 533  
534 -Downstream Flow
535 535  
182 +
183 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
184 +
185 +(% class="box infomessage" %)
186 +(((
187 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**
188 +)))
189 +
190 +mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
191 +
192 +(% class="box infomessage" %)
193 +(((
194 +**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"**
195 +)))
196 +
536 536  (% 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"]]**
537 537  
199 +Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
538 538  
539 -= 5. How to Debug =
201 +[[image:image-20220613192816-6.png||height="440" width="1056"]]
540 540  
541 -User can login the gateway's console and run (% style="color:#4f81bd" %)**logread -f**(%%). It will shows the output when there is packet arrive.User can see if it is correct.
542 542  
204 +== 3.3 Use LoRaWAN Protocol for communication ~-~- For LPS8V2 ==
543 543  
544 -= 6. How to ask for Support =
545 545  
207 +
208 +
209 += 4.  How to ask for Support =
210 +
211 +
546 546  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
547 547  
548 548  * Detail of your LoRaWAN end node.
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