Intrusion Alarm when disarmed

[Piasa]

What could cause M1 to announce an intrusion alarm when it was not armed?

 

[RAL]

Do you have a zone defined as Burglary 24 Hour ?  24 hour zone types will cause an alarm condition even if the M1 is disarmed.

 

[Piasa]

No.  No 24 hour zones.

 

[RAL]

Can you describe the conditions when you see this a bit more?
 
Are you getting just a keypad indication, and/or voice announcement, or sirens too?
 
Do you have to do anything to clear the condition (e.g. enter a code to disarm)? 
 
Does it happen when a sensor is activated, or at random times when nothing obvious is happening?
 
Anything in the log?

 

[Piasa]

Thanks for helping.
 
System is disarmed.  Some sensors are violated. 
 
I did not see the keypad.  I'll try to see next time this occurs.
 
Only a voice anouncement.  I have no sirens.
 
I did not need to clear the condition.
 
I did not observe any sensors activated, but that doesn't mean than none were.  As previously stated, a number of sensors were in the "open" state.
 
Seems to be random.  (other random stuff happening...)
 
Nothing in the log.

 

[RAL]

From the voice message you hear, do you know which zone is being violated?  Or is this happening with multiple zones?  Wondering if they are door or window contacts, or say motion detectors.
 
If you have Chime enabled for a zone, and voice chime messages are enabled, it is normal to hear the voice announcement as zones change from secure to violated. Question is whether the zone is really changing state or not. 
 
If you believe the contact isn't changing state, then it could be an intermittent short in the wiring, or maybe a flaky contact or PIR.  First step would be to figure out which zones are causing the problem.  If you are able to eliminate wiring or contact problems, it's possible that you have a bad zone input.

 

[Piasa]

Zones are legitimately changing state on a regular basis as doors are opened and closed, windows opened and closed, motion detected.  But I do not believe that Elk should be announcing an intrusion alarm if it is in a disarmed state.  Am I wrong?  If not, whether the state change was caused by a normal action or an abnormal action, Elk should not announce an intrusion alarm.
 
Elk does chime for state changes so programmed.
 
The announcement does not specify zone.

 

[RAL]

I probably got off track a bit with my previous post thinking about bad contacts or zone inputs while I was trying to understand what might be happening. 
 
So, if I understand what you are saying correctly, you are hearing a voice alarm status message, rather than a zone status message.  Even though the system is unarmed? 
 
That being the case, then it leads me back to a zone being configured as a 24 hour zone.  I would double check (triple check?) all the zones just to be sure.
 
Had things been working properly, and then this problem suddenly popped up?  Just wondering what might have changed to bring it on.  New firmware update or anything like that?

 

[Del91574]

While it's not perfect, have you investigated your zone/system response times?
 
Generally it's a sign of a different issue altogether (bad contacts/wiring issues) but modifying the time to be in the 250-400 ms response time and not "fast" is a good idea. Fast RT is more if you had inertia based detectors installed.