> 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/assistance/assistance-en/assistance/using-lora-easy.md).

# Using LoRa Easy

<h2 align="center">Frequently Asked Questions</h2>

<p align="center">Discover the answers to the most frequently asked questions</p>

<p align="center"><a href="/pages/89170fb9963fb77b6468a92c202b64d3b4f5fab0" class="button secondary">All questions</a><a href="https://enless.gitbook.io/centre-aide/assistance/assistance/utilisation-en-lora-easy" class="button primary">Use in LoRa Easy mode</a><a href="https://enless.gitbook.io/centre-aide/assistance/assistance/utilisation-en-lorawan" class="button secondary">Use in LoRaWAN mode</a></p>

<p align="center"></p>

<details>

<summary><strong>What is the power consumption of a LoRa Easy receiver?</strong></summary>

Power consumption is normally less than 50 mA at 12 V. During the sensor installation phase, there may be peaks at 500 mA.

To avoid any problem, please maintain 1 A 12 V on the power terminal block.

</details>

<details>

<summary><strong>Update my LoRa Easy receiver</strong></summary>

The firmware files for LoRa Easy receivers and the update procedure are available in the RESOURCES section: <https://enless.gitbook.io/centre-aide/ressources/recepteurs-lora-easy/fichiers-firmware>

</details>

<details>

<summary><strong>What is the maximum number of simultaneous TCP clients on a LoRa Easy Modbus receiver?</strong></summary>

The Enless receiver acts as a server and can only accept one client at a time. Being queried by another Modbus device may disrupt Modbus communication with the current TCP client.

</details>

<details>

<summary><strong>I have a solid orange LED on my sensor, what does that mean?</strong></summary>

The solid orange L2 LED is characteristic of a low battery level. We invite you to try powering your transmitter with a newer battery to confirm this hypothesis.

</details>

<details>

<summary><strong>I can't connect my sensor to my LoRa Easy receiver</strong></summary>

If you can't connect your sensor to your LoRa Easy receiver, first check that the product's jumper or switch is properly set to LoRa mode before powering the sensor.&#x20;

If not:

1. Power off your sensor
2. Set the switch or jumper to the LoRa position
3. Power the sensor back on

{% hint style="info" %}
Also check that the sensor's LoRa ID has been correctly declared on your receiver.
{% endhint %}

</details>

<details>

<summary><strong>How do I decode my sensor's battery status in the Modbus table of a LoRa Easy receiver?</strong></summary>

The battery status must be decoded in the "Status" register.

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/101009608712/original/f3oC4twesrcDfz6VSMz7jbOY7Yze_y19IA.png?1649261600)

Here, the value read is 0004 (hexadecimal). Convert this hexadecimal value to binary on 16 bits.

0004 (hex) = 00000000 0000**01**00 (binary)

Bits 3 and 2 **in red** are the ones that provide information about the battery level:

**00** = 100%\
**01** = 75%\
**10** = 50%\
**11** = 25%

</details>

<details>

<summary><strong>How do I decode my sensor's battery status in the BACnet objects of a LoRa Easy receiver?</strong></summary>

The battery status must be read in the "Battery level" object.

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/101044873159/original/dwyD7FwhINS0mGB15KqpgXCxAhq0gjjF1Q.png?1669025289)

The battery alert level is given on 4 levels:

**0** = 100% remaining\
**1** = 75% remaining \
**2** = 50% remaining \
**3** = 25% remaining (battery replacement to be planned)

</details>

<details>

<summary><strong>How do I read the statuses (open/closed) of the TX IO inputs and outputs?</strong></summary>

The information regarding the status (open/closed) of the inputs and outputs is given in the Status Registers sheet of the Modbus Table Excel file: [Modbus Table](https://enless.gitbook.io/centre-aide/ressources/recepteurs-lora-easy/table-modbus)

The open/closed statuses of the Ch1 and Ch2 inputs are indicated respectively on bits 4 and 5 of the "Status" register. (0 = open / 1 = closed).

</details>

<details>

<summary><strong>What is the minimum delay between sending two commands to the TX IO?</strong></summary>

The minimum delay between sending two commands to the TX IO is 2 seconds. If you send a second command before this 2-second delay, it will not be taken into account by the TX IO.

</details>

<details>

<summary><strong>What is the consumption of the TX IO?</strong></summary>

The power consumption of the TX IO is normally less than 85 mA at 12 V. During the sending of periodic message frames, there may be peaks at 130 mA.

To avoid any problem, please maintain 1 A 12 V on the power terminal block.

</details>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://enless.gitbook.io/centre-aide/assistance/assistance-en/assistance/using-lora-easy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
