> For the complete documentation index, see [llms.txt](https://enless.gitbook.io/centre-aide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enless.gitbook.io/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan.md).

# RX LORAWAN

<h2 align="center">RX LORAWAN</h2>

<p align="center"><a class="button secondary">Product reference: RX LORAWAN 500-602</a></p>

<p align="center">Designed to communicate with the Enless sensor ecosystem as well as with LoRaWAN sensors from other brands, the Enless LoRaWAN gateway natively converts Enless sensor data into a Modbus table or BACnet objects for seamless availability on your BMS. Integration of third-party sensors is done via decoders and data mapping.</p>

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-circle-info">:circle-info:</i></td><td><h4>Information </h4></td><td>About the Enless LoRaWAN gateway</td><td><a href="/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan/general-information.md">General information</a></td></tr><tr><td><i class="fa-wrench">:wrench:</i></td><td><h4>Installation</h4></td><td>Mounting and installation of the gateway</td><td><a href="/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan/installation.md">Installation</a></td></tr><tr><td><i class="fa-globe-pointer">:globe-pointer:</i></td><td><h4>Configuration</h4></td><td>From the configuration server</td><td><a href="/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan/configuration.md">Configuration</a></td></tr><tr><td><i class="fa-keyboard-brightness">:keyboard-brightness:</i></td><td><h4>LEDs</h4></td><td>Behavior of the gateway LEDs</td><td><a href="/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan/led-behavior.md">LED behavior</a></td></tr><tr><td><i class="fa-screwdriver-wrench">:screwdriver-wrench:</i></td><td><h4>Controls</h4></td><td>Physical and manual interfaces</td><td><a href="/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan/commands.md">Commands</a></td></tr><tr><td><i class="fa-comment-question">:comment-question:</i></td><td><h4>Troubleshooting</h4></td><td>Frequently asked questions</td><td><a href="/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

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

```
GET https://enless.gitbook.io/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan.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 `build a script that syncs our docs to a CMS` 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.