I’ve had my emonPi and Solar install for about 18 months now… very happy.
We currently have no PV battery, no immersion/header tank as both central heating and DHW are through the 3 year old combi-boiler.
So to this point i’ve not really had to worry about any scheduling of large electricity draw items.
Moving to Agile has changed the mindset a little, avoiding washing, tumble drier etc between 4pm and 7pm… but its all manual and we try to use the Solar where we can for those bigger bits.
But now, we are contemplating an EV.
It seems like the majority of EV chargers are either good at being hooked up to a house with Solar (like a Zappi)… or being developed with API and TOU tariffs in mind (Ohme Charger).
I can’t seem to find an EV charger than can do BOTH?
Is this where OpenEVSE and Demand Shaper fills the gap?
Ideally you want a simple tick list / set of rules like.
Is there excess Solar generation - yes, that always takes priority
Is Car battery below 50% AND Agile pricing below 3p - yes
Good question @Zarch. We would like to support both modes simultaneously. I like your idea for the tick list. The demandshaper is designed to automate the process of making sure the EV reaches the desired state of charge by a specified end time. In an ideal world it needs to take into account both the Agile forecast and an estimation of how much its going to get from the sun in the day to work out how much to charge and when…
I see the list as maybe a set of simple rules that could be set up.
A bit like a priority ordered set of rules?
I’m also thinking that something similar could work with a battery too?
So in winter, the emphasis could be towards filling the battery overnight when prices are cheap and through the summer just fill up on solar.
The obvious problem with batteries is what appears a distinct lack of API integration with the majority of battery inverters/smarts.
Back to the EV charger then and the Govt grant.
Would this be the order of things?
I realised I had not tried both the PV diversion and the timer function on the EmonEvse together yet (as I have only the EV here) and so had a go at testing this earlier with a simulated solar input, it looks like the timer needs to not be engaged for the eco mode divert to work - which means I need to adapt the demandshaper to switch between modes at the right time - at least to support a basic implementation.
@glyn.hudson is the best person to talk to about the EmonEvse charger and electrical installation details, he was away from the office today in a meeting, I will send him a message to take a look at your questions.
The EmonEvse measures the current draw of the charger and reports this alongside other properties back to the emonPi.
Most installers will claim the grant on your behalf so you only need the price with £500 discount. However, if you prefer you can claim it yourself
It can vary a lot depending on if your electrical setup e.g how close the EVSE is to your fuse board, length of cable, ground works required. Normally installation is around £500. It could be lower for an easy install or more if you need lots of ground works!
I would recommend contacting EcoPlugg, they install nationwide and are familer with our unit:
I was looking at ecmfw data and then getting the metrogram info, then using the cloud base to determine the cloud cover… just trying to find a source for it… I can get some predictive cloudbase from my acurite weather station but that only predictive for a few hours in advance.
but I think this would work involve a bit of scraping info.
each day scrap the next two day of cloud cover during the day time on a hourly bases
I just never scraped svg image before should be doable just to figure out how
all you have to do is edit the time [2020-02-10-03] year- month -day- hour and grab the predictive cloud cover forecast.
Maybe you already know about this but - for UK users at least - the Met Office Datapoint has worked for me. It doesn’t supply cloud cover data but perhaps reasonable use could be made of the “Weather Type” field, specifically looking for values “Sunny day” and “Partly cloudy (day)”. It can provide a local 5-day 3-hour forecast in XML or JSON.
I had a go at importing historic and forecast data from the darksky api yesterday, the intention was to get a precipitation forecast to forecast the output of a local micro hydro generator, but I also pulled in all the other observations and forecast values, here’s an example of UV index and cloud cover:
Maybe… there are a few things that do make it more complicated… API allows historic access of one day at a time, I created a batch script to read a year of history in… that would need to be customised to something more generic for wider use…
No, your end-users should not sign up for Dark Sky API keys as a means for you to circumvent the daily cap of 1,000 free calls. The 1,000 free calls per day are intended for one developer or company to explore the API.
So we might need to do something there to play fair…
Yes I was aware of that but if it was only forward looking (as that is what most people would look for) and only picked up an updated forecast a few times a day, then I think it would meet the fair use.
With elements to fill in for API key etc, could be quite easy for someone to use.
You could also get wind data, to predict if there might be an excess of renewables as well.
However, I’m not sure the automation stuff is worthwhile developing within EmonCMS as there are some good automation tools out there already.
FWIW, DataPoint is being replaced by DataHub, so that would be the one to build a new service on, but that doesn’t provide cloud cover or solar irradiation either unfortunately. The Met Office have told me I will need to pay if I want that data. Their forecast website does provide some indications of ‘sunny’ and it’s possible to scrape that.