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: Test Please Ignore


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

Re: W800 Service Updated


  • Subject: Re: W800 Service Updated
  • From: "Mal Lansell" <mlansell@xxxxxxxxxxxxxx>
  • Date: Mon, 20 Dec 2004 00:14:50 -0000



You can safely uninstall the old version and then install the new
one.  The config is not lost because I don't remove it from the
registry.

Mal


--- In ukha_xpl@xxxxxxx, "gmotichka" <gmotichka@h...>
wrote:
>
> Mal,
>
> Thanks for the update again.
> It looks like the only way to update is to do a full install. Is
> this the way of all xpl devices or is it possible to just copy
files
> over older one?
>
> I'm alway leary of ruining something that is working.
>
> George M
>
>
>
>
>
> --- In ukha_xpl@xxxxxxx, "Mal Lansell" <mlansell@f...>
wrote:
> >
> > I've updated the W800RF32 service to handle messages from X10
> > security RF devices
> >
> > Unfortunately, the security devices are intended to be used only
> with
> > their base stations, rather than as general X10 controls.  The
> > messages they send have no relation to any of the standard X10
> > functions.  Therefore, the service sends security messages using
> the
> > remote.basic schema (standard X10 RF commands are still sent
using
> > X10.basic).
> >
> > It uses two of the remote.basic message body elements -
> >     keys=num1 (where num1 is the keycode sent by the device
0-255)
> >     device=num2 (where num2 is the id of the security device 0-
255)
> >
> > This should be sufficient to distinguish between controllers, and
> to
> > use their commands to trigger determinators etc.
> >
> > Mal






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.