> 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/general-information.md).

# General information

<div data-with-frame="true"><figure><img src="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2F3B4JrMma9F0ZKZ578xzy%2FGateway%20banner.png?alt=media&amp;token=d3207db5-70fa-4f92-af27-aff856c8c626" alt=""><figcaption></figcaption></figure></div>

The Enless LoRaWAN gateway is a gateway designed to ensure the collection, decoding, and availability of data from LoRaWAN radio sensors.

A true bridge between LoRaWAN sensors and your BMS, it makes it possible to transform radio frames into data usable by your PLCs and supervisory systems, in Modbus or BACnet (BACnet version available starting October 2026).

## More information

* **Multi-brand Reception** : Native support for the full range of Enless sensors and allows integration of third-party sensors via a library of customizable profiles.
* **Protocol Conversion** : Translates LoRaWAN messages into Modbus RTU (RS485) and/or Modbus TCP/IP registers.
* **Intuitive Configuration Interface** : An embedded web server allows simple, complete configuration as well as real-time diagnostics without third-party software.
* **Offloaded Intelligence** : Thanks to its JavaScript codec engine and its JSON mapping, the *gateway* provides autonomous, local decoding, ensuring low latency and high data reliability.
* The *gateway* acts as a Modbus Server (*Slave*). It keeps a dynamic exchange table in memory where each sensor datum is assigned to a specific register, thus allowing smooth reading by a Modbus Client (*Master*): PLC, Supervisory system, etc.


---

# 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://enless.gitbook.io/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan/general-information.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.