Solved

Can we get access to the live usage API?



Show first post

138 replies

That reminds me. Need to sort out leaving for a better company.
Not happy with the fact I've been on the waiting list for the API for over a year now and heard little from it except that it's now being backbenched, and the rediculous price hike recently.
Wish me luck 👍
Userlevel 4
Badge

Advanced programmers could no doubt script the whole session connection to recover the session cookies. I am one, but I haven't bothered.


Further to @ErTnEc's git contribution, I have updated this to do the V2 API for historic consumption. I run the following script daily to download the previous day's half-hourly consumption into the MySQL DB that underpins my NodeRED installation: load_readings.py.
There's an issue with NodeRED HTTPrequest which causes logon problems so I haven't got the native NodeRED version working. Sorry. It's not worth my spending time on this because I will moving supplier when my contract ends. I really like OVO, but a 30+% price hike is just too much, when other suppliers offer better deals.


Thanks for this. I haven't managed to get your load_readings.py script to run on Windows, but as long as I'm already logged into MyOvo, pasting a handcrafted url from your script certainly returns the data, which is great because the url which I was using last winter no longer works! I copy the displayed data into a python script which then parses and outputs something human readable and graphable into a csv file.
Thanks Terry, Im quiet new to Python but learning fast. Ive not ventured into NodeRED yet. When I ran the script there was issues with MySQL but the data was displayed on the screen as it should.

Trying to work out how to adapt the code to capture gas data.
Userlevel 3
works a treat.
@jdenver, If you check, I've updated the script slightly. What I've found is that the Smart Meter sends its SMS message once a day about 02:00, so the consumption figures for the previous day are only available after that. The message occasionally fails for whatever reason, so you can miss a day, but it does retry at some point. So what I've done is to query the max DTS from my readings table and set the FROM to 30 mins after the last end. That way, the reading will catch up and you don't end up dropping data in your table.

I am note sure why the NodeRED native version fails to authenticate, but it is just easier to trigger the flow by a cron injector (actually I use node-red-contrib-pkjq as this is better maintained) and then exec the python script.
Thanks TerryE works a treat.
Userlevel 3

Advanced programmers could no doubt script the whole session connection to recover the session cookies. I am one, but I haven't bothered.


Further to @ErTnEc's git contribution, I have updated this to do the V2 API for historic consumption. I run the following script daily to download the previous day's half-hourly consumption into the MySQL DB that underpins my NodeRED installation: load_readings.py.

There's an issue with NodeRED HTTPrequest which causes logon problems so I haven't got the native NodeRED version working. Sorry. It's not worth my spending time on this because I will moving supplier when my contract ends. I really like OVO, but a 30+% price hike is just too much, when other suppliers offer better deals.
Just PM'd you Tim account number ending in ****910, very interested in the API trials for integration into our home automation system.
It's been a bit quiet here. Quite a long trial it seems. @Tim_OVO is there any further news?
Userlevel 3
@ErTnEc, this is exactly what I want to be able to do. I use NodeRED to poll darksky.net for current weather readings. Can you send me your python script to play with?

Sorry I've had a hectic time lately and not had chance to pick this back up.

https://gist.github.com/PaulW/7f3ce29c3469757c26504b572597a45c

I still need to add in some extra error handling (specifically around initial auth requests as it takes a while for the authtoken to be fully active it seems) but it's a fairly simple process which people can easily build upon if need be.
Userlevel 3
@SianiAnni At the moment, I cludged this by running the query in my browser after creating my session interactively and then using a small perl script to upload this into my nodered db.

I haven' bother to retro-engineer the sequence of POST requests to establish fresh set of session cookies for each AJAX callback to work as retro-engineering this is all a bit of a dog, and iIt could take me a day to do this so there isn't the payback: one day's work to save a minute or so every month.

Which is why we really need to wait for the proper API if you want to automate this fully.
Userlevel 4
Badge
Thanks for the url @TerryE. It works a treat! And I have retrieved usage for both electricity and gas.
Given that I check MyUsage on the website several times each day anyway, running this daily shouldn't cause Ovo any additional overheads. However, I run nodeRed on my raspberry pi, so I will have to figure out how to set up a session in order to fully automate this.
Userlevel 3
You already have an internal RESTful API that your node.js framework uses for callbacks withing the Usage page et al. And this JSON return is all that you need for a Node RED flow.

Just in case anyone is interested in doing this, the JS code in the graphics display package running on your browser does a callback to retrieve the JSON data which it uses to draw the pretty usage graphs. For this to work your session must have been properly authenticated with your account and passwork because the API does a security check to ensure that any request for your data has the correct session cookies so that only you can see your data. Notwithstanding this, once your browser has established a session, then you can execute a query of the following format in your browser to pull this data down. You can then open this in your favourite spreadsheet application and manipulate / store the data as your see fit.
code:
https://live.ovoenergy.com/api/live/meters/MPAN/consumptions/aggregated?from=FROM&to=TO&granularity=HH

where the MPAN comes from your profile and the FROM and TO fields are of the format YYYY-MM-DDTHH:00:00.000Z.
The API does not seem to limited the range size, so I do this once a month and use a script to load the data into my Home Automation MySQL database. Please don't abuse this or I am sure that the developers will apply extra validation. I personally think that 1 query a month is better than going on a couple of times a day as I was doing previously.

Advanced programmers could no doubt script the whole session connection to recover the session cookies. I am one, but I haven't bothered.
Hey @VibroAxe

If you can send @Tim_OVO a PM with your account number, name and DoB - he'll add you to a list for any future API trials we might do!

Cheers,
Emily
Hey guys

@Tim_OVO I'm a smarthome developer and log term ovo customer. It would be great to get involved in this trial!
Userlevel 3
You already have an internal RESTful API that your node.js framework uses for callbacks withing the Usage page et al. And this JSON return is all that you need for a Node RED flow.

However doing the page request to establish a valid session token is a bit of a PITA. It's a pity that you don;t faciliate direct access to your /api/live/meters/NNNNN/consumptions/aggregate read functions using a secret api key approach that many such system use.

Nonetheless, I'd rare do this the "approved " way, so can you sign me up for trials? Thanks.
Userlevel 4
Badge
@ErTnEc, this is exactly what I want to be able to do. I use NodeRED to poll darksky.net for current weather readings. Can you send me your python script to play with?
Userlevel 7
Badge +2
Would I be able to download the readings which had been sent....... Can this feature (which surely must be in the pipeline otherwise I would not have been told it was possible) be implenmented as soon as possible.

Can I also get trial access to the raw data API.

Hi @blakedrayson @MikeWilliams

At the moment, we only make available the monthly meter readings that are sent for your statement. This are available via My OVO here: http://ovoener.gy/myovo.

To be part of possible future trials which makes available your smart meter data (a trial is already in progress), send me a PM with your name, account number and DoB. I can't promise anything at the moment so I'm sorry if you were promised this feature as standard.

Tim
Userlevel 1
Badge
Can I also get trial access to the raw data API.
Badge
During the coneversations with rep when I was enquiring about a SMART meter I asked if I would be able to download the readings which had been sent.

It is now six plus months further on and there is no sight of this on the main web site.

THEREFORE I WAS LIED TO.

Can this feature (which surely must be in the pipeline otherwise I would not have been told it was possible) be implenmented as soon as possible.
Userlevel 3
Sorry, I know I'm jumping the gun... but I'm:

a) Impatient
b) Curious

I've spent about an hour messing about to try and aggregate the realtime metrics for my Smartmeter usage, and although somewhat inconclusive (due to gaps in data going back to ovo it seems). I've done some reading up on how the SmartThings integration points work, and between that and some trial and error, got a small python script up & running which will log in, poll for active smartmeters on the account, and check the instant usage data against them (if present):

vagrant@vagrant:~/Scripts# ./ovo.py
Getting readings for GAS meter with mpan 7********4:
Estimated Annual Usage is 7144 M3
Demand : 11.693 KW
Cost/Hour: 0.3776839
Getting readings for ELECTRICITY meter with mpan 1********3:
Estimated Annual Usage is 7091.1 KWH
Demand : 2.564 KW
Cost/Hour: 0.3610112

I'm looking now at doing historical polling, so aggregating data over a set period of time, which seems easy enough to do as it's just serialised JSON in the results for example:

{"power":[{"startTime":1513036800000,"instantPower":0.8766,"tariff":0.1408,"price":0.12342528},{"startTime":1513036860000,"instantPower":0.8114,"tariff":0.1408,"price":0.11424512},{"startTime":1513036920000,"instantPower":0.8276,"tariff":0.1408,"price":0.11652608},{"startTime":1513036980000,"instantPower":0.8102,"tariff":0.1408,"price":0.11407616},{"startTime":1513037040000,"instantPower":1.6943,"tariff":0.1408,"price":0.23855744},{"startTime":1513037100000,"dataError":"NotFound"},{"startTime":1513037160000,"dataError":"NotFound"},{"startTime":1513037220000,"dataError":"NotFound"},{"startTime":1513037280000,"dataError":"NotFound"},{"startTime":1513037340000,"instantPower":1.6696,"tariff":0.1408,"price":0.23507968},{"startTime":1513037400000,"instantPower":1.7693,"tariff":0.1408,"price":0.24911744},{"startTime":1513037460000,"instantPower":1.8,"tariff":0.1408,"price":0.25344},{"startTime":1513037520000,"instantPower":1.9155,"tariff":0.1408,"price":0.26970240},{"startTime":1513037580000,"dataError":"NotFound"},{"startTime":1513037640000,"dataError":"NotFound"},{"startTime":1513037700000,"instantPower":0.7824,"tariff":0.1408,"price":0.11016192},{"startTime":1513037760000,"instantPower":0.7688,"tariff":0.1408,"price":0.10824704},{"startTime":1513037820000,"dataError":"NotFound"},{"startTime":1513037880000,"dataError":"NotFound"},{"startTime":1513037940000,"instantPower":0.8776,"tariff":0.1408,"price":0.12356608},{"startTime":1513038000000,"instantPower":0.7783,"tariff":0.1408,"price":0.10958464},{"startTime":1513038060000,"dataError":"NotFound"},{"startTime":1513038120000,"dataError":"NotFound"},{"startTime":1513038180000,"dataError":"NotFound"},{"startTime":1513038240000,"dataError":"NotFound"},{"startTime":1513038300000,"instantPower":0.8985,"tariff":0.1408,"price":0.12650880},{"startTime":1513038360000,"instantPower":0.833,"tariff":0.1408,"price":0.1172864},{"startTime":1513038420000,"instantPower":0.8089,"tariff":0.1408,"price":0.11389312},{"startTime":1513038480000,"instantPower":0.7962,"tariff":0.1408,"price":0.11210496}]}

I just wish that the signal from the meter was more reliable so not to have gaps in the metrics... (hence the NotFound events)
Userlevel 7
Badge +2
@Simonfea @obiwanzamora @AdamJ @dorinho @Ross2411 @Chrherms

If you haven't already, I'll need a PM with your account number, name and DoB to add you to a list for any future API trials we might do! :$

Tim
I'd also be interested in this. Was planning to create a https://homeassistant.io component as soon as the API is available. @Tim_OVO I'll be sending you a pm shortly.
Can you stick me on that list to? Quite fancy getting my Alexa in on the action 😉
I would also like to sign up for trial access to raw data.
Hi,

I too would be interested in being part of the trial and accessing my raw data via the API. How do I sign up?

Adam

Reply