> 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/sensors/editor-2/activation-procedures/other-lorawan-networks-public-or-private.md).

# Other LoRaWAN networks (public or private)

TX T\&H E-INK AMB: other LoRaWAN networks (public or private)

The sensor is compatible with **public LoRaWAN networks** and **private ones**. To make the most of it, here are the items you will need.

## Declare the sensor

### Activation

Your transmitter activates via Over-The-Air (**OTAA**) only thanks to its three identification keys.

<table data-header-hidden><thead><tr><th width="142.73046875">Information</th><th>Description</th></tr></thead><tbody><tr><td><strong>DevEUI</strong></td><td>Unique identifier, 64 bits (8 bytes / 16 hexadecimal characters). Example: <code>00:18:B2:00:00:00:00:01</code></td></tr><tr><td><strong>AppEUI</strong></td><td>Global identifier designating the entity responsible for activation, 64 bits (8 bytes / 16 hexadecimal characters). Example: <code>70:B3:D5:7E:D0:00:AF:12</code></td></tr><tr><td><strong>AppKey</strong></td><td>Symmetric encryption key, 128 bits (16 bytes / 32 hexadecimal characters). Example: <code>2B7E151628AED2A6ABF7158809CF4F3C</code></td></tr></tbody></table>

{% hint style="info" %}

#### Where can I find the keys?

The LoRaWAN keys for Enless sensors are available:

* By scanning the **QR Code** stuck on the sensor
* On **the rear label** of the sensor
* On **request** from our **Administration** **Sales** **<adv@enless.fr>** ([Decoding](mailto:adv@enless.fr))
  {% endhint %}

### Enless Wireless provides various

codecs **to decode the** uplinks *from your transmitter, but also to generate* downlinks *to send to it.* Cover image

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Chirpstack codecs</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Check that your sensor is indeed in LoRaWAN mode</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FJm3c35o45CIeSV4UjUbO%2FExcel.png?alt=media&amp;token=c7782215-6330-442b-8d15-170cd8454d89">Excel.png</a></td><td><a href="/centre-aide/ressources/ressources-en/lora-sensors/codecs-and-decoding/frame-decoding-excel.md">Frame decoding Excel</a></td></tr><tr><td>Multitech AP Conduit BACnet codecs</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FIZLJqJvCIfA5eQWthJw2%2FJavaScript%20logo.png?alt=media&amp;token=d2b2f7a7-dbb3-4482-adc9-2235705c5a34">JavaScript logo.png</a></td><td><a href="/centre-aide/ressources/ressources-en/lora-sensors/codecs-and-decoding/javascript.md">JavaScript</a></td></tr><tr><td>JavaScript codecs</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2Fwuo7aIDanOoVbtqvmnmJ%2FTTN%20logo.png?alt=media&amp;token=9f62d382-e42a-4757-b5a2-932a8857896f">TTN logo.png</a></td><td><a href="/centre-aide/ressources/ressources-en/lora-sensors/codecs-and-decoding/ttn.md">TTN</a></td></tr><tr><td>TTN codecs</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FdRTJjmfwze4EOPD7RDqz%2FLogo%20chirpstack.png?alt=media&amp;token=70928d52-ec93-4f42-b131-0398c9031728">Logo chirpstack.png</a></td><td><a href="/centre-aide/ressources/ressources-en/lora-sensors/codecs-and-decoding/chirpstack.md">Chirpstack</a></td></tr><tr><td>Excel file for frame decoding</td><td><a href="https://1715332350-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3HoPKoOlgG9Qj4E6fu0w%2Fuploads%2FKTmkmRqvbYRapju84C2V%2FLogo%20Multitech.png?alt=media&amp;token=e0ebe62c-5d3d-401e-b480-0c347c970d15">Logo Multitech.png</a></td><td><a href="/centre-aide/ressources/ressources-en/lora-sensors/codecs-and-decoding/multitech-ap-conduit-bacnet.md">Multitech AP Conduit BACnet</a></td></tr></tbody></table>

## The switch located on the back of the product must be set to

{% columns %}
{% column width="41.66666666666667%" %}

<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%2F6ctqxhvWKF7fiDq9Sjkg%2FSwitch%20wan.png?alt=media&amp;token=81f8fbd3-c126-4b11-976a-bddab0c4fed1" alt=""><figcaption></figcaption></figure></div>
{% endcolumn %}

{% column width="58.33333333333333%" %}
WAN **The**.

{% hint style="info" icon="circle-info" %}
switch **position change** is only **taken into account** when the product is **powered off**. Make sure your product is completely powered off before setting the switch to the position **The**.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

## Getting started

Only a few steps remain to get the sensor up and running **:**

{% stepper %}
{% step %}

### Power supply

Power the sensor by removing the tab insulating the battery.
{% endstep %}

{% step %}

### Activation

The sensor will proceed with activation on your LoRaWAN network; the status LED will flash and then take on one of the following three colors for 30 seconds:

* <mark style="color:$success;">**Green**</mark> : The sensor is activated.
* <mark style="color:$warning;">**Orange**</mark> : The sensor is activated but the RSSI is low
* <mark style="color:$danger;">**Red**</mark> : The sensor was not activated. There may be several reasons:\
  1\. Check that the switch was in the LoRaWAN position\
  2\. Check that the DevEUI, AppEUI and AppKey keys were correctly declared.
  {% endstep %}

{% step %}

### Operation

After activation, the LED flashes let you monitor the sensor status:

<table data-header-hidden><thead><tr><th width="134.90625"></th><th></th></tr></thead><tbody><tr><td><mark style="color:$success;"><strong>Green</strong></mark></td><td>Flash every minute</td></tr><tr><td><mark style="color:$warning;"><strong>Orange</strong></mark></td><td>Flash each time a frame is sent from the push button</td></tr><tr><td><mark style="color:$danger;"><strong>Red</strong></mark></td><td>Flash every 1 min in case of alarm</td></tr></tbody></table>
{% endstep %}

{% step %}

### Installation

Once the sensor is correctly activated on the network, all that remains is to install it on the wall:

* With the supplied adhesive.
* By screwing the back plate in place (screws and wall plugs not supplied).
  {% endstep %}
  {% endstepper %}

## Network connectivity management

Enless sensors include advanced connectivity management mechanisms to ensure the reliability and optimization of communications on the LoRaWAN network.

**Join Requests (Activation procedure)**

* **Initialization** : The sensors automatically initiate a procedure for *Join* as soon as they are powered on.
* **Link check** : In normal operation, the sensor sends a control request (LinkCheckReq) every 37 hours.
* **Link maintenance** : To confirm that the session is valid, the sensor must receive LinkCheckAck responses from the network.
* **Automatic reactivation** : In the event of prolonged failure (if 6 *LinkCheckReq* consecutive requests go unanswered), the sensor considers the session lost and initiates a new *Join*.

**ADR (Adaptive Data Rate)**

* **Initial configuration** : During the first *Join*, the transmitter uses SF12 and BW125 parameters by default.
* **Dynamic optimization** : The sensor keeps these maximum robustness settings as long as it does not receive a LinkADRReq command from the network server (via the gateway) instructing it to adapt its *Spreading Factor* to optimize power consumption and bandwidth.

Go to the [Usage](/centre-aide/guides-installation/documentation-en/sensors/editor-2/use.md) section to learn more about the sensor installation and features.


---

# 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/sensors/editor-2/activation-procedures/other-lorawan-networks-public-or-private.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.