> 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/expert-center/es/vehicle-telematics-technology/vehicle-sensors.md).

# Sensores del vehículo

Los sensores telemáticos inalámbricos para el monitoreo de Flota usan Bluetooth Low Energy y frecuencias UHF para transmitir TPMS, temperatura y otras lecturas.

Esta sección cubre los sensores inalámbricos utilizados junto con dispositivos GPS para recopilar datos adicionales de la Flota, incluido cómo los sensores BLE y UHF transmiten lecturas de TPMS, temperatura y ambientales a la plataforma.

## Contenido

* [Sensores inalámbricos de telemática](/docs/expert-center/es/vehicle-telematics-technology/vehicle-sensors/wireless-telematics-sensors.md): Cómo los sensores BLE y UHF usan los protocolos GATT/ATT para transmitir telemetría de la Flota a dispositivos GPS.


---

# 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/expert-center/es/vehicle-telematics-technology/vehicle-sensors.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.