Arm failure too easy

[steefdebruijn]

Hi,

I have a front door configured as type EntryDoor and Entry=Yes.
I also hava a PIR in my hall configured as PirAwayNightAlert which is a copy of PirNightAway with Night=alert instead of immediate and also Entry=Yes.

The system is configured to arm on Final Door.

We have the habit to open the front door and then arm the system. If we wait for the \"front door\" announcement a couple of times the system arms successfully. But if we more or less immediately close the front door the system often raises an arm failure.

My guess is it is because the system is flushing the queue of zone detections while arming; so if i ran through the house just before arming these zone detections seem to be processed *after* system arming triggering an arm failure. Or something like that.

What can i change in my setup to prevent these failures?

Tia
Steef

[slychiu]

After the entry door is closed the system will wait for 6 seconds and then arm to away mode if no ipen zones are found. If there are open zones at the end of 6 seconds then there is arm failure
Perhaps your motion sensor is set to remian on after 6 seconds? This would cause arm failure

[Vangelis]

Are all these sensors wired or wireless?

Vangelis

[steefdebruijn]

All aritech DD1012PI wired sensors

[Vangelis]

Ok, good, so that rules out any latency in Wireless comms...

Next, (if you have a UCM/Eth) I would take a look at the realtime Serial output from Comfigurator. Reference this with the Serial Cmds guide on cytech.biz to see the order of sensor activations and Arm status

Vangelis

[slychiu]

also read the event log. This shows which sensor caused the arm failurelook for the zone activated after the arm failure alarm