The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024

Latest message you have seen: Re: plugin XML files


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

Re: Developing with lib v4...


  • Subject: Re: Developing with lib v4...
  • From: "Mal Lansell" <mal@xxxxxxxxxxx>
  • Date: Thu, 22 Sep 2005 16:36:30 -0000

Scrub that - the vendor xml is for determinators isn't it?

It looks like you're app is not receiving messages from xPLHal - so
it won't respond to xPLHals config requests.  xPLHal therefore won't
be updated with the new config items.

I'd use CPorts and see what everything is bound to (BTW, why does
xPLHal bind to 30-odd UDP ports?)

Mal


--- In ukha_xpl@xxxxxxx, "Mal Lansell" <mal@l...> wrote:
> Don't you have to add the config items to your vendor xml file to
> have them show up in xPLHal (or is that for some other reason...?)
>
>
>
> --- In ukha_xpl@xxxxxxx, "Ian Lowe" <ian.lowe@w...>
wrote:
> >
> > And having some problems, which might be just me being a bit
> daft...
> >
> > I have added a couple of config items like this:
> >
> >     xPLListener = New
xpllib.XplListener("wmute-vswitch", 1)
> >     xPLListener.ConfigItems.Add("label1", "Item
1",
> > xpllib.xplConfigTypes.xConfig)
> >     xPLListener.ConfigItems.Add("label2", "Item
2",
> > xpllib.xplConfigTypes.xConfig)
> >
> > When I run it, the device appears awaiting config in xplhal
manager
> > *but* the extra config items are not present...
> >
> > It also spams the crap out of the network - it seems to fail
doing
> the
> > config, and does so every 3 seconds!
> >
> > I'm stepping my code back a bit to find out where this became
> unstable -
> > soemthing is definetly wrong though.. :
> >
> > Ian.






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.