Can we get access to the OVO energy online account API to download our smart meter usage data?

​@Firedog - I have fixed the issues with the json data set having both PEAK and OFF_PEAK readings...

Import of your meter readings data shows:-

• Meter Registers: 10
• Meter Readings: 1,648

New version at https://github.com/MikeWilliams-UK/My-Ovo-Data/releases/tag/V1.0.7

​@MikeWilliams Thanks again. That’s much better. I got 1650 readings - today’s turned up in the short time between your retrieval and mine.

There are some odd gaps in the record, which I’m sure aren’t the result of the retrieval process. There are three meters involved - non-smart, SMETS1 and SMETS2 - and their designation of registers to peak and offpeak tiers was a bit of a moveable feast over the years. This came to a head when they tried to enrol and adopt my SMETS1 meter on to the DCC; it turned out that DCC would not accept the first tier as offpeak, so we had to swap them over. 

I suspect that readings for most of 2018-2022 have been lost from my OVO account. I’m not sure if I have them salted away somewhere. I do certainly have month-end readings for the whole period, so losing the daily ones is no great problem.

Anyway, it’s great to be able to retrieve readings in a useable format along with the usage data. I hope those who download the code show their appreciation! 

You are welcome, the extra readings are due to me injecting your JSON file (instead of fetching my readings), which was created yesterday.

I was surprised that so many readings were available as we have previously been told that the system only stores the last 400 readings???

/Mike

Bit of confusion here.

The meter has a datastore which saves (a) 400 days’ Hh usage data and (b) 31 days’ billing data, i.e. midnight snapshots of register readings etc. Suppliers will normally send a request for the previous day’s records once a day, so 48 Hh bucket contents and readings for each register.

It’s then up to suppliers what they do with these data, but OVO seem to salt everything away in the customer’s account. This what your app accesses. Utilities like n3rgy and Bright connect via DCC to the meters themselves to retrieve the contents of their datastores.

I see that the JSON file I shared with you has lots of register details, which OVOData pushes to the DB’s Meter Registers table. There has clearly been some mucking about with these data, because there were periods when the lowest register tier was the offpeak one, a state which DCC chokes on. So I think the R01/02 labels were changed around with no alteration to the underlying data. Theis means that OVO’s (or Kaluza’s) own systems can’t successfully retrieve the data for the upside-down periods. I’ll have another look.  

I am leaving OVO in a few days time.

This has led to a new bug raising its head in obtaining the meter readings

// Previous
"accountSupplyPoints": [
{
  "startDate": "2014-12-01",
  "end": null,
  "supplyPoint": {

// Now that I have a exit date
"accountSupplyPoints": [
{
  "startDate": "2014-12-01",
  "end": {
	"date": "2025-11-25"
  },
  "supplyPoint": {		

Notice the unexpected formatting of end.date which give an error

Exception thrown: 'System.Text.Json.JsonException' in System.Text.Json.dll System.Text.Json.JsonException: The JSON value could not be converted to System.String. Path: $.data.account.accountSupplyPoints[0].end | LineNumber: 0 | BytePositionInLine: 91.

I have fixed the error.

I will be releasing it later today - providing my testing finds no further issues.

Sadly, I didn't have time to release my "final" version today. That's assuming that I will lose access when my account is closed.

I am hoping to get time to do it tomorrow.

/Mike

Version 1.0.8 released

https://github.com/MikeWilliams-UK/My-Ovo-Data/releases/tag/V1.0.8

PS: After today I will have limited ability to fix issues...

/Mike

Thanks as always, Mike. I’ve taken it for a test drive and all seems to be well.

I’m sorry to see you go, but I assume you found a better deal elsewhere. You’re always welcome in these forums whoever has your energy allegiance from time to time.

Au revoir, and bonne chance!

​@MikeWilliams  - I would also like to thank you for your help and creation as well as updating of your program!

On a side note, does anyone know if there is any way to tell if the data being retrieved is estimate or actual readings?

I ask only as I just found out that our meter has not been sending data to OVO for over 2 months, but there have also been days where it dropped before that too (we have a SMETS1).  Mike’s tool has half-hourly reads for our entire account, so I just wondered if there is some easy way to tell which are estimates and which are actual.

Or, based on some of the recent discussion just above about 400 days worth of data being stored, are these actual readings that didn’t get sent to OVO?

I’m a little confused and would appreciate any clarity, if anyone knows.

Thank you!

​@X10 - If you have used my program and look into the data in the SQLite database using a program such as SQLite Studio (which is free https://sqlitestudio.pl/) you will be able to see in the table MeterReadings when the column Type has a value of “ESTIMATE”
 

/Mike