> 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/activation-procedure/enless-lorawan-gateway.md).

# Enless LoRaWAN gateway

TX T\&H MINI AMB: Enless LoRaWAN gateway

Let's see here how to use your TX T\&H MINI AMB with the **Enless LoRaWAN Gateway**.

{% hint style="warning" %}
If you have not yet gotten familiar with your **LoRaWAN Gateway**, first consult the [installation guide](/centre-aide/guides-installation/documentation-en/gateway-and-receivers/rx-lorawan.md) for the LoRaWAN gateway (ref: RX LORAWAN 500-602)
{% endhint %}

## Declare the sensor

Log in to the configuration interface of your **LoRaWAN Gateway** and go to the **TX CONFIG tab**.

When adding a sensor manually, the following information must be entered:

1. **Profile** : Select the corresponding Enless sensor model (`600-050 | TX T&H MINI AMB`). 
2. **DevEUI** : Unique 16-character hexadecimal identifier specific to the sensor (available on the product label and in the QR Code).
3. **AppKey** : 32-character hexadecimal security key required for LoRaWAN pairing (available on the product label and in the QR Code).
4. **Location** : Free text field allowing the sensor's physical location in the building to be identified (e.g. `Office 202 - 2nd floor`).
5. **Interval** : Defines the desired periodicity in minutes between two data transmissions (*uplinks*).
6. **Advanced Settings** : Depending on the chosen profile, this section unlocks specific parameters (alert thresholds, special operating mode, etc.).

Finish adding the sensor by clicking the **Add**.

{% hint style="info" %}
The **activation** keys **LoRaWAN** Enless can be provided in the **format** **.csv** by our **Administration** **or** **Sales**. \
Please **contact** <mark style="color:blue;"><adv@enless.fr></mark>&#x20;
{% endhint %}

Once the sensor has been added, it should appear in the Enless sensor list.

## Check that your sensor is indeed in LoRaWAN mode

{% 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%" %}
The switch on the back of the product must be set to **WAN**.

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

## Getting started

Only a few steps remain to get the TX T\&H MINI AMB up and running **:**

{% stepper %}
{% step %}

### Position the sensor at its final location

It is important that you power the sensor where it will be permanently installed.\
**Why is that?** Once powered, the sensor will lock onto a [Spreading Factor](https://enless.gitbook.io/centre-aide/assistance/assistance/utilisation-en-lorawan#quest-ce-quun-spreading-factor) suited to its distance from the gateway. If you power your sensor too close to the gateway, then move it away later to install it in its final location, it may keep a low Spreading Factor, and as a result the communication may no longer be established once it is moved away from the gateway. The ideal is for the sensor to lock onto the correct Spreading Factor as soon as it is installed.
{% endstep %}

{% step %}

### Power

Power the TX T\&H MINI AMB by removing the battery insulating tab.
{% endstep %}

{% step %}

### Activation

The TX T\&H MINI AMB will proceed with its activation with the *gateway* Enless; the status LED will flash 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, so there is a risk of frame loss.
* <mark style="color:$danger;">**Red**</mark> : The sensor is not activated. Several possible factors: \
  1\. The switch was not in LoRaWAN position when it was activated\
  2\. The DevEUI and AppKey keys were not entered correctly\
  3\. The sensor is too far from the *gateway.*
  {% endstep %}

{% step %}

### Operation

After activation, the LED flashes let you monitor the sensor's 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 with each frame transmission 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 an alarm</td></tr></tbody></table>
{% endstep %}

{% step %}

### Installation

Once the TX T\&H MINI AMB is properly activated, all that remains is to install it on the wall:

* With the supplied adhesive.
* By screwing on the backplate (screws and wall plugs not supplied).
  {% endstep %}
  {% endstepper %}

## Connectivity management

TX sensors incorporate connectivity management mechanisms to ensure the reliability and optimization of communications with the LoRaWAN gateway.

**Join Requests (Activation procedure)**

* **Initialization** : The sensors automatically initiate a *Join* procedure as soon as they are powered on.
* **Link check** : In nominal operation, the sensor sends a control request (LinkCheckReq) every 37 hours.
* **Maintaining the link** : To confirm the validity of the session, the sensor must receive LinkCheckAck responses from the network.
* **Automatic reactivation** : In the event of a prolonged failure (if 6 *LinkCheckReq* requests in a row receive no response), 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 retains 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 consumption and bandwidth.

Go to the [Usage](/centre-aide/guides-installation/documentation-en/sensors/editor/use.md) to learn more about the sensor's 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/activation-procedure/enless-lorawan-gateway.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.