The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: Vendor ID and a question


  • Subject: RE: Vendor ID and a question
  • From: "Eric Vickery" <ericvic@xxxxxxxxxxx>
  • Date: Fri, 9 Dec 2005 17:31:10 -0600

Ian,

Lets make it EVISIONS

Can you give me an example of a status request packet?

I'm reading over the prior messages. Lots of good info out there, so
hopefully I won't ask too many questions that have already been
answered.

Thanks,
Eric

-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On
Behalf Of Ian Lowe
Sent: Friday, December 09, 2005 3:56 PM
To: ukha_xpl@xxxxxxx
Subject: RE: [ukha_xpl] Vendor ID and a question



Hi Eric -

How about EVISION as a Vendor ID? That's nice and short.

The scenario you describe is quite a common one that we have encountered
- the way to represent many devices like this is to use a command
structure
like:

Device=
Command=
Value=

Etc

Where "device=" would be a suitable label for your end nodes.

(this is like the x10.basic schema, also sensor.basic and control.basic)

There's a nice simple rule for whether you change the instance or use a
device= label - the last point in the chain which talks xPL natively
should be used in the header as the instance, anything talking a non xpl
protocol should use a device=.

As a simple example, it would be wrong to use:

wmute-myx10gate.A1
wmute-myx10gate.E3

Etc.

More appropriate is:

Wmute-myx10gate.gateway
Device=A1

Wmute-myx10gate.gateway
Device=E3

Your gateway can (and should) list the devices it knows about when
queried by a status request packet.

Hope that helps :)

Let me know which vendor ID you would like, and I'll get it registered

Ian.

-----Original Message-----
From: ukha_xpl@xxxxxxx [mailto:ukha_xpl@xxxxxxx] On
Behalf Of mustang8760
Sent: 09 December 2005 20:31
To: ukha_xpl@xxxxxxx
Subject: [ukha_xpl] Vendor ID and a question

I would like to get a vendor ID. I have a little "company" called
Electronic Visions and would like a vendor ID for it.

Also I have been reading up on xAP and xPL and I like the device
discovery and configuration that xPL has. I'm trying to figure out if
the discovery mechanism built into xPL would work for what I want to do.
Say I have a application that holds the state of all the lighting
devices in my house, some of them may be X-10 and some may be UPB or
Insteon so I want to present them to the rest of the xPL world as just
lighting devices and keep how they interact with the actual physical
devices hidden. Would I have to have a different xPL device for each
light or could just the instance ID change? For instance could I say (I
know this is not realy valid xPL but it is just for example)
electronicvisions-deviceholder.(some instance ID) and keep the
electronicvisions-deviceholder. for each light? If I can then how would
other xPL application be able to discover that my application held the
state for 10 lights? Sorry if this is a bit confusing, I'm still very
new to xPL but I want to get a better handle on it before I start
coding.

Thanks,
Eric







xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.