> 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.md).

# Discrete sensors

Discrete sensors report on/off (binary) states from a device input, such as ignition, doors, panic button, engine, alarm, charging, or tamper/detach.

## Availability

Available when the device model has digital inputs.

## Adding a discrete sensor

To add a discrete sensor, click ![Discrete sensor](https://www.navixy.com/wp-content/uploads/2019/06/plus.jpg) and select **Discrete sensor** in the pop-up menu:

Configure the required sensor parameters :

* **Sensor label:** Enter the name of the sensor in the system. You can choose any name you want.
* **Sensor type**: Choose the sensor type.
* **Input**: Enter the number of the terminal input to which you are connecting the sensor.

To confirm your changes, click **Save**.

You can connect discrete sensors and buttons of the following types:

1. Ignition
2. Panic button
3. External power
4. Engine status
5. Car alarm
6. Doors
7. Custom


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/user/guide/devices-and-settings/vehicle-sensors/discrete-sensors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.