> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/connectors/lns-connector.md).
# LNS Connector
Activate the built-in LoRaWAN Network Server via the LNS connector — no external LNS to configure, no credentials swap.
Kilo's LNS connector gives your deployment a built-in **LoRaWAN Network Server**: the software that manages communication between LoRaWAN sensors, their radio gateways, and the platform. You can bring sensor readings into dashboards and automation without installing and maintaining a separate network server.
LoRaWAN is the wireless protocol used by the sensors and gateways. Add the LNS connector, connect a compatible **Basics Station** gateway, and register your devices. Kilo handles the network-server side; the gateway provides the radio connection at your site.
## Adding the LNS connector
1. Navigate to **Connectors** in the sidebar.
2. Click **Add connector**.
3. In the **Connector type** dropdown, select **LNS**.
4. Click **Add**.
The connector is created immediately with the name assigned automatically. No additional configuration is needed — the server's LoRaWAN network integration activates for your organization.
Each organization can have only one LNS connector. If your organization already has one, the LNS option will not appear in the dropdown.
## Inside the LNS connector
Click the LNS connector row in the connectors table to open it. The page is a summary — connector type, creation date, connected device count, and when data last arrived — and it states that this connector type has no editable settings. Everything the connector enables is worked on elsewhere in the sidebar:
* **Gateways** — Register and monitor the gateways that carry LoRaWAN traffic. See [LoRaWAN Gateways](/gateways.md).
* **Devices** — Register and manage the devices themselves. See [Registering Devices](/devices/registering-devices.md) and [Device Management](/devices/device-management.md).
## LoRaWAN Reference
The LNS connector uses LoRaWAN — a long-range, low-power wireless protocol designed for IoT. These reference pages cover the protocol, frequency bands, and the built-in network server:
* [What is LoRaWAN?](/connectors/lns-connector/what-is-lorawan.md) — Protocol overview, core benefits, and ideal use cases
* [LoRaWAN Frequencies](/connectors/lns-connector/lorawan-frequencies.md) — Regional frequency bands by country and compliance guidance
* [LoRa 2.4 GHz](/connectors/lns-connector/lora-2g4.md) — The global 2.4 GHz ISM band for cross-border and high-throughput deployments
* [LR-FHSS](/connectors/lns-connector/lr-fhss.md) — Frequency-hopping for massive-scale networks and interference resistance
* [Built-in Network Server](/connectors/lns-connector/built-in-lns.md) — How the integrated LPWAN server eliminates external infrastructure
For the device-level setup, follow [LoRaWAN Devices](/devices/lorawan-devices.md). It covers the physical identifier, connection fields, measurement mapping and checking retained history.
---
# 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.kiloiot.io/connectors/lns-connector.md?ask=&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.
