Incomplete usage reporting on 'Month' reporting for gas

this is exactly the same as mine but to get OVO “Tech team” to fix it is a joke, they are very happy to say it is your equipment because their “Tech Team” is inexperienced in problems arising on their website. Perhaps another company should do their reporting from them I now use Loop App because they can't fix their own website. Even though they are as far as I know not connected with OVO Perhaps Martin Lewis can help because he says he talks to OVO Quite regularly withe their CEO perhaps he can help us consumers to bring pressure to bear.

It's not dropping the connection though.

All the gas data is available on the Day tab but not on the Month tab. That's why I included the screen shots. That is a processing/display error. It's failing to recognise the collected gas data on Month tab.

Thanks for the reply though.

Peter

Yes, understood. They do have to process the gas readings a little differently, given the calculations for calorific value and such which aren’t available from National Grid until after supply - it is frustrating when it’s missing though. I’m always surprised at the interest, given that not long ago we used to look for readings each quarter rather than every 30 mins 😂

@BPLightlog I would agree but they have calculated an energy value for the missing days which assumes they have the calorific value. No, it’s the difference between the two screens that is strange.

Thanks. Peter

So, the Month screen has mostly caught up with the Day data apart from the 20th (which is present with kWh values) so it just seems to be a lag in the system which I’ve not seen before. I hope this is not going to get worse.

Thanks for all your comments.

Peter

PS If you’re wondering about the high electric usage I have an EV. The trip down memory lane about quarterly readings was thought provoking.  It also seems mad now that the house is has now become a ‘filling station’ and powering the car!

Mine did this for a couple of days, but when I checked this morning it had sorted itself out.

Yes mine too. Looks like there was a wider system issue which has now been sorted