> 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/sensor-data/air-quality-sensor-power-requirements.md).

# Air Quality Sensor Power Requirements

Learn about the PoE requirements for Verkada Sensors

Verkada [Environmental Sensors](https://docs.verkada.com/docs/sensors-quick-start-guide.pdf) use industry-standard 802.3af (Power over Ethernet \[PoE]). The average bandwidth consumption is less than 5 kbps. Verkada [Air Quality Sensors](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) may consume additional power when performing operations, such as firmware upgrades or initial calibration.

The table reflects the maximum power draw for a particular sensor model within the normal temperature.

{% hint style="info" %}
We recommended to provide an additional power budget on your switch for the sum of all of your sensors.
{% endhint %}

|                                                                        |                                |
| ---------------------------------------------------------------------- | ------------------------------ |
| **Model**                                                              | **Normal Operation (802.3af)** |
| [SV11](https://www.verkada.com/sensors/sv11/)                          | 4W                             |
| [SV21](http://sv21)                                                    | 3W                             |
| [SV23](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) | 3W                             |
| [SV25](https://docs.verkada.com/docs/air-quality-sensors-overview.pdf) | 3W                             |


---

# 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/sensor-data/air-quality-sensor-power-requirements.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.