Wiki source code of MQTT Forward Instruction

Last modified by Xiaoling on 2022/09/02 18:11

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

Wiki source code of MQTT Forward Instruction

Applications

Navigation