Happy user of a 2GIG GC2 system for about six weeks now. However, on April 11th, 4:29pm local time here in California I received the following push notification/log entry on alarm.com:
Living Room Glass Break Sensor-Left-Open Restoral
I do have a glass break sensor named “Living Room Glass Break”. The system was NOT armed at that time and no alarm was triggered. – Confirmed that someone was at home at that time, but supposedly no glass was broken/nothing happened that could have possibly triggered that sensor.
Does anyone know what that message means/what triggers it? – I had at some point accidentally enabled sensor monitoring on the glass break sensor, but that was only for a couple of hours, and it was turned off weeks ago.
That is a sensor left open rule. Sensor left open does not require activity monitoring active for the sensor.
It looks like a sensor left open rule was created including all sensors on this account. It is now marked “off” but you may want to limit it to only applicable sensors.
It still leaves some questions:
When did you turn off the notification?
What model of sensor is the Living Room Glass Break?
The rule was set for 5 minutes, a glass break should not remain open for 5 minutes. Can you run a sensor test and verify which sensor this particular zone is to make sure nothing is errantly labeled?
I have fixed the “Sensor left open” notification. While I was playing around with the system when I installed it a couple of weeks ago, I don’t specifically recall creating a “sensor left open Notification” at that time, but maybe I just forgot. However, I am pretty certain I did not turn on/create/turn off that Notification, say, within the past two weeks or so.
FYI: I just turned the notification on, but just for door sensors…
As for the glass break sensor:
This is a Honeywell 5853 Glass Break Sensor.
I just ran a sensor test and used my Honeywell FG-701 glass break simulator to put the sensor into test mode and then triggered it after starting a sensor test on the panel. “Living Room Glass Break” was announced, so this is not a mislabeled sensor.
Also, we managed to set off the alarm on March 15th at 11:30pm by accidentally dropping a very heavy ring binder onto hardwood floor right in front of that sensor, and the alarm event reads “Living Room Glass Break – Alarm”.
After this event I changed the sensitivity of the sensor to low. I can still trigger it in test mode with the glass break simulator, but further “folder drop tests” no longer triggered it.
Likely not defective, it is hard to say what would have triggered it and it remained open.
Where is this sensor in relation to the alarm panel? Is it fairly far away? Is there a lot of metal nearby? I’m wondering if the close signal just had trouble reaching the panel.
For glass breaks and motion detectors, the best way to test real-world scenarios is to place your account on test mode with the central station (if you have monitoring) and arm your system. Then trip the sensors.
For glass breaks this can be tough to test, but a loud audio file of breaking glass in addition to a simultaneous thud from a stomp (or falling binder) should do the trick.
The sensor and the panel are actually mounted on the same interior wall (just 2x4s and drywall). Panel is on the hallway side of the wall, sensor is on the living room side of the wall. And they are literally back to back, glass break is just mounted higher up. During sensor test the sensor in question shows full bars, so likely not a signal strength issue. Also, this is a fairly small 70 year old wood frame house, so signal strength shows full bars for all sensors.
I personally wasn’t at home when that event occurred. There is a kitchen that opens to the living room, but the sensor does not face it and sensitivity on the sensor is set to low, but the best explanation I can come up with is that some activity in the kitchen might have repeatedly triggered the sensor somehow, keeping it open for 5 minutes. — Does this sound plausible?
Generally the kitchen is not in use when the alarm is armed (either stay or away), so not too worried about false alarms. – But apparently we like to drop heavy binders late at night when the alarm is armed…
BTW: Haven’t yet signed up for central station monitoring (just self monitored through suretydiy right now) since I wanted to work out kinks (like this one… ;)) first to avoid false alarms.
but the best explanation I can come up with is that some activity in the kitchen might have repeatedly triggered the sensor somehow, keeping it open for 5 minutes. — Does this sound plausible
Possible. If the sensor opened and closed a bunch of times in a row, ADC would not have registered each one separately if they were not actually generating an alarm and just background activity. There is a delay between like signals.
