Summary

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

Details

Page properties

Content

...	...	@@ -7,12 +7,13 @@
7	7
8	8	Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
9	9
	10	+
10	10	== 1.1 Support Devices ==
11	11
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]])
	16	+* LG01N, OLG01N ((% style="color:red" %)**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]])
16	16	* LG02, OLG02
17	17	* LG308, DLOS8
18	18	* LPS8
...	...	@@ -37,7 +37,7 @@
37	37	* 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.
38	38	* 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	39
40		-[[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png||height="348" width="600"]]
	41	+[[image:image-20220527133547-1.png]]
41	41
42	42	General MQTT structure
43	43
...	...	@@ -55,7 +55,7 @@
55	55	The data flow works as below diagram.
56	56	)))
57	57
58		-[[~[~[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]]
	59	+[[image:image-20220527134000-2.png]]
59	59
60	60	(((
61	61	Upstream path
...	...	@@ -77,7 +77,7 @@
77	77	Below are the data flow for downstream.
78	78	)))
79	79
80		-[[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png||height="368" width="600"]]
	81	+[[image:image-20220527134038-3.png]]
81	81
82	82	Downstream path
83	83
...	...	@@ -87,7 +87,9 @@
87	87	The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
88	88
89	89	(((
90		-Currently the (% class="mark" %)**-t (topic)**(%%) and (% class="mark" %)**-m (message)**(%%) support Macros.
	91	+Currently the (% style="color:#4f81bd" %)**-t (topic)**(%%) and (% style="color:#4f81bd" %)**-m (message)**(%%) support Macros.
	92	+
	93	+
91	91	)))
92	92
93	93	=== 3.3.1 -t topic macro ===
...	...	@@ -108,7 +108,7 @@
108	108
109	109	=== 3.3.3 Example for Macro ===
110	110
111		-[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png||height="385" width="600"]]
	114	+[[image:image-20220527134251-4.png]]
112	112
113	113	MQTT Publish configure
114	114
...	...	@@ -119,12 +119,12 @@
119	119
120	120	When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:
121	121
122		-[[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png||height="325" width="600"]]
	125	+[[image:image-20220527134332-5.png]]
123	123
124	124	Sensor Data
125	125
126	126	(((
127		-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.
	130	+According to above macro. Gateway will publish (% style="color:#4f81bd" %)**field1=22.0&field2=49.0**(%%) to topic: (% style="color:#4f81bd" %)**dragino-1b7060/78901/data**(%%), where 78901 is the remote channel for this node ID.
128	128	)))
129	129
130	130
...	...	@@ -183,7 +183,7 @@
183	183	~-~-help : display this message.
184	184	~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
185	185	~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.
186		-~-~-quiet : (% class="mark" %)don't print error messages.
	189	+~-~-quiet : (% style="color:red" %)don't print error messages.
187	187	~-~-will-payload : payload for the client Will, which is sent by the broker in case of
188	188	unexpected disconnection. If not given and will-topic is set, a zero
189	189	length message will be sent.
...	...	@@ -221,7 +221,7 @@
221	221
222	222	(% class="box" %)
223	223	(((
224		-# Call MQTT Publish command
	227	+//# Call MQTT Publish command
225	225	\\# 1. Case with User, Password and Client ID present  (e.g. Azure)
226	226	if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
227	227	case="1"
...	...	@@ -248,9 +248,9 @@
248	248	mosquitto_pub $D -h $server -p $port -q $pub_qos  -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
249	249	\\# 0. Else - invalid parameters, just log
250	250	else
251		-case="Invalid parameters"
252		-logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
253		-fi
	254	+case="(% style="color:red" %)Invalid parameters" (%%)
	255	+logger (% style="color:red" %)"[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."(%%)
	256	+fi//
254	254	)))
255	255
256	256
...	...	@@ -260,6 +260,7 @@
260	260
261	261	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/]].
262	262
	266	+
263	263	== 4.2 Simulate via MQTT.fx utility ==
264	264
265	265	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.
...	...	@@ -268,16 +268,18 @@
268	268	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.
269	269	)))
270	270
271		-[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png||height="201" width="600"]]
	275	+[[image:image-20220527134929-6.png]]
272	272
273	273	Connect to MQTT Broker
274	274
	279	+
275	275	After connected, use publish to public some thing to MQTT server. This to simulate upsteam
276	276
277		-[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png||height="149" width="600"]]
	282	+[[image:image-20220527135037-7.png]]
278	278
279	279	Upstream: Publish message to MQTT Broker
280	280
	286	+
281	281	To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
282	282
283	283	[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png||height="279" width="600"]]
...	...	@@ -477,8 +477,10 @@
477	477
478	478
479	479	(((
	486	+(((
480	480	**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
481	481	)))
	489	+)))
482	482
483	483	[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png||height="385" width="600"]]
484	484
...	...	@@ -485,7 +485,7 @@
485	485	Publish mush use META as data format for LG308
486	486
487	487
488		-Step 4: Map the Device Address to Remote ID in MQTT server.
	496	+**Step 4**: Map the Device Address to Remote ID in MQTT server.
489	489
490	490	[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png||height="335" width="600"]]
491	491
...	...	@@ -492,7 +492,7 @@
492	492	Map Dev Addr to remote ID
493	493
494	494
495		-Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
	503	+**Step 5: Upstream**: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
496	496
497	497	[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png||height="279" width="600"]]
498	498
...	...	@@ -506,20 +506,21 @@
506	506
507	507	LHT65 Decoder
508	508
509		-Step 6: Set up subscribe: Subscribe a topci for downstream.
510	510
	518	+**Step 6: Set up subscribe:** Subscribe a topci for downstream.
	519	+
511	511	[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png||height="176" width="600"]]
512	512
513	513	Subscribe to a topic
514	514
515	515
516		-Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
	525	+**Step 7**: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
517	517
518	518	[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png||height="298" width="600"]]
519	519
520	520	Downstream Flow
521	521
522		-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]]
	531	+(% class="mark" %)**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]]**
523	523
524	524
525	525	= 5. Example For Different MQTT Servers =
...	...	@@ -535,7 +535,6 @@
535	535	)))|=(% style="width: 242px;" %)(((
536	536	[[image:https://wiki.dragino.com/images/thumb/3/3b/Lewei50.png/200px-Lewei50.png||alt="Lewei50.png" height="65" width="223"]]
537	537
538		-== ==
539	539
540	540	== [[乐联网平台>>url:https://www.lewei50.com/]] ==
541	541

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