BottlecapDave / HomeAssistant-OctopusEnergy

Unofficial Home Assistant integration for interacting with Octopus Energy
https://bottlecapdave.github.io/HomeAssistant-OctopusEnergy/
MIT License
535 stars 49 forks source link

Huge correction in import consumption during early hours #817

Closed pacemaker82 closed 2 months ago

pacemaker82 commented 2 months ago

Describe the bug

Edit: Wondering if this is something to do with the BST change and how OE adjusts consumption? I noticed the day of BST change (31st March) my consumption was unusually high, so maybe what happened below was a correction they do?

Original Issue:

Unsure if this is a bug with the integration or OE or what has happened... during the early hours where I was consistently charging my car, I had a massive energy consumption correction:

Screenshot 2024-04-02 at 12 38 22

Was a roughly ~6kWh correction, when usually this sensor just increases over time from zero every day.

Today I have received the previous day consumption for 1st April, its showing no usage for many early hours:

Screenshot 2024-04-02 at 12 41 38

From 2.30am to 4.30am there is no import consumption, which is strange since the Current Accumulative Consumption clearly showed there was (despite being a weird correction)

Reproduction steps

as above

Expected behaviour

I did not expect the ~6kWh correction

I expected the previous day accumulation to reflec energy consumption between 2.30-4.30am

Tariff Code

E-1R-INTELLI-BB-VAR-23-03-01-J

Integration Version

Latest

Home Assistant Version

Latest

Fresh Install?

Fresh install

Home Assistant Logs

none

Confirmation

BottlecapDave commented 2 months ago

Hello and sorry for the late response.

The sensor requests the data from the API at the specified intervals (default 1 minute) and sets the state to this value. If there was a correction, it was a change in the data returned by the API. As it's the current consumption sensor, this comes from the mini which might have done it's own corrections on the data it had calculated.

I'm afraid there's very little else to go on, so closing this issue.