Re: Concord 4 issue or user issue?

[Effenpig1 <dirtyspicevent@xxxxxxxxxxx>]

On Dec 7, 6:22=A0pm, mleuck <m.le...@xxxxxxxxx> wrote:
> On Dec 7, 2:51=A0pm, Effenpig1 <dirtyspicev...@xxxxxxxxxxx> wrote:
>
>
>
> > On Dec 7, 11:17=A0am, "alarman" <nos...@xxxxxxxx> wrote:
>
> > > Effenpig1 wrote:
> > > > On Dec 6, 9:38 pm, "alarman" <nos...@xxxxxxxx> wrote:
> > > >> Effenpig1 wrote:
> > > >>> 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, a=
nd
> > > >>> then she changes it to away when she leaves. Her daughter and
> > > >>> son-in-law are visiting, she left early in the morning and switch=
ed
> > > >>> from stay to 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 what
> > > >>> 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 sir=
en
> > > >>> stopping but a full clear)
>
> > > >>> I checked the event logs and heres what I found:
>
> > > >>> Zone 11 alarm then 5 seconds later an E406 cancel/abort by user #
> > > >>> U846 ( master code)
>
> > > >>> I'm thinking frazzled daughter gets crap scared out of her, panic=
s,
> > > >>> punches in code, then somehow forgets that she did it. Her and he=
r
> > > >>> husband were the only ones there and he didn't even know the code
> > > >>> anyway, so I'm sure he didn't cancel the alarm. Also, there are n=
o
> > > >>> keyfobs or wireless keypads/remotes, 2 hardwired ATP1000 keypads.
>
> > > >>> I tested the system, arming it the same way they did that morning=
,
> > > >>> no issues. I'm going to run it by GE tech support tomorrow mornin=
g.
> > > >>> 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 w=
hat
> > > >>> else it would be. Any thoughts?
>
> > > >> Get ready for a shock.
>
> > > >> Ready?
>
> > > >> People lie.
>
> > > >> To your face. Even though the evidence, plain to all, is there. Th=
ey
> > > >> lie even whe the truth will suit them better. With some people, is=
't
> > > >> a sport.
>
> > > >> Now repeat after me: People lie.
>
> > > >> --
> > > >> js
>
> > > >> Si Vis Pacem, Para Bellum
>
> > > > I'm not sure what your point is, yes, people do lie. You lie, =A0I =
lie,
> > > > we all lie. In fact I have an older sister who falls into the categ=
ory
> > > > of "lies for the sport of it". =A0Very annoying. However, I'm willi=
ng to
> > > > take someones word to an extent, until proven otherwise. I believe
> > > > that the customers daughter really doesn't think she disarmed it.
> > > > Maybe, she did remember later on that she did disarm it and was too
> > > > embarassed tell me. I'm certainly not going to call her an outright
> > > > liar over it.
>
> > > No one told you to call anyone a liar. The point is, people lie. Just=
 file
> > > it away.
>
> > > --
> > > js
>
> > > Si Vis Pacem, Para Bellum
>
> > Well, like I said, I didn't want to just write it off without at least
> > checking into it. I have tried to re-create the issue, and it worked
> > fine, I reviewed the event logs, and have checked with GEI to confirm
> > that there are no known issues of this type.I feel I have done my due
> > diligence, whether it was a lie or just simply an error, and now I
> > will "write it off".
>
> Look it's real simple, poke around in programming then test the system
> then tell the customer to let you know if it happens again
>
> Worked for me

I didn't "poke around' in programming, but I did double check
everything when I downloaded the log. I did test the system, even went
so far as to "recreate" the situation. I'm sure they will call me if
it happens again.

My main concern was if there was the possibility of a system "glitch",
and this was my biggest reason for posting. I figured I'd check here
to see if anyone had encountered this problem and it turned out to be
something other than user error.