> 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/products/editor-20/troubleshooting.md).

# Troubleshooting

<h2 align="center">Troubleshooting</h2>

<p align="center">Need help with your TX CONTACT + LEAK SPOT? Access our FAQ below or ask your question to the assistant</p>

<p align="center"><button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask your question</button><a href="/spaces/U3XwH6UkADTyDLjIXiu3/pages/89170fb9963fb77b6468a92c202b64d3b4f5fab0" class="button primary">Go to the FAQ</a></p>

<h4 align="center"><i class="fa-arrow-trend-up">:arrow-trend-up:</i> Frequently asked questions</h4>

<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 jumper or switch is correctly 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 make sure that the sensor's LoRa ID has been correctly declared on your receiver.
{% endhint %}

</details>

<details>

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

A 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>How do I decode the contact status of the TX CONTACT + LEVEL PROBE in the LoRa Easy receiver Modbus table?</strong></summary>

The contact status (open or closed) of the TX CONTACT is decoded in the "Status" register, which comes after the "Device type and firmware version" register:

<div align="left"><img src="https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/101009605333/original/VV0PQ37cbASVD1YXY_ZHK9CNRjn6WrcQiQ.png?1649260847" alt=""></div>

The open/closed statuses of inputs Ch1, Ch2, and OC are indicated respectively on bits 5, 6, and 7 (0 = open / 1 = closed).

</details>

<details>

<summary><strong>I can't connect my sensor to my LoRaWAN network</strong></summary>

If you can't connect your transmitter to the network, first check that the jumper is correctly set to LoRaWAN mode before powering the transmitter. The WAN green LED should blink when you power the transmitter. The jumper positions are:

* **LoRaWAN** : a single pin
* **LoRa** **Easy** : two pins

{% hint style="warning" %}
It is essential to declare the transmitter by entering its LoRaWAN keys on your network backend or on your gateway interface **BEFORE connecting the battery**.
{% endhint %}

</details>

<details>

<summary><strong>How do I decode my sensor's battery status in the LoRa Easy receiver's Modbus table?</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 LoRa Easy receiver's BACnet objects?</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>Decoding my sensor's frames when I use it in LoRaWAN mode</strong></summary>

To decode the frames of an Enless LoRaWAN sensor, please use our decoding help tools: <https://enless.gitbook.io/centre-aide/ressources/capteurs/codecs-et-decodage>

</details>

<details>

<summary><strong>On which port should downlinks be sent in LoRaWAN?</strong></summary>

Downlinks should be sent on port number 1.

</details>

<details>

<summary><strong>What is a Spreading Factor?</strong></summary>

The Spreading Factor (SF) in LoRaWAN is used to define how a sensor sends its data. The lower the SF (e.g. SF7), the faster the message is sent, with lower battery consumption, but over a shorter distance. Conversely, a higher SF (e.g. SF12) allows data to be sent much farther, even with obstacles, but the transmission is slower and uses more energy. This can be compared to someone speaking quickly to someone nearby, or slowly and clearly to be heard from far away. The choice of SF is therefore a compromise between radio range, battery life, and transmission speed.

</details>

<details>

<summary><strong>How do I change my sensor's transmission periodicity in LoRaWAN mode?</strong></summary>

Changing the transmission frequency of a transmitter in LoRaWAN is done by Downlink. &#x20;

The Excel file below allows you to decode frames and generate configuration downlinks: <https://enless.gitbook.io/centre-aide/ressources/capteurs/codecs-et-decodage/excel-de-decodage-des-trames>

**Example**: We want to change the periodicity of a 600-023 transmitter to 15 minutes.&#x20;

Step 1: Please open the attached Excel file and go to the sheet for the transmitter in question.&#x20;

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/101093132290/original/C80jBgFLd5kEIM9EQJ_hFcO-8GJhuy2fYw.png?1688571054)

Step 2: Please change the periodicity and press "Enter" to validate.&#x20;

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/101093132675/original/gbZW487hsohW7xQZP8e7LF6gAw1_Re-37w.png?1688571134)

Step 3: A new Downlink taking into account the new periodicity will be generated. Please copy this downlink and paste it into the appropriate field on your gateway. Downlinks should be sent on port **port1**.&#x20;

![](https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/101093133181/original/yhkXgx6lghNz_EZ9y0waXLt-swlt1tpmVw.png?1688571240)

</details>

<details>

<summary><strong>How do I switch from one LoRaWAN network to another?</strong></summary>

To switch a sensor from one LoRaWAN network to another, you do not need to physically intervene on the sensor. You just need to remove it from the old LoRaWAN network, then declare it on the new LoRaWAN network.

Indeed, every 24 hours, the transmitters send a LinkCheckReq message that must be confirmed by a LinkCheckAck from the network. As long as the LinkCheckReq messages are confirmed by a LinkCheckAck, the transmitter will not send a new JOIN. If the transmitters are still declared on the old LoRaWAN network, they remain connected to it. On the other hand, if they are declared on the new LoRaWAN network and are no longer provisioned on the old one, the switch to the new LoRaWAN network takes place.&#x20;

\***JOIN:** this is a network access phase in LoRaWAN that makes it possible to dynamically renew the network parameters between the end device and the LoRa Server.

</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/guides-installation/documentation-en/products/editor-20/troubleshooting.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.
