Community
OpenEnergyMonitor

OpenEnergyMonitor Community

emonESP to emoncms

Tags: #<Tag:0x00007fc9b0bac0a8> #<Tag:0x00007fc9af293cd8>

After a fair bit of trial and error my WeMos D1 Mini has emonESP loaded and can update emoncms.

There’s a bug in the example API syntax which shows http://192.168.1.128/input?string=CT1:3935,CT2:325,T0=20.5 but should be http://192.168.1.128/input?string=CT1:3935,CT2:325,T0:20.5

SSL (https) is crashing the ESP but http is OK. I can send an odd SSL API command but it quickly runs out of memory so I’m guessing there’s a memory leak in the code somewhere.

Based on the test API url of http://192.168.1.128/input?string=CT1:3935,CT2:325,T0:20.5 I have the inputs set up as log processes and feeds updating in emoncms. I can also set up gauge and thermometer widgets but I’m not seeing anything in the graphs of the dashboard or the Data Viewer. Is there some kind of averaging taking place and any idea why I don’t see any data?

I added the Android Emoncms app and that does show some data but still nothing in the Dashboard graph and graph sections of emoncms.org.

Nice work getting EmonESP up and running.

Thanks for reporting. Where exactly do you see this example API typo?

You need a certain amount of data for the graph vis to work. Could you post a screenshot? The Emoncms Apps module requires 24hrs of data.

Highlighted in yellow in the screenshot below (section 4 Latest Data).
API Syntax error

Data finally arrived, thanks.

@glyn.hudson I am still not seeing any data in the Email Reports for daily KWH. How long should it take to see data in the email preview facility and does it matter if there is a break for a few hours in the data streaming i.e. does it need to be a continuous 24 / 48 / 72 hour stream before the data becomes available?

Thanks, typo has been fixed:

Yes, I would imagine you will need minimum 24hrs of data for the email reporting to work. Maybe @TrystanLea can clarify?

1 Like

I am a few days into data streaming now so I think I have something set up incorrectly for email reporting.
I will keep an eye on it over the next 48 hours but I wondered how it differed from the dashboard etc.

I have a feed called “KWH” and that is fine for the dashboard and I am also selecting it in the email interface for the following drop down box:

Select cumulative kwh consumptiion feed: (autoname: use_kwh)

Do I specifically need to name the feed use_kwh ?

Also now that my datastreams are “live” it’s nice to see the gauges and thermometer moving in “real time” in the dashboard but am I right in thinking the graphs don’t have any automatic scrolling, even if very slowly depending on the granularity?

@TrystanLea and @glyn.hudson as per the screenshot below I can get a graph of daily KWH’s (presently simulated until my CT’s arrive) from Visualization.

But I still can’t get an email of the KWH’s from Email Reports.

Edit: scrap that the data has finally started to appear on day 6.
Email Report

Is the 6th day normal? I can understand perhaps day 3 so you at least have 1 full day’s data but the 6th day seems rather odd.

Are you sure it’s a daily report? I have no experience of the email reports myself, but I suspect from what you’ve posted it’s a weekly report of daily data and sent out on the first day of the week with the previous weeks data. hence the data included is for Monday to Sunday including 2 days at 0.0 kWh since you only have data for the proceeding 5 days.

1 Like

Yes @pb66 looks like that’s how it works so it could take as long as the 8th day before you know it’s working.
I actually received my first email today.
The email system has a “preview” and “test” feature which gives the impression you can see the data before waiting for the email. This is true but it will not show any data until the first week ends.