> 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/vehicle-sensors/discrete-sensors/doors-trunk-and-hood-sensor.md).

# Doors, trunk, and hood sensor

Set up door, trunk, and hood sensors for vehicles that transmit this data via the CAN bus. The platform logs open status events as they arrive from the device.

Track the open/closed status of doors, trunk, and hood for vehicles that transmit this data over the CAN bus.

## Availability

Available on devices and vehicles that report door, trunk, and hood status via the CAN bus.

## Setup

No special configuration is required. However, several factors need to be considered.

First, not all car models transmit this information via the CAN bus. Unfortunately, you can only learn it by testing or requesting detailed documentation from the manufacturer.

Second, due to some peculiarities of the device's data transfer protocol, you aren't able to track the status of doors, etc., until Navixy receives the **Open** status at least once. For correct operation, leave the trunk, hood, and all doors open for several minutes with the engine running.


---

# 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/vehicle-sensors/discrete-sensors/doors-trunk-and-hood-sensor.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.