My Net Costs dashboard

sumnerboy's picture

Re: My Net Costs dashboard

Not as pretty as yours...but still gives me warm fuzzies!

BTW - this graph is being rendered using Grafana on top of an InfluxDB database. My EmonTX is publishing MQTT messages which EmonCMS receives (via mqttwarn) and generates my solar 'dial' widgets and daily bar graphs. But openHAB also subscribes to the same topics and logs all the readings to its persistence engine (in my case I am using InfluxDb), which I can graph using Grafana.

dBC's picture

Re: My Net Costs dashboard

Very similar actually.  That evening peak seems pretty much universal.  I'm not even going to pretend to know what your last paragraph means, but it sounds great ;-).

sumnerboy's picture

Re: My Net Costs dashboard

Ha - sorry - was just trying to show the benefit of using MQTT as a message delivery protocol. By configuring my EmonTX to publish MQTT messages rather than direct updates to EmonCMS, I can configure multiple systems to consume those readings.

Keen2bGreen's picture

Re: My Net Costs dashboard

SummerBoy - Nice Post.

Grafana and InfluxDB look very interesting to me.

I'm keen to learn more about how you generate your feeds to a InfluxDB server.  I have InfluxDB running on my Pi.  My gut feeling is that this is a much more flexible and powerful place to store timeseries data from my OpenEnergy Monitors than using EmonCms, Personally I'm not a big fan of FLOT - it's pretty out-dated and ugly in my opinion. 

Also querying InfluxDB and using its aggregation features could be really cool - especially if you have some r/rstudio skill (which is an ambition/work in progress for me).  As a side topic I do have EmonCMS data passing into RStudio via the Average API.  This can produce some interesting visuals with the rCharts module,

Anyway - If you could post a tutorial on getting the feeds into InfluxDB - I'd be very grateful.

 

sumnerboy's picture

Re: My Net Costs dashboard

Hi Keen2bGreen - sorry I missed your post - the lack of notifications on this forum is very frustrating.

I am using openHAB (www.openhab.org) as my central home automation controller. This has a binding for MQTT which means all the values published by my EmonTX can be subscribed to directly by openHAB. openHAB also has support for persisting values to InfluxDB. Therefore my system looks a little like;

 

  [EmonTX]  ------ MQTT ----->  [*EmonCMS]

                                    ----->  [openHAB]  ----->  [InfluxDB]  ----->  [Grafana]

* via mqttwarn - a python script which subscribes to MQTT topics and republishes the values to EmonCMS in the appropriate format

Keen2bGreen's picture

Re: My Net Costs dashboard

Thanks Ben - that is helpful.  Actually I have cracked on and setup those components - all on my trusty little Pi (with a 1TB HDD).  It is amazing what the Pi can do.

My current config is EmonTX->EmonCMS (via EmonHub)->Mosquitto (via MQTT Event)->OpenHAB (via MQTT binding)->InfluxDB (via InfluxDB persist)->Grafana

I'm not aware of MQTTwarn, so will dig into that option - as I think the Event module on EmonCMS could be quite an overhead if I were to have many of my feeds replicate into OpenHAB/InfluxDB.

I've seen you are very active on many of the openHAB communities - so thanks from me on that.  openHAB is quickly becoming my new obsession... being able to take automated action from events and data monitored by many of my smart devices, plus EmonCMS is lots of fun, and potentially quite valuable - time will tell.

Thanks again - no doubt I'll be in touch with more questions/clarifications (openHAB has been a pig to wrestle with - but I'm getting the hang of the basics now)

sumnerboy's picture

Re: My Net Costs dashboard

Yep openHAB can be a struggle to get going initially - it is far from a finished/polished product yet - but once you get control of it the possibilities are endless!

If you are transmitting your sensor readings via RF then you will need something like EmonHub to translate those to something. I am using a custom version of the EmonTX (actually Robins PV diverter) sketch which publishes readings directly to MQTT - so no RF at all. This means openHAB and EmonCMS (via mqttwarn) both subscribe to the one feed and (I think) simplifies things a bit.

The downside is you need an ethernet connected EmonTX which I realise is not standard. Otherwise your scheme of using EmonHub to forward to EmonCMS is fine. If you could tweak EmonHub to also generate the MQTT publishes you would eliminate the need for EmonCMS to be doing this.

Fun and games to be had!

 

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.