> 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/ko/sensor-data.md).

# 센서 데이터

- [공기질 센서 측정값](https://help.verkada.com/air-quality/ko/sensor-data/air-quality-sensor-readings.md): Verkada 공기질 센서 판독값 이해하기
- [공기질 센서 데이터 보기](https://help.verkada.com/air-quality/ko/sensor-data/view-air-quality-sensor-data.md): Verkada 공기질 센서 데이터 판독값에 대해 자세히 알아보기
- [공기질 센서 설정](https://help.verkada.com/air-quality/ko/sensor-data/air-quality-sensor-settings.md): 공기질 센서 설정을 변경하는 방법 알아보기
- [센서 대시보드 관리](https://help.verkada.com/air-quality/ko/sensor-data/manage-your-sensor-dashboard.md): 센서 대시보드를 설정, 보기, 수정, 공유 및 삭제하는 방법 알아보기
- [공기질 센서 상태 LED](https://help.verkada.com/air-quality/ko/sensor-data/air-quality-sensor-status-led.md): Verkada 센서에는 상태 LED가 있어 한눈에 상황을 확인할 수 있습니다
- [공기질 센서 전원 요구 사항](https://help.verkada.com/air-quality/ko/sensor-data/air-quality-sensor-power-requirements.md): Verkada 센서의 PoE 요구 사항 알아보기
- [전자담배 감지 모범 사례](https://help.verkada.com/air-quality/ko/sensor-data/best-practices-for-vape-detection.md): 베이핑 활동을 정확하게 감지하는 방법 알아보기
- [일산화탄소 감지 및 이해](https://help.verkada.com/air-quality/ko/sensor-data/detect-and-understand-carbon-monoxide.md): 일산화탄소 수치는 한눈에 보기엔 무서울 수 있습니다. 이 문서는 CO 이벤트의 의미를 이해하는 데 도움이 될 것입니다
- [SV25로 오디오 녹음](https://help.verkada.com/air-quality/ko/sensor-data/audio-recording-with-the-sv25.md): 특수 용도에서 SV25의 오디오 녹음 기능 알아보기


---

# 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/ko/sensor-data.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.