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

# Sensor pintu, bagasi, dan kap mesin

Atur sensor pintu, bagasi, dan kap mesin untuk Kendaraan yang mengirimkan data ini melalui bus CAN. Platform mencatat peristiwa status terbuka saat diterima dari perangkat.

Lacak status terbuka/tertutup pintu, bagasi, dan kap mesin untuk kendaraan yang mengirimkan data ini melalui bus CAN.

## Ketersediaan

Tersedia pada perangkat dan kendaraan yang melaporkan status pintu, bagasi, dan kap mesin melalui bus CAN.

## Penyiapan

Tidak diperlukan konfigurasi khusus. Namun, beberapa faktor perlu dipertimbangkan.

Pertama, tidak semua model mobil mengirimkan informasi ini melalui bus CAN. Sayangnya, Anda hanya dapat mengetahuinya dengan menguji atau meminta dokumentasi terperinci dari produsen.

Kedua, karena beberapa kekhasan pada protokol transfer data perangkat, Anda belum dapat melacak status pintu, dll., sampai Navixy menerima **Buka** status setidaknya sekali. Agar berfungsi dengan benar, biarkan bagasi, kap mesin, dan semua pintu tetap terbuka selama beberapa menit dengan mesin menyala.


---

# 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/id/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.