Building materials, obstructions, distance, and general radio frequency (RF) interference are highly variable across different environments and from the time of day. As such, we highly suggest that you read and follow guidelines outlined in this article to ensure that your wireless system operates to the best of its ability.
Add your wireless alarm hub to Command
Remove the cover from your alarm hub and plug the device into a Power over Ethernet (PoE) switch.
In Verkada Command, go to All Products > Add Devices and select a site. This will be your Alarms site.
Find and enter the 12-character serial number, beginning with "DQ6", located at the bottom of the device or on the box that was provided.
Once you activate your hub, follow the setup flow to configure your Alarms site. If you added it to an existing Alarms site, you can skip this step.
Navigate to the Alarms > Devices tab and verify that your wireless hub is reporting online and the LED on the hub is solid blue.
Add your wireless sensors to Command
Place your wireless sensors next to the wireless hub.
Add your wireless sensors by SN
In Verkada Command, go to All Products > Devices.
At the top right, click Add Devices and select a site. This is the Alarms site associated to your wireless sensor.
Find and enter the 12-character serial number, located at the bottom of the device or on the box that was provided.
Click Activate to automatically associate the sensor to the Alarms site and the hub(s) in your organization.
Power on your wireless sensors
When the sensors are first powered on, they automatically try to join the closest hub to report their status.
Pull the battery tabs from your sensor(s) to power on the device.
Initiate trigger event(s), as detailed in Set Up Your Wireless Devices, for your particular sensor (door open/close, motion detected, button press, and so on).
Validate wireless sensor coverage
Place the hub as close to the desired location as possible, such as the center of the floor/building for maximum coverage.
The most recent sensor events are time-stamped in the Alarms site > Devices tab. You can monitor this page to ensure that sensor events and the sensor's current signal strength are properly reported to Command.
Relocate your wireless sensors to their desired install locations and send several trigger events (door open/close, motion detected, panic button press, glass break tester, and shorting the metal contacts on the water sensor). The lowest recommended Received Signal Strength Indicator (RSSI) is -85. We recommend not allowing lower values (for example, 90, -95, and so on); this weak signal strength means that the sensors will likely drop offline and experience difficulties upgrading. The -85 RSSI provides a safer barrier to the variability in environmental changes.
If the events are reported to Command, install the sensor in its final location and send 1 more event for good measure; otherwise:
If no events are being received, move closer to the hub to determine if the issue is related to signal coverage.
If you find that events are received when you move closer to the hub, perform a site walk to determine if there are any obstructions that could be dampening the signal.
Reposition the hub for better coverage and restart the testing.
If all else fails, you may want to consider purchasing an additional hub and license to fully cover your floor/building.
Before you begin this configuration, verify your Alarms site settings and validate system operations by raising a few test alarms.
Step 1: Put your Alarm site in test mode
When the system is put in test mode, the system and monitoring agents still go through the Alarms flow, but do not dispatch emergency services, unless you explicitly request it.
Toggle on Enable Emergency Dispatch.
Toggle on Monitoring Test Mode.
Step 2: Configure the user call list and notifications
In the screenshot example, the first person listed receives a call and then the following person would be the second to be called if the first person is unavailable, and so on. Each user will receive SMS and email notifications when an alarm is raised.
Step 3: Add wireless or wired sensors as triggers
On the Alarm Triggers page (for Wireless Sensor Events or Wired Sensor Events), click Add Sensor.
For some sensors, such as door contact sensors and panic buttons, there are additional settings that you can configure. Click the Edit icon next to the sensor to access these settings.
Step 4: Arm the site and raise a test alarm
Arm the Alarms site from Command and monitor the Activity tab.
Trigger your sensors and after the entry delay has elapsed, an alarm should be raised. Users on the notification list can resolve the alarm by spelling out their last name and phone number associated with their account to the monitoring agent. Command users can also manually resolve the alarm banner or by disarming their system.
You can expand the alarm-raised event to see all of the sensors that were tripped. To do so, under the alarm period, click See Details. In this view, you can see details about the flow of events for the raised alarm event. Click See more to expand the list of device events and include context camera footage for raise-alarm events, if configured.
Step 5: Ensure the event population
Under the Alarm site > Devices tab, ensure that all of the wireless sensors have populated at least 1 event.
Need more help? Contact Verkada Support