Wiki source code of Notes for TTN

Version 2.3 by Xiaoling on 2022/05/17 09:28

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.3	38	[[image:https://wiki.dragino.com/images/thumb/0/0c/TTN_v3_Primary_001.png/600px-TTN_v3_Primary_001.png\|\|height="296" width="600"]]
1.2	39
	40	Register Gateway
	41
	42
1.3	43	[[image:https://wiki.dragino.com/images/thumb/b/ba/TTN_v3_Primary_002.png/600px-TTN_v3_Primary_002.png\|\|height="283" width="600"]]
	44
1.2	45	Put Gateway ID
	46
	47
1.3	48	[[image:https://wiki.dragino.com/images/thumb/a/a6/TTN_v3_Primary_003.png/600px-TTN_v3_Primary_003.png\|\|height="279" width="600"]]
	49
1.2	50	Choose Frequency Band
	51
	52
1.3	53	[[image:https://wiki.dragino.com/images/thumb/4/44/TTN_v3_Primary_004.png/600px-TTN_v3_Primary_004.png\|\|height="350" width="600"]]
	54
1.2	55	Show Status
	56
1.3	57	== 2.2 Secondary LoRaWAN Server ==
1.2	58
1.3	59	=== 2.2.1 Introduction ===
1.2	60
	61	The Dragino gateway has supports the Secondary server settings.
	62
1.3	63	=== 2.2.2 Below list the support products and Requirements: ===
1.2	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
	67	1. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
	68
1.3	69	=== 2.2.3 Example ===
1.2	70
	71	The following takes Helium as a Secondary LoRaWAN server as an example,
	72
1.3	73	=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
1.2	74
	75	The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
	76
1.3	77	[[image:https://wiki.dragino.com/images/thumb/f/f8/Helium_Secondary_001.png/600px-Helium_Secondary_001.png\|\|height="350" width="600"]]
1.2	78
	79	Download and Install gateway-rs
	80
1.3	81	=== 2.2.5 Step 2: Back to Semtech UDP page ===
1.2	82
	83	Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
	84
1.3	85	[[image:https://wiki.dragino.com/images/thumb/c/c8/Helium_Secondary_002.png/600px-Helium_Secondary_002.png\|\|height="415" width="600"]]
1.2	86
	87	Configuration of helium
	88
1.3	89	= 3. Gateway Registration for Basics Station =
1.2	90
1.3	91	== 3.1 Introduction ==
1.2	92
1.3	93	(((
1.6	94	(((
1.2	95	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	96	)))
1.6	97	)))
1.2	98
1.6	99	(((
1.2	100	Below list the support products and Requirements:
1.6	101	)))
1.2	102
1.6	103	(((
	104	(((
	105	~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	106	)))
1.2	107
1.6	108	(((
	109	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	110	)))
1.6	111	)))
1.2	112
1.6	113	(((
1.2	114	What do you need to prepare
1.6	115	)))
1.2	116
1.3	117	(((
1.6	118	(((
1.2	119	A gateway that can access the internet normally
1.3	120	)))
1.6	121	)))
1.2	122
1.3	123	== 3.2 Step 1. Add Gateway ==
1.2	124
1.3	125	(((
1.7	126	(((
1.2	127	The example for EU
1.3	128	)))
1.7	129	)))
1.2	130
1.3	131	(((
1.7	132	(((
1.2	133	User can add your gateway into The Things Network V3 according to the previous step
1.3	134	)))
1.7	135	)))
1.2	136
1.3	137	(((
1.7	138	(((
1.2	139	Following picture is the successful added.
1.3	140	)))
1.7	141	)))
1.2	142
1.3	143	[[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	144
	145	Add Gateway
	146
1.3	147	== 3.3 Step 2. Create the API key ==
1.2	148
	149	user need to create the CUPS API key and LNS API key.
	150
1.3	151	[[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	152
	153	Create CUPS API key
	154
	155
1.3	156	[[image:https://wiki.dragino.com/images/thumb/5/55/Create_lns_api_key.png/600px-Create_lns_api_key.png\|\|height="403" width="600"]]
	157
1.2	158	Create LNS API key
	159
1.7	160	(% style="color:red" %)Note : Please copy the API key.
1.2	161
1.3	162	== 3.4 Step 3. Update the gateway setting ==
1.2	163
	164	In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
	165
1.3	166	[[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	167
	168	paste the API key
	169
1.3	170	== 3.5 Step 4. Access the gateway GUI ==
1.2	171
	172	User need to update the API key and install the Certificate
	173
1.3	174	[[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	175
	176	Access the gateway GUI
	177
1.3	178	== 3.6 Step 5. Configure Station ==
1.2	179
	180	User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
	181
	182	just to clarify.
	183
1.7	184	(% class="box" %)
	185	(((
	186	CUPS Server URI ~-~-> Server Adress
	187	CUPS Authorization Key ~-~-> Server CUPS API Key
	188	LNS Authorization Key ~-~-> Server LNS API Key
	189	CUPS certificate ~-~-> Server CA(user can use the button to install the certificate by default)
	190	)))
1.2	191
1.3	192	[[image:https://wiki.dragino.com/images/thumb/8/8c/Confiure_station_cao.png/600px-Confiure_station_cao.png\|\|height="321" width="600"]]
1.2	193
	194	Congfigure Station
	195
1.3	196	== 3.7 Start Station ==
1.2	197
1.3	198	(((
1.2	199	When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
1.3	200	)))
1.2	201
1.3	202	== 3.8 Siccessful Connection ==
1.2	203
	204	If user completes the above steps,which will see live date in the TTN.
	205
1.3	206	[[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	207
	208	Station live date
	209
1.3	210	== 3.9 Trouble Shooting ==
1.2	211
	212	User can check the station log in the logread/system log page.
	213
1.3	214	[[image:https://wiki.dragino.com/images/thumb/7/7c/Station_log_xiao.png/600px-Station_log_xiao.png\|\|height="457" width="600"]]
1.2	215
	216	Station Log
	217
	218	and recode the station log in the system/Recode log page.
	219
1.3	220	[[image:https://wiki.dragino.com/images/thumb/5/50/Recore_log_xiao.png/600px-Recore_log_xiao.png\|\|height="147" width="600"]]
1.2	221
	222	Recore Log
	223
1.3	224	= 4. Configure node connection to TTNv3 =
1.2	225
1.3	226	(((
1.8	227	(((
1.2	228	Following is an example for how to join the TTN v3 LoRaWAN Network.
1.3	229	)))
1.8	230	)))
1.2	231
1.3	232	(((
1.8	233	(((
1.2	234	The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
1.3	235	)))
1.8	236	)))
1.2	237
1.3	238	(((
1.8	239	(((
1.2	240	We take LES01 as an example.
1.3	241	)))
1.8	242	)))
1.2	243
1.3	244	== 4.1 Step1 ==
1.2	245
1.3	246	(((
1.8	247	(((
1.2	248	Create a device in TTN with the OTAA keys from LSE01.
1.3	249	)))
1.8	250	)))
1.2	251
1.3	252	(((
1.8	253	(((
1.2	254	Each LSE01 is shipped with a sticker with the default device EUI as below:
1.3	255	)))
1.8	256	)))
1.2	257
1.3	258	(((
1.8	259	(((
1.2	260	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
1.3	261	)))
1.8	262	)))
1.2	263
1.3	264	[[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	265
1.3	266	[[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	267
1.3	268	== 4.2 Step2 ==
1.2	269
1.3	270	(((
1.8	271	(((
1.2	272	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	273	)))
1.8	274	)))
1.2	275
1.3	276	[[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	277
1.3	278	== 4.3 Step3 ==
1.2	279
	280	Add APP EUI in the application:
	281
1.3	282	[[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	283
1.3	284	== 4.4 Step4 ==
1.2	285
	286	Add APP KEY and DEV EUI:
	287
1.3	288	[[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	289
1.3	290	= 5. TTN V3 integrated into MQTT server =
1.2	291
1.3	292	== 5.1 Introduction ==
1.2	293
1.3	294	(((
1.9	295	(((
1.2	296	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	297	)))
1.9	298	)))
1.2	299
1.3	300	== 5.2 Create device steps at MQTT ==
1.2	301
1.3	302	(((
1.9	303	(((
1.2	304	The user creates a new API KEY after creating a device on TTN V3.
1.3	305	)))
1.9	306	)))
1.2	307
1.3	308	(((
1.9	309	(((
1.2	310	Then copy the password and open MQTT.fx.
1.3	311	)))
1.9	312	)))
1.2	313
1.3	314	(((
1.9	315	(((
1.2	316	Fill in Broker Address and Broker port.
1.3	317	)))
1.9	318	)))
1.2	319
1.3	320	[[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	321
	322	Fill in the username and password into MQTT.
	323
	324
1.3	325	[[image:https://wiki.dragino.com/images/thumb/6/6a/V3_MQTT2.png/600px-V3_MQTT2.png\|\|alt="V3 MQTT2.png" height="434" width="600"]]
	326
1.2	327	The Application Server publishes uplink traffic on the following topics:
	328
1.9	329	(% class="box" %)
	330	(((
	331	v3/{application id}@{tenant id}/devices/{device id}/join
1.2	332	v3/{application id}@{tenant id}/devices/{device id}/up
	333	v3/{application id}@{tenant id}/devices/{device id}/down/queued
	334	v3/{application id}@{tenant id}/devices/{device id}/down/sent
	335	v3/{application id}@{tenant id}/devices/{device id}/down/ack
	336	v3/{application id}@{tenant id}/devices/{device id}/down/nack
	337	v3/{application id}@{tenant id}/devices/{device id}/down/failed
	338	v3/{application id}@{tenant id}/devices/{device id}/service/data
	339	v3/{application id}@{tenant id}/devices/{device id}/location/solved
1.9	340	)))
1.2	341
1.3	342	(((
1.9	343	(((
	344	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	345	)))
1.9	346	)))
1.2	347
1.3	348	[[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	349
1.3	350	(((
1.9	351	(((
1.2	352	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	353	)))
1.9	354	)))
1.2	355
1.3	356	[[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	357
1.3	358	(((
1.10	359	(((
1.2	360	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
1.3	361	)))
1.10	362	)))
1.2	363
1.3	364	(((
1.10	365	(((
2.2	366	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	367	)))
1.10	368	)))
1.2	369
1.3	370	(((
1.10	371	(((
1.2	372	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	373	)))
1.10	374	)))
1.2	375
1.3	376	[[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	377
1.3	378	(((
1.2	379	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	380	)))
1.2	381
1.3	382	(((
2.2	383	Note: Use this handy tool to convert hexadecimal to base64.
1.3	384	)))
1.2	385
1.3	386	[[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	387
1.3	388	== 5.3 Send Downlink message ==
1.2	389
1.3	390	(((
1.2	391	How to configure downlink in TTN V3?
1.3	392	)))
1.2	393
1.3	394	(((
1.2	395	A few examples: set the transmission interval to 90 seconds.
1.3	396	)))
1.2	397
1.3	398	(((
1.2	399	Downlink command:01 00 00 5A
1.3	400	)))
1.2	401
1.3	402	[[image:https://wiki.dragino.com/images/thumb/9/90/Downlink_50.png/600px-Downlink_50.png\|\|height="327" width="600"]]
1.2	403
	404	downlink
	405
	406	After sending, you can view it in live data.
	407
1.3	408	[[image:https://wiki.dragino.com/images/thumb/1/15/Downlink_51.png/600px-Downlink_51.png\|\|height="141" width="600"]]
1.2	409
	410	downlink
	411
1.3	412	(((
1.2	413	When downlink is successfully sent, the downlink information can be received on the serial port.
1.3	414	)))
1.2	415
1.3	416	(((
2.2	417	Note: If the downlink byte sent is longer, the number of bytes will be displayed.
1.3	418	)))
1.2	419
1.3	420	[[image:https://wiki.dragino.com/images/thumb/c/c9/Downlink_52.png/600px-Downlink_52.png\|\|height="407" width="600"]]
1.2	421
	422	downlink
	423
1.3	424	(((
1.14	425	(((
1.2	426	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
1.3	427	)))
1.14	428	)))
1.2	429
1.3	430	(((
1.14	431	(((
2.2	432	If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
1.3	433	)))
1.14	434	)))
1.2	435
1.3	436	(((
1.14	437	(((
2.2	438	If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
1.3	439	)))
1.14	440	)))
1.2	441
1.3	442	(((
1.14	443	(((
1.2	444	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
1.3	445	)))
1.14	446	)))
1.2	447
1.3	448	[[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png\|\|height="127" width="600"]]
1.2	449
	450	downlink
	451
1.3	452	= 6. Request Remote Support =
1.2	453
1.3	454	(((
1.2	455	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	456	\\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	457	)))
1.2	458
	459	* End node is connected to serial port to show the Join frequency and DR. (If possible)
	460	* Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
	461	* Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
	462	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
	463	* 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)
	464
	465	~1. End Device Join Screen shot, we can check:
	466
	467	* If the device is sending join request to server?
	468	* What frequency the device is sending?
	469
1.3	470	[[image:https://wiki.dragino.com/images/thumb/7/77/LoRaWAN_Communication_Debug1.png/600px-LoRaWAN_Communication_Debug1.png\|\|height="596" width="600"]]
1.2	471
	472	Console Output from End device to see the transmit frequency
	473
2.3	474	User can run AT+CFG command to print configuration information.
1.2	475
2.3	476	* Is the device in OTAA mode or ABP mode? AT+NJM=1 (OTAA mode), AT+NJM=0 (ABP mode)
1.2	477
1.3	478	[[image:https://wiki.dragino.com/images/thumb/c/c5/LoRaWAN_Communication_Debug23.png/600px-LoRaWAN_Communication_Debug23.png\|\|height="514" width="600"]]
1.2	479
	480	Console Output from End device to see the transmit frequency
	481
	482	2. Gateway packet traffic in gateway web or ssh. we can check:
	483
1.13	484	* (((
	485	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
	486	)))
	487	* (((
	488	If the gateway gets the Join Accept message from server and transmit it via LoRa?
	489	)))
1.2	490
1.3	491	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png\|\|height="325" width="600"]]
1.2	492
	493	Console Output from Gateway to see packets between end node and server.
	494
	495
	496	3. Gateway Traffic Page in LoRaWAN Server
	497
1.12	498	* (((
	499	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	500	)))
	501	* (((
	502	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.
	503	)))
	504	* (((
	505	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.
	506	)))
1.2	507
1.3	508	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png\|\|height="268" width="600"]]
1.2	509
	510	The Traffic for the End node in the server, use TTNv3 as example
	511
	512
1.3	513	[[image:https://wiki.dragino.com/images/thumb/4/4b/LoRaWAN_Communication_Debug3.png/600px-LoRaWAN_Communication_Debug3.png\|\|height="281" width="600"]]
	514
1.2	515	The Traffic for the End node in the server, use TTNv3 as example
	516
	517	4. Data Page in LoRaWAN server
	518
1.3	519	* (((
1.11	520	(((
2.3	521	(((
1.3	522	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.
	523	)))
1.11	524	)))
2.3	525	)))
1.2	526
1.3	527	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png\|\|height="222" width="600"]]
1.2	528
	529	The data for the end device set in server
	530
1.3	531	[[image:https://wiki.dragino.com/images/thumb/6/69/LoRaWAN_Communication_Debug5.png/600px-LoRaWAN_Communication_Debug5.png\|\|height="279" width="600"]]
1.2	532
	533	Check if OTAA Keys match the keys in device

Wiki source code of Notes for TTN

Applications

Navigation