> 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/external-sensors/bluetooth.md).

# Bluetooth

Manage the Bluetooth connection on a GPS device in Navixy with the Bluetooth block, used to pair accessories such as a driver-ID key.

Manages the device's Bluetooth connection for driver identification. The device identifies the driver by their phone over Bluetooth when the ignition is switched on.

## Settings

* **Enable or disable Bluetooth**: turn the device's Bluetooth radio on or off.
* **Add phone**: store a phone's Bluetooth address on the device for driver identification.
* **Clear phone list**: remove all paired phones from the device.

## Availability

Appears on device models that expose Bluetooth pairing controls.

## See also

* [Bluetooth sensors](/docs/user/guide/devices-and-settings/device-specific-controls/external-sensors/bluetooth-sensors.md): map Bluetooth sensor channels to platform sensors.


---

# 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/external-sensors/bluetooth.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.
