Wiki source code of MQTT Forward Instruction

Version 46.2 by Xiaoling on 2022/07/14 16:19

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

Wiki source code of MQTT Forward Instruction

Applications

Navigation