Skip to Content

Changes for page MQTT Forward Instruction

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

Summary

Details

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