Skip to Content

Changes for page MQTT Forward Instruction

Last modified by Xiaoling on 2025/07/31 16:59
From version 49.2
edited by Xiaoling
on 2022/08/09 16:18
Change comment: There is no comment for this version
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
... ... @@ -1,22 +1,18 @@
1 -**~ Table of Contents：**
1 +**~ Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -= 1.  Introduction =
6 += 1. Introduction =
7 7  
8 -
9 9  Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
10 10  
10 +== 1.1 Support Devices ==
11 11  
12 -
13 -== 1.1  Support Devices ==
14 -
15 -
16 16  This MQTT forward instruction is for below devices:
17 17  
18 18  * Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
19 -* LG01N, OLG01N ((% style="color:red" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>doc:Through MQTT to upload data.WebHome]])
15 +* LG01N, OLG01N ((% class="mark" %)**Warning**(%%): LG01-P LG01-S use another instruction: [[MQTT for LG01-P/LG01S>>url:https://wiki.dragino.com/index.php/Through_MQTT_to_upload_data]])
20 20  * LG02, OLG02
21 21  * LG308, DLOS8
22 22  * LPS8
... ... @@ -24,11 +24,8 @@
24 24  * MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
25 25  
26 26  
23 += 2. Firmware Change Log for MQTT feature =
27 27  
28 -
29 -= 2.  Firmware Change Log for MQTT feature =
30 -
31 -
32 32  (((
33 33  This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
34 34  )))
... ... @@ -37,95 +37,70 @@
37 37  ** Initiate version
38 38  
39 39  
33 += 3. MQTT forward operating principle =
40 40  
35 +== 3.1 Network Structure ==
41 41  
42 -= 3.  MQTT forward operating principle =
43 -
44 -
45 -== 3.1  Network Structure ==
46 -
47 -
48 48  Below shows the network structure for MQTT forwarding.
49 49  
50 -* **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.
51 -* **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.
39 +* For Uplink: The sensor sends data to LoRa Gateway via LoRa wireless, The gateway will process these data and forward to remote MQTT Broker via Internet.
40 +* For Downlink: The gateway subscribe a topic in the MQTT broker, when there is update on the topic, the gateway will know and broadcast the data to Local LoRa network,
52 52  
42 +[[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png||height="348" width="600"]]
53 53  
54 -
55 -[[image:image-20220527133547-1.png]]
56 -
57 57  General MQTT structure
58 58  
59 59  
47 +== 3.2 How sensor data is forwarded ==
60 60  
61 -== 3.2  How sensor data is forwarded ==
62 -
63 -
64 64  In this MQTT forward feature, the key point is how the gateway process the sensor data.
65 65  
66 66  
52 +=== 3.2.1 Upstream ===
67 67  
68 -=== 3.2.1  Upstream ===
69 -
70 -
71 71  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.
72 72  
73 73  (((
74 74  The data flow works as below diagram.
75 -
76 -
77 77  )))
78 78  
79 -[[image:image-20220527134000-2.png]]
60 +[[~[~[image:https://wiki.dragino.com/images/thumb/2/2a/MQTT_Forward_2.png/600px-MQTT_Forward_2.png~|~|height="355" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:MQTT_Forward_2.png]]
80 80  
81 81  (((
82 82  Upstream path
83 -
84 -
85 85  )))
86 86  
87 87  (((
88 -(% style="color:red" %)**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 +Note: The sensor data can base or LoRa or other method, as long as there are data on the file /var/iot/channels. /span>
89 89  )))
90 90  
91 91  (((
92 92  
93 -
94 -
95 95  )))
96 96  
97 -=== 3.2.2  Downstream ===
74 +=== 3.2.2 Downstream ===
98 98  
99 -
100 100  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.
101 101  
102 102  (((
103 103  Below are the data flow for downstream.
104 -
105 -
106 106  )))
107 107  
108 -[[image:image-20220527134038-3.png]]
82 +[[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png||height="368" width="600"]]
109 109  
110 110  Downstream path
111 111  
112 112  
87 +== 3.3 Macro Definition ==
113 113  
114 -== 3.3  Macro Definition ==
115 -
116 -
117 117  The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
118 118  
119 119  (((
120 -Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros.
121 -
122 -
123 -
92 +Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros.
124 124  )))
125 125  
126 -=== 3.3.1  -t topic macro ===
95 +=== 3.3.1 -t topic macro ===
127 127  
128 -
129 129  * CHANNEL: Remote Channel ID
130 130  * CLIENTID: Client ID , Same as -i
131 131  * WRITE_API: Remote Channel Write API
... ... @@ -132,12 +132,8 @@
132 132  * USERNAME: User ID (-u)
133 133  * HOSTNAME: Device Hostname
134 134  
103 +=== 3.3.2 -m message macro ===
135 135  
136 -
137 -
138 -=== 3.3.2  -m message macro ===
139 -
140 -
141 141  * HOSTNAME: Device Hostname
142 142  * CHANNEL: Remote Channel ID
143 143  * DATA: Sensor Data without time stamp and rssi
... ... @@ -144,211 +144,193 @@
144 144  * META: Completely sensor data with time stamp and rssi
145 145  * JSON: Convert META to json format.
146 146  
111 +=== 3.3.3 Example for Macro ===
147 147  
113 +[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
148 148  
149 -
150 -=== 3.3.3  Example for Macro ===
151 -
152 -
153 -[[image:image-20220527134251-4.png]]
154 -
155 155  MQTT Publish configure
156 156  
117 +Above screen shots shows below format:
157 157  
158 -**Above screen shots shows below format:**
159 -
160 160  * -t: CLIENTID/CHANNEL/data
161 161  * -m: DATA
162 162  
163 163  When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:
164 164  
165 -[[image:image-20220527134332-5.png]]
124 +[[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]]
166 166  
167 167  Sensor Data
168 168  
169 -
170 170  (((
171 -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.
129 +According to above macro. Gateway will publish (% class="mark" %)**field1=22.0&field2=49.0**(%%) to topic: (% class="mark" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID.
172 172  )))
173 173  
174 174  
133 +== 3.4 Modify the MQTT to support more options ==
175 175  
176 -== 3.4  Modify the MQTT to support more options ==
177 -
178 -
179 179  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:
180 180  
181 -(% class="box" %)
182 -(((
183 -root@dragino-1ec39c:~~# mosquitto_pub ~-~-help
137 +{{{root@dragino-1ec39c:~# mosquitto_pub --help
184 184  mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
185 185  mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
186 -\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
140 + 
141 +Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
187 187   {-f file | -l | -n | -m message}
188 - [-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]
143 + [-c] [-k keepalive] [-q qos] [-r] [--repeat N] [--repeat-delay time]
189 189   [-A bind_address]
190 190   [-i id] [-I id_prefix]
191 - [-d] [~-~-quiet]
146 + [-d] [--quiet]
192 192   [-M max_inflight]
193 193   [-u username [-P password]]
194 - [~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
195 - [{~-~-cafile file | ~-~-capath dir} [~-~-cert file] [~-~-key file]
196 - [~-~-ciphers ciphers] [~-~-insecure]
197 - [~-~-tls-alpn protocol]
198 - [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
199 - [~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
200 - [~-~-proxy socks-url]
201 - [~-~-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]
202 202   [-D command identifier value]
203 - mosquitto_pub ~-~-help
204 -\\-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
205 205   the client communicates over.
206 --d : enable debug messages.
207 --D : Define MQTT v5 properties. See the documentation for more details.
208 --f : send the contents of a file as the message.
209 --h : mqtt host to connect to. Defaults to localhost.
210 --i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id.
211 --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
212 212   broker is using the clientid_prefixes option.
213 --k : keep alive in seconds for this client. Defaults to 60.
214 --L : specify user, password, hostname, port and topic as a URL in the form:
215 - mqtt(s):~/~/[username[:password]@]host[:port]/topic
216 --l : read messages from stdin, sending a separate message for each line.
217 --m : message payload to send.
218 --M : the maximum inflight messages for QoS 1/2..
219 --n : send a null (zero length) message.
220 --p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS.
221 --P : provide a password
222 --q : quality of service level to use for all messages. Defaults to 0.
223 --r : message should be retained.
224 --s : read message from stdin, sending the entire input as a message.
225 --t : mqtt topic to publish to.
226 --u : provide a username
227 --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.
228 228   Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311.
229 -~-~-help : display this message.
230 -~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
231 -~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.
232 -~-~-quiet : (% style="color:red" %)don't print error messages.
233 -~-~-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
234 234   unexpected disconnection. If not given and will-topic is set, a zero
235 235   length message will be sent.
236 -~-~-will-qos : QoS level for the client Will.
237 -~-~-will-retain : if given, make the client Will retained.
238 -~-~-will-topic : the topic on which to publish the client Will.
239 -~-~-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
240 240   communication.
241 -~-~-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
242 242   communication.
243 -~-~-cert : client certificate for authentication, if required by server.
244 -~-~-key : client private key for authentication, if required by server.
245 -~-~-keyform : keyfile type, can be either "pem" or "engine".
246 -~-~-ciphers : openssl compatible list of TLS ciphers to support.
247 -~-~-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.
248 248   Defaults to tlsv1.2 if available.
249 -~-~-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
250 250   hostname. Using this option means that you cannot be sure that the
251 251   remote host is the server you wish to connect to and so is insecure.
252 252   Do not use this option in a production environment.
253 -~-~-tls-engine : If set, enables the use of a TLS engine device.
254 -~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.
255 -~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.
256 -~-~-psk-identity : client identity string for TLS-PSK mode.
257 -~-~-proxy : SOCKS5 proxy URL of the form:
258 - 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]
259 259   Only "none" and "username" authentication is supported.
260 -\\See https:~/~/mosquitto.org/ for more information.
261 -)))
216 + 
217 +See https://mosquitto.org/ for more information.}}}
262 262  
263 263  
264 -(((
265 265  and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:
266 -)))
267 267  
268 -(% class="box" %)
269 -(((
270 -//# Call MQTT Publish command
271 -\\# 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)
272 272  if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
273 -case="1" 
274 -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"
275 -\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
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)
276 276  elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
277 -case="2" 
278 -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"
279 -\\# 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 + 
234 +# 3. Case with no User, Certificate or ClientID present
280 280  elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
281 -case="3" 
282 -mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
283 -\\# 4. Case with no User, Certificate, but with ClientID present
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
284 284  elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
285 -case="4" 
286 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
287 -\\# 5. Case with User and ClientID present, but no Password and no Certificate present
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
288 288  elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
289 -case="5" 
290 -mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
291 -\\# 6. Case with User and Password present, but no ClientID and no Certificate present
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
292 292  elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
293 -case="6" 
294 -mosquitto_pub $D -h $server -p $port -q $pub_qos  -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
295 -\\# 0. Else - invalid parameters, just log
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
296 296  else
297 -case="(% style="color:red" %)Invalid parameters" (%%)
298 -logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%)
299 -fi//
300 -)))
256 + case="Invalid parameters"
257 + logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
258 +fi}}}
301 301  
302 302  
261 += 4. Example to communicate to a simple MQTT server =
303 303  
304 -= 4.  Example to communicate to a simple MQTT server =
263 +== 4.1 Overview ==
305 305  
306 -
307 -== 4.1  Overview ==
308 -
309 -
310 310  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/]].
311 311  
267 +== 4.2 Simulate via MQTT.fx utility ==
312 312  
313 -
314 -== 4.2  Simulate via MQTT.fx utility ==
315 -
316 -
317 317  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.
318 318  
319 -(((
320 320  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.
321 -)))
322 322  
323 -[[image:image-20220527134929-6.png]]
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]]
324 324  
325 325  Connect to MQTT Broker
326 326  
327 -
328 328  After connected, use publish to public some thing to MQTT server. This to simulate upsteam
329 329  
330 -[[image:image-20220527135037-7.png]]
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]]
331 331  
332 332  Upstream: Publish message to MQTT Broker
333 333  
334 -
335 335  To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
336 336  
337 -[[image:image-20220527135215-8.png]]
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]]
338 338  
339 339  Downstream: Subscribe a topic to get downstream
340 340  
341 341  
290 +== 4.3 Simulate via Dragino Command Line ==
342 342  
343 -== 4.3  Simulate via Dragino Command Line ==
344 -
345 -
346 346  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.
347 347  
348 348  In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
349 349  
350 350  
351 -(% style="color:blue" %)**For Upstream**
297 +For Upstream
352 352  
353 353  command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
354 354  
... ... @@ -356,116 +356,84 @@
356 356  
357 357  Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
358 358  
359 -[[image:image-20220527135310-9.png]]
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]]
360 360  
361 361  mosquitto_pub
362 362  
363 363  
310 +For Downstream
364 364  
365 -(% style="color:blue" %)**For Downstream**
366 -
367 367  Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
368 368  
369 -[[image:image-20220527135440-10.png]]
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]]
370 370  
371 371  mosquitto_sub
372 372  
318 +== 4.4 Configure Dragino UI for MQTT connection ==
373 373  
374 -
375 -== 4.4  Configure Dragino UI for MQTT connection ==
376 -
377 -
378 378  This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
379 379  
380 -(((
381 -Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client**
382 -)))
322 +Go to Dragino Menu ~-~-> MQTT Client
383 383  
384 -[[image:image-20220714155901-1.png]]
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]]
385 385  
386 386  go to mqtt configure menu
387 387  
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.
388 388  
389 -(((
390 -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.
391 -)))
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]]
392 392  
393 -[[image:image-20220527135742-11.png]]
394 -
395 395  forward to MQTT
396 396  
334 +=== 4.4.1 Configure the MQTT Client for Upstream ===
397 397  
336 +Below screenshot is same as the publish command:
398 398  
399 -=== 4.4.1  Configure the MQTT Client for Upstream ===
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 +}}}
400 400  
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]]
401 401  
402 -**Below screenshot is same as the publish command:**
403 -
404 -(% class="box" %)
405 -(((
406 -**mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
407 -~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
408 -~/~/CLIENTID: dragino-1b7060
409 -~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
410 -~/~/DATA: The data stores in /var/iot/channels/**
411 -)))
412 -
413 -
414 -[[image:image-20220527135828-12.png]]
415 -
416 416  MQTT Publish configure
417 417  
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]]
418 418  
419 -
420 -[[image:image-20220527135929-13.png]]
421 -
422 422  MQTT Channel settings
423 423  
424 -
425 -(((
426 426  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:
427 -)))
428 428  
429 -(% class="box" %)
430 -(((
431 -mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
432 -)))
355 +{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
356 +}}}
433 433  
434 -(((
435 435  to MQTT broker.
436 -)))
437 437  
438 438  
439 -(((
440 440  Below is a simulation to put this data to active the MQTT publish.
441 -)))
442 442  
443 -[[image:image-20220527140023-14.png]]
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]]
444 444  
445 445  MQTT Publish
446 446  
447 447  
368 +=== 4.4.2 Configure the MQTT Client for Downstream ===
448 448  
449 -=== 4.4.2  Configure the MQTT Client for Downstream ===
450 -
451 -
452 452  Below screen shot equal to this subscribe command:
453 453  
454 -(% class="box" %)
455 -(((
456 -mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
457 -)))
372 +{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
373 +}}}
458 458  
459 -[[image:image-20220527140100-15.png]]
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]]
460 460  
461 461  MQTT Subscribe
462 462  
463 463  
464 -(((
465 465  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:
466 -)))
467 467  
468 -[[image:image-20220527140148-16.png]]
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]]
469 469  
470 470  LoRa Broadcast parameters.
471 471  
... ... @@ -472,178 +472,141 @@
472 472  
473 473  And below is the subscribe simulation:
474 474  
475 -[[image:image-20220527140238-17.png]]
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]]
476 476  
477 477  downstream simulation
478 478  
479 479  
480 -== 4.5  Add LoRa support to communicate with remote sensor ==
481 481  
395 +== 4.5 Add LoRa support to communicate with remote sensor ==
482 482  
483 483  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.
484 484  
399 +=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
485 485  
486 -
487 -=== 4.5.1  Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
488 -
489 -
490 -(((
491 491  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.
492 -)))
493 493  
494 -(((
495 495  The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]
496 -)))
497 497  
498 -(((
499 499  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.
500 500  
501 -
502 -)))
503 -
504 -(((
505 505  What does the Arduino Sketch do? The Arduino Sketch will:
506 -)))
507 507  
508 508  * 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).
509 509  * Downstream: Listening broadcast message from gateway, and print it in console.
510 510  * The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
511 511  
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]]
512 512  
513 -
514 -[[image:image-20220527140354-18.png]]
515 -
516 516  LoRa Parameter should match
517 517  
518 518  
519 -
520 520  Below is the test result after the Arduino Sketch is running.
521 521  
522 -[[image:image-20220527140459-19.png]]
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]]
523 523  
524 524  Upstream Data Flow
525 525  
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]]
526 526  
527 -
528 -[[image:image-20220527140542-20.png]]
529 -
530 530  Downstream Data Flow
531 531  
532 532  
429 +=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
533 533  
534 -=== 4.5.2  Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
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.
535 535  
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.
536 536  
537 -(((
538 -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.
539 -)))
540 540  
541 -(((
542 -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.
543 543  
437 +Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
438 +
544 544  
545 -(% style="color:blue" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
546 -)))
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.
547 547  
548 -(((
549 -(% 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.
550 -)))
442 +Step 2: Make sure your Radio settings match the End Node settings.
551 551  
552 -(((
553 -(% style="color:blue" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
554 -)))
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]]
555 555  
556 -[[image:image-20220527141235-21.png]]
557 -
558 558  Use Same Frequency Band as End Node
559 559  
560 560  
561 -(((
562 -(((
563 -(% 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.
564 -)))
565 -)))
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
566 566  
567 -[[image:image-20220613191345-4.png]]
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]]
568 568  
453 +Publish mush use META as data format for LG308
569 569  
570 570  
571 -(% style="color:blue" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
456 +Step 4: Map the Device Address to Remote ID in MQTT server.
572 572  
573 -[[image:image-20220613190635-2.png]]
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]]
574 574  
460 +Map Dev Addr to remote ID
575 575  
576 576  
577 -(% style="color:blue" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
463 +Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
578 578  
579 -[[image:image-20220527141843-24.png]]
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]]
580 580  
467 +Upstream Process
581 581  
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]]
582 582  
583 -
584 -[[image:image-20220527141933-25.png]]
585 -
586 586  Choose ASCII Format
587 587  
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]]
588 588  
589 -
590 -[[image:image-20220527142028-26.png]]
591 -
592 592  LHT65 Decoder
593 593  
477 +Step 6: Set up subscribe: Subscribe a topci for downstream.
594 594  
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]]
595 595  
596 -(% style="color:blue" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
481 +Subscribe to a topic
597 597  
598 -[[image:image-20220613191426-5.png]]
599 599  
484 +Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
600 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]]
601 601  
602 -(% style="color:blue" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
488 +Downstream Flow
603 603  
604 -[[image:image-20220527142239-28.png]]
490 +Notice: The text use for Downstream must meet the requirement from [[LG308 Downstream Payload>>url:https://wiki.dragino.com/index.php/Communication_with_ABP_End_Node#Downstream]]
605 605  
606 606  
493 += 5. Example For Different MQTT Servers =
607 607  
608 -=== 4.5.3 MQTT Downstream format ===
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]]
609 609  
498 +=== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ===
610 610  
611 -mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
612 612  
613 -(% class="box infomessage" %)
614 -(((
615 -**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"**
616 -)))
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]]
617 617  
618 -mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
505 +=== [[乐联网平台>>url:https://www.lewei50.com/]] ===
619 619  
620 -(% class="box infomessage" %)
621 -(((
622 -**mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2"**
623 -)))
624 624  
625 -Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
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]]
626 626  
627 -[[image:image-20220613192816-6.png||height="440" width="1056"]]
512 +=== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ===
628 628  
629 629  
630 -(% 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"]]**
515 +[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
516 +)))
631 631  
518 += 6. How to Debug =
632 632  
633 -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]]
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.
634 634  
522 += 7. How to ask for Support =
635 635  
636 -
637 -= 5.  How to Debug =
638 -
639 -
640 -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.
641 -
642 -
643 -
644 -= 6.  How to ask for Support =
645 -
646 -
647 647  If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
648 648  
649 649  * Detail of your LoRaWAN end node.
image-20220527133547-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -199.3 KB
Content
image-20220527134000-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -115.8 KB
Content
image-20220527134038-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -94.2 KB
Content
image-20220527134251-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20220527134332-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.7 KB
Content
image-20220527134929-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -61.6 KB
Content
image-20220527135037-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.1 KB
Content
image-20220527135215-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -125.6 KB
Content
image-20220527135310-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -87.9 KB
Content
image-20220527135440-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 KB
Content
image-20220527135742-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -18.2 KB
Content
image-20220527135828-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20220527135929-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.0 KB
Content
image-20220527140023-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -182.2 KB
Content
image-20220527140100-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.2 KB
Content
image-20220527140148-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.0 KB
Content
image-20220527140238-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.3 KB
Content
image-20220527140354-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.7 KB
Content
image-20220527140459-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -151.0 KB
Content
image-20220527140542-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -165.4 KB
Content
image-20220527141235-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.3 KB
Content
image-20220527141450-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -46.5 KB
Content
image-20220527141727-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.6 KB
Content
image-20220527141843-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -164.3 KB
Content
image-20220527141933-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -100.1 KB
Content
image-20220527142028-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -95.2 KB
Content
image-20220527142115-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -9.3 KB
Content
image-20220527142239-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.1 KB
Content
image-20220527142638-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -62.3 KB
Content
image-20220527142706-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -43.1 KB
Content
image-20220527142733-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -10.3 KB
Content
image-20220527142820-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -155.6 KB
Content
image-20220613190254-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220613190635-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -44.1 KB
Content
image-20220613191154-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -56.1 KB
Content
image-20220613191345-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.4 KB
Content
image-20220613191426-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -55.8 KB
Content
image-20220613192816-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -22.1 KB
Content
image-20220714155901-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -75.2 KB
Content