The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


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

Re: Vendor Id registration


  • Subject: Re: Vendor Id registration
  • From: "m.rintala" <mikko.rintala@xxxxxxxxx>
  • Date: Mon, 31 Mar 2008 16:39:45 -0000

Hi,

Thanks! Most probably I will use TSC schema, since that covers allmost
all my needs. I assume that it is not possible use more than one
schema
in one message. I have temperature sensors and relays attached to
temperature alarm messages, TSC would cover sensor level and BSC
relay status. So, two different messages are required if schema is
respected?

Best regards,

Mikko Rintala
MR Soft

--- In xAP_developer@xxxxxxx, Kevin Hawkins
<yahoogroupskh@...> wrote:
>
> Welcome Mikko - and you have 'MRSoft' reserved for your Vendor ID.
>
> You should probably consider using the BSC and/or TSC schema for
your
> application
>
> BSC is most prolific and hence a favourite for compatibility but it
> doesn't handle temperature too well - meaning that you will have to
> present your devices as 'TEXT' rather than 'LEVEL' based devices.
This
> is because BSC Level devices can't have negative values and also
there
> is no provision for identifying the units of measurement.
> http://www.xapautomation.org/index.php?
title=Basic_Status_and_Control_Schema
>
> TSC is a new schema aimed at exactly your needs  (Telemetry Status
and
> Control) .   It is based around BSC but includes other approriate
> aspects for sensor data.
> http://www.xapautomation.org/index.php?
title=xAP_Telemetry_Status_and_Control_Schema
>
>   Any questions... just ask away.
>
>    cheers Kevin




------------------------------------


xAP_Development Main Index | xAP_Development Thread Index | xAP_Development 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.