Changes for page MQTT Forward Instruction

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 38 added, 0 removed)
  • image-20220527133547-1.png
  • image-20220527134000-2.png
  • image-20220527134038-3.png
  • image-20220527134251-4.png
  • image-20220527134332-5.png
  • image-20220527134929-6.png
  • image-20220527135037-7.png
  • image-20220527135215-8.png
  • image-20220527135310-9.png
  • image-20220527135440-10.png
  • image-20220527135742-11.png
  • image-20220527135828-12.png
  • image-20220527135929-13.png
  • image-20220527140023-14.png
  • image-20220527140100-15.png
  • image-20220527140148-16.png
  • image-20220527140238-17.png
  • image-20220527140354-18.png
  • image-20220527140459-19.png
  • image-20220527140542-20.png
  • image-20220527141235-21.png
  • image-20220527141450-22.png
  • image-20220527141727-23.png
  • image-20220527141843-24.png
  • image-20220527141933-25.png
  • image-20220527142028-26.png
  • image-20220527142115-27.png
  • image-20220527142239-28.png
  • image-20220527142638-29.png
  • image-20220527142706-30.png
  • image-20220527142733-31.png
  • image-20220527142820-32.png
  • image-20220613190254-1.png
  • image-20220613190635-2.png
  • image-20220613191154-3.png
  • image-20220613191345-4.png
  • image-20220613191426-5.png
  • image-20220613192816-6.png

Details

Page properties

Content

...	...	@@ -1,18 +1,21 @@
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		-== 1.1 Support Devices ==
11	11
	12	+== 1.1  Support Devices ==
	13	+
	14	+
12	12	This MQTT forward instruction is for below devices:
13	13
14	14	* Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
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]])
	18	+* 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]])
16	16	* LG02, OLG02
17	17	* LG308, DLOS8
18	18	* LPS8
...	...	@@ -20,8 +20,10 @@
20	20	* MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
21	21
22	22
23		-= 2. Firmware Change Log for MQTT feature =
24	24
	27	+= 2.  Firmware Change Log for MQTT feature =
	28	+
	29	+
25	25	(((
26	26	This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
27	27	)))
...	...	@@ -30,26 +30,30 @@
30	30	** Initiate version
31	31
32	32
33		-= 3. MQTT forward operating principle =
34	34
35		-== 3.1 Network Structure ==
	39	+= 3.  MQTT forward operating principle =
36	36
	41	+
	42	+== 3.1  Network Structure ==
	43	+
	44	+
37	37	Below shows the network structure for MQTT forwarding.
38	38
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,
	47	+* **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.
	48	+* **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,
41	41
42		-[[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png||height="348" width="600"]]
	50	+[[image:image-20220527133547-1.png]]
43	43
44	44	General MQTT structure
45	45
46	46
47		-== 3.2 How sensor data is forwarded ==
	55	+== 3.2  How sensor data is forwarded ==
48	48
	57	+
49	49	In this MQTT forward feature, the key point is how the gateway process the sensor data.
50	50
51	51
52		-=== 3.2.1 Upstream ===
	61	+=== 3.2.1  Upstream ===
53	53
54	54	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.
55	55
...	...	@@ -57,14 +57,16 @@
57	57	The data flow works as below diagram.
58	58	)))
59	59
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]]
	69	+[[image:image-20220527134000-2.png]]
61	61
62	62	(((
63	63	Upstream path
	73	+
	74	+
64	64	)))
65	65
66	66	(((
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>
	78	+(% 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>**
68	68	)))
69	69
70	70	(((
...	...	@@ -71,8 +71,9 @@
71	71
72	72	)))
73	73
74		-=== 3.2.2 Downstream ===
	85	+=== 3.2.2  Downstream ===
75	75
	87	+
76	76	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.
77	77
78	78	(((
...	...	@@ -79,21 +79,25 @@
79	79	Below are the data flow for downstream.
80	80	)))
81	81
82		-[[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png||height="368" width="600"]]
	94	+[[image:image-20220527134038-3.png]]
83	83
84	84	Downstream path
85	85
86	86
87		-== 3.3 Macro Definition ==
	99	+== 3.3  Macro Definition ==
88	88
	101	+
89	89	The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
90	90
91	91	(((
92		-Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros.
	105	+Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros.
	106	+
	107	+
93	93	)))
94	94
95		-=== 3.3.1 -t topic macro ===
	110	+=== 3.3.1  -t topic macro ===
96	96
	112	+
97	97	* CHANNEL: Remote Channel ID
98	98	* CLIENTID: Client ID , Same as -i
99	99	* WRITE_API: Remote Channel Write API
...	...	@@ -100,8 +100,12 @@
100	100	* USERNAME: User ID (-u)
101	101	* HOSTNAME: Device Hostname
102	102
103		-=== 3.3.2 -m message macro ===
104	104
	120	+
	121	+
	122	+=== 3.3.2  -m message macro ===
	123	+
	124	+
105	105	* HOSTNAME: Device Hostname
106	106	* CHANNEL: Remote Channel ID
107	107	* DATA: Sensor Data without time stamp and rssi
...	...	@@ -108,30 +108,38 @@
108	108	* META: Completely sensor data with time stamp and rssi
109	109	* JSON: Convert META to json format.
110	110
111		-=== 3.3.3 Example for Macro ===
112	112
113		-[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
114	114
	133	+
	134	+=== 3.3.3  Example for Macro ===
	135	+
	136	+
	137	+[[image:image-20220527134251-4.png]]
	138	+
115	115	MQTT Publish configure
116	116
117		-Above screen shots shows below format:
118	118
	142	+**Above screen shots shows below format:**
	143	+
119	119	* -t: CLIENTID/CHANNEL/data
120	120	* -m: DATA
121	121
122	122	When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:
123	123
124		-[[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]]
	149	+[[image:image-20220527134332-5.png]]
125	125
126	126	Sensor Data
127	127
	153	+
128	128	(((
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.
	155	+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.
130	130	)))
131	131
132	132
133		-== 3.4 Modify the MQTT to support more options ==
134	134
	160	+== 3.4  Modify the MQTT to support more options ==
	161	+
	162	+
135	135	The MQTT Client Utility used in Dragino is **mosquitto_pub** and **mosquitto_sub**. User can add more options to the mqtt commands. User can check the valid options by command mosquitto_pub ~-~-help. as below:
136	136
137	137	(% class="box" %)
...	...	@@ -139,8 +139,7 @@
139	139	root@dragino-1ec39c:~~# mosquitto_pub ~-~-help
140	140	mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
141	141	mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
142		-
143		-Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
	170	+\\Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic | -L URL}
144	144	{-f file | -l | -n | -m message}
145	145	[-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]
146	146	[-A bind_address]
...	...	@@ -150,16 +150,15 @@
150	150	[-u username [-P password]]
151	151	[~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
152	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]]
	180	+ [~-~-ciphers ciphers] [~-~-insecure]
	181	+ [~-~-tls-alpn protocol]
	182	+ [~-~-tls-engine engine] [~-~-keyform keyform] [~-~-tls-engine-kpass-sha1]]
156	156	[~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
157	157	[~-~-proxy socks-url]
158	158	[~-~-property command identifier value]
159	159	[-D command identifier value]
160	160	mosquitto_pub ~-~-help
161		-
162		--A : bind the outgoing socket to this host/ip address. Use to control which interface
	188	+\\-A : bind the outgoing socket to this host/ip address. Use to control which interface
163	163	the client communicates over.
164	164	-d : enable debug messages.
165	165	-D : Define MQTT v5 properties. See the documentation for more details.
...	...	@@ -187,7 +187,7 @@
187	187	~-~-help : display this message.
188	188	~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
189	189	~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.
190		-~-~-quiet : (% class="mark" %)don't print error messages.
	216	+~-~-quiet : (% style="color:red" %)don't print error messages.
191	191	~-~-will-payload : payload for the client Will, which is sent by the broker in case of
192	192	unexpected disconnection. If not given and will-topic is set, a zero
193	193	length message will be sent.
...	...	@@ -215,8 +215,7 @@
215	215	~-~-proxy : SOCKS5 proxy URL of the form:
216	216	socks5h:~/~/[username[:password]@]hostname[:port]
217	217	Only "none" and "username" authentication is supported.
218		-
219		-See https:~/~/mosquitto.org/ for more information.
	244	+\\See https:~/~/mosquitto.org/ for more information.
220	220	)))
221	221
222	222
...	...	@@ -226,43 +226,36 @@
226	226
227	227	(% class="box" %)
228	228	(((
229		-# Call MQTT Publish command
230		-
231		-# 1. Case with User, Password and Client ID present  (e.g. Azure)
	254	+//# Call MQTT Publish command
	255	+\\# 1. Case with User, Password and Client ID present  (e.g. Azure)
232	232	if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
233	233	case="1"
234	234	mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user -P "$pass" $C $cafile $PUB_FLAG "$mqtt_data"
235		-
236		-# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
	259	+\\# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
237	237	elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
238	238	case="2"
239	239	mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic ~-~-cert $cert ~-~-key $key $C $cafile $PUB_FLAG "$mqtt_data"
240		-
241		-# 3. Case with no User, Certificate or ClientID present
	263	+\\# 3. Case with no User, Certificate or ClientID present
242	242	elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
243	243	case="3"
244	244	mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
245		-
246		-# 4. Case with no User, Certificate, but with ClientID present
	267	+\\# 4. Case with no User, Certificate, but with ClientID present
247	247	elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
248	248	case="4"
249	249	mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
250		-
251		-# 5. Case with User and ClientID present, but no Password and no Certificate present
	271	+\\# 5. Case with User and ClientID present, but no Password and no Certificate present
252	252	elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
253	253	case="5"
254	254	mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
255		-
256		-# 6. Case with User and Password present, but no ClientID and no Certificate present
	275	+\\# 6. Case with User and Password present, but no ClientID and no Certificate present
257	257	elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
258	258	case="6"
259	259	mosquitto_pub $D -h $server -p $port -q $pub_qos  -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
260		-
261		-# 0. Else - invalid parameters, just log
	279	+\\# 0. Else - invalid parameters, just log
262	262	else
263		-case="Invalid parameters"
264		-logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
265		-fi
	281	+case="(% style="color:red" %)Invalid parameters" (%%)
	282	+logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%)
	283	+fi//
266	266	)))
267	267
268	268
...	...	@@ -272,25 +272,30 @@
272	272
273	273	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/]].
274	274
	293	+
275	275	== 4.2 Simulate via MQTT.fx utility ==
276	276
277	277	The [[MQTT.fx>>url:http://mqttfx.jensd.de/index.php/download]] is a MQTT client tool. We can use this to simulate a MQTT connection to our MQTT broker first to make sure the MQTT broker works. This will also help us understand how it works.
278	278
	298	+(((
279	279	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.
	300	+)))
280	280
281		-[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]
	302	+[[image:image-20220527134929-6.png]]
282	282
283	283	Connect to MQTT Broker
284	284
	306	+
285	285	After connected, use publish to public some thing to MQTT server. This to simulate upsteam
286	286
287		-[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]
	309	+[[image:image-20220527135037-7.png]]
288	288
289	289	Upstream: Publish message to MQTT Broker
290	290
	313	+
291	291	To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
292	292
293		-[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]
	316	+[[image:image-20220527135215-8.png]]
294	294
295	295	Downstream: Subscribe a topic to get downstream
296	296
...	...	@@ -302,7 +302,7 @@
302	302	In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
303	303
304	304
305		-For Upstream
	328	+(% style="color:#4f81bd" %)**For Upstream**
306	306
307	307	command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
308	308
...	...	@@ -310,16 +310,16 @@
310	310
311	311	Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
312	312
313		-[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png||height="188" width="600"]]
	336	+[[image:image-20220527135310-9.png]]
314	314
315	315	mosquitto_pub
316	316
317	317
318		-For Downstream
	341	+(% style="color:#4f81bd" %)**For Downstream**
319	319
320	320	Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
321	321
322		-[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png||height="267" width="600"]]
	345	+[[image:image-20220527135440-10.png]]
323	323
324	324	mosquitto_sub
325	325
...	...	@@ -328,16 +328,21 @@
328	328
329	329	This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
330	330
331		-Go to Dragino Menu ~-~-> MQTT Client
	354	+(((
	355	+Go to (% style="color:#4f81bd" %)**Dragino Menu ~-~-> MQTT Client**
	356	+)))
332	332
333	333	[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png||height="249" width="600"]]
334	334
335	335	go to mqtt configure menu
336	336
337		-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.
338	338
339		-[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png||height="240" width="600"]]
	363	+(((
	364	+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.
	365	+)))
340	340
	367	+[[image:image-20220527135742-11.png]]
	368	+
341	341	forward to MQTT
342	342
343	343
...	...	@@ -345,32 +345,44 @@
345	345
346	346	Below screenshot is same as the publish command:
347	347
348		-{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
349		-//where the CLIENTID, CHANNEL & DATA are macro. represent for
350		-//CLIENTID: dragino-1b7060
351		-//CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
352		-//DATA: The data stores in /var/iot/channels/
353		-}}}
	376	+(% class="box" %)
	377	+(((
	378	+mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
	379	+~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
	380	+~/~/CLIENTID: dragino-1b7060
	381	+~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
	382	+~/~/DATA: The data stores in /var/iot/channels/
	383	+)))
354	354
355		-[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
	385	+[[image:image-20220527135828-12.png]]
356	356
357	357	MQTT Publish configure
358	358
359		-[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png||height="544" width="600"]]
360	360
	390	+[[image:image-20220527135929-13.png]]
	391	+
361	361	MQTT Channel settings
362	362
	394	+
	395	+(((
363	363	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:
	397	+)))
364	364
365		-{{{mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
366		-}}}
	399	+(% class="box" %)
	400	+(((
	401	+mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
	402	+)))
367	367
	404	+(((
368	368	to MQTT broker.
	406	+)))
369	369
370	370
	409	+(((
371	371	Below is a simulation to put this data to active the MQTT publish.
	411	+)))
372	372
373		-[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png||height="308" width="600"]]
	413	+[[image:image-20220527140023-14.png]]
374	374
375	375	MQTT Publish
376	376
...	...	@@ -379,17 +379,21 @@
379	379
380	380	Below screen shot equal to this subscribe command:
381	381
382		-{{{ mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
383		-}}}
	422	+(% class="box" %)
	423	+(((
	424	+mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
	425	+)))
384	384
385		-[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png||height="173" width="579"]]
	427	+[[image:image-20220527140100-15.png]]
386	386
387	387	MQTT Subscribe
388	388
389	389
	432	+(((
390	390	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:
	434	+)))
391	391
392		-[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png||height="300" width="600"]]
	436	+[[image:image-20220527140148-16.png]]
393	393
394	394	LoRa Broadcast parameters.
395	395
...	...	@@ -396,7 +396,7 @@
396	396
397	397	And below is the subscribe simulation:
398	398
399		-[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png||height="255" width="600"]]
	443	+[[image:image-20220527140238-17.png]]
400	400
401	401	downstream simulation
402	402
...	...	@@ -405,134 +405,150 @@
405	405
406	406	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.
407	407
	452	+
408	408	=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
409	409
	455	+(((
410	410	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.
	457	+)))
411	411
	459	+(((
412	412	The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]
	461	+)))
413	413
	463	+(((
414	414	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.
	465	+)))
415	415
	467	+(((
416	416	What does the Arduino Sketch do? The Arduino Sketch will:
	469	+)))
417	417
418	418	* 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).
419	419	* Downstream: Listening broadcast message from gateway, and print it in console.
420	420	* The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
421	421
422		-[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png||height="197" width="600"]]
	475	+[[image:image-20220527140354-18.png]]
423	423
424	424	LoRa Parameter should match
425	425
426	426
	480	+
427	427	Below is the test result after the Arduino Sketch is running.
428	428
429		-[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png||height="319" width="600"]]
	483	+[[image:image-20220527140459-19.png]]
430	430
431	431	Upstream Data Flow
432	432
433		-[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png||height="309" width="600"]]
434	434
	488	+
	489	+[[image:image-20220527140542-20.png]]
	490	+
435	435	Downstream Data Flow
436	436
437	437
438	438	=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
439	439
440		-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.
	496	+(((
	497	+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.
	498	+)))
441	441
442		-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.
	500	+(((
	501	+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.
	502	+(% style="color:#4f81bd" %)**Video Instruction**(%%): (% style="color:blue" %)[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
	503	+)))
443	443
	505	+(((
	506	+(% 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.
	507	+)))
444	444
	509	+(((
	510	+(% style="color:#4f81bd" %)**Step 2**(%%): Make sure your Radio settings match the End Node settings.
	511	+)))
445	445
446		-Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
447		-
	513	+[[image:image-20220527141235-21.png]]
448	448
449		-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.
	515	+Use Same Frequency Band as End Node
450	450
451		-Step 2: Make sure your Radio settings match the End Node settings.
452	452
453		-[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png||height="387" width="600"]]
	518	+(((
	519	+(((
	520	+(% 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.
	521	+)))
	522	+)))
454	454
455		-Use Same Frequency Band as End Node
	524	+[[image:image-20220613191345-4.png]]
456	456
457	457
458		-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
459	459
460		-[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]]
	528	+(% style="color:#4f81bd" %)**Step 4**(%%): Map the Device Address to Remote ID in MQTT server.
461	461
462		-Publish mush use META as data format for LG308
	530	+[[image:image-20220613190635-2.png]]
463	463
464	464
465		-Step 4: Map the Device Address to Remote ID in MQTT server.
466	466
467		-[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]]
	534	+(% style="color:#4f81bd" %)**Step 5: Upstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server
468	468
469		-Map Dev Addr to remote ID
	536	+[[image:image-20220527141843-24.png]]
470	470
471	471
472		-Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
473	473
474		-[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]
475	475
476		-Upstream Process
	541	+[[image:image-20220527141933-25.png]]
477	477
478		-[[image:https://wiki.dragino.com/images/thumb/0/07/LG308_MQTT_6_1.png/600px-LG308_MQTT_6_1.png||height="246" width="600"]]
479		-
480	480	Choose ASCII Format
481	481
482		-[[image:https://wiki.dragino.com/images/thumb/a/a3/LG308_MQTT_6_2.png/600px-LG308_MQTT_6_2.png||height="248" width="600"]]
483	483
	546	+
	547	+[[image:image-20220527142028-26.png]]
	548	+
484	484	LHT65 Decoder
485	485
486		-Step 6: Set up subscribe: Subscribe a topci for downstream.
487	487
488		-[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]
489	489
490		-Subscribe to a topic
	553	+(% style="color:#4f81bd" %)**Step 6: Set up subscribe**(%%)**:** Subscribe a topci for downstream.
491	491
	555	+[[image:image-20220613191426-5.png]]
492	492
493		-Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
494	494
495		-[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]]
496	496
497		-Downstream Flow
	559	+(% style="color:#4f81bd" %)**Step 7: Downstream**(%%): Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
498	498
499		-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]]
	561	+[[image:image-20220527142239-28.png]]
500	500
501	501
502		-= 5. Example For Different MQTT Servers =
503	503
504		-(% style="width:731.222px" %)
505		-|=(% style="width: 270px;" %)(((
506		-[[image:https://wiki.dragino.com/images/thumb/7/73/ThingSpeak1.png/200px-ThingSpeak1.png||alt="ThingSpeak1.png" height="114" width="233"]]
	565	+=== MQTT Downstream format ===
507	507
508		-== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==
509	509
	568	+mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload**"
510	510
511		-[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]
512		-)))|=(% style="width: 242px;" %)(((
513		-[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]]
	570	+(% class="box infomessage" %)
	571	+(((
	572	+mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello"
	573	+)))
514	514
515		-(% class="wikigeneratedid" %)
516		-== ==
	575	+mosquitto_pub -h $server_address -p $server_port -t $Client_ID -m "**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**"
517	517
518		-== [[乐联网平台>>url:https://www.lewei50.com/]] ==
	577	+(% class="box infomessage" %)
	578	+(((
	579	+mosquitto_pub -h 10.130.2.192 -p 1883 -t dragino-1d25dc/ -m "260211D,time,txt,hello,20,1,SF12,923300000,2 > /var/iot/push/test"
	580	+)))
519	519
	582	+Or use [[MQTT.fx>>https://mqttfx.jensd.de/index.php/download]]
520	520
521		-[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
522		-)))|=(% style="width: 214px;" %)(((
523		-[[image:https://wiki.dragino.com/images/thumb/a/aa/AWS-IOT.png/200px-AWS-IOT.png||alt="AWS-IOT.png" height="112" width="183"]]
	584	+[[image:image-20220613192816-6.png||height="440" width="1056"]]
524	524
525		-== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==
	586	+(% 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"]]**
526	526
	588	+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]]
527	527
528		-[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
529		-)))
	590	+= 5. How to Debug =
530	530
531		-= 6. How to Debug =
	592	+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.
532	532
533		-User can login the gateway's console and run (% class="mark" %)**logread -f**(%%). It will shows the output when there is packet arrive.User can see if it is correct.
534	534
535		-= 7. How to ask for Support =
	595	+= 6. How to ask for Support =
536	536
537	537	If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
538	538

image-20220527133547-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+199.3 KB

Content

image-20220527134000-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+115.8 KB

Content

image-20220527134038-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+94.2 KB

Content

image-20220527134251-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+35.1 KB

Content

image-20220527134332-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+34.7 KB

Content

image-20220527134929-6.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+61.6 KB

Content

image-20220527135037-7.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+65.1 KB

Content

image-20220527135215-8.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+125.6 KB

Content

image-20220527135310-9.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+87.9 KB

Content

image-20220527135440-10.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+111.5 KB

Content

image-20220527135742-11.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+18.2 KB

Content

image-20220527135828-12.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+35.1 KB

Content

image-20220527135929-13.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+31.0 KB

Content

image-20220527140023-14.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+182.2 KB

Content

image-20220527140100-15.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+8.2 KB

Content

image-20220527140148-16.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+34.0 KB

Content

image-20220527140238-17.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+126.3 KB

Content

image-20220527140354-18.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+62.7 KB

Content

image-20220527140459-19.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+151.0 KB

Content

image-20220527140542-20.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+165.4 KB

Content

image-20220527141235-21.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+83.3 KB

Content

image-20220527141450-22.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+46.5 KB

Content

image-20220527141727-23.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+23.6 KB

Content

image-20220527141843-24.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+164.3 KB

Content

image-20220527141933-25.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+100.1 KB

Content

image-20220527142028-26.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+95.2 KB

Content

image-20220527142115-27.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+9.3 KB

Content

image-20220527142239-28.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+181.1 KB

Content

image-20220527142638-29.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+62.3 KB

Content

image-20220527142706-30.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+43.1 KB

Content

image-20220527142733-31.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+10.3 KB

Content

image-20220527142820-32.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+155.6 KB

Content

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