Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -292,30 +292,22 @@
292	292	== 5.1 Introduction ==
293	293
294	294	(((
295		-(((
296	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.
297	297	)))
298		-)))
299	299
300	300	== 5.2 Create device steps at MQTT ==
301	301
302	302	(((
303		-(((
304	304	The user creates a new API KEY after creating a device on TTN V3.
305	305	)))
306		-)))
307	307
308	308	(((
309		-(((
310	310	Then copy the password and open MQTT.fx.
311	311	)))
312		-)))
313	313
314	314	(((
315		-(((
316	316	Fill in Broker Address and Broker port.
317	317	)))
318		-)))
319	319
320	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"]]
321	321
...	...	@@ -326,9 +326,7 @@
326	326
327	327	The Application Server publishes uplink traffic on the following topics:
328	328
329		-(% class="box" %)
330		-(((
331		- v3/{application id}@{tenant id}/devices/{device id}/join
	321	+{{{ v3/{application id}@{tenant id}/devices/{device id}/join
332	332	v3/{application id}@{tenant id}/devices/{device id}/up
333	333	v3/{application id}@{tenant id}/devices/{device id}/down/queued
334	334	v3/{application id}@{tenant id}/devices/{device id}/down/sent
...	...	@@ -337,41 +337,31 @@
337	337	v3/{application id}@{tenant id}/devices/{device id}/down/failed
338	338	v3/{application id}@{tenant id}/devices/{device id}/service/data
339	339	v3/{application id}@{tenant id}/devices/{device id}/location/solved
340		-)))
	330	+}}}
341	341
342	342	(((
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}.
	333	+Note: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
345	345	)))
346		-)))
347	347
348	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"]]
349	349
350	350	(((
351		-(((
352	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.
353	353	)))
354		-)))
355	355
356	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"]]
357	357
358	358	(((
359		-(((
360	360	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
361	361	)))
362		-)))
363	363
364	364	(((
365		-(((
366	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.
367	367	)))
368		-)))
369	369
370	370	(((
371		-(((
372	372	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
373	373	)))
374		-)))
375	375
376	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"]]
377	377
...	...	@@ -445,7 +445,7 @@
445	445
446	446	(((
447	447	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.
448		-\\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:**
	428	+\\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]] 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:
449	449	)))
450	450
451	451	* End node is connected to serial port to show the Join frequency and DR. (If possible)
...	...	@@ -473,12 +473,8 @@
473	473
474	474	**2. Gateway packet traffic in gateway web or ssh. we can check:**
475	475
476		-* (((
477		-If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
478		-)))
479		-* (((
480		-If the gateway gets the Join Accept message from server and transmit it via LoRa?
481		-)))
	456	+* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
	457	+* If the gateway gets the Join Accept message from server and transmit it via LoRa?
482	482
483	483	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
484	484
...	...	@@ -487,15 +487,9 @@
487	487
488	488	**3. Gateway Traffic Page in LoRaWAN Server**
489	489
490		-* (((
491		-If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
492		-)))
493		-* (((
494		-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.
495		-)))
496		-* (((
497		-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.
498		-)))
	466	+* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	467	+* 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.
	468	+* 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.
499	499
500	500	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
501	501
...	...	@@ -509,10 +509,8 @@
509	509	**4. Data Page in LoRaWAN server**
510	510
511	511	* (((
512		-(((
513	513	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.
514	514	)))
515		-)))
516	516
517	517	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
518	518