Wiki source code of TTN Stack 3
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | **~ Table of Contents:** | ||
2 | |||
3 | {{toc/}} | ||
4 | |||
5 | |||
6 | |||
7 | |||
8 | = 1. Introduction = | ||
9 | |||
10 | |||
11 | Notes for using Dragino Devices with TTN Stack3. | ||
12 | |||
13 | |||
14 | |||
15 | = 2. Downlink = | ||
16 | |||
17 | |||
18 | Use MQTT API for downlink: Reference: [[TTN Stack v3 MQTT reference>>url:https://thethingsstack.io/v3.1.0/guides/getting-started/mqtt/]] | ||
19 | |||
20 | ((( | ||
21 | (% style="color:blue" %)**Download command is:** | ||
22 | ))) | ||
23 | |||
24 | (% class="box" %) | ||
25 | ((( | ||
26 | mosquitto_pub -h eu1.cloud.thethings.industries -p 1883 -t v3/akXXXXXps@XXXXXX/devices/lsn50/down/push -u akXXXXXps@XXXXXX -P NNSXS.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX.LVQZECLX5FZ3XO5ACOW47IZ6HM54DMBBU776C53ZQHPLPQALIXYA -m '{"downlinks":[{"f_port": 2,"frm_payload":"AwAA","priority": "HIGH","confirmed": true}]}' | ||
27 | ))) | ||
28 | |||
29 | ((( | ||
30 | |||
31 | |||
32 | The MQTT command use (% style="color:blue" %)**-h,-p,-u,-P** (%%)options. We can find them in the website. | ||
33 | |||
34 | |||
35 | ))) | ||
36 | |||
37 | [[image:image-20220526142338-3.png]] | ||
38 | |||
39 | **find -h : broker address , -p port and -u: user name** | ||
40 | |||
41 | |||
42 | |||
43 | [[image:image-20220526142307-2.png]] | ||
44 | |||
45 | **find -P : Password** | ||
46 | |||
47 | |||
48 | |||
49 | User MQTT.FX to simulate a downlink | ||
50 | |||
51 | [[image:image-20220526142421-4.png]] | ||
52 | |||
53 | Use MQTT.FX to simulate downlink | ||
54 | |||
55 | |||
56 | |||
57 | Input connection info | ||
58 | |||
59 | [[image:image-20220526142512-5.png]] | ||
60 | |||
61 | Input MQTT connection info | ||
62 | |||
63 | |||
64 | |||
65 | Send a downstream | ||
66 | |||
67 | [[image:image-20220526142539-6.png]] | ||
68 | |||
69 | Gateway traffic for downstream | ||
70 | |||
71 | |||
72 | |||
73 | [[image:image-20220526142616-7.png||height="579" width="1407"]] | ||
74 | |||
75 | |||
76 | |||
77 | Downstream data flow will like below: | ||
78 | |||
79 | [[image:image-20220526142741-8.png]] | ||
80 | |||
81 | [[image:image-20220526142826-9.png]] | ||
82 | |||
83 | |||
84 | |||
85 | = 3. Trouble Shooting = | ||
86 | |||
87 | == 3.1 Problem when register a device to TTNv3 if it is already register to TTNv2 == | ||
88 | |||
89 | |||
90 | When you register the device in V2 and V3 with the same key and EUI, the device can only connect to V2. | ||
91 | |||
92 | |||
93 | [[image:image-20220526142914-10.png]] | ||
94 | |||
95 | [[image:image-20220526143018-11.png||height="619" width="1049"]] | ||
96 | |||
97 | |||
98 | If you want the device to connect to V3. You must change your key and EUI, or delete the device registered on V2. | ||
99 | |||
100 | |||
101 | |||
102 | == 3.2 MIC Mismatch or MIC Failed == | ||
103 | |||
104 | |||
105 | ((( | ||
106 | ((( | ||
107 | When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. | ||
108 | ))) | ||
109 | ))) | ||
110 | |||
111 | ((( | ||
112 | ((( | ||
113 | Under normal circumstances, users need to change the APPKEY to solve this problem. | ||
114 | |||
115 | |||
116 | ))) | ||
117 | ))) | ||
118 | |||
119 | [[image:image-20220526143057-12.png]] | ||
120 | |||
121 | MIC Mismatch |