|
ECS-L Home Automation and Security Archives |
learn more
| view messages for this
month | NetBloc® | terms of use | search
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects
Subject: From: Date: | Re: [ECS] 4.1.002 Mark Gilmore Fri, 02 Jul 1999 05:49:23 -0700 |
Bill, I have no idea what is happening with your remote
phone access - anyone else seeing this ?
I am also lost on the 2nd topic below
(need big picture):What are you trying to do ?
Bill Walters wrote:
>
> Mark,
>
> Just returned from mini vacation (family reunion) and got a chance to do
> a little playing with 4.1.002.
>
> Here are several things I've found. Don't know if they are the result
> of my poor understanding or are operating incorrectly, or ???
>
> 1. Remote Phone Access....
>
> When system is called and # pressed after it answers the phone, all you
> get is "dead" air until you press the # key again; system then asks you
> for "Password" and operates ok. Is this correct?
>
> 2. I had set up an event to test for "Phone-Interface-C" state of
> "Busy". If it found test to be true, it closed the intercom relay.
> Here's what the event looks like:
>
> If Speak-Messages Is Now Busy/VC
> Or Voice-Interface-C Is Now Busy
> Then Intercom Set High
>
> If Speak-Messages Is Now Idle
> Or Voice-Interface-C Is Not Now Busy
> Then Intercom Set Low
>
> I have subsequently commented out the two lines which begin with "OR"
> since any X-10 console activity triggered a momentary relay closure on
> the intercom module... The clicking was annoying late at night when we
> use the X-10 consoles by our bed to shut down the house, etc.. In
> other words - if ECS sensed any X-10 signal, it triggered the intercom
> relay closed/open.
>
> Is this due to my incredibly stupid logic or???
>
> Thanks -
> Bill Walters
--
Mark Gilmore
Omnipotence (ECS Home Automation Software)
omnip@usit.net
http://www.usit.com/omnip
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects