Wiki source code of TTN Stack 3
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
1.5 | 1 | **~ Contents:** |
![]() |
1.1 | 2 | |
![]() |
1.5 | 3 | {{toc/}} |
![]() |
1.3 | 4 | |
![]() |
14.2 | 5 | |
6 | |||
7 | |||
![]() |
1.3 | 8 | = 1. Introduction = |
9 | |||
![]() |
1.2 | 10 | Notes for using Dragino Devices with TTN Stack3. |
![]() |
1.1 | 11 | |
![]() |
2.2 | 12 | |
![]() |
1.3 | 13 | = 2. Downlink = |
![]() |
1.1 | 14 | |
![]() |
1.2 | 15 | Use MQTT API for downlink: Reference: [[TTN Stack v3 MQTT reference>>url:https://thethingsstack.io/v3.1.0/guides/getting-started/mqtt/]] |
![]() |
1.1 | 16 | |
![]() |
1.7 | 17 | ((( |
![]() |
1.2 | 18 | **Download command is:** |
![]() |
1.7 | 19 | ))) |
![]() |
1.1 | 20 | |
![]() |
1.3 | 21 | (% class="box" %) |
22 | ((( | ||
![]() |
1.2 | 23 | 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}]}' |
![]() |
1.3 | 24 | ))) |
![]() |
1.1 | 25 | |
![]() |
1.7 | 26 | ((( |
![]() |
1.3 | 27 | The MQTT command use (% style="color:#4f81bd" %)**-h,-p,-u,-P** (%%)options. We can find them in the website. |
![]() |
1.7 | 28 | ))) |
![]() |
1.1 | 29 | |
![]() |
4.2 | 30 | [[image:image-20220526142338-3.png]] |
![]() |
1.1 | 31 | |
![]() |
1.2 | 32 | find -h : broker address , -p port and -u: user name |
![]() |
1.1 | 33 | |
![]() |
4.2 | 34 | [[image:image-20220526142307-2.png]] |
![]() |
1.1 | 35 | |
![]() |
1.2 | 36 | find -P : Password |
![]() |
1.1 | 37 | |
38 | |||
![]() |
1.2 | 39 | User MQTT.FX to simulate a downlink |
![]() |
1.1 | 40 | |
![]() |
5.2 | 41 | [[image:image-20220526142421-4.png]] |
![]() |
1.2 | 42 | |
43 | Use MQTT.FX to simulate downlink | ||
44 | |||
45 | |||
46 | Input connection info | ||
47 | |||
![]() |
10.2 | 48 | [[image:image-20220526142512-5.png]] |
![]() |
1.2 | 49 | |
50 | Input MQTT connection info | ||
51 | |||
52 | |||
53 | Send a downstream | ||
54 | |||
![]() |
10.2 | 55 | [[image:image-20220526142539-6.png]] |
![]() |
1.2 | 56 | |
57 | Gateway traffic for downstream | ||
58 | |||
![]() |
10.2 | 59 | [[image:image-20220526142616-7.png||height="579" width="1407"]] |
![]() |
1.2 | 60 | |
61 | |||
62 | Downstream data flow will like below: | ||
63 | |||
![]() |
10.2 | 64 | [[image:image-20220526142741-8.png]] |
![]() |
1.2 | 65 | |
![]() |
10.2 | 66 | [[image:image-20220526142826-9.png]] |
![]() |
1.2 | 67 | |
![]() |
10.2 | 68 | |
![]() |
1.3 | 69 | = 3. Trouble Shooting = |
![]() |
1.2 | 70 | |
![]() |
1.3 | 71 | == 3.1 Problem when register a device to TTNv3 if it is already register to TTNv2 == |
![]() |
1.2 | 72 | |
73 | When you register the device in V2 and V3 with the same key and EUI, the device can only connect to V2. | ||
74 | |||
![]() |
13.2 | 75 | [[image:image-20220526142914-10.png]] |
![]() |
1.2 | 76 | |
![]() |
13.2 | 77 | [[image:image-20220526143018-11.png||height="619" width="1049"]] |
![]() |
1.2 | 78 | |
79 | If you want the device to connect to V3. You must change your key and EUI, or delete the device registered on V2. | ||
80 | |||
![]() |
13.2 | 81 | |
![]() |
1.3 | 82 | == 3.2 MIC Mismatch or MIC Failed == |
![]() |
1.2 | 83 | |
![]() |
1.3 | 84 | ((( |
![]() |
1.4 | 85 | ((( |
![]() |
1.2 | 86 | When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. |
![]() |
1.3 | 87 | ))) |
![]() |
1.4 | 88 | ))) |
![]() |
1.2 | 89 | |
![]() |
1.3 | 90 | ((( |
![]() |
1.4 | 91 | ((( |
![]() |
1.2 | 92 | Under normal circumstances, users need to change the APPKEY to solve this problem. |
![]() |
1.3 | 93 | ))) |
![]() |
1.4 | 94 | ))) |
![]() |
1.2 | 95 | |
![]() |
13.2 | 96 | [[image:image-20220526143057-12.png]] |
![]() |
1.2 | 97 | |
98 | MIC Mismatch |