<div dir="ltr"><div>Hum, good idea. Should be easy (assuming you are running on Linux) to pull that info from the relevant files (/proc/meminfo and /proc/loadavg) using the file node, parse (probably with a Javascript function) and post to EmonCMS. I will try and have a go at that but I am sure someone has probably done it (at least the CPU/Mem usage) already.<br></div><div><br></div><div>WARNING: Linux is designed to essentially use all the memory. THIS IS NOT A BAD THING as it caches loads of things and that helps with performance, MemFree is not actually the amount of free memory from a practical sense Buffers and Cached are also essentially free memory. </div><div><br></div><div>Jeremy</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 17 December 2015 at 13:14, Bo Herrmannsen <span dir="ltr"><<a href="mailto:bo.herrmannsen@gmail.com" target="_blank">bo.herrmannsen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">hijacking it even more.... and then again the guy from belgium wanted integration between opentrv and emoncms<div><br></div><div>this is half the deal :-D</div><div><br></div><div><br></div><div>but Q.... bit OT... how would i store CPU load and Memory load? just so i can keep an eye on it</div><span class=""><div><br><div class="gmail_extra"><br><div class="gmail_quote">2015-12-17 14:06 GMT+01:00 Jeremy Poulter <span dir="ltr"><<a href="mailto:jeremy@bigjungle.net" target="_blank">jeremy@bigjungle.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks I will look through those. <div><br></div><div>Jeremy</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 17 December 2015 at 12:43, Damon Hart-Davis <span dir="ltr"><<a href="mailto:dhd@exnet.com" target="_blank">dhd@exnet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Up to my eyes today (major delivery on Monday) but here are some pointers. I’ll try to do better on another round...<br>
<br>
<a href="http://www.earth.org.uk/note-on-IoT-comms-backhaul.html" rel="noreferrer" target="_blank">http://www.earth.org.uk/note-on-IoT-comms-backhaul.html</a><br>
<a href="http://www.earth.org.uk/OpenTRV-protocol-discussions-201411-2.html" rel="noreferrer" target="_blank">http://www.earth.org.uk/OpenTRV-protocol-discussions-201411-2.html</a><br>
<a href="http://www.earth.org.uk/note-on-IoT-data-sets-and-processing.html" rel="noreferrer" target="_blank">http://www.earth.org.uk/note-on-IoT-data-sets-and-processing.html</a><br>
<a href="https://github.com/DamonHD/OpenTRV/blob/master/javasrc/uk/org/opentrv/comms/util/EventDrivenV0p2CLIFollower.java" rel="noreferrer" target="_blank">https://github.com/DamonHD/OpenTRV/blob/master/javasrc/uk/org/opentrv/comms/util/EventDrivenV0p2CLIFollower.java</a><br>
<br>
Rgds<br>
<span><font color="#888888"><br>
Damon<br>
</font></span><div><div><br>
<br>
> On 17 Dec 2015, at 12:28, Jeremy Poulter <<a href="mailto:jeremy@bigjungle.net" target="_blank">jeremy@bigjungle.net</a>> wrote:<br>
><br>
> Thanks, I think they may help, can you point out the location of the concentrator and protocol docs?<br>
><br>
> Jeremy<br></div></div></blockquote></div></div></blockquote></div></div></div></span></div>
<br>_______________________________________________<br>
OpenTRV-dev mailing list<br>
<a href="mailto:OpenTRV-dev@lists.opentrv.org.uk">OpenTRV-dev@lists.opentrv.org.uk</a><br>
<a href="http://lists.opentrv.org.uk/listinfo/opentrv-dev" rel="noreferrer" target="_blank">http://lists.opentrv.org.uk/listinfo/opentrv-dev</a><br>
<br></blockquote></div><br></div>