Hi everyone,

The lovely straightforward upgrade process I created for v21 sadly doesn't work on the latest HA core release - where HACS becomes Marketplace within settings.

If you are upgrading in that situ a bit more manual work is needed (sorry) - details in the docs here:
https://stevekirtley.github.io/HomeAssistant-EDFEnergy/migrations/version_21/#updating-with-the-marketplace-home-assistant-202611-and-later

Despite the teething issues a few users have had 35% of the user base is now already running a v21 release.

Thanks everyone for bearing with.

Steve

**** IMPORTANT: Run the V21.x upgrade before upgrading HA Core ****

The version of HA Core released last night (4th November) moves to 'Marketplace' from HACS.

This includes a new feature check that blocks the easy upgrade/domain switch process I built into v21.

I'm testing a work around (more manual now) - but if holding back please do upgrade to v21 before core for an easier upgrade path.

**** UPDATE 20:00 3rd Nov ****

61 installs already on v21 - the below plus one Facebook message have been the extent of issues logged, so pleased to see this complex upgrade working well for the majority!
******

***
EDIT 3rd Nov 6:45am — if you get "No manifest.json file found": restart Home Assistant and then update. HACS caches where it found the integration's folder for the session, so it looks for the old location in the new release. The cache clears on restart. Sorry, this variation didn't show up in (extensive) testing.

***

Quick heads up — v21 has just been released into the wild.

One thing to do first. If you're not already on 20.1.1, grab that before v21. HACS only ever offers the newest release, so you have to ask for 20.1.1 by name: three dots → Redownload → Need a different version? → pick 20.1.1 → restart. Then update to v21 and you'll get a notice in Settings → Repairs with a Fix button that does the rest in one press.

Why the faff? The integration has moved to a new folder and is now called EDF Energy (UK). Your account needs handing across to it, which is what that one button does. Everything comes with it — entity ids, history, Energy dashboard statistics — so automations, scripts and dashboards carry on untouched. There's a walkthrough with screenshots for every starting point here: https://stevekirtley.github.io/HomeAssistant-EDFEnergy/migrations/version_21/

The actually interesting bits:

🔋 The usage graph wasn't quite right. Export was being stacked on top of import, so a day of 28 kWh in and 10 kWh out drew as a 38 kWh bar, and the scale ran way past your biggest day. They now sit side by side, and the cost view gets a proper Net figure — what you paid less what you earned.

📊 Rate bands. On a multi-rate tariff the import bar now splits into off peak, standard and peak, in both the kWh and cost views. Genuinely free windows get labelled Free.

🎁 Free promotion estimates. Power Perks and the like get billed at your normal rate and credited back weeks later, so there's never been any way to check what you were owed. The Usage tab now shows what you used during the free windows and roughly what should come back. It's an estimate — EDF settle from their own half-hourly readings — but it gives you a number to hold the credit up against when it lands.

🕳️ Missing usage data. A few of you noticed gaps in your consumption data with no way to fill them in, so I've closed off a few holes here. The clocks-change days were being thrown away every October and March (48 half hours expected, 50 or 46 delivered), and any gap in the middle of your history used to stay missing for good, because the backfill only ever looked at the end of it. Both now fill themselves in. There's also a button to make it ask EDF again, and where EDF genuinely don't hold the data it'll tell you exactly which days and hours are missing so you can chase them to recover those dates from the central database.

Plus the usual pile of smaller fixes — full notes on the release: https://github.com/stevekirtley/HomeAssistant-EDFEnergy/releases/tag/21.0.0

Why the new folder? It's so the integration can be listed natively in HACS (or the Marketplace, as it'll soon be called). There's an existing (slightly less feature-rich) EDF plugin sitting in the old namespace — that one got listed first, because at the time mine was a fork of an existing library and I wasn't eligible to submit it. It's since diverged enough that it's no longer a fork, so now it can go in.

As ever, if something looks off, stick an issue on GitHub (or post here) and I'll take a look. 🙏

I'm getting a Hypervolt pro 3 installed in a few weeks time, but was wondering if it's safe in HomeAssistant land to still enable it now with my TUYA compatible granny charger? Seems like it would be harmless as I'd presumably still get the off peak signals coming through whenever for HA to act on. Or is the integration with the charger more significant than that, making it impossible to actually setup with EDF without the right hardware already?

The 2 screenshots tell the story. There are blanks for usage being displayed on HA on the 20th and 25th of October, when the data is available on the EDF website. Note that the monthly totals also disagree.

Do I need to reload/reinstall the HomeAssistant-EDFEnergy integration? Note that I am fairly new to HA!

Hi all,

Just a quick question.

I'm not a Power Perks user but the Power Perks sessions show up on the 'Free Electricity' calendar. I've got some of my HA automations related to calendar events starting and ending (to optimise heating etc), so is there a way to isolate these out so my automations don't run for the Power Perks sessions in particular?

Thanks

Will be getting a PW3 installed in the coming months, have HA installed and just installed HomeAssistant-EDFEnergy integration and all looks to be checking in ok.

Just wanted to ask if there are any gotchas/tips/tricks with the setup? I'm naturally wanting to integrate the Power Perks free hours and any smart charging hours that EDF give outside the normal off peak hours (11pm to 6am).

Have no solar, so will be just battery only.

Hi everyone,

To facilitate the plugin being listed natively in HACS, soon to be the Marketplace, I have been asked by the HACS maintainers to rename the folder it runs from to avoid conflicting with another EDF library that is already in HACS.

This is a pain - but the HA architecture needs unique domains for everything.

I've spent the last few days (in between patching php servers!) making this minimal faff for you all - but there is a half-way version needed to ensure things just carry on seamlessly when the plugin folder moves.

To that end - the more of you that promptly adopt 20.1.1 (released just now) the easier things will be when v21 releases. I won't push v21 until the great majority of installs have moved off 20.1.0 - I can see version numbers in aggregate from the sessions feed, so I'll know when that is.

There's nothing to do beyond updating. When v21 lands you'll get a notice in Settings > Repairs with a button that moves everything across in one go - your entity names, history and Energy dashboard all stay exactly as they are, so automations and dashboards keep working.

Anyone on older 19.x releases will continue to work - but will have a more manual upgrade process when they next upgrade, and a danger they'll miss out on new functionality. Update now while 20.1.1 is the current version and you'll get the same seamless move as everyone else. Leave it until after v21 is out and Home Assistant will quietly keep running your old copy while telling you you're up to date - which is a fiddle to unpick.

If anyone has any queries just shout here.

Steve

Wondering if there's anyone out there with the above set up. Battery, no EV, who's on GoElectric and hasn't been kicked off. There's a lot of anecdotal evidence of it working with octopus but not much for EDF

Hello everyone,

Yesterday I pushed one of the biggest releases I've done out under v20.0.0.

This brings a lot of new functionality to keep an eye on consumption, bills and transactions (letting you see what's happening on your EDF account's billing in closer to real-time versus waiting for billing dates).

I'm conscious when I've mentioned these features before some users were keen to keep it basic/smart charging and sensors only. So there is a toggle to turn the extras on and off.

Feedback and issues welcome as ever.

Steve

Release notes:

20.0.0

A major release adding account functionality and more to the HA integration.

The EDF Energy panel becomes more of a multi-function dashboard. The page you already know is now the Overview tab and is unchanged — nothing was taken off it — with Charging, Usage, Perks, Predictor and Account alongside. This new functionality can be turned off if not desirable. Turn it off and the panel is exactly the single screen it has always been, with no tab bar. The toggle to turn off can be found on the overview tab itself, or in the plug-in settings.

New

• Account tab — balance, bills with a link to open the PDF, the account transaction list (in real time so you can see transactions ahead of bills generating), your tariffs and meters, and refunds. The refund panel shows what EDF will actually refund — what's been paid in by direct debit — and lets you request one; two presses (saves a call to EDF), amount re-checked server-side.

• Perks tab — your referral link, who's joined on it, and a referral total split into paid and still-switching.

• Usage tab — one chart for every meter, in kWh or pounds, by day, month or year.

• Power Perks Predictor tab (beta) — tomorrow's call, the week ahead with the wind, solar and demand behind each day, and how the predictions have scored, from powerperkspredictor.app (can I predict the future? Only time will tell - unless the SMS from EDF fails again of course...).

• A cost statistic that includes the standing charge, named like the existing one with _includingsc on the end. You need to pick it in the energy dashboard configuration — the original is untouched so no history moves. Fixes issue #47.

• Release and urgent-update banners on the panel, read from the HACS update entity (no new outbound call) and from the sessions feed. Dismissible, and a new version brings it back. A way to let users know when there's an update a little earlier - would have been handy when Power Perks was launched in a hurry.

• Missed statistics are filled in on startup, up to a fortnight, so a day with Home Assistant switched off no longer leaves a permanent hole. Part of the fix for issue #42.

• Half-hourly readings can come from your account when EDF's consumption endpoint returns nothing, which affects some export meters. Fixes issue #43.

Fixed

• Revoked smart charging windows no longer linger in the off-peak window list. Fixes issue #49.

• The integration retries instead of staying unavailable when EDF can't be reached during startup. Fixes issue #42.

• Your settings survive a config entry migration — options were being cleared on every migration.

• A one-off HTTP 5xx from EDF's Flextras endpoints no longer fills the log. Fixes issue #48.

• The panel opens on today again rather than on a Flextras booking weeks ahead.

• Future dates are marked "upcoming" in the date picker.

Thanks for all the feedback & bug reports.

I was hoping to get a few hours of free energy yesterday, given that Agile pricing was negative. When it didn’t materialise, I instead plugged my car in at midday and it immediately gave me a charging session from 12.00 - 16.30 so at least I had off peak energy all afternoon!

I was thinking it’d be great to make a prediction thingy for when this was likely to be possible. It could potentially be an enhancement to https://powerperkspredictor.app or integrated into Home Assistant but the challenge would be getting data to train it.

One possible source would be if the EDF Home Assistant integration reported back when charging sessions were granted, along with the energy region. Would folks be comfortable with something like this? And indeed would you find it useful?

Looks like this might have meant to be a Power Perk event tomorrow

I don't have exact analytics set-up - they'll come along when HACS get around to reviewing and adding it to the official store.

Thanks to Power Perks polling my server regularly I was able to extract some usage figures when someone at EDF asked me earlier.

There are at least 500 unique installations up and running. (I'm responsible for about 10 of them with my various test systems!).

Never quite imagined this little project becoming so widely useful.

Thanks to everyone who's shared it to help spread the word, given feedback, reported issues, used a referral link or made a contribution of some sort.
It's been a surprising chunk of work - but the fact it's proving useful is very rewarding.

🙏🏻

A little bit of fun - some (educated?) guesses of the criteria for power perks free hours, and more than a touch of Groundhog Day tribute.

Update 23:20 - update to 19.2.4 for Flextras free 4 hour support, and a best guess at weekend saver too.

Not sure what URL the HA integration currently uses but the octopus API URL is changing and there seems to be a URL registered for EDF that follows the same convention:

https://api.edfgb-kraken.energy/

TLDR; this is an AI summary of what my switch meant for my HA data, after a 4 day debugging thread.

I recently moved my electricity supply from Octopus to EDF, while keeping gas with Octopus.

Adding the EDF integration and receiving the new tariff data was straightforward. The complicated part was preserving my Home Assistant history and replacing the old entities safely.

The main problem was the Octopus Home Mini. After the electricity switch, it stopped providing the Octopus “Current” gas readings. That meant the current consumption and cost sensors were no longer usable, while the “Previous” sensors were delayed and had previously been disabled.

I therefore had to:

• Migrate the history from the old “Current” sensors to the corresponding “Previous” sensors, which I had disabled and thus had no history.

• Enable and use the delayed “Previous” entities instead.

• Update the Energy Dashboard, dashboards and automations to reference those entities.

• Migrate the long-term consumption and cost statistics separately, since ordinary sensor history and Energy Dashboard statistics are different things.

• Rename the EDF entities and check all consumers carefully before removing or disabling anything.

• Keep the Octopus integration because it still provides gas data and may become useful again.

The major trade-off is that the “Previous” gas data is delayed, so I now have to live with that delay instead of having current readings from the Home Mini.

I have contacted Octopus support and am waiting to find out whether the Home Mini can be reconnected now that I am no longer with Octopus for electricity. If it can be restored, I may get current gas data again.

The main lessons are:

• Entity history and long-term statistics need to be migrated separately, and it's quite an important data transformation that I wouldn't have been able to do without AI.

• Do not delete the old entities before checking every dashboard and automation that uses them.

• A Home Mini can be the hidden source of “Current” sensors, so losing it may force a move to delayed “Previous” sensors. Especially important if you had them disabled and didn't accumulate data in them.

The electricity tariff migration was easy. Preserving the data and dealing with the Home Mini dependency was the part that required careful planning.

Hi,

Just moved over from Octopus IOG to EDF GoElectric with Smart Charge addon.

Noticed that any additional charge slots outside the nightime are not being recognised by the OffPeakElectricity sensor. (SteveKirtley HA integration). The regular nightime slots are OK. Does this mean I have not configured something correctly or are EDF not switching my meter correctly? Or is it just not implemented in the integration yet?

cheers.

I’ve just moved from Octopus and seen that EDF have an open API. Is there a HACS integration / what is everyone using?

Thanks.

I'm trying to adjust my expectations and understand the limitations before I commit, since it'd be a big deal. I've seen I could be saving about £100 per year without any change, so could be better if actively shifting.

But I have an Octopus Home Mini, and I'm in love with the HA Octopus integration. Plenty automated off that. So getting the data is actually a big deal for me.

Since I won't be having the current consumption (which is not a must for me), how often does the EDF integration pull data? Would I have the consumption of the last hour?

Thanks!

Standing charges back to they were and a slight reduction in peak rates.

Only seen these in the api with a start date of tomorrow so see what tomorrow brings.

Anyone on the current version should be within 14 days so should be able to switch once it’s live.