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: xap with W800RF32


  • Subject: Re: xap with W800RF32
  • From: "glhopital" <glhopital@xxxxxxxxx>
  • Date: Mon, 19 Feb 2007 17:35:14 -0000

Yes, I would really be interested to get your code and try it.


--- In xap_automation@xxxxxxx, "darrenp_lock"
<darrenlock@...>
wrote:
>
> Hi,
>
> I currently use the W800RF32 => ACRF Plugn => Homeseer <=>
xap plugin
> <=> xap route but this is largely because I was already using
> HomeSeer.
>
> I did write a .NET (1.1) service back in Oct 2005 (prior to haveing
> HoemSeer) to process the W800RF32 directly to xAP.  I think it worked
> OK other than I hadn't got the debounce logic working quite right.
> Because it was using .NET 1.1 I was using a 3rd party Serial Port
> component. I guess this should now be modified to use .NET 2 (3.0?)
> and remove that dependency.
>
> The source code is all VB.NET and I'll make it available if anybody
> wishes?
>
> Rgds, Darren.
> http://www.darrensgarage.com/nodezero
>
>
> --- In xap_automation@xxxxxxx, glhopital@ wrote:
> >
> > Hello,
> > I'm searching a way to make WGL's W800RF32 work with xap.
> > Found two path :
> >
> > W800RF32 => Garyga plugin => Homeseer <=> xap plugin
<=> xap
> >
> > W800RF32 => W800 device => XPL <=> XAP
> >
> > Does anybody knows a simplier way for XAP ?
> >
> >
> >
> >
> >
> >
> ______________________________________________________________________
> ______________
> > Food fight? Enjoy some healthy debate
> > in the Yahoo! Answers Food & Drink Q&A.
> > http://answers.yahoo.com/dir/?link=list&sid=396545367
> >
>






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.