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: Re: Consensus on BSC temperature reporting?



Hi Lehane,

Quoting Lehane Kellett (8/29/06 1:01 PM):
> OK - so how about new classes - sensor.report and sensor.cmd?
>
> Devices could be simple (one wire) or complex (complete CH system).

One reaction that I had is that it appears that each sensor.report
message has a single body.  Is that correct?  I am asking as a result of
having wrestled w/ how to treat one of my physical devices that reports
both humidity and temperature (the chip itself does that).  For the time
being, I've decided to "virtualize" this single device into
multiple
subaddresses--each having their own xAP UID.  While that keeps the
mapping of single block to single device clean, it does cause some
complications--among them having to track multiple UIDs to single real
device (which often has it's own real ID).  It also means that the
reporting interval is somewhat arbitrary from a command standpoint in
that both ought to give out their values together.  On the other hand,
it does make sense from an event standpoint (vice info) as one of the 2
measurements passed some delta (change) and not both.

Also, while I can't think of any sensors off-hand that don't limit to
single, scalar values, I don't see how the value example is extended to
multi-variant.  If it were multi-variant, would values be comma separated?

Somewhat related, I've been working on a "raw anemometer" project
that
uses the NetIOM xAP to report pulse counts on x revolutions.  In turn, I
calculate wind-speed.  One good thing about this is I have more control
over the reporting and calculation of instantaneous wind speed than most
consumer weather stations.  But, if I were to use the schema that you
posted, I seem to only have room for one "value".  How are
"instantaneous" vice "average" values handled?  Also, I
can change the
baseline for the averaging "window".  How might that ancillary
parameters that provide a context (e.g., averaging window in seconds)
for "value" be reflected in the schema?

Gregg




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