Re: Z-Wave Getting Started?

["davepow16" <Davepow16@xxxxxxxxx>]

That was great info.  I have read up on the BSC schemas now and
understand the concept.  Now I need a kick start to implementing
what I have learned.

As I said I am developing in C#

In my solution I currently have:
Service Project
Service Installer Project
Service Configuration Project

The service project is where the z-wave sdk classes will live and it
is where the connection to the z-wave network will be esablished.
This is also where xAP will be implemented.

The Service installer is pretty much complete and does what its name
implies. It provides an interface for installing the service.

The Service Configuration project is where the user can setup the
xAP Connection information such as IP and other information yet to
be determined.

I am now thinking that a fourth project is needed which will be a
ZWave xAP GUI client interface.  This will allow the user to pick
meaningful address names by filing out a collection of location
fields. This will also be the place where polling intervals are
setup and will be the place for the user to add and remove device
and do any other network configuration that might be needed.  This
application would typically only be run when a new device is added
or an old device is removed.

Z-wave stores a lot of information in its primary controller, but an
enumerated location of the device is not one of them.  The
Controller stores it own unique ID as well as information to
wheather it is a primary or secondary controller. To access this
information I would create a controller object using the
ControlThink SDK.  The controller object would also contain a
collection of devices on the network.  That collection is accessible
by nodeid and index.  I would use nodeids since this never changes
once a device is added.

My current thoughts are to have the Service Project connect to the z-
wave controller and pull the list of devices.  Look up each device
type by its node ID and concatenate that to a generic location for
starters until the user has changed that location.  Before it
creates the location it would first look up the node ID in an xml
file and determine if the address already exist.  The user would
edit that same xml file and that same xml file would be used to
create the addresses to the devices.  The order of all this still
needs to be worked out.

My main goal is to be able to make the Service Project indepentent
from any other projects during normal execution.

I think my next order of business is to setup a z-wave network
connection in my service project and write the code for determining
if the address exist in the xml file.  If it does not then it will
create the address using a generic location.

Does this sound like a good plan to you guys?