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: xPLRioNet v3.9.01 Released


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

Re: Control schema


  • Subject: Re: Control schema
  • From: steve.cooper@xxxx
  • Date: Mon, 08 Dec 2003 10:50:00 +0000


In the xPL_HomeVision app I use a control.basic message with a
current=REQUEST to achieve this.

So the messaging for the probe would go

XPL-CMND
{
...
}
CONTROL.BASIC
{
DEVICE=X
TYPE=PROBE
CURRENT=REQUEST
DATA1=ZONE NAME
}

and the hub replies

XPL-STAT
{
...
}
SENSOR.BASIC
{
DEVICE=X
TYPE=PROBE
CURRENT=HIGH OR LOW
DATA1=ZONE NAME
}

Now ZONE isn't supported in the basic type so you could either

1) use DATA1 to hold the details
2) if each zone is a separate unit have a xpl interface for each with a
separate xpl instance in the header eg. source=FRANK-PROBES.UNIT1 and
source=FRANK-PROBES.UNIT2
3) or my preferred solution would be to have a control.zoned and
sensor.zoned schema which has a ZONE= in the body.

S.





___________________________________________________________________________
The information contained in this message is confidential and may be
legally privileged. If you are not the intended recipient, please do not
read, copy or otherwise use it and do not disclose it to anyone else.
Please notify the sender of the delivery error and then delete the
message from your system.
Any views or opinions expressed in this email are those of the author only.
Communications will be monitored regularly to improve our service and for
security and regulatory purposes.
Thank you for your assistance.
___________________________________________________________________________






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.