Wiki source code of MQTT Forward Instruction

Version 49.2 by Xiaoling on 2022/08/09 16:18

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

Wiki source code of MQTT Forward Instruction

Applications

Navigation