RE: [misterhouse-users] XAP Hub website down

[Ian L. <ia...@wi...>]

Hi Bruce, (and hello list, as this is my first post here)=20

I'm one of the xPL team, and just signed up here to see if we can help -

Misterhouse already has an xPL Vendor ID assigned - MHOUSE, this is used
in the Source and target fields of the xPL message.

It's worth getting some separation in place between xAP and xPL - we
forked from the xAP project over 18 months ago and the protocols have
separated far enough that they need to be handled (both in protocol
terms, and in operation) separately.

xPL has an IANA assigned port - 3865, and doesn't have the concept of a
UID (our message header is much simpler)

To integrate with existing systems, we do need an XML vendor description
file for Misterhouse - the various configuration and scripting tools all
use this xml description to identify the commands accepted by an app,
and the triggers that it can generate.

I have to confess to not knowing much about MH, but I'd imagine that the
xml fragments we already have in place for xPL devices would be of use
in integration with MH.

I'm happy to spend some time getting MH's xPL support up to scratch
using the currently defined Schemas.

Ian.



-----Original Message-----
From: mis...@li...
[mailto:mis...@li...] On Behalf Of
Bruce Winter
Sent: 29 May 2004 15:16
To: mis...@li...
Subject: RE: [misterhouse-users] XAP Hub website down

> > classes listen on the same port--originally defined for xAP (3639).
> >  If xPL is all that you really want, then consider redefining your
> > xpl port in your parms file as xap_port=3D3865 (be forewarned--I've
> > not tried this). =20
>=20
> But it does work :) Another problem though is that xPLHal doesn't=20
> know the Misterhouse scheme and therefor doesn't accept messages=20
> from it. Could someone encourage the developer to support Mister House
:-)

This might be more of a MisterHouse issues.  I've used and debuged a
number of xAP/xPL clients that SEND data to mh, but not many that
RECEIVE data from mh.   It could be the syntax of the data packet needs
to debuged a bit. =20

What kind of data were you trying to send from mh?  Some things like X10
and callerid have schemes already defined, so all we should have to do
is match up to that.  Other things we would need to come up with a
scheme and have xPLHal support it.

Also, the uid mh defaults to is a generic FF123400, not one that
officially designates the source of the data as mh.   Now that we have
some interest and users of the xAP and xPL data, I'll apply for official
xAP and xPL uids we can use. =20

Bruce