Wiki source code of MQTT Forward Instruction

Version 33.1 by Xiaoling on 2022/05/27 14:27

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

Wiki source code of MQTT Forward Instruction

Applications

Navigation