[OpenTRV-dev] Possible basis of OpenTRV hub?

[Damon Hart-Davis]

Don’t know.

I think that Mike has some of the RFM23 setup worked out, but with the information that Kevin gathered, and an OEM unit to play with, I could probably do it.  Just depends as I say what other priorities there are and how much time I have!

Or maybe someone here could tinker with a REV1 or REV2 board to get it to talk OEM and contribute a code module?

Rgds

Damon


On 9 Apr 2014, at 19:50, Bo Herrmannsen <EMAIL ADDRESS HIDDEN> wrote:

> Yo Damon
> 
> How hard do you think it is to extend OpenTRV to talk OEM'ish ?
> 
> 
> 
> -----Oprindelig meddelelse----- From: Damon Hart-Davis
> Sent: Wednesday, April 09, 2014 8:19 PM
> To: Closed list for developer discussions
> Subject: Re: [OpenTRV-dev] Possible basis of OpenTRV hub?
> 
> Hi Kevin,
> 
> Thanks for all the juicy RFM12 info: I have replicated it to a number of places where I (and others) might actually be able to find it again!
> 
> Wow, my excuses may be evaporating!
> 
> Rgds
> 
> Damon
> 
> 
> On 9 Apr 2014, at 14:15, Kevin Wood <EMAIL ADDRESS HIDDEN> wrote:
> 
>> I've actually just come across this, which looks to be quite a good
>> description of the Jeelib RFM12 implementation.
>> 
>> http://jeelabs.org/2011/01/14/nodes-addresses-and-interference/
>> 
>> Kevin
>> 
>> _______________________________________________
>> OpenTRV-dev mailing list
>> EMAIL ADDRESS HIDDEN
>> http://lists.opentrv.org.uk/listinfo/opentrv-dev
>> 
> 
> _______________________________________________
> OpenTRV-dev mailing list
> EMAIL ADDRESS HIDDEN
> http://lists.opentrv.org.uk/listinfo/opentrv-dev 
> _______________________________________________
> OpenTRV-dev mailing list
> EMAIL ADDRESS HIDDEN
> http://lists.opentrv.org.uk/listinfo/opentrv-dev
>