> 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/new-alarms/fr/rapports-et-surveillance/alarms-devices-bandwidth-usage.md).

# Utilisation de la bande passante des appareils d’alarme

Utilisation de la bande passante pour les appareils Verkada Alarms

{% hint style="success" %}
Cet article est un guide pour les nouveaux Alarms. Consultez ce [article](/classic-alarms/fr/surveillance-et-rapports/classic-alarms-devices-bandwidth-usage.md) si vous avez des alarmes classiques. Consultez [Nouvelles alarmes vs alarmes classiques](/new-alarms/fr/prise-en-main/new-alarms-vs-classic-alarms.md) si vous ne savez pas quelle version d’alarmes vous avez.
{% endhint %}

## BP52 (boîtier de raccordement)

* Taux de sortie sur 5 minutes : 10 kps
* Taux d’entrée sur 5 minutes : 10 bps

{% hint style="warning" %}
Ces nombres peuvent être plus élevés ou plus faibles selon le nombre de capteurs connectés à un boîtier de raccordement donné, qu’ils soient filaire ou sans fil, et le nombre d’événements que ces capteurs génèrent. D’autres facteurs incluent la mise à jour de BK22/BE32, car cela utilisera davantage de bande passante réseau.
{% endhint %}


---

# 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/new-alarms/fr/rapports-et-surveillance/alarms-devices-bandwidth-usage.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.