Eve released firmware version 3.5.0 for their Eve Energy smart plugs yesterday. I went ahead and installed it on one of my smart plugs. The update went through without an issue… but then:
As per this article, it seems that this firmware release removes the “custom manufacturer solution” they had to report energy usage over matter/thread and replaces it with the official matter way of reporting energy usage, now that matter supports this - which is a good thing!
As Home Assistant previously recognized and used the “custom manufacturer solution”, which has now been replaced by the new solution, I end up with 2 entities for each energy-related sensor: the old one (which has now become unavailable), and the new one (which works):
Also, the update sensor is in state “Unknown” now.
In the energy dashboard, however, I had previously added the “old” entity. The dashboard configuration page keeps telling me that this entity is no longer available, so I went ahead and added the new one.
But if I remove the old one, this falsifies my energy usage history. So I’d have to chose between living with all the warnings about unavailable entities or “losing” my energy usage history by removing the old entity.
Also, the new entity id’s have like “_2” in them, which is very ugly.
I think what would be ideal would be if the old, now “unavailable”, entities get removed, the new entities use their entity IDs instead and the history remains intact.
Is this something an upcoming Home Assistant release could fix (maybe someone’s already working on it even)?
I’m experiencing the exact same issue. Also, the update doesn’t show up on Apple Home.
Someone on Reddit suggested that all devices should be disconnected, then the update should show up on Home when the first device is brought back online. I have yet to try it, but this doesn’t change the fact that the update isn’t working in HA.
I have an Apple TV acting as the router. Home Assistant notified me first of the update but could not complete the updates as they always failed. About 12 hours later Apple Home notified me. I was able to update through Apple Home. But double entities were created in Home Assistant.
I saw the duplicate entries and deleted the original (now unavailable) entities and renamed each of the _2 entities to the original entity id (remove the _2). It seems history retained.
Thanks a lot for the info! I wasn’t expecting an entity’s history to be kept when it gets deleted, but I guess it’s a good thing : I followed your instructions and was able to “reconnect” the entities with their history.
Now I’m only left with 2 days worth of history dangling with the “_2” entity names.
After some research, it seems there’s no simple way to “merge” the “_2” entitie’s history into the right ones (I wish that was an option on the Developer Tools > Statistics page ).
For those interested though, I found this thread where history merging is discussed in depth.
The Update sensor changed to “Up-to-date” after I updated HA to 2025.4.2 - not sure though if it was the update or just the reboot, but it solved itself indeed. Update: I saw that the update sensor stayed “Unknown” for exactly 12 hours before changing to “Up-to-date”, so I guess it only needed to refresh.
The “Identify” button is still named “Identify (1)” even after I delete the old, unavailable “Identify” button but I can override its name in the UI. That’s a bit unfortunate but not too big of a deal
Just to summarise my experiences on this, thanks to the previous posts which helped me feel confident that it wasn’t something strange in my setup. I’ve been on the Eve Energy journey for many years as I really like the build quality of the devices and confident to use them on high availability devices like fridges. I have a total of 25 of the devices and working through the updates and edits below.
My setup historically has been factory reset devices added via the Home Assistant iOS app, I do not use the Apple Home infrastructure. I have a mixture of devices that included factory shipped Matter and also older upgraded devices that specified Matter support was available via an upgrade (which I did prior to factory resetting).
You cannot (currently?) do an update if you use Apple thread border routers (in my case two HomePod Minis which I had been using solely as thread border routers as I was an early adopter of Matter and an attempt to use a Sonoff USB failed). I had been planning to swap out the HomePods for a SMLight SZLB-06M which I successfully did yesterday (the process was incredibly smooth, bit like swapping out wireless LAN APs) and then removed the Apple HomePods. This then allowed me to perform the update (I had to have both Apple HomePods removed before it would work).
After updating, you have additional entities created with an _2 suffix. I deleted the ‘old’ entities and renamed the _2 to drop the _2 suffix. The history is indeed retained in this case (thanks @D34DC3N73R for noting this as I actually initially thought it hadn’t!).
There is an annoying Identify(1) button created which seems to require a manual Name set to get rid of it (annoying but can live with it!).
Thank you very much for your detailed experience report. However, my experiences are different:
In addition to other Eve devices (all of them already delivered with Matter), I have 10 of the Eve Energy sockets and all of them are connected via an Apple HomePod. All these devices have been updated to the new firmware 3.5 one after the other in the last week. A manual update via Home Assistant didn’t work for me either, but the update came all by itself over the days, I would guess it took about 4-5 days for everyone to have the update.
In my case, I was able to get the update pushed by shutting off/pulling power from all my apple thread border routers (2 homepods and an appletv), making sure they plugs were within range of my home assistant hub (could still be operated in home assistant, in my case I had 2 and one could and one couldn’t), power cycling the plugs, and then pushing the update via home assistant.
I hope this gets resolved at some point so you don’t have to go through this but at least there is this path forward for now. Hope that helps.
In my case, for unknown reasons the Apple Home app started noticing there was an update pending, so I tried through Apple Home. Updates went ahead on the first try, and HA stopped alerting me to the no-longer-pending update. I’m not sure why it took so long for Apple to notice, but that did it.
Just set up a new Eve Energy and was surprised about the update. Too bad HA doesn’t automatically detect overlapping entities and merge them smartly. Funny enough, today two Eve Weather devices are also notifying me about the 3.5.0 update, but somehow I can’t get them installed at the moment. I can’t use the Eve app either because I’m on iOS, and the app doesn’t work with SkyConnect, unfortunately…
: I followed your instructions and was able to “reconnect” the entities with their history.
).