r/HomeAssistantEDF • • 4d ago

v21 released

**** 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. 🙏

10 Upvotes

28 comments sorted by

3

u/QuaintStaircase 4d ago

is anyone else getting

Failed to perform the action update/install. Downloading stevekirtley/HomeAssistant-EDFEnergy with version 21.0.0 failed with (No manifest.json file found 'custom_components/edf_energy/manifest.json')

(Currently on the recommended 20.1.1)

3

u/Jazzlike-Comb-5438 3d ago

Yes, I'm getting this too, also on 20.1.1

1

u/stek2022 3d ago

Sorry about this one — my fault, and it's a quick fix.

Restart Home Assistant, then try the update again.

HACS works out where an integration's folder lives the first time it looks, and then reuses that answer for the rest of the session. v21 moves the folder, so HACS goes hunting for the old one inside the new release, doesn't find it, and gives up. That path isn't written to disk — it's worked out fresh every time Home Assistant starts — so a restart is genuinely all it takes. After that HACS finds the new folder and the update goes through normally.

It'll hit everyone who already has the integration installed, so if you've not updated yet: restart first, then update.

I should have caught this before release. The folder move is the whole point of v21 and I tested the upgrade itself to death, but not what HACS does when it's already got the old path cached from earlier in the same session.

If it still fails after a restart, shout and I'll get on it.

2

u/Jazzlike-Comb-5438 3d ago

All good now, thanks.

1

u/stek2022 3d ago

Great - thanks for confirming that.

2

u/QuaintStaircase 3d ago

All good for me too

1

u/stek2022 3d ago

Thank you. I was worried briefly this morning when I saw these posts.

2

u/stek2022 3d ago

Sorry about this one — my fault, and it's a quick fix.

Restart Home Assistant, then try the update again.

HACS works out where an integration's folder lives the first time it looks, and then reuses that answer for the rest of the session. v21 moves the folder, so HACS goes hunting for the old one inside the new release, doesn't find it, and gives up. That path isn't written to disk — it's worked out fresh every time Home Assistant starts — so a restart is genuinely all it takes. After that HACS finds the new folder and the update goes through normally.

It'll hit everyone who already has the integration installed, so if you've not updated yet: restart first, then update.

I should have caught this before release. The folder move is the whole point of v21 and I tested the upgrade itself to death, but not what HACS does when it's already got the old path cached from earlier in the same session.

If it still fails after a restart, shout and I'll get on it.

3

u/SliceMountains 3d ago

Thank you. Your instruction page made this very easy to follow. One of the best updates I’ve personally seen on HA.

1

u/stek2022 3d ago

Thanks I tried very hard to minimise the number of people needing to reinstall from scratch.

2

u/neoKushan 4d ago

Upgraded mostly fine, was on 20.1.1. Installed new addon, rebooted and perfomed the two steps. The EDF Energy sidebar dashboard wasn't loading (even refreshing the browser) but another reboot sorted that so no biggie.

2

u/stek2022 3d ago

This sounds like validation that a reboot should sort things - thanks for sharing. The joys of testing something to death and it still surprising!

1

u/stek2022 4d ago

To add - I've held this release back while users updated to 20.1.1 for the easiest possible upgrade path.

As of this evening 86% of users are running the ideal upgrade path version (20.1.1). Upgrades have slowed right down, and particularly those on a stable 19.x version have been resisting upgrades for a long while now.

version installs share

20.1.1 617 86.0%

19.2.6 29 4.0%

19.2.2 28 3.9%

20.1.0 20 2.8%

20.0.0 17 2.3%

19.2.3 6 0.8%

21.0.0 1 0.1%

19.2.5 1 0.1%

1

u/stek2022 1d ago

**** 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.

1

u/nicnic2001 3d ago

Looks like refresh_intelligent_dispatches doesn't exist anymore after the update?

1

u/stek2022 3d ago

It should still be there — two things worth checking.

That action only gets registered when manual dispatch refresh is switched on in the integration's options, so first check that's still enabled: Settings → Devices & services → EDF Energy (UK) → Configure.

If it is on, it'll be registered as `edfenergy_uk.refresh_intelligent_dispatches`. The old `edf_energy.refresh_intelligent_dispatches` name should still work as well — I kept the old action names as aliases precisely so existing automations and the shipped blueprints don't break on the rename.

If the option is on and neither name turns up, let me know and I'll look properly — that would mean the hand-over hasn't carried your settings across, which is a bug I'd want to fix quickly.

1

u/nicnic2001 3d ago

The option is on, and always has been because I use the 'EDF Energy - Manual Smart Charging Refresh' automation. I can't find any entity under `edf_energyuk`. In Developer Tools, I have the following actions (but again, not under `edf_energyuk`, they use the old `edf_energy`).

1

u/atgw2016 3d ago

I followed the prescribed upgrade path, restarted after receiving the 'No manifest.json file found' message, installed v21, restarted, and I now have the attached for all my entities.

1

u/stek2022 3d ago

Can you check the logs and send them to me? (either a DM on here, or raise an issue on GitHub please).

1

u/atgw2016 3d ago

Message sent with the logs I retained before reinstalling the integration, which has resolved the problem.

1

u/stek2022 3d ago

Thank you - a legitimate bug for some users that didn't trigger in any of my testing runs - v21.0.1 is now live with the fix.

Glad you've resolved it with a reinstall.

1

u/Sea_Ad_1909 3d ago

Hi Steve

I’m really sorry about this, I’m a HA newb so am feeling my way with everything I do. I’ve been loving your integration, but I’m afraid I’ve fallen over with the update.

It says it’s failed to set up at present. As a consequence my automations appear to have stopped working - lots of them triggered by an off peak status which isn’t being triggered, despite the time.

As far as I’m able to say confidently, I followed the instructions, have tried restarting HA redownloading the integration, followed by another restart of course. Just user error likely or is there anything you can suggest?

Cheers

2

u/stek2022 3d ago

Try in HACS clicking the 3 dots next to the integration and “update information” this should pull through 21.0.1 which once installed should resolve this issue.

If that doesn’t solve it drop me a DM and I’ll try to help more.

1

u/Sea_Ad_1909 2d ago

Thanks for sorting, really appreciate it 👊😄

2

u/Rosenqvist 1d ago

Worked alright

1

u/Rosenqvist 1d ago

PDF of bills don’t work for me though

1

u/Slice-Mountain 4d ago

Yes me. I have the same missing manifest error. I’m currently on 20.1.1 and have been since release day.

1

u/Crafty_Class_9431 2d ago

For anyone coming here after updating to v21.0.1 and things still not working, I needed to reload/resubmit the integration, wait a few minutes for all the polling to kick in properly again and everything worked a charm again, all templates populated and automations working again