🚀 go-pugleaf

In article <1684@trantor.harris-atd.com> jad@dayton.UUCP (J. Deters) writes:
>In article <6449@dayton.UUCP> jad@dayton.UUCP (J. Deters) writes:
>>
>>The X-10 control format has been patented by X-10 Inc.  Specifically,
>>it means that you do not have the license to transmit X-10 format data
       .,..
>
>Just because I want the schematics for the X-10 modules does not mean I
>plan on building any.  At about $10 a piece, it probably would not be
>cost effective.  I have the complete manuals for my car, but I
>certainly have no intention of building another one.  My intention is to
>understand them, and possibly add a few extra features which X-10 Inc. left

One feature I have always wanted, and none of the X10 devices I have found
supports, is the ability for the computer interface to determine the
status of the remote modules.  Example: my porch light, which I absolutely
do not want turned off during certain hours, but don't mind if it is
turned on manually during other hours.  Currently I have to program the
unit to force the light on every half hour during 'critical' time. Not
only is this inefficient in terms of timed events, but the porch light
could be off for up to 29 minutes.  Example 2: My coffee pot is set
to be controlled by a controller by the bed.  When I wake up I bash the
button to start the coffee, dress, and go have a cup.  Then I run out
of the house and forget to turn off the coffee.  If the computer interface
could determine that I had turned on the coffee, it could insure that the
pot was shut down at some time interval after that.

-- 
del (Erik Lindberg) 
uw-beaver!tikal!pilchuck!del