> 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-5/use/motion-guard.md).

# Motion Guard

TX LIGHT PIR T\&H: Motion Guard

Enabling the option **Motion Guard** allows **protection of the transmitter against tearing off**. When a sudden movement occurs, the transmitter detects it thanks to its **built-in accelerometer** and triggers a **tamper alarm**.

{% hint style="success" %}
When a **tear-off** of the transmitter or a **sudden movement** is detected, it immediately sends **immediately** a uplink **frame** notifying the triggering of the**Motion alarm** **Guard**.
{% endhint %}

Below is a detailed explanation of the activation and operation of the Motion Guard feature in **LoRa Easy mode** and in **LoRaWAN mode**.

## With LoRa Easy receivers

The feature **Motion Guard** becomes operational **24 hours after the transmitter is activated**, provided that the Motion Guard option has been **enabled** from the Config **TX** **page** of the receiver.

If the transmitter was powered on for the first time while this option was disabled, enabling it later constitutes a **configuration change**. This change can be taken into account: 

*  **Automatically** if the "New config" feature is enabled when the transmitter is added.
*  **Manually** with the following steps:
  * **Disconnect** the **the battery** then **reconnect it** so that the transmitter receives the new configuration as if it were the first time.
  * Press the **button** on the transmitter for **5 seconds** to simulate a power-off and restart the initialization cycle to receive the new configuration.
  * Enable the "**New configuration**" option (you will find it in the advanced settings), which will allow the transmitter to receive a new configuration every 24 hours.

In any case, **a 24-hour delay** is required before the feature *Motion Guard* becomes fully operational.

## With the *gateway* RX LoRaWAN

From the **TX CONFIG** tab of the LoRaWAN RX, it is possible, when adding or editing a sensor, to enable the **Motion Guard** from the **advanced** **settings**.

The transmitter will **take** its configuration **into account automatically** as soon as its next uplink transmission*'uplink* of data*.*

## In LoRaWAN mode

Enabling the Motion Guard feature requires sending a ***downlink***. You will find in the Resources the tools needed to generate a *downlink* configuration downlink for your TX by clicking on the link below.

{% content-ref url="/spaces/SivuVFNeBsenUAqOB2m6/pages/33137e39f5ffa74c47f9d170409a68b30e04e220" %}
[Codecs and decoding](/centre-aide/ressources/ressources-en/lora-sensors/codecs-and-decoding.md)
{% endcontent-ref %}

{% hint style="info" %}
In any case, **a 24-hour delay** is required before the feature *Motion Guard* becomes fully operational.
{% 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 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-5/use/motion-guard.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.