Wiki source code of Notes for TTN

Version 3.1 by Xiaoling on 2022/05/25 08:49

version	line-number	content
1.4	1	~ Contents：
1.1	2
1.4	3	{{toc/}}
1.1	4
	5
1.2	6	= 1. The Things Network-V3 =
1.1	7
1.2	8	== 1.1 Introduction ==
1.1	9
1.2	10	=== 1.1.1 What is The Things Network ===
1.1	11
1.2	12	(((
	13	The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
	14	)))
1.1	15
1.2	16	(((
	17	The Things Network runs The Things Stack Community Edition, which is a crowdsourced, open and decentralized LoRaWAN network. This network is a great way to get started testing devices, applications, and integrations, and get familiar with LoRaWAN.
	18	)))
1.1	19
1.2	20	=== 1.1.2 Login or crate an account ===
1.1	21
1.2	22	(((
	23	[[Login or create an account>>url:https://console.cloud.thethings.network/]] to get started with The Things Network and start using The Things Stack Console.
	24	)))
1.1	25
1.2	26	(((
	27	Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
	28	)))
1.1	29
1.2	30	=== 1.1.3 List the support products and Requirements ===
1.1	31
1.2	32	LoRaWAN Gateway model: Existing Gateway
1.1	33
1.2	34	= 2. Gateway Registration for Semtech UDP =
1.1	35
1.3	36	== 2.1 Primary LoRaWAN Server ==
1.1	37
1.2	38
	39	Register Gateway
	40
	41
1.3	42	[[image:https://wiki.dragino.com/images/thumb/b/ba/TTN_v3_Primary_002.png/600px-TTN_v3_Primary_002.png\|\|height="283" width="600"]]
	43
1.2	44	Put Gateway ID
	45
	46
1.3	47	[[image:https://wiki.dragino.com/images/thumb/a/a6/TTN_v3_Primary_003.png/600px-TTN_v3_Primary_003.png\|\|height="279" width="600"]]
	48
1.2	49	Choose Frequency Band
	50
	51
1.3	52	[[image:https://wiki.dragino.com/images/thumb/4/44/TTN_v3_Primary_004.png/600px-TTN_v3_Primary_004.png\|\|height="350" width="600"]]
	53
1.2	54	Show Status
	55
1.3	56	== 2.2 Secondary LoRaWAN Server ==
1.2	57
1.3	58	=== 2.2.1 Introduction ===
1.2	59
	60	The Dragino gateway has supports the Secondary server settings.
	61
1.3	62	=== 2.2.2 Below list the support products and Requirements: ===
1.2	63
2.4	64	(((
	65	~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
	66	)))
1.2	67
2.4	68	(((
	69	2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
	70	)))
1.2	71
1.3	72	=== 2.2.3 Example ===
1.2	73
	74	The following takes Helium as a Secondary LoRaWAN server as an example,
	75
1.3	76	=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
1.2	77
	78	The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
	79
1.3	80	[[image:https://wiki.dragino.com/images/thumb/f/f8/Helium_Secondary_001.png/600px-Helium_Secondary_001.png\|\|height="350" width="600"]]
1.2	81
	82	Download and Install gateway-rs
	83
1.3	84	=== 2.2.5 Step 2: Back to Semtech UDP page ===
1.2	85
	86	Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
	87
1.3	88	[[image:https://wiki.dragino.com/images/thumb/c/c8/Helium_Secondary_002.png/600px-Helium_Secondary_002.png\|\|height="415" width="600"]]
1.2	89
	90	Configuration of helium
	91
1.3	92	= 3. Gateway Registration for Basics Station =
1.2	93
1.3	94	== 3.1 Introduction ==
1.2	95
1.3	96	(((
1.6	97	(((
1.2	98	The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
1.3	99	)))
1.6	100	)))
1.2	101
1.6	102	(((
1.2	103	Below list the support products and Requirements:
1.6	104	)))
1.2	105
1.6	106	(((
	107	(((
	108	~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
1.3	109	)))
1.2	110
1.6	111	(((
	112	2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
1.3	113	)))
1.6	114	)))
1.2	115
1.6	116	(((
1.2	117	What do you need to prepare
1.6	118	)))
1.2	119
1.3	120	(((
1.6	121	(((
1.2	122	A gateway that can access the internet normally
1.3	123	)))
1.6	124	)))
1.2	125
1.3	126	== 3.2 Step 1. Add Gateway ==
1.2	127
1.3	128	(((
1.7	129	(((
1.2	130	The example for EU
1.3	131	)))
1.7	132	)))
1.2	133
1.3	134	(((
1.7	135	(((
1.2	136	User can add your gateway into The Things Network V3 according to the previous step
1.3	137	)))
1.7	138	)))
1.2	139
1.3	140	(((
1.7	141	(((
1.2	142	Following picture is the successful added.
1.3	143	)))
1.7	144	)))
1.2	145
1.3	146	[[image:https://wiki.dragino.com/images/thumb/5/5f/Add_gateway_1.1.png/600px-Add_gateway_1.1.png\|\|height="397" width="600"]]
1.2	147
	148	Add Gateway
	149
1.3	150	== 3.3 Step 2. Create the API key ==
1.2	151
	152	user need to create the CUPS API key and LNS API key.
	153
1.3	154	[[image:https://wiki.dragino.com/images/thumb/c/c6/Create_cups_api_key.png/600px-Create_cups_api_key.png\|\|height="394" width="600"]]
1.2	155
	156	Create CUPS API key
	157
	158
1.3	159	[[image:https://wiki.dragino.com/images/thumb/5/55/Create_lns_api_key.png/600px-Create_lns_api_key.png\|\|height="403" width="600"]]
	160
1.2	161	Create LNS API key
	162
1.7	163	(% style="color:red" %)Note : Please copy the API key.
1.2	164
1.3	165	== 3.4 Step 3. Update the gateway setting ==
1.2	166
	167	In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
	168
1.3	169	[[image:https://wiki.dragino.com/images/thumb/2/2f/Paste_the_lns_API_key.png/600px-Paste_the_lns_API_key.png\|\|height="363" width="600"]]
1.2	170
	171	paste the API key
	172
1.3	173	== 3.5 Step 4. Access the gateway GUI ==
1.2	174
	175	User need to update the API key and install the Certificate
	176
1.3	177	[[image:https://wiki.dragino.com/images/thumb/a/a3/Access_gateway_gui_ttnstation.png/600px-Access_gateway_gui_ttnstation.png\|\|height="354" width="600"]]
1.2	178
	179	Access the gateway GUI
	180
1.3	181	== 3.6 Step 5. Configure Station ==
1.2	182
	183	User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
	184
	185	just to clarify.
	186
1.7	187	(% class="box" %)
	188	(((
	189	CUPS Server URI ~-~-> Server Adress
	190	CUPS Authorization Key ~-~-> Server CUPS API Key
	191	LNS Authorization Key ~-~-> Server LNS API Key
	192	CUPS certificate ~-~-> Server CA(user can use the button to install the certificate by default)
	193	)))
1.2	194
1.3	195	[[image:https://wiki.dragino.com/images/thumb/8/8c/Confiure_station_cao.png/600px-Confiure_station_cao.png\|\|height="321" width="600"]]
1.2	196
	197	Congfigure Station
	198
1.3	199	== 3.7 Start Station ==
1.2	200
1.3	201	(((
1.2	202	When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
1.3	203	)))
1.2	204
1.3	205	== 3.8 Siccessful Connection ==
1.2	206
	207	If user completes the above steps,which will see live date in the TTN.
	208
1.3	209	[[image:https://wiki.dragino.com/images/thumb/4/49/Station_live_date_cao.png/600px-Station_live_date_cao.png\|\|height="391" width="600"]]
1.2	210
	211	Station live date
	212
1.3	213	== 3.9 Trouble Shooting ==
1.2	214
	215	User can check the station log in the logread/system log page.
	216
1.3	217	[[image:https://wiki.dragino.com/images/thumb/7/7c/Station_log_xiao.png/600px-Station_log_xiao.png\|\|height="457" width="600"]]
1.2	218
	219	Station Log
	220
	221	and recode the station log in the system/Recode log page.
	222
1.3	223	[[image:https://wiki.dragino.com/images/thumb/5/50/Recore_log_xiao.png/600px-Recore_log_xiao.png\|\|height="147" width="600"]]
1.2	224
	225	Recore Log
	226
1.3	227	= 4. Configure node connection to TTNv3 =
1.2	228
1.3	229	(((
1.8	230	(((
1.2	231	Following is an example for how to join the TTN v3 LoRaWAN Network.
1.3	232	)))
1.8	233	)))
1.2	234
1.3	235	(((
1.8	236	(((
1.2	237	The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
1.3	238	)))
1.8	239	)))
1.2	240
1.3	241	(((
1.8	242	(((
1.2	243	We take LES01 as an example.
1.3	244	)))
1.8	245	)))
1.2	246
1.3	247	== 4.1 Step1 ==
1.2	248
1.3	249	(((
1.8	250	(((
1.2	251	Create a device in TTN with the OTAA keys from LSE01.
1.3	252	)))
1.8	253	)))
1.2	254
1.3	255	(((
1.8	256	(((
1.2	257	Each LSE01 is shipped with a sticker with the default device EUI as below:
1.3	258	)))
1.8	259	)))
1.2	260
1.3	261	(((
1.8	262	(((
1.2	263	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
1.3	264	)))
1.8	265	)))
1.2	266
1.3	267	[[image:https://wiki.dragino.com/images/thumb/c/c7/TTNv3--01.png/600px-TTNv3--01.png\|\|alt="TTNv3--01.png" height="277" width="600"]]
1.2	268
1.3	269	[[image:https://wiki.dragino.com/images/thumb/1/17/TTNv3--02.png/600px-TTNv3--02.png\|\|alt="TTNv3--02.png" height="226" width="600"]]
1.2	270
1.3	271	== 4.2 Step2 ==
1.2	272
1.3	273	(((
1.8	274	(((
1.2	275	There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
1.3	276	)))
1.8	277	)))
1.2	278
1.3	279	[[image:https://wiki.dragino.com/images/thumb/f/fc/TTNv3--03.png/600px-TTNv3--03.png\|\|alt="TTNv3--03.png" height="333" width="600"]]
1.2	280
1.3	281	== 4.3 Step3 ==
1.2	282
	283	Add APP EUI in the application:
	284
1.3	285	[[image:https://wiki.dragino.com/images/thumb/9/9f/TTNv3--04.png/600px-TTNv3--04.png\|\|alt="TTNv3--04.png" height="439" width="600"]]
1.2	286
1.3	287	== 4.4 Step4 ==
1.2	288
	289	Add APP KEY and DEV EUI:
	290
1.3	291	[[image:https://wiki.dragino.com/images/thumb/a/a4/TTNv3--05.png/600px-TTNv3--05.png\|\|alt="TTNv3--05.png" height="500" width="600"]]
1.2	292
1.3	293	= 5. TTN V3 integrated into MQTT server =
1.2	294
1.3	295	== 5.1 Introduction ==
1.2	296
1.3	297	(((
1.9	298	(((
1.2	299	The Application Server exposes an MQTT server to work with streaming events. In order to use the MQTT server you need to create a new API key, which will function as connection password. You can also use an existing API key, as long as it has the necessary rights granted.
1.3	300	)))
1.9	301	)))
1.2	302
1.3	303	== 5.2 Create device steps at MQTT ==
1.2	304
1.3	305	(((
1.9	306	(((
1.2	307	The user creates a new API KEY after creating a device on TTN V3.
1.3	308	)))
1.9	309	)))
1.2	310
1.3	311	(((
1.9	312	(((
1.2	313	Then copy the password and open MQTT.fx.
1.3	314	)))
1.9	315	)))
1.2	316
1.3	317	(((
1.9	318	(((
1.2	319	Fill in Broker Address and Broker port.
1.3	320	)))
1.9	321	)))
1.2	322
1.3	323	[[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png\|\|alt="V3 MQTT1 .png" height="325" width="600"]]
1.2	324
	325	Fill in the username and password into MQTT.
	326
	327
1.3	328	[[image:https://wiki.dragino.com/images/thumb/6/6a/V3_MQTT2.png/600px-V3_MQTT2.png\|\|alt="V3 MQTT2.png" height="434" width="600"]]
	329
1.2	330	The Application Server publishes uplink traffic on the following topics:
	331
1.9	332	(% class="box" %)
	333	(((
	334	v3/{application id}@{tenant id}/devices/{device id}/join
1.2	335	v3/{application id}@{tenant id}/devices/{device id}/up
	336	v3/{application id}@{tenant id}/devices/{device id}/down/queued
	337	v3/{application id}@{tenant id}/devices/{device id}/down/sent
	338	v3/{application id}@{tenant id}/devices/{device id}/down/ack
	339	v3/{application id}@{tenant id}/devices/{device id}/down/nack
	340	v3/{application id}@{tenant id}/devices/{device id}/down/failed
	341	v3/{application id}@{tenant id}/devices/{device id}/service/data
	342	v3/{application id}@{tenant id}/devices/{device id}/location/solved
1.9	343	)))
1.2	344
1.3	345	(((
1.9	346	(((
	347	Note: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
1.3	348	)))
1.9	349	)))
1.2	350
1.3	351	[[image:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png\|\|alt="V3 MQTT3.png" height="400" width="600"]]
1.2	352
1.3	353	(((
1.9	354	(((
1.2	355	While you could subscribe to all of these topics separately, for the simplicity of this tutorial we use # to subscribe to all topics, i.e. to receive all uplink traffic.
1.3	356	)))
1.9	357	)))
1.2	358
1.3	359	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg\|\|alt="V3 MQTT4.jpg" height="326" width="600"]]
1.2	360
1.3	361	(((
1.10	362	(((
1.2	363	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
1.3	364	)))
1.10	365	)))
1.2	366
1.3	367	(((
1.10	368	(((
2.2	369	Note: Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.
1.3	370	)))
1.10	371	)))
1.2	372
1.3	373	(((
1.10	374	(((
1.2	375	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
1.3	376	)))
1.10	377	)))
1.2	378
1.3	379	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png\|\|alt="V3 MQTT5.png" height="289" width="600"]]
1.2	380
1.3	381	(((
1.2	382	To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
1.3	383	)))
1.2	384
1.3	385	(((
2.2	386	Note: Use this handy tool to convert hexadecimal to base64.
1.3	387	)))
1.2	388
1.3	389	[[image:https://wiki.dragino.com/images/thumb/9/9f/V3_MQTT6.png/600px-V3_MQTT6.png\|\|alt="V3 MQTT6.png" height="313" width="600"]]
1.2	390
1.3	391	== 5.3 Send Downlink message ==
1.2	392
1.3	393	(((
1.2	394	How to configure downlink in TTN V3?
1.3	395	)))
1.2	396
1.3	397	(((
1.2	398	A few examples: set the transmission interval to 90 seconds.
1.3	399	)))
1.2	400
1.3	401	(((
1.2	402	Downlink command:01 00 00 5A
1.3	403	)))
1.2	404
1.3	405	[[image:https://wiki.dragino.com/images/thumb/9/90/Downlink_50.png/600px-Downlink_50.png\|\|height="327" width="600"]]
1.2	406
	407	downlink
	408
	409	After sending, you can view it in live data.
	410
1.3	411	[[image:https://wiki.dragino.com/images/thumb/1/15/Downlink_51.png/600px-Downlink_51.png\|\|height="141" width="600"]]
1.2	412
	413	downlink
	414
1.3	415	(((
1.2	416	When downlink is successfully sent, the downlink information can be received on the serial port.
1.3	417	)))
1.2	418
1.3	419	(((
2.2	420	Note: If the downlink byte sent is longer, the number of bytes will be displayed.
1.3	421	)))
1.2	422
1.3	423	[[image:https://wiki.dragino.com/images/thumb/c/c9/Downlink_52.png/600px-Downlink_52.png\|\|height="407" width="600"]]
1.2	424
	425	downlink
	426
1.3	427	(((
1.14	428	(((
1.2	429	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
1.3	430	)))
1.14	431	)))
1.2	432
1.3	433	(((
1.14	434	(((
2.2	435	If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
1.3	436	)))
1.14	437	)))
1.2	438
1.3	439	(((
1.14	440	(((
2.4	441	If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
1.3	442	)))
1.14	443	)))
1.2	444
1.3	445	(((
1.14	446	(((
1.2	447	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
1.3	448	)))
1.14	449	)))
1.2	450
1.3	451	[[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png\|\|height="127" width="600"]]
1.2	452
	453	downlink
	454
1.3	455	= 6. Request Remote Support =
1.2	456
1.3	457	(((
1.2	458	These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
1.13	459	\\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:
1.3	460	)))
1.2	461
	462	* End node is connected to serial port to show the Join frequency and DR. (If possible)
	463	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
	464	* Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
	465	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
	466	* End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
	467
	468	~1. End Device Join Screen shot, we can check:
	469
	470	* If the device is sending join request to server?
	471	* What frequency the device is sending?
	472
1.3	473	[[image:https://wiki.dragino.com/images/thumb/7/77/LoRaWAN_Communication_Debug1.png/600px-LoRaWAN_Communication_Debug1.png\|\|height="596" width="600"]]
1.2	474
	475	Console Output from End device to see the transmit frequency
	476
2.3	477	User can run AT+CFG command to print configuration information.
1.2	478
2.3	479	* Is the device in OTAA mode or ABP mode? AT+NJM=1 (OTAA mode), AT+NJM=0 (ABP mode)
1.2	480
1.3	481	[[image:https://wiki.dragino.com/images/thumb/c/c5/LoRaWAN_Communication_Debug23.png/600px-LoRaWAN_Communication_Debug23.png\|\|height="514" width="600"]]
1.2	482
	483	Console Output from End device to see the transmit frequency
	484
	485	2. Gateway packet traffic in gateway web or ssh. we can check:
	486
1.13	487	* (((
	488	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
	489	)))
	490	* (((
	491	If the gateway gets the Join Accept message from server and transmit it via LoRa?
	492	)))
1.2	493
1.3	494	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png\|\|height="325" width="600"]]
1.2	495
	496	Console Output from Gateway to see packets between end node and server.
	497
	498
	499	3. Gateway Traffic Page in LoRaWAN Server
	500
1.12	501	* (((
	502	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	503	)))
	504	* (((
	505	If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
	506	)))
	507	* (((
	508	If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
	509	)))
1.2	510
1.3	511	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png\|\|height="268" width="600"]]
1.2	512
	513	The Traffic for the End node in the server, use TTNv3 as example
	514
	515
1.3	516	[[image:https://wiki.dragino.com/images/thumb/4/4b/LoRaWAN_Communication_Debug3.png/600px-LoRaWAN_Communication_Debug3.png\|\|height="281" width="600"]]
	517
1.2	518	The Traffic for the End node in the server, use TTNv3 as example
	519
	520	4. Data Page in LoRaWAN server
	521
1.3	522	* (((
1.11	523	(((
2.3	524	(((
1.3	525	If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
	526	)))
1.11	527	)))
2.3	528	)))
1.2	529
1.3	530	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png\|\|height="222" width="600"]]
1.2	531
	532	The data for the end device set in server
	533
1.3	534	[[image:https://wiki.dragino.com/images/thumb/6/69/LoRaWAN_Communication_Debug5.png/600px-LoRaWAN_Communication_Debug5.png\|\|height="279" width="600"]]
1.2	535
	536	Check if OTAA Keys match the keys in device

Wiki source code of Notes for TTN

Applications

Navigation