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

# 有線および無線ドアセンサー向けのドア開放状態（DHO）アラームトリガーを構成する

{% hint style="success" %}
この記事は新しいアラームのガイドです。こちらを参照してください。 [New アラームと Classic アラームの違い](/new-alarms/ja/hajimeni/new-alarms-vs-classic-alarms.md) どのバージョンのアラームをお使いか不明な場合は、こちらをご覧ください。
{% endhint %}

Door Held Open (DHO) Delay は、ドアが設定された期間より長く開いたままになっているとアラームを発生します。アラームは、ドアが指定時間以上開いたままになってからのみ作動します。

***

## 構成

{% stepper %}
{% step %}
**Verkada Command で、すべての製品 > アラーム に移動します。**
{% 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/ja/she-ding/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.