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: Homeseer Schema?


  • Subject: Re: Homeseer Schema?
  • From: "twitty_davis" <mick@xxxxxxxxxxxx>
  • Date: Fri, 28 Sep 2007 15:52:50 -0000

Great!  Thank you.

Mick

--- In xAP_developer@xxxxxxx, "max barker"
<max.adamiec@...>
wrote:
>
> The schema for James original Homeseer plugin is here:-
> http://mi4.biz/modules.php?name=Content&pa=showpage&pid=10
>
> There is an alternative , .net based, plugin available from the
homeseer
> forums. I'm not sure if that uses the same, or a modified schema.
>
> Max
>
> On 28/09/2007, twitty_davis <twitty_davis@...> wrote:
> >
> >   Hi,
> >
> > I've been a member of the group for some time now, but I finally
have
> > some time to start doing some development.
> >
> > I'm currently working on a web browser based user interface to my
HA
> > system, which is based on Homeseer and the Elk M1G. I'm writing
the
> > app in Ruby on Rails. So the first thing I'm developing is a Ruby
xAP
> > library. I've got the basics working, it connects (to a hub or
> > standalone) and listens for messages, sends heartbeats and has
the
> > ability to send messages. Now I'm working on adding built in
support
> > for the various schemas.
> >
> > When I click on the link for the Homeseer schema on the
xapautomation
> > web site I get a message saying I must be logged in to edit. Is
the
> > schema for this available somewhere else or am I just being
really
dense?
> >
> > After I get the Ruby xAP libary finished, if there is any
interest in
> > it I would be happy to share it.
> >
> > Thanks!
> >
> > Mick
> >
> >
> >
>






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.