Changes for page Notes for TTN
Last modified by Mengting Qiu on 2024/08/20 17:29
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 9 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -265,6 +265,8 @@ 265 265 ((( 266 266 ((( 267 267 We take LES01 as an example. 268 + 269 + 268 268 ))) 269 269 ))) 270 270 ... ... @@ -288,10 +288,11 @@ 288 288 ))) 289 289 ))) 290 290 291 -[[image:image-2022052 5090739-16.png]]293 +[[image:image-20220526140015-17.png]] 292 292 293 -[[image:image-2022052 5090833-17.png]]295 +[[image:image-20220526140044-18.png]] 294 294 297 + 295 295 == 4.2 Step2 == 296 296 297 297 ((( ... ... @@ -300,20 +300,23 @@ 300 300 ))) 301 301 ))) 302 302 303 -[[image:image-2022052 5090920-18.png]]306 +[[image:image-20220526140132-19.png]] 304 304 308 + 305 305 == 4.3 Step3 == 306 306 307 307 Add APP EUI in the application: 308 308 309 -[[image:image-2022052 5091022-19.png]]313 +[[image:image-20220526140205-20.png]] 310 310 315 + 311 311 == 4.4 Step4 == 312 312 313 313 Add APP KEY and DEV EUI: 314 314 315 -[[image:image-2022052 5091128-20.png]]320 +[[image:image-20220526140251-21.png]] 316 316 322 + 317 317 = 5. TTN V3 integrated into MQTT server = 318 318 319 319 == 5.1 Introduction == ... ... @@ -321,6 +321,8 @@ 321 321 ((( 322 322 ((( 323 323 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. 330 + 331 + 324 324 ))) 325 325 ))) 326 326 ... ... @@ -344,12 +344,12 @@ 344 344 ))) 345 345 ))) 346 346 347 -[[image:image-2022052 5091251-22.png]]355 +[[image:image-20220526140347-22.png]] 348 348 349 349 Fill in the username and password into MQTT. 350 350 351 351 352 -[[image:image-2022052 5091333-23.png]]360 +[[image:image-20220526140420-23.png]] 353 353 354 354 The Application Server publishes uplink traffic on the following topics: 355 355 ... ... @@ -372,7 +372,7 @@ 372 372 ))) 373 373 ))) 374 374 375 -[[image:image-2022052 5091430-24.png]]383 +[[image:image-20220526140452-24.png]] 376 376 377 377 ((( 378 378 ((( ... ... @@ -380,7 +380,7 @@ 380 380 ))) 381 381 ))) 382 382 383 -[[image:image-2022052 5091458-25.png]]391 +[[image:image-20220526140708-25.png]] 384 384 385 385 ((( 386 386 ((( ... ... @@ -400,7 +400,7 @@ 400 400 ))) 401 401 ))) 402 402 403 -[[image:image-2022052 5091618-27.png]]411 +[[image:image-20220526140856-26.png]] 404 404 405 405 ((( 406 406 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:
- image-20220526140044-18.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +42.0 KB - Content
- image-20220526140132-19.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +60.2 KB - Content
- image-20220526140205-20.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.6 KB - Content
- image-20220526140251-21.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +67.9 KB - Content
- image-20220526140347-22.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +63.0 KB - Content
- image-20220526140420-23.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.4 KB - Content
- image-20220526140452-24.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.4 KB - Content
- image-20220526140708-25.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +827.1 KB - Content
- image-20220526140856-26.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +114.9 KB - Content