From: "Bruce Lawton" <bruce-AT-alwaysthinking.com>
Date: 24 Apr 2000 11:49:49 UTC   (07:49:49 AM in author's locale)
To: "XTension Discussion" <XTension_Discussion-AT-lists.bzzzzzz.com>

Hi Greg,

I recently started mucking with Garage Door sensors and am finding some
results different than what you described. The first clue is that my
transceiver has no receptacle for an appliance to plug into. I've heard
other descriptions consistent with yours, so maybe mine's some odd
variation. It's a Vehicle Interface Module, model 30001 with the HomeLink
trademark on it.

Operationally, I get no address at all. The report is sent with just the
function portion as follows:
5A05 0157 0311 1D

I have been gleaning the address info from the bits of the first extended
byte, 0x03 above. I'm using two sensors, hence two bits set. These are
interpreted as G1 and G2.

So I'm wondering if your hardware is actually sending an address or if
XTension is doing some handy preprocessing before reporting.

Bruce

>Subject: Garage Door scripting
>From: "Greg Satz" <satz-AT-iranger.com>
>Date: Fri, 21 Apr 2000 20:16:19 -0600
>
>Enclosed is the Attachment's handler I use to manage the garage doors using
>the wireless garage door sensors. These sensors were discussed on this last
>fall. Over the winter I acquired the hardware which comprised of the
>transmitters which mount on the garage doors and the transceiver which plugs
>into the wall. The transceiver also appears to work with the palmpads which
>is a nice feature. The garage door mounted transmitter/sensors detect when
>the garage door orientation changes and sends the status change to the
>transceiver which sends the update over the powerline. The interesting
>information is an integer value (number) which conveys which of three garage
>doors have opened or are open or have closed or are closed. The garage door
>status is also sent over the powerline on a periodic basis so a dead battery
>check could be written.
>
>To integrate this handler into your XTension setup, you will need to paste
>the applescript included below into your attachments window. Make sure you
>don't already have a <<event xtenRxEv>> handler present in your attachments
>or this won't work. If you do have this handler, you will need to integrate
>my changes with yours.
>
>As far as I know this will only work with a CM11A as it requires the
>extended data for the garage door integer status value.
>
>This script assumes you have defined up to three units for garage doors,
>Garage Door 1, Garage Door 2 and Garage Door 3. The setting of the garage
>door on/off or open/close is done with "no transmit". This allows you to
>have universal modules with the same names and have the wireless sensors
>update the units without creating an infinite loop (open/closing them
>forever). Also the unit Garage Sensor is the transceiver itself. The
>transceiver picks a unit code out of the air, as far as I can tell. You will
>need to define the Garage Sensor unit with the unit code it chooses. You can
>set the house code with the usual rotary dial. This may require that you
>move a module that the transceiver steps on.
>
>Let me know if you have any questions.
>
>Greg