> 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/installation.md).

# 설치

- [WH32 설정하기](https://help.verkada.com/new-alarms/ko/installation/set-up-the-wh32.md)
- [WH52 설정하기](https://help.verkada.com/new-alarms/ko/installation/set-up-the-wh52.md)
- [BK22 설정하기](https://help.verkada.com/new-alarms/ko/installation/set-up-a-bk22.md): BK22 설정 및 기본 구성 방법
- [BSP 어댑터 설정](https://help.verkada.com/new-alarms/ko/installation/set-up-bsp-adapters.md)
- [여러 BE32 데이지 체인 연결](https://help.verkada.com/new-alarms/ko/installation/daisy-chain-multiple-be32s.md): BE32를 데이지 체인 연결할 수 있도록 준비하고 설정에 필요한 올바른 거리를 지정하세요
- [BR31에 범용 송신기 모드 설정](https://help.verkada.com/new-alarms/ko/installation/set-up-universal-transmitter-mode-on-a-br31.md): BR31 무선 도어 센서에 범용 송신기 모드를 설정하세요
- [BP52에 필요한 배터리 수 계산하기](https://help.verkada.com/new-alarms/ko/installation/calculate-how-many-batteries-are-needed-for-the-bp52.md): 정전 시 원하는 작동 시간을 제공하는 데 필요한 VBX 배터리 수를 계산하세요
- [무선 설치 FAQ](https://help.verkada.com/new-alarms/ko/installation/wireless-installations-faq.md)


---

# 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/installation.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.