> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/air-quality/es/datos-del-sensor/air-quality-sensor-status-led.md).
# LED de estado del sensor de calidad del aire
Los sensores Verkada tienen un LED de estado para que sepas qué está pasando de un vistazo
Cada Verkada [sensor de calidad del aire](https://www.verkada.com/air-quality/sensors#overview) está equipado con una luz LED exterior. Esta luz indica su estado operativo. Verkada ofrece la [SV11](https://www.verkada.com/sensors/sv11/) serie y la serie SV20 (incluida [SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf), [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf), [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf)).
***
## serie SV20
La nueva serie SV20 ([SV21](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf), [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf), [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf)) utiliza un indicador LED blanco; sin embargo, su estado es análogo al del LED azul en la SV11.
## serie SV11
La [SV11](https://www.verkada.com/sensors/sv11/) serie sigue la misma convención de LED que todas las cámaras Verkada.
---
# 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://help.verkada.com/air-quality/es/datos-del-sensor/air-quality-sensor-status-led.md?ask=&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.
