Wiki source code of MQTT Forward Instruction

Version 37.18 by Xiaoling on 2022/06/01 10:48

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

Wiki source code of MQTT Forward Instruction

Applications

Navigation