> 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-5/troubleshooting.md).

# Troubleshooting

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

<p align="center">Need help with your TX WINDOW? 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">Access 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 switch is set to LoRa mode before powering the sensor.&#x20;

If this is not the case:

1. Set the switch or jumper to LoRa position (position 0)
2. Press the push button so that the mode change is taken into account.

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

</details>

<details>

<summary><strong>I don't detect any change in state with the magnet</strong></summary>

The minimum distance between the sensor and the magnet housing must be 2 cm.\
Make sure to respect this distance so that the change in state is correctly taken into account.&#x20;

{% hint style="info" %}
When a state change is detected, a frame is sent by the TX WINDOW and its orange LED lights up.
{% endhint %}

</details>

<details>

<summary><strong>How do I decode the battery status of my sensor in the LoRa Easy receiver 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 read value 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 the battery status of my sensor in the BACnet objects of the 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 should be planned)

</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 switch is set to WAN mode before powering the sensor.&#x20;

<div align="left" data-with-frame="true"><figure><img src="/files/5174a7f6b91072abaf9d54644c49488ba669845c" alt="" width="188"><figcaption></figcaption></figure></div>

{% hint style="info" icon="circle-info" %}
The **change** of the switch position is **taken into account** only when the product is **unpowered**. Make sure your product is completely unpowered before setting the switch.&#x20;
{% endhint %}

{% hint style="warning" %}
You must declare the sensor by entering its LoRaWAN keys on your network backend or on your gateway interface **BEFORE connecting the battery**.
{% endhint %}

</details>

<details>

<summary><strong>Decoding the frames of my sensor 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>Which port should downlinks be sent to in LoRaWAN?</strong></summary>

Downlinks should be sent to 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 low 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 transmission is slower and consumes more energy. It can be compared to a person 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 the transmission period of my sensor in LoRaWAN mode?</strong></summary>

Changing the transmission frequency of a LoRaWAN transmitter 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 transmission period 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 transmission period 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 the new period into account will be generated. Please copy this downlink and paste it into the appropriate field on your gateway. Downlinks should be sent to **port 1**.&#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 simply need to remove it from the old LoRaWAN network, then declare it on the new LoRaWAN network.

Indeed, every 24 hours, transmitters send a LinkCheckReq message that must be confirmed by a LinkCheckAck from the network. As long as 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 LoRaWAN network access phase that allows network parameters to be dynamically renewed 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-5/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.
