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

# Configurar disparadores de alarma de puerta mantenida abierta (DHO) para sensores de puerta con cable e inalámbricos

{% hint style="success" %}
Este artículo es una guía para Nuevas alarmas. Consulte [Nuevas alarmas frente a Alarmas clásicas](/new-alarms/es/primeros-pasos/new-alarms-vs-classic-alarms.md) si no está seguro de qué versión de alarmas tiene.
{% endhint %}

El retardo de puerta mantenida abierta (DHO) activa una alarma cuando una puerta permanece abierta más tiempo que la duración configurada. La alarma se activa solo después de que la puerta haya estado abierta durante al menos el tiempo especificado.

***

## Configuración

{% stepper %}
{% step %}
**En Verkada Command, vaya a Todos los productos > Alarmas.**
{% endstep %}

{% step %}
**Seleccione su sitio de alarma.**
{% endstep %}

{% step %}
**En la navegación de la izquierda, haga clic en Dispositivos.**
{% endstep %}

{% step %}
**Seleccione el sensor de puerta con cable o inalámbrico para abrir su página de detalles.**
{% endstep %}

{% step %}
**En Retardo de puerta mantenida abierta, elija una duración del retardo.**
{% endstep %}
{% endstepper %}

**Opciones de retardo disponibles:** 30 segundos, 60 segundos, 5 minutos, 10 minutos.

{% hint style="warning" %}
La alerta DHO permanece como *Puerta abierta* hasta que la puerta se cierre.
{% 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/es/configuracion/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.