> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/configuration-scenarios/scenario-deactivate-a-siren-after-a-se.md).

# Deactivate a siren after a delay or alarm-zone disarm

Configure virtual outputs and logic blocks to deactivate a siren automatically.

This configuration turns a siren off automatically after a set delay (10 minutes in the example) or when the alarm zone is disarmed. It uses two virtual outputs and three logic blocks.

**Create two Virtual Outputs:**

* `VO Alarm Armed`
* `Event Response`

**Create three Logic Blocks:**

* `Latched On`
* `Delay`
* `Clear Logic`

### Wire the configuration

1. Add `VO Alarm Armed` to the **Reflected output** tab of the alarm zone.

![VO Alarm Armed on the alarm zone reflected output tab](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-dee63c325fe199355435f4bc61e4d44f82d78173%2FSECHUB-CCS-SIREN-01-vo-alarm-armed-reflected.png?alt=media)

2. Make sure the access zone has the correct alarm zone assigned on its **Event Response** tab.

![Access zone Event Response tab](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-cc0d4cda083ee3c6aa5ee55cdfeb2ce71ab9eccb%2FSECHUB-CCS-SIREN-02-access-zone-event-response.png?alt=media)

3. Add the `Event Response` virtual output to the **Armed** tab of a new action plan.

![Event Response VO on the action plan Armed tab](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d0bcf3aac843ef4b67448a5594154d1c4f7ea677%2FSECHUB-CCS-SIREN-03-action-plan-armed-tab.png?alt=media)

4. Assign the new action plan to the PIR's **Event Response**. In the example, the action plan is assigned to **Closed/On** as the PIR is Normally Open. Also assign the PIR to the correct alarm zone.

![PIR Event Response with the action plan assigned](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ea36407426cd019ff00349e617d5dd158a5fad27%2FSECHUB-CCS-SIREN-04-pir-event-response.png?alt=media)

#### Logic Block 1: Latched On

![Logic Block 1 Latched On configuration](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-b90bac13012f0445efdf1bb258ec75cb3ff9e966%2FSECHUB-CCS-SIREN-05-lb1-latched-on-a.png?alt=media)

![Logic Block 1 Latched On configuration continued](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-7fde7d82c1c8e14f9ad1956b9dc5843fd73d8d7c%2FSECHUB-CCS-SIREN-06-lb1-latched-on-b.png?alt=media)

![Logic Block 1 Latched On configuration continued](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-48ea15cefa9905fa8ac7df4e1049aef0be7fef68%2FSECHUB-CCS-SIREN-07-lb1-latched-on-c.png?alt=media)

#### Logic Block 2: 10-minute delay (countdown)

![Logic Block 2 delay countdown](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-d600e5ee046da0c6a61fbbc9d9449a76bb211545%2FSECHUB-CCS-SIREN-08-lb2-delay-a.png?alt=media)

![Logic Block 2 delay countdown continued](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-765c868e45b4bf6ae03cec316fe1c02087f2c18c%2FSECHUB-CCS-SIREN-09-lb2-delay-b.png?alt=media)

#### Logic Block 3: Reset latch logic block

![Logic Block 3 reset latch](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-aaec2f10beb627d580e0d76c0c0b065a7cd7fc9b%2FSECHUB-CCS-SIREN-10-lb3-reset-a.png?alt=media)

![Logic Block 3 reset latch continued](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-169600ab139abf885d7ebcbafed86a7d003a3185%2FSECHUB-CCS-SIREN-11-lb3-reset-b.png?alt=media)

**Result:** the siren activates on alarm, then deactivates automatically once the delay (10 minutes in the example) elapses, or when the alarm zone is disarmed.

### Related links

* [Scenario - Pulsing an output using Logic Blocks](/knowledge-hub/products/cc-software/configure/configuration-scenarios/scenario-pulsing-an-output-using-logic.md). A second logic-block recipe.
* [Command Centre - Alarm Zones](/knowledge-hub/products/cc-software/configure/alarm-zones.md). The alarm zone that arms and disarms the siren.


---

# 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.security.gallagher.com/knowledge-hub/products/cc-software/configure/configuration-scenarios/scenario-deactivate-a-siren-after-a-se.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.