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