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

# Motion Guard

Enabling the option **Motion Guard** allows **to protect the transmitter against tampering**. 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 **tampering** 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 page **Config** **TX** of the receiver.

If the transmitter was powered on for the first time while this option was disabled, its subsequent activation 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 **battery** then **reconnect it** so that the transmitter receives the new configuration as if it were the first time.
  * Press the **button** of 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 all cases, **a 24-hour delay** is required before the feature *Motion Guard* is 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 **into account** its configuration **automatically** as of its next transmission of*'uplink* data*.*

## In LoRaWAN mode

Enabling the Motion Guard feature requires sending a ***downlink***. In Resources, you will find the tools needed to generate a *downlink* configuration 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 all cases, **a 24-hour delay** is required before the feature *Motion Guard* is 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 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-3/use/motion-guard.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.