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: Hardware thing names


  • Subject: RE: Hardware thing names
  • From: "Ian B" <ian.bird@xxxxxxxxx>
  • Date: Fri, 10 Dec 2004 08:47:29 -0000


Hi David

I a no expert here but as a side consideration would the 'unit' with
subaddresses only send out one heartbeat whereas if it was pretending to be
multiple units it would have to have multiple heartbeats?

Other than that there is probably (please correct me if I am wrong) no
reason other than your preference for either way. My own units use
subaddressing as I like it.

Ian

>-----Original Message-----
>From: David Buckley [mailto:db@xxxxxxx]
>Sent: 10 December 2004 06:26
>To: xAP_developer@xxxxxxx
>Subject: [xAP_developer] Hardware thing names
>
>
>
>
>
>Having a little confusion with naming conventions.
>
>Its to do with when one device "represents" many devices,
much in the
>way that the HomeSeer interface and the CBus interface do.  I have
>neither of these things so I'm going at this from some distance.
>
>I think what these interfaces do is to represent the foreign devices
>as a sort of interface:device type format, whereby all the represented
>devices are subaddresses of a single device, eg
>    acme.homeseer.pc1:loungetablelamp
>    acme.homeseer.pc1:loungeceilinglamp
>
>
>Is there any specification reason why the interface representing these
>devices cant pretend to be lots of hardware devices
>    acme.lamp.lounge.table
>    acme.lamp.lounge.ceiling
>
>Much as they would be if there were not represented devices but real
>devices???
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>




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.