> 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/configuration/configure-doors-as-alarm-triggers/configure-door-held-open-dho-alarm-triggers-for-wired-and-wireless-door-sensors.md).

# Configurer les déclencheurs d’alarme de porte maintenue ouverte (DHO) pour les capteurs de porte filaires et sans fil

{% hint style="success" %}
Cet article est un guide pour les nouvelles alarmes. Voir [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 %}

Le délai Door Held Open (DHO) déclenche une alarme lorsqu’une porte reste ouverte plus longtemps que la durée configurée. L’alarme s’active uniquement après que la porte est restée ouverte pendant au moins le temps spécifié.

***

## Configuration

{% stepper %}
{% step %}
**Dans Verkada Command, accédez à Tous les produits > Alarmes.**
{% endstep %}

{% step %}
**Sélectionnez votre site d’alarme.**
{% endstep %}

{% step %}
**Dans la navigation de gauche, cliquez sur Appareils.**
{% endstep %}

{% step %}
**Sélectionnez le capteur de porte filaire ou sans fil pour ouvrir sa page de détails.**
{% endstep %}

{% step %}
**Sous Délai Door Held Open, choisissez une durée de délai.**
{% endstep %}
{% endstepper %}

**Options de délai disponibles :** 30 secondes, 60 secondes, 5 minutes, 10 minutes.

{% hint style="warning" %}
L’alerte DHO reste comme *Porte ouverte* jusqu’à ce que la porte soit fermée.
{% 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/configuration/configure-doors-as-alarm-triggers/configure-door-held-open-dho-alarm-triggers-for-wired-and-wireless-door-sensors.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.