> 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/configuration-client/site-monitoring/event-viewer/events-with-restorals.md).

# Events with Restorals

### Introduction

Events belonging to the following Event Groups in Command Centre are considered stateful, and hence have 'Return to Normal' events, (i.e. Restorals). These are the events that can have a red bell icon in the Alarm Viewer window.

**Note:**

Each of these Event Groups is able to send Contact ID alarms and restores. See [External Alarm Monitoring](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-alarm-monitoring.md) for further detail.

<table><thead><tr><th width="245">Event Group</th><th>Event Type</th></tr></thead><tbody><tr><td>Open/Off</td><td>Input Open<br>Output Off</td></tr><tr><td>Closed/On</td><td>Input Closed<br>Output On</td></tr><tr><td>Tamper</td><td>Controller tampered (front)<br>Controller tampered (rear)<br>Input Break<br>Input Short<br>Unit Tampered (Front)<br>Unit Tampered (Rear)</td></tr><tr><td>Input Shunted/Isolated</td><td>Input Isolated<br>Input Shunted</td></tr><tr><td>Unit Stopped Responding</td><td>Unit Not Responding</td></tr><tr><td>Door Open Too Long</td><td>Door Open Too Long</td></tr><tr><td>Door Not Locked</td><td>Door Not Locked</td></tr><tr><td>Forced Door</td><td>Forced Door</td></tr><tr><td>Power out of Range</td><td>Controller power high<br>Controller power low<br>Unit - power high<br>Unit - power low</td></tr><tr><td>Command Centre Comms Interrupted</td><td>Comms failed to Command Centre</td></tr></tbody></table>


---

# 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/configuration-client/site-monitoring/event-viewer/events-with-restorals.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.
