Sorry not much improvement.
08:15 20/7/26
3b8df610-e0e7-4977-a562-524d9a3ca2ad
I know i have said this before 
but i think good news @Darren_McCarthy — I think we’ve finally cracked it!
Your last diagnostic was the key. It turns out this was never a smart-meter or Home Mini problem at all — it’s specific to how Intelligent Octopus Go publishes prices.
Unlike Agile or a standard variable tariff, IOG doesn’t expose your half-hourly unit rates through Octopus’s public price feed — there simply are no rows there (which is exactly what your primaryCount: 0 / fallbackCount: 0 was telling us). For IOG, the only place your real household day/night rate lives is on your account agreement. The app already knew to look there… but it was matching on the exact tariff code stored against your meter, and on your account that code had drifted slightly out of step. So the app kept looking for a code that no longer matched your live agreement and — frustratingly — walked straight past the real one sitting right next to it. Hence the endless “no rate covering the current time”.
I’ve reworked that recovery so it now:
• reads your actual active IOG day/night agreement from the account even when the stored tariff code has changed (and quietly adopts the correct code so it stays fixed);
• keeps everything fail-safe — it will only ever use a genuine, active IOG import agreement, never guess, and never invent a price;
• stops those “Kraken request budget exhausted” lines showing up as errors. Those were actually harmless — the app deliberately skipping an optional refresh to stay under Octopus’s shared rate limit and keeping your last value — but they read like faults in the log, which wasn’t fair on you. They’re now treated as the quiet, expected skips they are.
This is all in v1.0.18, which I’ve just pushed to Test. Octopus Energy | Homey , could you update and let it run for a bit? Your import price and the connection warning should both sort themselves out.
One honest caveat: I can’t see your account from my side, so while I’m confident in the fix, you’re my ground truth here. If anything’s still off, the new build writes a much clearer (still fully anonymised) diagnostic that will tell me straight away whether your account is handing over the agreement as expected — so a fresh log would pin it down immediately.
Thanks again for sticking with me on this one and for the brilliant diagnostics — genuinely couldn’t have found it without them. 
I am going to nail this… this feels like a total challenge… just got back from Swimming… going to review the diagnostic data in a minute… thanks @Darren_McCarthy
Right @Darren_McCarthy — hands up, my last update didn’t crack it, and your new log showed me why. So thank you for grabbing it.
Here’s the honest version of what happened. Last time I got you looking in the right place — your account agreement, which for Intelligent Octopus Go is the only place your real day/night rate lives. But it turns out Octopus can describe that agreement in several different “shapes”, and the app only understood two of them. Your account uses one of the others — so the app fetched your agreement, didn’t recognise the shape it came in, quietly discarded it, and then reported “no active agreement” as if there was nothing there at all. There was — the app just didn’t speak that dialect. That’s squarely on me, not your setup, but i am trying to cut away at these items, as when i designed the app it was around Agile.
v1.0.20 fixes that properly:
• it now understands every shape of household tariff Octopus can hand back — including the single-rate style that IOG accounts like yours often use;
• when your stored tariff code has drifted, it reads your live agreement, adopts the correct code, and then pulls your real prices straight from Octopus’s own feed for that up-to-date code (so you get the genuine article, not a guess);
• it stays completely fail-safe — it will never invent or approximate a price; if it genuinely can’t be sure, it holds off rather than show you something wrong;
• and I’ve added a much clearer, fully anonymised diagnostic that tells me at a glance exactly which shape your account uses and whether Octopus is handing it over as expected.
This is live in v1.0.20, which I’ve just pushed. When you get a moment, could you update to it and let it run for a little while? Your import price and the connection warning should both come good.
And the honest caveat still stands: I can’t see your account from here, so you’re my ground truth. If it’s still blank after the update, one more fresh diagnostic will now tell me precisely what your account is doing — and at that point I’ll know whether there’s anything left for me to fix on the app side or whether it’s something to raise with Octopus directly.
Really appreciate your patience on this one — you’ve basically co-debugged it with me from the logs, and I’m grateful. Let’s get you that day rate.
Hi. Great work on the app, thank you.
Love the dashboard widgets too. Could I please request / suggest an update if possible please
Could it be possible that the graphs in the dashboard have customisable colours. So E.g when negative its blue, when between 1p and 10p its green, then yellow then orange then red.
is that possible?
I have tried to make a custom using the customised option but it does not let me select my meter despite the fact its pulling all the correct data
Thanks
Let me have a look and see what the art of the possible is…
@Welshsmarthome Thanks for the suggestion — I’ve now built this into v1.0.36 by enhancing the existing Agile Prices and Price Timeline widgets.
You can configure five price bands:
- Negative prices — blue
- Green — default up to 10p/kWh
- Yellow — default up to 20p/kWh
- Orange — default up to 30p/kWh
- Red — above 30p/kWh
The three thresholds are editable, and there are Standard, colour-blind-friendly and high-contrast palettes. The Agile Prices widget also retains its original cheapest-slot colour mode if you prefer the existing display.
I’ve added clearer legends and price-band labels for accessibility, while keeping the current-price and cheapest-slot markers visible separately. You can also select which electricity meter each widget should use.
The update has been uploaded as v1.0.36 / Build 36. Once Build 36 is promoted to the Test channel, you can install or update it here:
Install the Octopus Energy Test version
Feedback on the colours, default thresholds and widget layout would be very welcome.
Amazing thanks
Today the Saving Session was Announced flow card has started triggering every 15 minutes. Apart from being frustrating, it’s really messing with my flows.
@Zarbie do you have any idea what might be causing such an oddity?
And is anyone else experiencing similar? Or am I just a special case 
Diagnostic Report: c9fa126c-f2fa-434d-ac39-7e705a52c89a
Screenshot of push notifications demonstrating the 15 minute interval (generated by the most basic flow I could, 2 cards Announcement → Push Notification)
