[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: xplHal - unknown vendor
- Subject: Re: xplHal - unknown vendor
- From: Jon Payne
- Date: Thu, 18 Mar 2004 14:36:00 +0000
Hi John,
Yep, developing my own Java framework.
Ah, what I said wasn't quite true, it says this:
"The xPLHal server returned an unexpected response.
The following response was returned by the server:
418 No vendor information for specified device"
I think I am sending out responses as required, below is the log of what's
received/sent out:
Send first message:
------- sending xPL message ---------
xpl-stat
{
hop=1
source=jgp-callerid.default
target=*
}
config.app
{
interval=5
port=50001
remote-ip=192.168.0.1
}
-------------------------------------
* Recevied a CURRENT config message. COMMAND is REQUEST
------- sending xPL message ---------
xpl-stat
{
hop=1
source=jgp-callerid.default
target=xpl-xplhal.bliss1
}
CONFIG.CURRENT
{
interval=5
newconf=default
}
-------------------------------------
* Received a LIST config message. COMMAND is REQUEST
------- sending xPL message ---------
xpl-stat
{
hop=1
source=jgp-callerid.default
target=xpl-xplhal.bliss1
}
CONFIG.LIST
{
OPTION=interval
RECONF=newconf
}
----- Original Message -----
From: "John B" <<a
href="/group/ukha_xpl/post?postID=Dx48TdKNJhKvd0KTH8jLLXl3ws9fQpPAgTUwm-RdraHE7ZENMajj3ZtER-__jhZ8nVJOEqPaC7Eduey4IUX4P0iA5H12rA">home-automation@j...</a>>
To: <<a
href="/group/ukha_xpl/post?postID=gmKFau1wprVYbWUmuoB_mYwsP_YVx0BwBfSj7iqByXo2LoppNwxTOiHfSF5zAJjMH3XAAydHl9p2grv8xOQMsw">ukha_xpl@xxxxxxx</a>>
Sent: Thursday, March 18, 2004 7:30 AM
Subject: Re: [ukha_xpl] xplHal - unknown vendor
> Hi Jon,
>
> > Was doing a bit of dev work last night and found that xplHal
wouldn't
> > configuration my device saying it was an unknown vendor. The
question is
how
> > do I tell it I am a known vendor?
>
> You shouldn't have to.
>
> You can go into writing plugins etc. to improve the ease with which it
configures your device (as per Ian's post) but even without this
information
it should still configure your device.
>
> When your device heartbeats for the first time, xPLHal will send it
two
messages:
>
> xpl-cmnd
> {
> ...
> }
> config.list
> {
> command=request
> }
>
> To which you should reply with a list of all config items that you
support, e.g.
>
> xpl-stat
> {
> ...
> }
> config.list
> {
> reconf=newconf
> option=interval
> option=filter[16]
> option=group[16]
> }
>
> The other message xPLHal will send is:
>
> xpl-cmnd
> {
> ...
> }
> config.current
> {
> command=request
> }
>
> To which you reply with the values of your current config items, e.g.
>
> xpl-stat
> {
> ...
> }
> config.current
> {
> newconf=myinstance
> interval=5
> }
>
> If you are using one of the development frameworks (either my .NET DLL
or
Tony's OCX) then all this config handling is done for you and you shouldn't
need to be aware of it.
>
> However, if you're developing entirely yourself, then you'll need to
make
sure you are sending out config.list and config.current messages when
requested to do so by xPLHal, otherwise you'll receive errors from xPLHal
saying your device cannot be configured.
>
> HTH,
>
> John
>
>
>
> xPL Links: <a href="http://www.xplproject.org.uk">http://www.xplproject.org.uk</a>
<a href="http://www.xplhal.com">http://www.xplhal.com</a>
<a href="http://www.xpl.myby.co.uk">http://www.xpl.myby.co.uk</a>
> To Post a Message: <a
href="/group/ukha_xpl/post?postID=gmKFau1wprVYbWUmuoB_mYwsP_YVx0BwBfSj7iqByXo2LoppNwxTOiHfSF5zAJjMH3XAAydHl9p2grv8xOQMsw">ukha_xpl@xxxxxxx</a>
> To Subscribe: <a
href="/group/ukha_xpl/post?postID=iJV5G8KOEIIN0TVj1-EAT7hnRHoPHg7UldqshYa8ToSe9F2Ur2z9I_2DidV17sR3AjIrP-94cRu684Ah7sVxclV5X3HypUqo">ukha_xpl-subscribe@xxxxxxx</a>
> To Unsubscribe: <a
href="/group/ukha_xpl/post?postID=XTwES3_fkcUf9i-NoAsOgw_hT3IqUAZ4DiWHDvp50BkiOhpvQlYz7gSR1ZbN1nDBboo4PaLBXCBTNahskaT5q_GyzD9OkU84jWk">ukha_xpl-unsubscribe@xxxxxxx</a>
> Yahoo! Groups Links
>
>
>
>
xPL Main Index |
xPL Thread Index |
xPL Home |
Archives Home
|