> 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/rx-lorawan/configuration/tx-config-tab.md).
# TX CONFIG tab
The TX CONFIG tab is the central area for declaring, configuring, and managing your LoRaWAN sensor fleet. It natively supports Enless Wireless brand sensors as well as third-party sensors (external brands) through the creation of custom profiles.
The TX CONFIG tab has two subtabs: **Add sensors** and **Sensor library**.
## Add sensors tab
### Enless sensors
From this section, you can add Enless sensors using the add button.\
You will then find each declared Enless sensor in the table in the Enless sensors section.
#### Enless sensor add form
When manually adding an Enless sensor, the following information must be entered:
1. **Profile** : Select the corresponding Enless sensor model (e.g.: `600-051 | TX T&H AMB`). The selected profile automatically adjusts the decoding options.
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 you to physically identify the sensor's location in the building (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 selected profile, this section unlocks specific parameters (alert thresholds, special operating mode, etc.).
Finish adding the sensor by clicking the **Add**.
### Enless sensors
From this section, you can add third-party sensors using the add button.\
You will then find each declared Enless sensor in the table in the Enless sensors section.
#### Third-party sensor add form
When manually adding a third-party sensor, the following information must be entered:
1. **Profile** : Select the corresponding third-party sensor model (e.g.: `MClimate 16A`). By default, the LoRaWAN gateway does not include pre-built third-party sensor profiles. The selected profile automatically adjusts the decoding options. \
It is also possible to **+ Create a sensor profile**
2. **DEVEUI** : Unique 16-character hexadecimal identifier specific to the sensor.
3. **APPEUI** : Unique 16-character hexadecimal identifier specific to the sensor manufacturer.
4. **APPKEY** : 32-character hexadecimal security key required for LoRaWAN pairing.
5. **Location** : Free text field allowing you to physically identify the sensor's location in the building (e.g.: `DHW room`).
Finish adding the sensor by clicking the **Add**.
## Sensor library tab
The subtabs **Sensor library** contains two sensor lists for the **Enless sensor** and the **Third-party sensor**.
### Enless sensor
This list is preloaded and maintained by Enless. It guarantees the "Plug & Play" operation of the range's products:
* **Profile name** : Product reference (e.g.: `600-034 | TX T&H EXT`).
* **Pairing type** : OTAA (Over-The-Air Activation).
* **LoRa class** & **Version** : Native technical parameters of the sensor.
* Statuses (**Encoder** / **Decoder** / **Mapping**): Confirmation that the profile is complete and operational.
{% hint style="info" %}
These **profiles** are **automatically updated** during firmware version upgrades of the *gateway*.
{% endhint %}
### Third-party sensors
This section lets you create your own profiles for any LoRaWAN sensor on the market.
The table displays the following columns:
* **Profile** : The name of the selected third-party sensor profile (e.g.: `Adeunis TIC Linky single-phase`).
* **LoRa class** & **Version** : Native technical parameters of the sensor.
* **Pairing type** : OTAA (Over-The-Air Activation).
* Statuses (**Encoder** / **Decoder** / **Mapping**): Confirmation that the profile is complete and operational.
* **Actions** :
* **Edit** (Edit icon): Allows you to modify all settings defining a third-party sensor profile.
* **Delete** (Trash icon): Permanently removes the sensor from the Gateway database.
You have two options:
#### 1. Start from existing codecs and mappings
See the page :code: [Third-party sensor decoders](https://enless.gitbook.io/centre-aide/ressources/gateway-lorawan/decodeurs-capteurs-tiers) to access the list of sensors for which decoders are already available.
{% embed url="" %}
#### 2. Develop the codec and mapping yourself
See the page [Codec and Mapping tutorial](/centre-aide/ressources/ressources-en/lorawan-gateway/codec-and-mapping-tutorial.md) from the **Resources** section to learn how to integrate a new sensor by configuring its decoding script and JSON mapping table.
Finish creating the profile with the **Add**.
{% hint style="warning" %}
A **third-party sensor profile** cannot be **deleted** if it is used by one or more **devices** **active** ; you must **absolutely** **delete** all **sensors** **linked** to this profile in the **TX CONFIG** tab before you can remove the profile from your library.
{% endhint %}
---
# 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/rx-lorawan/configuration/tx-config-tab.md?ask=&goal=
```
`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.