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

# 유선 및 무선 도어 센서의 문 열림 유지(DHO) 알람 트리거 구성

{% hint style="success" %}
이 문서는 New Alarms에 대한 안내입니다. 자세한 내용은 [New Alarms와 Classic Alarms 비교](/new-alarms/ko/getting-started/new-alarms-vs-classic-alarms.md) 어떤 버전의 Alarms를 사용 중인지 확실하지 않은 경우.
{% endhint %}

Door Held Open (DHO) 지연은 문이 설정된 시간보다 더 오래 열려 있을 때 경보를 트리거합니다. 경보는 문이 지정된 시간 이상 열려 있은 후에만 활성화됩니다.

***

## 구성

{% stepper %}
{% step %}
**Verkada Command에서 All Products > Alarms로 이동합니다.**
{% endstep %}

{% step %}
**알람 사이트를 선택합니다.**
{% endstep %}

{% step %}
**왼쪽 탐색 메뉴에서 장치를 클릭합니다.**
{% endstep %}

{% step %}
**세부 정보 페이지를 열려면 유선 또는 무선 도어 센서를 선택하세요.**
{% endstep %}

{% step %}
**Door Held Open Delay에서 지연 시간을 선택하세요.**
{% endstep %}
{% endstepper %}

**사용 가능한 지연 옵션:** 30초, 60초, 5분, 10분.

{% hint style="warning" %}
DHO 경고는 ...으로 유지됩니다 *문 열림* 문이 닫힐 때까지 활성 상태로 유지됩니다.
{% 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/ko/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.