Subject: From: Date:

Re: [ECS] 4.1.002 Bill Walters Fri, 02 Jul 1999 08:28:57 -0500

---

Mark Gilmore wrote:
> 
> 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 ?
> 


I'd rather NOT have to turn the intercom relay on and off within each
event that needs to speak. 

I've changed the code to the following (instead of what I reported
earler):

If      Voice-Interface-C     Is Now      Busy
Then    Intercom              Set         High

If      Voice-Interface-C     Is Not Now  Busy
Then    Intercom              Set         Low



and it still clicks the relay whenever I issue an X-10 command from a
console, or save an item or event within ECS.


Bill Walters




> >
> > 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

---