Re: xAP Plugin for HouseBot - a touchscreen based frontend.

["Taras" <tartheode@xxxxxxxxx>]

Kevin,

Thanks for pointing me in the right direction.

I think Premise should prove flexible enough to allow for a full-
featured xAP interface. It's architecture is object-oriented and it
contains many classes representing common devices like lights,
relays, temperature sensors, motion detectors, thermostats, etc.  You
can also create new classes that inherit from others or a new class
that extends an existing one.

Premise's architecture adopts the "bridge pattern", where an
object
(a light) is decoupled from its implementation (UPB/Insteon/Zwave).

So a generic object (i.e. a light or relay) is "bound" to a
driver
object representing the physical device (i.e. Insteon-based dimmer or
Weeder relay board).  All of the control logic (i.e. when to turn the
light on and off) resides with the generic object and not the driver.

Light object #1 <----> Insteon driver object
Light object #2 <----> UPB driver object
Light object #3 <----> xAP driver object

Based on what little I now know :) here's my plan of attack:

I'll need to create a xAP driver object that exposes the BSC for
several types of devices.  For example, there'll be a folder
containing xAP Lights.  Within this folder will be all the instances
of xAP-based lights discovered by the driver.

.XAP
...Lights
.....KitchenLight
.....BedroomLight
...Relays
.....SprinklerFront
.....SprinklerRear

Each instance contains properties that are common to a Premise object
and a xAP device.  For example, a light's brightness level and
powerstate.

Am I on the right track here?

Taras





------------------------------------