# Why are sensors sometimes combined as an open/closed event and sometimes separate in the activity history?

**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

A sensor's Open and Close events typically get combined into one line in the activity history when the events occur within a few minutes of each other. If a sensor is opened and then not closed again for a longer period of time, there will be two separate events in the activity history: one for the sensor being opened and another for the sensor being closed. For more information about configuring Sensor Activity Monitoring for sensors, see Turn sensor activity monitoring on/off.

<table id="bkmrk-platformgeneral-%2F-de"> <tbody> <tr><th>Platform</th><td>General / Device</td></tr> <tr><th>Content type</th><td>FAQ / Explanation</td></tr> <tr><th>Source last updated</th><td>2023-11-15</td></tr> </tbody></table>

## Procedure

A sensor's Open and Close events typically get combined into one line in the activity history when the events occur within a few minutes of each other.

If a sensor is opened and then not closed again for a longer period of time, there will be two separate events in the activity history: one for the sensor being opened and another for the sensor being closed.

For more information about configuring Sensor Activity Monitoring for sensors, see Turn sensor activity monitoring on/off.

## Source and support

For GoSafer Security assistance, visit [gosafersecurity.com](https://gosafersecurity.com/).

Original Alarm.com reference: [https://answers.alarm.com/Customer/Website\_and\_App/System\_Management/System\_History/Why\_are\_sensors\_sometimes\_combined\_as\_an\_open\_closed\_event\_and\_sometimes\_separate\_in\_the\_activity\_history](https://answers.alarm.com/Customer/Website_and_App/System_Management/System_History/Why_are_sensors_sometimes_combined_as_an_open_closed_event_and_sometimes_separate_in_the_activity_history)

<small>Always verify safety, installation, compatibility, and current UI details against the original manufacturer documentation before operational use.</small>