Octopus Energy Integration (BottleCapDave) stopped receiving data

Third party integrations
1

Hi all, I cannot find any reference to my issue on here or Google…

At 06:20 yesterday (UTC+1, 4 Sep 2026) my fairly new HA stopped receiving data from Octopus. I don’t know if this relates to the Octopus website, my meter, or the Octopus mini (that I’ve had happily running for a few weeks).

The first error in the logs says:

This error originated from a custom integration.

Logger: custom_components.octopus_energy.coordinators.current_consumption
Source: custom_components/octopus_energy/coordinators/current_consumption.py:58
Integration: Octopus Energy (documentation, issues)
First occurred: 4 September 2026 at 06:21:38 (1 occurrence)
Last logged: 4 September 2026 at 06:21:38

Failed to retrieve smart meter consumption data - using cached version. See diagnostics sensor for more information.

When I try to download the diagnostics for the entities, I get a 500 error:

The server at homeassistant.local:8123 sent back an error: 500 Internal Server Error

I’m a complete newbie with very minimal devices/integrations. I have only one alert set up (less than a week ago), and that is to notify me of excessive power consumption overnight. It worked correctly a couple of times. I don’t see how this could cause the problem though.

Any advice warmly welcomed. Thank you.

2

Solved.

I tried resetting the Octopus Mini, but still not joy. Then I forced HA to do a full restart, and bingo.

Hopefully this helps someone else looking for an answer to the same problem.

PS. Thanks BottleCapDave for this integration - it’s great, thank you :slight_smile:

Edit: There are still two mysteries unsolved.

  1. Why did it go down in the first place
  2. Why does the diagnostics download produce a 500 error.
3

I had a similar issue with Octopus a couple of days ago. It was actually flagged by my home battery overnight charge automation when it notified me that the Target Timeframes entity hadn’t selected any slots. In the end it turned out to be an upstream issue with the Octopus Energy integration and a reload sorted it. I’ve no idea why it happened, but I’d also seen a few reports from IOG users that they were also having issues and it can happen at the start of a month, or if tariff data changes.

I’ve now written a fix in my automation that automatically reloads the integration if it detects that no overnight slots have been selected or if the slots contain stale times.