> 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/ja/sensdta.md).

# センサーデータ

- [空気質センサーの測定値](https://help.verkada.com/air-quality/ja/sensdta/air-quality-sensor-readings.md): Verkada 空気質センサーの読み取り値を理解する
- [空気質センサーデータを表示](https://help.verkada.com/air-quality/ja/sensdta/view-air-quality-sensor-data.md): Verkada 空気質センサーのデータ読み取り値について詳しく学ぶ
- [空気質センサーの設定](https://help.verkada.com/air-quality/ja/sensdta/air-quality-sensor-settings.md): 空気質センサーの設定を変更する方法を学ぶ
- [センサーダッシュボードを管理](https://help.verkada.com/air-quality/ja/sensdta/manage-your-sensor-dashboard.md): センサーダッシュボードの設定、表示、変更、共有、削除の方法を学ぶ
- [空気質センサーのステータスLED](https://help.verkada.com/air-quality/ja/sensdta/air-quality-sensor-status-led.md): Verkadaセンサーには、状況をひと目で把握できるステータスLEDがあります
- [空気質センサーの電源要件](https://help.verkada.com/air-quality/ja/sensdta/air-quality-sensor-power-requirements.md): VerkadaセンサーのPoE要件について学ぶ
- [ベイプ検知のベストプラクティス](https://help.verkada.com/air-quality/ja/sensdta/best-practices-for-vape-detection.md): ベイピング活動を正確に検出する方法を学ぶ
- [一酸化炭素を検出して理解する](https://help.verkada.com/air-quality/ja/sensdta/detect-and-understand-carbon-monoxide.md): 一酸化炭素の値は一目で見ると怖く感じることがあります。この記事はCOイベントの意味を理解するのに役立ちます
- [SV25での音声録画](https://help.verkada.com/air-quality/ja/sensdta/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/ja/sensdta.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.