> 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/troubleshooting/wireless-signal-troubleshooting.md).
# Wireless Signal Troubleshooting
If a sensor disconnects frequently, it’s likely due to poor signal strength between the sensor and the hub device. To confirm signal strength, go to the sensor in your alarm site and hover over the green wireless icon.
**Sensor Repair:** Initiate a sensor repair from Command to ensure your sensor pairs with the strongest nearby hub, and easily check signal strength across all available candidate hubs. For immediate results, trigger your sensor manually right after starting the repair, or wait for up to 30 min for the sensor to repair automatically.
**Minimum Recommended Strength:** Wireless signal strength is measured in RSSI. The sensor RSSI must be -85dBm or higher for a reliable connection. This leaves room for error, as the environment can change. Changes include doors opening and closing, windows, boxes blocking paths, people, walls, etc.\
\
If the signal strength falls below -85 dBm, consider adding additional hubs and/or repeaters. Additionally, ensure that the sensors are in line of sight of any hubs and not in closed-off areas with poor coverage. Lastly, install the sensors away from metal, which can degrade signal performance.
{% hint style="warning" %}
When testing wireless signal strength, mount the sensor and hub in their final positions and close any doors in the area.
This will ensure a more accurate representation of signal strength. If the signal strength still does not exceed -85 dBm, install a WH32 repeater to boost the signal from the hub or an additional hub.
See [BR31 Troubleshooting Guide](/new-alarms/troubleshooting/br31-troubleshooting-guide.md) for more information.
{% 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/troubleshooting/wireless-signal-troubleshooting.md?ask=&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.
