> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/guide/devices-and-settings/device-specific-controls/anti-theft-and-security/accelerometer.md).

# Accelerometer

Configure impact force thresholds on the device so it detects and reports collisions to Navixy. Some models support separate weak and strong impact levels.

Reports an impact when the device detects force above a configured threshold for a configured duration.

## Settings

Some models expose a single threshold; others provide separate **Weak impact** and **Strong impact** thresholds.

* **Force** (weak / strong): the minimum impact force required to register an event. On models with two levels, the weak threshold triggers a low-priority event and the strong threshold triggers a high-priority event.
* **Duration**: how long the force must be sustained to register an impact. Single bumps shorter than this value are ignored.

{% hint style="info" %}
Both values are minimums for detection. A lower value makes the sensor more sensitive.
{% endhint %}

## Availability

Appears on device models with a configurable impact accelerometer.


---

# 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://navixy.com/docs/user/guide/devices-and-settings/device-specific-controls/anti-theft-and-security/accelerometer.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.