Re: Concord 4 issue or user issue?

[Effenpig1 <dirtyspicevent@xxxxxxxxxxx>]

On Dec 8, 2:30=A0pm, "Crash Gordon" <webmas...@xxxxxxxxxxxxxxxxxxxxx>
wrote:
> no problem...didn't think you were being a smart ass - I just wasn't sure
> what you meant.
>
> if you enable and send opening closings there would be no question of
> whether the system was armed or disarmed, you'd have a time & date stampe=
d
> printout from your CS to show them. yes, some panels can disarm themselve=
s
> on schedule (intentionally) but the open/close reports would even show th=
at
> too. So if it didn't show them arming/disarming and you went there and tr=
ied
> to replicate the situation and it showed all open/closes properly, then
> there is no argument....if you wanted to take it that far.
>
> I've had to do this several times with clients.
>
> --
> **Crash Gordon**
>
> "Effenpig1" <dirtyspicev...@xxxxxxxxxxx> wrote in message
>
> news:fc027362-eb24-4873-a9c6-32c213c27c75@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> > On Dec 8, 12:25 am, "Crash Gordon" <webmas...@xxxxxxxxxxxxxxxxxxxxx>
> > wrote:
> >> Whaddya mean? You don't know what open/close reports are...or you don'=
t
> >> know
> >> how they would have helped you in this instance?
>
> >> --
> >> **Crash Gordon**
>
> >> "Effenpig1" <dirtyspicev...@xxxxxxxxxxx> wrote in message
>
> >>news:fb0cbc01-8595-4755-ab5f-94ceee501a2a@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
.
>
> >> > On Dec 6, 10:35 pm, "Crash Gordon" <webmas...@xxxxxxxxxxxxxxxxxxxxx>
> >> > wrote:
> >> >> happens all the time...if it's chronic I turn on open/closing repor=
ts
> >> >> temporarily.
>
> >> >> --
> >> >> **Crash Gordon**
>
> >> >> "Doug" <n...@xxxxxxxx> wrote in message
>
> >> >>news:P4_Sm.58632$We2.51836@xxxxxxxxxxxxxxx
>
> >> >> > "Effenpig1" <dirtyspicev...@xxxxxxxxxxx> wrote in message
> >> >> >news:97070509-c3c5-4466-95fa-20534a6bdb8a@xxxxxxxxxxxxxxxxxxxxxxxx=
.com...
> >> >> >> Had a customer call with a issue I've never come across before.
> >> >> >> Here's
> >> >> >> what happened: Installed a Concord 4 at her house about 3 months
> >> >> >> ago.
> >> >> >> I taught her to arm to stay with no delay at night, and then she
> >> >> >> changes it to away when she leaves. Her daughter and son-in-law =
are
> >> >> >> visiting, she left early in the morning and switched from stay t=
o
> >> >> >> away. After she left the daughter came out of her bedroom and
> >> >> >> tripped
> >> >> >> the living room motion.
>
> >> >> >> Here's where it gets weird: Son-in-law calls me and tells me wha=
t
> >> >> >> happened, he says he's concerned because "the alarm went off for
> >> >> >> about
> >> >> >> 10 to 15 seconds and shut off by itself" ( Not just the siren
> >> >> >> stopping
> >> >> >> but a full clear)
>
> >> >> >> I checked the event logs and heres what I found:
>
> >> >> >> Zone 11 alarm then =A05 seconds later an E406 cancel/abort by us=
er #
> >> >> >> U846 ( master code)
>
> >> >> >> I'm thinking frazzled daughter gets crap scared out of her, pani=
cs,
> >> >> >> punches in code, then somehow forgets that she did it. Her and h=
er
> >> >> >> husband were the only ones there and he didn't even know the cod=
e
> >> >> >> anyway, so I'm sure he didn't cancel the alarm. Also, there are =
no
> >> >> >> keyfobs or wireless keypads/remotes, 2 hardwired ATP1000 keypads=
.
>
> >> >> >> I tested the system, arming it the same way they did that mornin=
g,
> >> >> >> no
> >> >> >> issues. I'm going to run it by GE tech support tomorrow morning.
> >> >> >> I'm
> >> >> >> 99.999% sure it's just user error, but that .001% bugs me.
>
> >> >> >> So what do you think, is it user error? because I can't imagine
> >> >> >> what
> >> >> >> else it would be. =A0Any thoughts?
>
> >> >> > She turns the alarm off.
> >> >> > He calls and says the alarm shut off by itself.
> >> >> > After he hangs up she tells him that she turned it off.
> >> >> > His ego won't let him admit that he's wrong.
>
> >> >> > Doug
>
> >> > You lost me with the opening/closing reports.
>
> > The 2nd one, as in how they would have helped in this instance. I'm
> > not trying to be a smart-ass, I really don't know.

There was no question that the system was armed to away. They told me
that. They also knew the motion acted as it should have, and the
system went into alarm. This was all agreed upon. The point of
contention was that they said after 10 or 15 second the alarm stopped
and cleared itself. The event log showed a the zone alarm, and the
subsequent E406 Cancel/Abort by User U846 ( system master code). If it
had been a question of whether or not the system was armed when it
went into alarm the opening/closing reports may have provided needed
info, but that wasn't the case at all.