Subject: From: Date:

Re: [ECS] any tips on this? Michael David Thu, 4 Feb 1999 09:40:47 -0500

---

Hi Scott!

You could also use a state-holder for "plc button A", and then just test the
state holder.  I often use state-holders for items that I am likely to
change in the future - especially when they occur a bunch of times in my
events.

Cheers!

Michael David
michael@michaeldavid.com
----- Original Message -----
From: Scott Reston <ih8gates@concentric.net>
To: <ecs-list@netbloc.com>
Sent: Thursday, February 04, 1999 8:22 AM
Subject: [ECS] any tips on this?


i use several DM10a motion sensors in my house (sends X10 on/off
commands via RF transciever). more often than not, i'll have several
things happen when a single motion sensor senses activity. the code
to handle this is in several events, but all look something like

if plc button A is 1/On
then do some things...

i've decided to switch unit codes on a couple of the sensors, and i'm
finding it tedious to go through and find all instances of a
plc-code. i'm guessing that there is a more elegant way to handle
this such as an event that translates x10 codes into a true/false
status... something like:

if plc button A is 1/On
then Motion Front Porch set True

if plc button A is not now 1/On
then Motion Front Porch set False

and have events look for "motion front porch is now true"

this way, if i need to change a unit code on my motion sensor, i only
change it in one place...

does this look like the best way to handle this? any tips or
thoughts?

thanks..
scott reston
ih8gates@concentric.net
http://www.indelible-blue.com/scott/

---