[OpenTRV-dev] Possible basis of OpenTRV hub?

[Bo Herrmannsen]

I think Damon got some spare units you can play with, if not I'm home going 
so can test code pretty often during the day

Do you have SVN access?

it will be 3 weeks or so before the boards get back from china so not so 
much rush




-----Oprindelig meddelelse----- 
From: Kevin Wood
Sent: Friday, April 11, 2014 12:22 PM
To: Closed list for developer discussions
Subject: Re: [OpenTRV-dev] Possible basis of OpenTRV hub?

I could probably add the code to OpenTRV reasonably easily - to send
values for logging on EMonCMS, at any rate. Receiving data from any
scheduling extension to EMonCMS might be more of a challenge.

The problem is, I don't have any OpenTRV hardware to test it on, so I'd
have to code it "blind".

One thing I would say about EMonCMS on the Pi is make sure you get the
RFM12Pi V2 rather than the earlier one, as the RFM12Pi firmware can then
be updated from the Pi itself and this makes it much easier to experiment.

Kevin

> if it helps anything i have thought of setting up a pi to run emoncms...
> need to have a platform to test my version of the GivMon interface anyway
>
> if anyone are up to coding a module for Emoncms and extending the OpenTRV
> i'm happy to provide ssh access etc to the pi and test arduino code...
>
> mind you i run Rev1 boards
>
>
> i imagine if anyone has the time and success with this we could almost
> drop
> the UI at the box and concentrate on a web ui instead :-D
>
>
>
> -----Oprindelig meddelelse-----
> From: Damon Hart-Davis
> Sent: Wednesday, April 09, 2014 9:04 PM
> To: Closed list for developer discussions
> Subject: Re: [OpenTRV-dev] Possible basis of OpenTRV hub?
>
> 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
>>
>
> _______________________________________________
> 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