Wiki source code of MQTT Forward Instruction

Version 1.20 by Xiaoling on 2022/05/12 16:26

version	line-number	content
1.5	1	~ Contents：
1.2	2
1.4	3	{{toc/}}
1.3	4
1.4	5
1.3	6	= 1. Introduction =
	7
1.2	8	Dragino LoRa/LoRaWAN gateway support MQTT forwarding. It can forward the sensor data from LoRa network to MQTT server , and vice verse.
	9
1.3	10	== 1.1 Support Devices ==
1.2	11
	12	This MQTT forward instruction is for below devices:
	13
	14	* Firmware Version > LG02_LG08-5.3.1580178039 [[Firmware Download>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
1.6	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]])
1.2	16	* LG02, OLG02
	17	* LG308, DLOS8
	18	* LPS8
	19	* LIG16
	20	* MS14 series if installed with the same firmware. (in this case, the MQTT forward will work , but no LoRa support)
	21
	22
1.3	23	= 2. Firmware Change Log for MQTT feature =
1.2	24
1.6	25	(((
1.2	26	This instruction is wrote start from LG02_LG08-5.3.1580178039. Below is related change log since this version of firmware.
1.6	27	)))
1.2	28
	29	* LG02_LG08-5.3.1580178039
	30	** Initiate version
	31
	32
1.3	33	= 3. MQTT forward operating principle =
1.2	34
1.3	35	== 3.1 Network Structure ==
1.2	36
	37	Below shows the network structure for MQTT forwarding.
	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,
	41
1.6	42	[[image:https://wiki.dragino.com/images/thumb/4/45/MQTT_Forward_1.png/600px-MQTT_Forward_1.png\|\|height="348" width="600"]]
1.2	43
	44	General MQTT structure
	45
1.6	46
1.3	47	== 3.2 How sensor data is forwarded ==
1.2	48
	49	In this MQTT forward feature, the key point is how the gateway process the sensor data.
	50
1.6	51
1.3	52	=== 3.2.1 Upstream ===
1.2	53
	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
1.6	56	(((
1.2	57	The data flow works as below diagram.
1.6	58	)))
1.2	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]]
	61
1.6	62	(((
1.2	63	Upstream path
1.6	64	)))
1.2	65
1.6	66	(((
1.2	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>
1.6	68	)))
1.2	69
1.6	70	(((
	71
	72	)))
	73
1.3	74	=== 3.2.2 Downstream ===
1.2	75
	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
1.6	78	(((
1.2	79	Below are the data flow for downstream.
1.6	80	)))
1.2	81
1.6	82	[[image:https://wiki.dragino.com/images/thumb/3/3a/MQTT_Forward_3.png/600px-MQTT_Forward_3.png\|\|height="368" width="600"]]
1.2	83
	84	Downstream path
	85
	86
1.3	87	== 3.3 Macro Definition ==
1.2	88
	89	The MQTT publish command use Macro settings to generate flexible upstream payload for MQTT publish.
	90
1.8	91	(((
1.7	92	Currently the (% class="mark" %)-t (topic)(%%) and (% class="mark" %)-m (message)(%%) support Macros.
1.8	93	)))
1.2	94
1.3	95	=== 3.3.1 -t topic macro ===
1.2	96
	97	* CHANNEL: Remote Channel ID
	98	* CLIENTID: Client ID , Same as -i
	99	* WRITE_API: Remote Channel Write API
	100	* USERNAME: User ID (-u)
	101	* HOSTNAME: Device Hostname
	102
1.3	103	=== 3.3.2 -m message macro ===
1.2	104
	105	* HOSTNAME: Device Hostname
	106	* CHANNEL: Remote Channel ID
	107	* DATA: Sensor Data without time stamp and rssi
	108	* META: Completely sensor data with time stamp and rssi
	109	* JSON: Convert META to json format.
	110
1.3	111	=== 3.3.3 Example for Macro ===
1.2	112
1.8	113	[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png\|\|height="385" width="600"]]
1.2	114
	115	MQTT Publish configure
	116
	117	Above screen shots shows below format:
	118
	119	* -t: CLIENTID/CHANNEL/data
	120	* -m: DATA
	121
	122	When there is a LoRa sensor arrive. it will be store at the /var/iot/channels as below:
	123
1.8	124	[[image:https://wiki.dragino.com/images/thumb/c/c4/MQTT_Command_20.png/600px-MQTT_Command_20.png\|\|height="325" width="600"]]
1.2	125
	126	Sensor Data
	127
1.8	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.
	130	)))
1.2	131
	132
1.3	133	== 3.4 Modify the MQTT to support more options ==
1.2	134
	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
1.9	137	(% class="box" %)
	138	(((
	139	root@dragino-1ec39c:~~# mosquitto_pub ~-~-help
1.2	140	mosquitto_pub is a simple mqtt client that will publish a message on a single topic and exit.
	141	mosquitto_pub version 1.6.4 running on libmosquitto 1.6.4.
1.9	142
1.2	143	Usage: mosquitto_pub {[-h host] [-p port] [-u username] [-P password] -t topic \| -L URL}
	144	{-f file \| -l \| -n \| -m message}
1.9	145	[-c] [-k keepalive] [-q qos] [-r] [~-~-repeat N] [~-~-repeat-delay time]
1.2	146	[-A bind_address]
	147	[-i id] [-I id_prefix]
1.9	148	[-d] [~-~-quiet]
1.2	149	[-M max_inflight]
	150	[-u username [-P password]]
1.9	151	[~-~-will-topic [~-~-will-payload payload] [~-~-will-qos qos] [~-~-will-retain]]
	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]]
	156	[~-~-psk hex-key ~-~-psk-identity identity [~-~-ciphers ciphers]]
	157	[~-~-proxy socks-url]
	158	[~-~-property command identifier value]
1.2	159	[-D command identifier value]
1.9	160	mosquitto_pub ~-~-help
	161
	162	-A : bind the outgoing socket to this host/ip address. Use to control which interface
1.2	163	the client communicates over.
1.9	164	-d : enable debug messages.
	165	-D : Define MQTT v5 properties. See the documentation for more details.
	166	-f : send the contents of a file as the message.
	167	-h : mqtt host to connect to. Defaults to localhost.
	168	-i : id to use for this client. Defaults to mosquitto_pub_ appended with the process id.
	169	-I : define the client id as id_prefix appended with the process id. Useful for when the
1.2	170	broker is using the clientid_prefixes option.
1.9	171	-k : keep alive in seconds for this client. Defaults to 60.
	172	-L : specify user, password, hostname, port and topic as a URL in the form:
	173	mqtt(s):~/~/[username[:password]@]host[:port]/topic
	174	-l : read messages from stdin, sending a separate message for each line.
	175	-m : message payload to send.
	176	-M : the maximum inflight messages for QoS 1/2..
	177	-n : send a null (zero length) message.
	178	-p : network port to connect to. Defaults to 1883 for plain MQTT and 8883 for MQTT over TLS.
	179	-P : provide a password
	180	-q : quality of service level to use for all messages. Defaults to 0.
	181	-r : message should be retained.
	182	-s : read message from stdin, sending the entire input as a message.
	183	-t : mqtt topic to publish to.
	184	-u : provide a username
	185	-V : specify the version of the MQTT protocol to use when connecting.
1.2	186	Can be mqttv5, mqttv311 or mqttv31. Defaults to mqttv311.
1.9	187	~-~-help : display this message.
	188	~-~-repeat : if publish mode is -f, -m, or -s, then repeat the publish N times.
	189	~-~-repeat-delay : if using ~-~-repeat, wait time seconds between publishes. Defaults to 0.
	190	~-~-quiet : (% class="mark" %)don't print error messages.
	191	~-~-will-payload : payload for the client Will, which is sent by the broker in case of
1.2	192	unexpected disconnection. If not given and will-topic is set, a zero
	193	length message will be sent.
1.9	194	~-~-will-qos : QoS level for the client Will.
	195	~-~-will-retain : if given, make the client Will retained.
	196	~-~-will-topic : the topic on which to publish the client Will.
	197	~-~-cafile : path to a file containing trusted CA certificates to enable encrypted
1.2	198	communication.
1.9	199	~-~-capath : path to a directory containing trusted CA certificates to enable encrypted
1.2	200	communication.
1.9	201	~-~-cert : client certificate for authentication, if required by server.
	202	~-~-key : client private key for authentication, if required by server.
	203	~-~-keyform : keyfile type, can be either "pem" or "engine".
	204	~-~-ciphers : openssl compatible list of TLS ciphers to support.
	205	~-~-tls-version : TLS protocol version, can be one of tlsv1.3 tlsv1.2 or tlsv1.1.
1.2	206	Defaults to tlsv1.2 if available.
1.9	207	~-~-insecure : do not check that the server certificate hostname matches the remote
1.2	208	hostname. Using this option means that you cannot be sure that the
	209	remote host is the server you wish to connect to and so is insecure.
	210	Do not use this option in a production environment.
1.9	211	~-~-tls-engine : If set, enables the use of a TLS engine device.
	212	~-~-tls-engine-kpass-sha1 : SHA1 of the key password to be used with the selected SSL engine.
	213	~-~-psk : pre-shared-key in hexadecimal (no leading 0x) to enable TLS-PSK mode.
	214	~-~-psk-identity : client identity string for TLS-PSK mode.
	215	~-~-proxy : SOCKS5 proxy URL of the form:
	216	socks5h:~/~/[username[:password]@]hostname[:port]
1.2	217	Only "none" and "username" authentication is supported.
1.9	218
	219	See https:~/~/mosquitto.org/ for more information.
	220	)))
1.2	221
	222
1.13	223	(((
1.2	224	and modify the /usr/bin/mqtt_process.sh script, the location to change the command option is below lines:
1.13	225	)))
1.2	226
1.9	227	(% class="box" %)
	228	(((
	229	# Call MQTT Publish command
	230
	231	# 1. Case with User, Password and Client ID present (e.g. Azure)
1.2	232	if [ ! -z "$pass" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
1.9	233	case="1"
	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
1.2	236	# 2. Case with Certificate, Key and ClientID present (e.g. AWS)
	237	elif [ ! -z "$certfile" ] && [ ! -z "$key" ] && [ ! -z "$clientID" ]; then
1.9	238	case="2"
	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
1.2	241	# 3. Case with no User, Certificate or ClientID present
	242	elif [ -z "$user" ] && [ -z "$certfile" ] && [ -z "$clientID" ]; then
1.9	243	case="3"
	244	mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic $PUB_FLAG "$mqtt_data"
	245
1.2	246	# 4. Case with no User, Certificate, but with ClientID present
	247	elif [ -z "$user" ] && [ -z "$certfile" ] && [ ! -z "$clientID" ]; then
1.9	248	case="4"
	249	mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic $PUB_FLAG "$mqtt_data"
	250
1.2	251	# 5. Case with User and ClientID present, but no Password and no Certificate present
	252	elif [ -z "$pass" ] && [ -z "$certfile" ] && [ ! -z "$user" ] && [ ! -z "$clientID" ]; then
1.9	253	case="5"
	254	mosquitto_pub $D -h $server -p $port -q $pub_qos -i $clientID -t $pub_topic -u $user $PUB_FLAG "$mqtt_data"
	255
1.2	256	# 6. Case with User and Password present, but no ClientID and no Certificate present
	257	elif [ ! -z "$user" ] && [ ! -z "$pass" ] && [ -z "$clientID" ] && [ -z "$certfile" ]; then
1.9	258	case="6"
	259	mosquitto_pub $D -h $server -p $port -q $pub_qos -t $pub_topic -u $user -P "$pass" $PUB_FLAG "$mqtt_data"
	260
1.2	261	# 0. Else - invalid parameters, just log
	262	else
1.9	263	case="Invalid parameters"
	264	logger "[IoT.MQTT]:Invalid Parameters - mosquitto_pub not called."
	265	fi
	266	)))
1.2	267
	268
1.3	269	= 4. Example to communicate to a simple MQTT server =
1.2	270
1.3	271	== 4.1 Overview ==
1.2	272
	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
1.3	275	== 4.2 Simulate via MQTT.fx utility ==
1.2	276
	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
1.14	279	(((
1.2	280	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.
1.14	281	)))
1.2	282
1.10	283	[[image:https://wiki.dragino.com/images/thumb/0/06/MQTT_Forward_4.png/600px-MQTT_Forward_4.png\|\|height="201" width="600"]]
1.2	284
	285	Connect to MQTT Broker
	286
	287	After connected, use publish to public some thing to MQTT server. This to simulate upsteam
	288
1.10	289	[[image:https://wiki.dragino.com/images/thumb/b/bd/MQTT_Forward_5.png/600px-MQTT_Forward_5.png\|\|height="149" width="600"]]
1.2	290
	291	Upstream: Publish message to MQTT Broker
	292
	293	To simulate a downstream, use MQTT.fx to subscribe a topic, and publish something to this topic. as Below:
	294
1.10	295	[[image:https://wiki.dragino.com/images/thumb/3/3d/MQTT_Forward_6.png/600px-MQTT_Forward_6.png\|\|height="279" width="600"]]
1.2	296
	297	Downstream: Subscribe a topic to get downstream
	298
	299
1.3	300	== 4.3 Simulate via Dragino Command Line ==
1.2	301
	302	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.
	303
	304	In the Dragino Gateway, we use [[mosquitto client>>url:https://mosquitto.org/]] for MQTT connection.
	305
	306
1.14	307	(% class="mark" %)For Upstream
1.2	308
	309	command is [[mosquitto_pub>>url:https://mosquitto.org/man/mosquitto_pub-1.html]]
	310
	311	Example: mosquitto_pub -h 192.168.199.148 -p 1883 -t /channel/6543 -m temp=36
	312
	313	Note: 192.168.199.148 is MQTT broker address, the gateway and the MQTT broker PC are in the same network.
	314
1.10	315	[[image:https://wiki.dragino.com/images/thumb/d/d0/MQTT_Command_6.png/600px-MQTT_Command_6.png\|\|height="188" width="600"]]
1.2	316
	317	mosquitto_pub
	318
	319
1.15	320	(% class="mark" %)For Downstream
1.2	321
	322	Use [[mosquitto_sub>>url:https://mosquitto.org/man/mosquitto_sub-1.html]] to subscribe the change on the topic.
	323
1.10	324	[[image:https://wiki.dragino.com/images/thumb/8/89/MQTT_Command_7.png/600px-MQTT_Command_7.png\|\|height="267" width="600"]]
1.2	325
	326	mosquitto_sub
	327
1.10	328
1.3	329	== 4.4 Configure Dragino UI for MQTT connection ==
1.2	330
	331	This chapter are step by step to show to configure the Dragino Menu for MQTT auto connection.
	332
1.16	333	(((
	334	Go to (% class="mark" %)Dragino Menu ~-~-> MQTT Client
	335	)))
1.2	336
1.10	337	[[image:https://wiki.dragino.com/images/thumb/b/bc/MQTT_Command_8.png/600px-MQTT_Command_8.png\|\|height="249" width="600"]]
1.2	338
	339	go to mqtt configure menu
	340
1.17	341	(((
	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.
	343	)))
1.2	344
1.10	345	[[image:https://wiki.dragino.com/images/thumb/1/14/MQTT_Commands_8.png/600px-MQTT_Commands_8.png\|\|height="240" width="600"]]
1.2	346
	347	forward to MQTT
	348
1.10	349
1.3	350	=== 4.4.1 Configure the MQTT Client for Upstream ===
1.2	351
	352	Below screenshot is same as the publish command:
	353
1.17	354	(% class="box" %)
	355	(((
	356	mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t CLIENTID/CHANNEL/data -m DATA
	357	~/~/where the CLIENTID, CHANNEL & DATA are macro. represent for
	358	~/~/CLIENTID: dragino-1b7060
	359	~/~/CHANNEL: Remote ID in Channel settings; here is 78901 or 567456
	360	~/~/DATA: The data stores in /var/iot/channels/
	361	)))
1.2	362
1.10	363	[[image:https://wiki.dragino.com/images/thumb/c/c7/MQTT_Command_9.png/600px-MQTT_Command_9.png\|\|height="385" width="600"]]
1.2	364
	365	MQTT Publish configure
	366
1.18	367
1.10	368	[[image:https://wiki.dragino.com/images/thumb/b/b7/MQTT_Command_10.png/600px-MQTT_Command_10.png\|\|height="544" width="600"]]
1.2	369
	370	MQTT Channel settings
	371
1.18	372	(((
1.2	373	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:
1.18	374	)))
1.2	375
1.18	376	(% class="box" %)
	377	(((
	378	mosquitto_pub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t dragino-1b7060/78901/data -m temp=46
	379	)))
1.2	380
1.18	381	(((
1.2	382	to MQTT broker.
1.18	383	)))
1.2	384
	385
	386	(((
	387	Below is a simulation to put this data to active the MQTT publish.
	388	)))
	389
1.10	390	[[image:https://wiki.dragino.com/images/thumb/3/30/MQTT_Command_11.png/600px-MQTT_Command_11.png\|\|height="308" width="600"]]
1.2	391
	392	MQTT Publish
	393
	394
1.3	395	=== 4.4.2 Configure the MQTT Client for Downstream ===
1.2	396
	397	Below screen shot equal to this subscribe command:
	398
1.19	399	(% class="box" %)
	400	(((
	401	mosquitto_sub -h 192.168.199.148 -p 1883 -i dragino-1b7060 -t command.
	402	)))
1.2	403
1.10	404	[[image:https://wiki.dragino.com/images/3/36/MQTT_Command_12.png\|\|height="173" width="579"]]
1.2	405
	406	MQTT Subscribe
	407
	408
1.19	409	(((
1.2	410	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:
1.19	411	)))
1.2	412
1.10	413	[[image:https://wiki.dragino.com/images/thumb/b/b8/MQTT_Command_13.png/600px-MQTT_Command_13.png\|\|height="300" width="600"]]
1.2	414
	415	LoRa Broadcast parameters.
	416
	417
	418	And below is the subscribe simulation:
	419
1.10	420	[[image:https://wiki.dragino.com/images/thumb/6/60/MQTT_Command_14.png/600px-MQTT_Command_14.png\|\|height="255" width="600"]]
1.2	421
	422	downstream simulation
	423
	424
1.3	425	== 4.5 Add LoRa support to communicate with remote sensor ==
1.2	426
	427	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.
	428
1.3	429	=== 4.5.1 Use LoRa Raw protocol for communication ~-~- For LG01/LG02 ===
1.2	430
	431	(((
	432	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.
	433	)))
	434
	435	(((
	436	The example Sketch for LoRa Shield +Arduino is here: [[LoRa_Shield_Sketch_For_MQTT>>url:http://www.dragino.com/downloads/index.php?dir=LoraShield/]]
	437	)))
	438
	439	(((
	440	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.
	441	)))
	442
	443	(((
	444	What does the Arduino Sketch do? The Arduino Sketch will:
	445	)))
	446
	447	* 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).
	448	* Downstream: Listening broadcast message from gateway, and print it in console.
	449	* The LoRa parameter settings in Arduino should match the LoRa settings in gateway, as below:
	450
1.10	451	[[image:https://wiki.dragino.com/images/thumb/3/3b/MQTT_Command_17.png/600px-MQTT_Command_17.png\|\|height="197" width="600"]]
1.2	452
	453	LoRa Parameter should match
	454
	455
	456	Below is the test result after the Arduino Sketch is running.
	457
1.10	458	[[image:https://wiki.dragino.com/images/thumb/6/63/MQTT_Command_18.png/600px-MQTT_Command_18.png\|\|height="319" width="600"]]
1.2	459
	460	Upstream Data Flow
	461
1.10	462	[[image:https://wiki.dragino.com/images/thumb/1/18/MQTT_Command_19.png/600px-MQTT_Command_19.png\|\|height="309" width="600"]]
1.2	463
	464	Downstream Data Flow
	465
	466
1.3	467	=== 4.5.2 Use LoRaWAN Protocol for communication ~-~- For LG308/LPS8/DLOS8 ===
1.2	468
	469	(((
	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.
	471	)))
	472
	473	(((
	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.
1.6	475	Video Instruction:[[https:~~/~~/youtu.be/qJTY441-t90>>url:https://youtu.be/qJTY441-t90]]
1.20	476	)))
	477
	478	(((
	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.
	480	)))
	481
	482	(((
	483	Step 2: Make sure your Radio settings match the End Node settings.
	484	)))
	485
1.10	486	[[image:https://wiki.dragino.com/images/thumb/f/f7/LG308_MQTT_5.png/600px-LG308_MQTT_5.png\|\|height="387" width="600"]]
1.2	487
	488	Use Same Frequency Band as End Node
	489
	490
	491	(((
	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
	493	)))
	494
1.10	495	[[image:https://wiki.dragino.com/images/thumb/8/8d/LG308_MQTT_3.png/600px-LG308_MQTT_3.png\|\|height="385" width="600"]]
1.2	496
	497	Publish mush use META as data format for LG308
	498
	499
	500	Step 4: Map the Device Address to Remote ID in MQTT server.
	501
1.10	502	[[image:https://wiki.dragino.com/images/thumb/7/7f/LG308_MQTT_4.png/600px-LG308_MQTT_4.png\|\|height="335" width="600"]]
1.2	503
	504	Map Dev Addr to remote ID
	505
	506
	507	Step 5: Upstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server
	508
1.10	509	[[image:https://wiki.dragino.com/images/thumb/b/be/LG308_MQTT_6.png/600px-LG308_MQTT_6.png\|\|height="279" width="600"]]
1.2	510
	511	Upstream Process
	512
1.10	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"]]
1.2	514
	515	Choose ASCII Format
	516
1.10	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"]]
1.2	518
	519	LHT65 Decoder
	520
	521	Step 6: Set up subscribe: Subscribe a topci for downstream.
	522
1.10	523	[[image:https://wiki.dragino.com/images/thumb/b/b9/LG308_MQTT_7.png/600px-LG308_MQTT_7.png\|\|height="176" width="600"]]
1.2	524
	525	Subscribe to a topic
	526
	527
	528	Step 7: Downstream: Save the change, we can see the log info via "sytem log", End Node and MQTT Server.
	529
1.10	530	[[image:https://wiki.dragino.com/images/thumb/9/97/LG308_MQTT_8.png/600px-LG308_MQTT_8.png\|\|height="298" width="600"]]
1.2	531
	532	Downstream Flow
	533
	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]]
	535
	536
1.3	537	= 5. Example For Different MQTT Servers =
1.2	538
1.11	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"]]
1.2	542
1.11	543	== [[ThingSpeak Server>>url:http://www.thingspeak.com/]] ==
1.2	544
	545
	546	[[Examples>>url:https://wiki.dragino.com/index.php/ThingSpeak_Examples]]
1.11	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"]]
1.2	549
1.12	550	(% class="wikigeneratedid" %)
	551	== ==
	552
1.11	553	== [[乐联网平台>>url:https://www.lewei50.com/]] ==
1.2	554
	555
1.10	556	[[lewei Example>>url:https://wiki.dragino.com/index.php/Lewei_Example_mqtt]]
1.11	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"]]
1.10	559
1.11	560	== [[AWS-IOT>>url:https://aws.amazon.com/cn/iot-platform/how-it-works/]] ==
1.2	561
	562
	563	[[AWS Examples>>url:https://wiki.dragino.com/index.php/MQTT_Forward_to_Amazon_AWS-IOT]]
	564	)))
	565
1.3	566	= 6. How to Debug =
1.2	567
1.10	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.
1.2	569
1.3	570	= 7. How to ask for Support =
1.2	571
	572	If a user still not have trouble making it works. please send a mail to support@dragino.com with the below info:
	573
	574	* Detail of your LoRaWAN end node.
	575	* Gateway Model and firmware version
	576	* A set of screenshots you configure in the gateway according to our instruction
	577	* A full log of "logread -f"

Wiki source code of MQTT Forward Instruction

Applications

Navigation