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

# Instalación

- [Configura el WH32](https://help.verkada.com/new-alarms/es/instalacion/set-up-the-wh32.md)
- [Configura el WH52](https://help.verkada.com/new-alarms/es/instalacion/set-up-the-wh52.md)
- [Configura un BK22](https://help.verkada.com/new-alarms/es/instalacion/set-up-a-bk22.md): Cómo configurar y realizar la configuración básica del BK22
- [Configurar adaptadores BSP](https://help.verkada.com/new-alarms/es/instalacion/set-up-bsp-adapters.md)
- [Conexión en cadena de varios BE32](https://help.verkada.com/new-alarms/es/instalacion/daisy-chain-multiple-be32s.md): Prepara los BE32 para la conexión en cadena y especifica las distancias correctas para la instalación
- [Configurar el modo de transmisor universal en un BR31](https://help.verkada.com/new-alarms/es/instalacion/set-up-universal-transmitter-mode-on-a-br31.md): Configura el modo de transmisor universal en un sensor de puerta inalámbrico BR31
- [Calcular cuántas baterías se necesitan para el BP52](https://help.verkada.com/new-alarms/es/instalacion/calculate-how-many-batteries-are-needed-for-the-bp52.md): Calcula el número de baterías VBX necesarias para proporcionar el tiempo de funcionamiento deseado en caso de un corte de energía
- [Preguntas frecuentes sobre instalaciones inalámbricas](https://help.verkada.com/new-alarms/es/instalacion/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/es/instalacion.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.