> 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/installation/set-up-the-wh52.md).

# Set up the WH52

The WH52 Wireless Hub is PoE-powered and connects locally to the Alarm Panel to transmit wireless sensor events from connected devices. Multiple hubs can be added as needed to ensure proper coverage throughout your building.

***

### Requirements

* An Alarm Panel(BP52, BP32 or BP42)
* The WH52 requires 15W PoE (802.3af) and must be on the same subnet (LAN) as the Alarm Panel for local communication. See [Alarm Network Settings](/new-alarms/getting-started/alarms-network-settings.md) for more information.

### Installation best practices

Install the WH52 facing down to ensure proper coverage of the Alarms signals.

Avoid installation near metal surfaces as these will reduce range.

{% hint style="warning" %}
See [Wireless Installation FAQ](/new-alarms/installation/wireless-installations-faq.md) for more information on optimal hub placement.
{% endhint %}

***

## WH52 setup

{% stepper %}
{% step %}
**Ensure that an Alarm Panel is added to your New Alarms site and online.**
{% endstep %}

{% step %}
[**Add the WH52**](/command/organization-settings/add-a-device-to-your-command-organization.md) **serial number to your Command account.**
{% endstep %}

{% step %}
**Move the WH52 from unassigned devices to your New Alarms site.**
{% endstep %}

{% step %}
**On the Devices page of your New Alarms site, verify the WH52 displays a "connected" event, confirming communication with the panel and readiness to route alarm events.**
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The WH52 will show online first and then connected.
{% endhint %}

### Status

* **Online -** The WH52 is connected to the internet.

{% hint style="warning" %}
This is a requirement for the WH52 to update its firmware from the cloud.
{% endhint %}

* **Connected -** The WH52 has a local connection with the Alarm panel. This is required for the WH52 to send events from its paired wireless sensors. Allow [Alarms Network Settings](/new-alarms/getting-started/alarms-network-settings.md) for multicast communication over the local network.

<div align="left" data-with-frame="true"><figure><img src="https://2259276529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNU1He6Uj2tgInV2VdCLQ%2Fuploads%2F8BsGjdZthd7OR1aHg8Cy%2FWH52.png?alt=media&amp;token=5aa8d294-bb9e-448c-a38c-aab97e422768" alt=""><figcaption></figcaption></figure></div>


---

# 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/installation/set-up-the-wh52.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.
