> 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/vibration-settings.md).

# Vibration settings

Adjust the device's motion sensor sensitivity to control how tow detection, impact alarms, and stop-time tracking respond to movement

Tunes the device's motion sensor sensitivity. This single setting affects all motion-based features on the device, tow detection, impact alarms, and stop-time tracking, so adjust it with those use cases in mind.

## Settings

* **Sensitivity**: how easily the sensor triggers.
  * **High**: triggers on lighter motion. Use when the vehicle is in a low-vibration environment or when you need to catch small disturbances.
  * **Normal**: the default balance between sensitivity and false alarms.
  * **Low**: requires stronger motion to trigger. Useful for heavy vehicles or rough terrain where normal motion would otherwise cause false alarms.
  * **Very low**: the least sensitive. Use only when frequent false alarms persist at Low.

## Availability

Appears on device models that expose a global motion sensor sensitivity setting.

## See also

* [Vibration detection](/docs/user/guide/devices-and-settings/device-specific-controls/anti-theft-and-security/vibration-detection.md): detect tampering after ignition off.
* [Accelerometer](/docs/user/guide/devices-and-settings/device-specific-controls/anti-theft-and-security/accelerometer.md): set impact force thresholds.
* [Tow detection](/docs/user/guide/devices-and-settings/location-and-movement/tow-detection.md): detect vehicle towing.


---

# 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/vibration-settings.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.