> 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/qna/using-navixy/parking-detection-0-km-h-max-idle-speed.md).

# Parking detection 0 km/h max idle speed

Set maximum idle speed above 0 km/h in Parking Detection to classify vehicles as parked; a value of 0 disables parking detection entirely

## Question

What happens if the max idle speed is set to 0 km/h in the Parking Detection configuration?

## Answer

If the idling speed is set to 0 km/h, the platform's logic requires receiving a speed lower than 0 km/h in order to classify the status as parked. This is impossible because devices never send negative speeds.

As a result, setting the threshold to 0 km/h negatively affects route processing:

* The platform can't separate trips by parking events.
* The unit always appears as "moving" (movement arrow), even when it is actually parked.

Therefore, setting the idle speed threshold to 0 km/h is not recommended.

For this reason, we recommend:

* Checking the motion sensitivity settings on the device.
* Possibly escalating the issue to the manufacturer, so they can help improve movement-detection accuracy.


---

# 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/qna/using-navixy/parking-detection-0-km-h-max-idle-speed.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.