> For the complete documentation index, see [llms.txt](https://docs.twtg.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.twtg.io/docs/installation-and-provisioning/provisioning/step-3-add-the-device-to-the-lns.md).

# Step 3: Add the device to the LNS

The steps to provision a device, although similar among every LNS, can differ according to the LoRa Network Server being used. For an up-to-date guide on how to add a device please refer to the documentation of your LNS.

Quick links to the most commonly used LNS are presented next:

* [Actility Thingpark](https://docs.thingpark.com/thingpark-enterprise/7.3/docs/user-guide-tpe/manage-devices/activate-new-devices/manual-provisioning-otaa-devices)
* [Chirpstack](https://www.chirpstack.io/docs/guides/connect-device.html)
* [Loriot](https://docs.loriot.io/display/LNS/Enroll+a+Device)
* [The Things Network & The Things Stack](https://www.thethingsindustries.com/docs/devices/adding-devices/#:~:text=Go%20to%20End%20devices%20in,%C2%AE%20Device%20Repository%20or%20manually.)

Additionally to the security keys, the LNS will require that you provide:

* LoRaWAN specification version
* LoRaWAN regional parameters version
* Region (ISM Band)
* LoRaWAN class

This information can be found in the overview table of the README file in the LoRa Communication folder of each product. Links to said folder for each product are presented as follows:

* [Pressure Gauge (PG)](https://github.com/TWTG-R-D-B-V/neon-product-documentation/tree/main/PG/LoRa%20Communication)
* [Pressure Sensor (PS)](https://github.com/TWTG-R-D-B-V/neon-product-documentation/tree/main/PS/LoRa%20Communication)
* [Temperature Sensor (TS)](https://github.com/TWTG-R-D-B-V/neon-product-documentation/tree/main/TS/LoRa%20Communication)
* [Temperature Transmitter (TT)](https://github.com/TWTG-R-D-B-V/neon-product-documentation/tree/main/TT/LoRa%20Communication)
* [Vibration Sensor (VB)](https://github.com/TWTG-R-D-B-V/neon-product-documentation/tree/main/VB/LoRa%20Communication)
* [Contact Sensor (VS-CS)](https://github.com/TWTG-R-D-B-V/neon-product-documentation/tree/main/VS-CS/LoRa%20Communication)
* [Valve Sensor - Multiturn (VS-MT)](https://github.com/TWTG-R-D-B-V/neon-product-documentation/tree/main/VS-MT/LoRa%20Communication)
* [Valve Sensor - Quarter Turn (VS-QT)](https://github.com/TWTG-R-D-B-V/neon-product-documentation/tree/main/VS-QT/LoRa%20Communication)

{% hint style="info" %}
All our devices use Over The Air Activation (OTAA)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.twtg.io/docs/installation-and-provisioning/provisioning/step-3-add-the-device-to-the-lns.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
