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: config.list ???


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

RE: Re: Vendor ID request


  • Subject: RE: Re: Vendor ID request
  • From: Tony T
  • Date: Wed, 15 Jan 2003 06:31:00 +0000

> DeviceCode=<code of currently stored ir command>
> KeyCode =<manufacturer key code>
>
> If the KeyCode was present then the DeviceCode would
> represent the manufacturers device code
>
> e.g.
>
> A device that stores learned IR would use
>
> DeviceCode=21
>
> to 'play back' the IR stored in location 21 (for example Homevision)
>
> A device that reproduced IR commands (like an All-for One
> remote type device)
>
> DeviceCode=10
> KeyCode=232
>
> in the above DeviceCode is 10 which is assigned to Hitachi,
> and the KeyCode is for the power button

Good points, I think my use of the word 'description' and the example I
gave
are misleading

Within xpl we should consider the value part of a name/value pair as a
variant (no data type, for anyone who hasn't come across the term i.e.
since
the value is always a string it is up to the receiving app/device to decide
whether to intrepret the value as text, number, date etc)

Within my redrat app device=10, button=232, zone=1 would be just as valid
as
device=dvd1, button=play, zone=lounge
It is whatever is assigned by the installer

The app/device which is the targetted zone, would intrepet the values as
required within the remote.basic schema.

Does this work for everyone?

I've put a revised schema at
<a href="http://www.xaphal.com/xpl/Schemas/REMOTE.BASIC.txt";>http://www.xaphal.com/xpl/Schemas/REMOTE.BASIC.txt</a>

Thanks
Tony






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.