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]

RFC xplOccupancy


  • Subject: RFC xplOccupancy
  • From: "Stuart Grimshaw" <stuart@xxxxxxxxxxxxxxxx>
  • Date: Wed, 09 Jun 2004 00:16:16 -0000

Recently I created a script at work to log when I entered and left the
building (I kept forgetting what time I started, and hence what time I
could leave)

I've been expanding on this idea tonight, and I have come up with
xplOccupancy. I'd like some feedback from you guys on my idea.

It's dead simple really, it's just a database to keep track of occupancy
of a location(s), with an xpl application sitting on top keeping it up to
date, and responding to requests.

At the moment I use kdebluetooth to watch for my phone, and when it see's
it (or loses it) it fires off a script. That script will fire off an xpl
occupancy message.

The schema I have in mind is loosely based on LOG.BASIC


Schema Definition
------------------

Class = OCCUPANCY
Type  = BASIC

This schema provides the ability for a device to transmit information
relating to occupancy.

xpl-cmnd Structure
------------------
Not applicable.


xpl-trig Structure
------------------
occupancy.basic
{
type=in  out
token=bluetooth  ibutton  biometric [  .... ]
id=Token ID
}

XPL-STAT Structure
------------------
Not applicable.

Pretty simple really. When a device detects the presence of a token that
represents occupancy, ie a bluetooth device, ibutton or some kind of
biometric device, it sends a message:

occupancy.basic
{
type=in
token=bluetooth
id=00:12:34:56:78:90
}

I havn't included a timestamp in the message, as I'm not sure it's needed.

There will also be a status message too, but I havn't thought that through
yet ...

--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/



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.