Posted: Friday Aug 29th, 2014 11:50 am |
|
1st Post |
Howser
Member
back to top
|
This morning I had a User (3) turn off the alarm. This user has only local disarm and arm enabled, and all the other options disabled (including Security).
A minute after the User (User# 3) disarmed the alarm, we a had a few zones being bypassed and unbypassed. These zones are not in any response code.
A minute or two later, we had Arm Failure, and I signed in to cancel the failure, and the keypad started announcing "zero" continuously. I was then forced to reset the panel, after which everything seemed to be back to normal.
Any idea what could have caused this?
I am using the following ....- Comfigurator 3.9.0 (Beta)
- Comfort Version 7.061
Event Log
08/29 08:27 Zone Activation # Kitchen_Door (6)
08/29 08:27 Alarm Type # EntryAlert (10)
08/29 08:27 Sign in - User # 3
08/29 08:27 Sign in - User # 3
08/29 08:27 Mode Change # Security Off
08/29 08:28 Sign in - User # 3
08/29 08:28 Bypass Zone # Kids_Bedroom_Movement (23)
08/29 08:28 UnBypass Zone # Kids_Bedroom_Movement (23)
08/29 08:29 Bypass Zone # Kids_Bedroom_Movement (23)
08/29 08:29 UnBypass Zone # Kids_Bedroom_Movement (23)
08/29 08:29 Bypass Zone # Kids_Bedroom_Movement (23)
08/29 08:30 UnBypass Zone # Kids_Bedroom_Movement (23)
08/29 08:30 Date/Time Change 18
08/29 08:30 Bypass Zone # Scullery_Movement (9)
08/29 08:30 Bypass Zone # Kitchen_Movement(17)
08/29 08:30 UnBypass Zone # Scullery_Movement (9)
08/29 08:30 UnBypass Zone # Kitchen_Movement(17)
08/29 08:30 Bypass Zone # Kitchen_Movement(17)
08/29 08:31 UnBypass Zone # Kitchen_Movement(17)
08/29 08:31 Bypass Zone # Kitchen_Movement(17)
08/29 08:31 UnBypass Zone # Kitchen_Movement(17)
08/29 08:32 Bypass Zone # Kitchen_Movement(17)
08/29 08:32 UnBypass Zone # Kitchen_Movement(17)
08/29 08:32 Bypass Zone # Kitchen_Movement(17)
08/29 08:32 UnBypass Zone # Kitchen_Movement(17)
08/29 08:32 Bypass Zone # Kitchen_Movement(17)
08/29 08:32 UnBypass Zone # Kitchen_Movement(17)
08/29 08:32 Bypass Zone # Kitchen_Movement(17)
08/29 08:32 UnBypass Zone # Kitchen_Movement(17)
08/29 08:34 Alarm Type # ArmFail (4)
08/29 08:34 Dial Number # 1
08/29 08:34 Remote Signin - User # SMS Acknowledge
08/29 08:34 Sign in - User # 1
08/29 08:34 Alarm Type # AlarmAbort (20)
08/29 08:34 Sign in - User # 1
08/29 08:34 Mode Change # Security Off
08/29 08:35 Reset 97 |
|
Posted: Friday Aug 29th, 2014 06:12 pm |
|
2nd Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
That is quite weird
The bypassing and unbypassing of the zones seems to indicate that the system is being armed by Time program or remotely
Note that all the zones are motion detectors
When you do auto arm or remote arm or local arm with force arm, and zones are open, Comfort will bypass the zones. When the zone is restored the zone is unbypassed
Hence it seems like there is an auto arm or force arm going on, and people are moving through the motion detector zones
Perhaps the user pressed the arm button and # key to force arm by mistake
|
Posted: Friday Aug 29th, 2014 07:10 pm |
|
3rd Post |
Howser
Member
back to top
|
ident wrote: The bypassing and unbypassing of the zones seems to indicate that the system is being armed by Time program or remotely
Note that all the zones are motion detectors
When you do auto arm or remote arm or local arm with force arm, and zones are open, Comfort will bypass the zones. When the zone is restored the zone is unbypassed
Hence it seems like there is an auto arm or force arm going on, and people are moving through the motion detector zones
Perhaps the user pressed the arm button and # key to force arm by mistake I thought in a force arm process, once the zone(s) are bypassed the system will arm and only unbypass after arming when the zone is sealed again.
The "zero" announcement is a bit of a concern, but hopefully it does not happen again.
|
Posted: Saturday Aug 30th, 2014 06:56 am |
|
4th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
When you force arm with open zones, the zones will be bypassed so that the system can arm. But the zones are unbypasses when the zone is closed again
hence if a window upstairs is open and you are arming on the downstairs keypad. When you hear the upstairs window announced, just press # to force arm. The system arms. When you go upstairs you can close the window. The window is then active and will cause an alarm if opened. hence this saves time as you do not need to close the window and then arm the system again
If you have motion sensors which are detecting motion when the system is being armed, then they will bypass and unbypass when you force arm, unless they are entry/exit zones
Hence your situation seems to be caused by someone pressing the Away key and then the # key. You can duplicate this very easily
|
Posted: Monday Sep 1st, 2014 09:51 am |
|
5th Post |
Posted: Monday Sep 1st, 2014 10:36 am |
|
6th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
This is definately caused by an arm attempt as there is an arm failure at the end
There is a difference between a zone that has the Entry Path attribute which does not cause an alarm if preceded by the Entry Door , and an Entry Door zone type which terminates the exit and starts an entry delay when the system is armed
|
|