You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: doc/content/api/concepts/lora-gateway/_index.md
+4-6
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
-
title: "LoRaWAN® Gateway specific APIs"
2
+
title: "LoRa® Gateway specific APIs"
3
3
description: ""
4
4
weight: 5
5
5
---
6
6
7
-
{{% tts %}} supports multiple LoRaWAN® gateway protocols which communicate the respective APIs.
7
+
{{% tts %}} supports multiple LoRa® gateway protocols which communicate the respective APIs.
8
8
9
9
<!--more-->
10
10
@@ -36,15 +36,13 @@ To communicate with the MQTT protocol, the Gateway Server and the gateway are ex
36
36
37
37
### MQTT v2
38
38
39
-
The MQTT v2 gateway APIs follows the [multi packet forwarder](https://github.com/kersing/packet_forwarder) reference.
40
-
41
-
Check the [protocol reference](https://github.com/kersing/packet_forwarder/blob/master/PROTOCOL.TXT) for more details.
39
+
The MQTT v2 gateway APIs are used by [The Things Kickstarter Gateway]({{< ref "/gateways/models/thethingskickstartergateway">}}) and use the [TTN v2 MQTT](https://github.com/TheThingsNetwork/lorawan-stack/blob/master/pkg/gatewayserver/io/mqtt/format_protobufv2.go) format.
42
40
43
41
### MQTT v3
44
42
45
43
The MQTT v3 protocol uses the {{% tts %}} v3 messages definitions.
46
44
47
-
Gateways can connect using the username `{gateway-id}@{tenant-id}` and an API key as the password. Check how to [register a gateway and create an API key]({{< ref "http://localhost:1313/gateways/concepts/adding-gateways/">}}).
45
+
Gateways can connect using the username `{gateway-id}@{tenant-id}` and an API key as the password. Check how to [register a gateway and create an API key]({{< ref "/gateways/concepts/adding-gateways/">}}).
Copy file name to clipboardexpand all lines: doc/content/api/concepts/troubleshooting/_index.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -24,17 +24,17 @@ Unlike other server components, the Identity Server component of {{% tts %}} is
24
24
25
25
This error indicates that the client HTTP protocol version is old, so the server refuses to perform the request and requires a client update to HTTP 1.1 version or higher.
26
26
27
-
###### "No_application_rights" or "No_user_rights" error
27
+
###### "no_application_rights" or "no_user_rights" error
28
28
29
29
The API key you are using doesn't have sufficient rights to perform the desired API request. It might also be caused by a missing `Bearer` keyword in the `Authorization` header used in the API call.
30
30
31
31
To resolve this issue, make sure your API key has necessary rights to interact with the desired entity. Also, make sure to use the `Bearer` keyword when specifying the `Authorization` header.
32
32
33
-
###### "Api_key_not_found" error
33
+
###### "api_key_not_found" error
34
34
35
35
This error indicates that the specified API key used for the API call is not valid or doesn't exist at all. Double-check that the API key you provided is correct and still valid. If it is expired, you can generate a new API key and update your API call request with the new one.
36
36
37
-
###### "Unauthenticated" error
37
+
###### "unauthenticated" error
38
38
39
39
This error occurs when the API request is made without proper authentication credentials. Make sure to include the correct API key in the authentication request header.
@@ -106,7 +106,7 @@ You can also pass `--with-session` to have a session generated.
106
106
107
107
{{< /tabs/tab >}}
108
108
109
-
{{< tabs/tab "HTTP(REST) API" >}}
109
+
{{< tabs/tab "HTTP(REST) API" >}}
110
110
111
111
{{% tts %}} stores end device data on the Identity Server, Application Server, Network Server. Since ABP devices do not have the concept of join, the Join Server is not used.
Copy file name to clipboardexpand all lines: doc/content/gateways/concepts/adding-gateways/_index.md
+16-16
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Do not follow this guide for a [The Things Indoor Gateway]({{< ref "/gateways/mo
22
22
23
23
If your {{% tts %}} deployment is connected to [Packet Broker]({{< ref "the-things-stack/packet-broker" >}}), you can take advantage of coverage from The Things Network without adding any gateways of your own. See the community sourced [TTN Mapper](ttnmapper.org) to find out if your location has nearby gateways.
Some gateways require an API Key with Link Gateway Rights to be able to connect to {{% tts %}}. In this section we explain how to create an API key with this right, but the procedure of creating an API key is identical for any other right as well.
@@ -412,7 +412,7 @@ To adjust the antenna gain of a gateway with ID `my-test-gateway` on `thethings.
412
412
"field_mask": {
413
413
"paths": ["antennas"]
414
414
}
415
-
415
+
}
416
416
```
417
417
418
418
The request using `cURL` is as follows.
@@ -436,7 +436,7 @@ Once a gateway has been added, get started with [Adding Devices]({{< ref "/devic
436
436
437
437
In deployments connected to [Packet Broker]({{< ref "/the-things-stack/packet-broker" >}}), you can control if you want uplinks received by your gateway to be forwarded to Packet Broker or not. In these deployments, uplinks received by your gateway are being forwarded to Packet Broker by default, but you can choose to disable this behavior.
Copy file name to clipboardexpand all lines: doc/content/gateways/concepts/udp/_index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ If `debug_conf.json` exists, the other files are ignored - otherwise, the parame
19
19
20
20
An example `global_conf.json` is available in the [{{% udp-pf %}} Github repository](https://github.com/Lora-net/packet_forwarder/blob/master/lora_pkt_fwd/global_conf.json). It is also possible to download a `global_conf.json` configured with your Gateway EUI and Frequency Plan directly from {{% tts %}}.
21
21
22
-
{{< tabs/container "Console" "HTTP(REST) API" >}}
22
+
{{< tabs/container "Console" "HTTP(REST) API" >}}
23
23
24
24
{{< tabs/tab "Console" >}}
25
25
@@ -31,7 +31,7 @@ To download a `global_conf.json` file for your gateway, open the Gateway overvie
@@ -113,7 +113,7 @@ End devices are also created within applications. See [Adding Devices]({{< ref "
113
113
114
114
Some applications require an API Key to write downlink traffic, read uplink traffic, manage integrations, etc. In this section we explain how to create an application API key on some basic examples, but this procedure is identical for any other right as well.
0 commit comments