[OpenTRV-dev] OpenTRV to EmonCMS, via Node-RED (was OpenTRV boards)

Thu Dec 17 12:43:24 GMT 2015

Hi,

Up to my eyes today (major delivery on Monday) but here are some pointers.  I’ll try to do better on another round...

http://www.earth.org.uk/note-on-IoT-comms-backhaul.html
http://www.earth.org.uk/OpenTRV-protocol-discussions-201411-2.html
http://www.earth.org.uk/note-on-IoT-data-sets-and-processing.html
https://github.com/DamonHD/OpenTRV/blob/master/javasrc/uk/org/opentrv/comms/util/EventDrivenV0p2CLIFollower.java

Rgds

Damon

> On 17 Dec 2015, at 12:28, Jeremy Poulter <jeremy at bigjungle.net> wrote:
> 
> Thanks, I think they may help, can you point out the location of the concentrator and protocol docs?
> 
> Jeremy
> 
> On 17 December 2015 at 12:17, Damon Hart-Davis <damon at opentrv.uk> wrote:
> @ lines are incoming binary format stats messages
> { lines are imcoming JSON format stats messages
> 
> = is local stats possibly with trailing JSON
> 
> At worst you can look at the Java code we have in our concentrator that will should how to mechanically parse them
> 
> We do also have defintions of the common values written up in a few places such as the protocol discussions.
> 
> Would any of those be useful?
> 
> Rgds
> 
> Damon
> 
> 
> > On 17 Dec 2015, at 12:15, Bo Herrmannsen <bo.herrmannsen at gmail.com> wrote:
> >
> > i have forgotten.... but damon knows the decode part
> >
> > otherwise you got it right
> >
> > 2015-12-17 12:58 GMT+01:00 Jeremy Poulter <jeremy at bigjungle.net>:
> > Ok, I may need some help deciphering the output ;-) My single unit only has the lines starting =F0%.... I assume that is the node directly connected to the Node-Red machine, The JSON blocks {"@": .... } I assume are coming from other nodes as I would assume are the @..... lines, but can someone explain the difference and point me at where I can get the info to decode these?
> >
> > Jeremy
> >
> > PS sorry for hijacking this thread ;-) but I hope it is useful
> >
> > On 17 December 2015 at 11:34, Bo Herrmannsen <bo.herrmannsen at gmail.com> wrote:
> > @151F;T19C2;L201;O1
> > @950;T19C0;L185;O1
> > @2101;T21CF;L235;O1
> > @2800;T48C2;L1;O1
> > {"@":"0950","+":6,"vac|h":13,"O":1,"B|mV":2686}
> > =F0%@31C1;T3 6 W255 0 F255 0 W255 0 F255 0;S7 7 16;C1;{"@":"c2a2","L":112,"B|mV":3230,"occ|%":0,"vC|%":0}
> >
> > >
> > {"@":"1008","+":2,"T|C16":318,"vC|%":3008,"O":1}
> > {"@":"0950","+":7,"v|%":0,"tT|C":15,"vC|%":274}
> >
> >
> > 2015-12-17 12:17 GMT+01:00 Jeremy Poulter <jeremy at bigjungle.net>:
> > Hum, I think you are getting slightly different format of messages to me :( Can you use PuTTY (or other telnet program) to connect to port 1234 on the Node-RED machine and send me the direct output? Note once connected you have to hit enter to start receiving the output.
> >
> > Jeremy
> >
> > On 17 December 2015 at 11:09, Bo Herrmannsen <bo.herrmannsen at gmail.com> wrote:
> > and the one to the far left:
> >
> > 17/12/2015 12.07.14dd103b81.22efc8
> > msg : Object
> > { "payload": "@950;T19C1;L193;O1\r\n", "_msgid": "4fdd14d4.b022ec" }
> > 17/12/2015 12.07.19dd103b81.22efc8
> > msg : Object
> > { "payload": "@2101;T21CE;L234;O1\r\n", "_msgid": "e1d32d21.1e2cd" }
> > 17/12/2015 12.07.19dd103b81.22efc8
> > msg : Object
> > { "payload": "{\"@\":\"151f\",\"+\":0,\"v|%\":0,\"tT|C\":15,\"vC|%\":1086}\r\n", "_msgid": "38f356d4.c70caa" }
> >
> > last one is 1 of 2 in the living room
> >
> >
> >
> >
> > 2015-12-17 12:06 GMT+01:00 Bo Herrmannsen <bo.herrmannsen at gmail.com>:
> > next one from the right:
> >
> > msg.payload : Object
> > { "frost": 1, "warm": 0, "bake": 0, "valve": "0", "temp": 31, "nominalTarget": 7, "frostTarget": 7, "warmTarget": 16, "battery": 3230, "occupancy": 0 }
> >
> > 2015-12-17 12:05 GMT+01:00 Bo Herrmannsen <bo.herrmannsen at gmail.com>:
> > msg : Object
> > { "payload": "frost:1,warm:0,bake:0,valve:0,temp:31.0625,nominalTarget:7,frostTarget:7,warmTarget:16,battery:3230,occupancy:0", "nodegroup": 26, "_msgid": "2ae206e9.d51dfa" }
> >
> > 2015-12-17 11:59 GMT+01:00 Bo Herrmannsen <bo.herrmannsen at gmail.com>:
> > one to far right enabled and wait for new debug data
> >
> >
> >
> >
> > _______________________________________________
> > OpenTRV-dev mailing list
> > OpenTRV-dev at lists.opentrv.org.uk
> > http://lists.opentrv.org.uk/listinfo/opentrv-dev
> >
> >
> >
> > _______________________________________________
> > OpenTRV-dev mailing list
> > OpenTRV-dev at lists.opentrv.org.uk
> > http://lists.opentrv.org.uk/listinfo/opentrv-dev
> >
> >
> >
> > _______________________________________________
> > OpenTRV-dev mailing list
> > OpenTRV-dev at lists.opentrv.org.uk
> > http://lists.opentrv.org.uk/listinfo/opentrv-dev
> >
> >
> >
> > _______________________________________________
> > OpenTRV-dev mailing list
> > OpenTRV-dev at lists.opentrv.org.uk
> > http://lists.opentrv.org.uk/listinfo/opentrv-dev
> >
> >
> 
> _______________________________________________
> OpenTRV-dev mailing list
> OpenTRV-dev at lists.opentrv.org.uk
> http://lists.opentrv.org.uk/listinfo/opentrv-dev
> 
> _______________________________________________
> OpenTRV-dev mailing list
> OpenTRV-dev at lists.opentrv.org.uk
> http://lists.opentrv.org.uk/listinfo/opentrv-dev