How do I configure a siren to buzz if a door was held or forced open?
GoSafer Security Knowledge Base
This operational reference is organized for GoSafer Security customers and staff. Alarm.com product names are retained where required for technical accuracy.
Overview
An input can be configured to trigger one or multiple Access Control doors with an Event-Triggered Rule using the GoSafer Security customer portal (powered by Alarm.com).
| Platform | Customer Website |
|---|---|
| Content type | How-to / Configuration |
| Source last updated | 2025-06-04 |
Procedure
To configure an Event-Triggered Rule for the siren when an Access Control door is held or forced open
Important: The Access Control door for the siren rule must have a door sensor programmed. Without a door sensor configured, the held open and forced open trigger actions will not be available.
- Log in to the GoSafer Security customer portal (powered by Alarm.com).
- Click Automation.
- Click Rules.
- Click Add New Rule and select Event-Triggered Rule (if applicable).
- Enter the desired name for the rule.
In Automate My, select Switches.
In When this event occurs, select Door Activity.
- Select the door that will trigger the siren and select is held open or is forced open.
Note: The held open event trigger time is set in the Add Door installation wizard or the Edit Door Sensor settings page for a door on the Partner Portal or Partner MobileTech app. Door held open events are not generated when the door is unlocked.
In Perform this action, select Turn ON when [door name] is held (or forced) open; Turn OFF when [door name] is closed.
In Select Devices, select which siren(s) the rule should apply to.
In During these time frames, select the desired time frames for the rule to operate.
- Click Save.
Source and support
For GoSafer Security assistance, visit gosafersecurity.com.
Original Alarm.com reference: https://answers.alarm.com/Customer/Website_and_App/Commercial/Access_Control/How_do_I_configure_a_siren_to_buzz_if_a_door_was_held_or_forced_open
Always verify safety, installation, compatibility, and current UI details against the original manufacturer documentation before operational use.