Changes for page MQTT Forward Instruction

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 39 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
  • image-20220714155901-1.png

Details

Page properties

Content

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