Eve Energy recreating entities when migrating to firmware 3.5.0

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)?
  • If not: is there a way to achieve this manually?

Best regards,
Mike

7 Likes

How did you update your Eve Energy, via HA?

I’ve tried several times but it fails with the following;

“Target did not process the update file”

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.

The update itself I did with HA, yes. It took a couple of minutes but succeeded first try.

Thanks for letting us know.

What do you use as a Thread boarder router? I have a AppleTV and a HomePod mini

I use a Home Assistant Connect ZBT-1 (formerly SkyConnect).

Same here.

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.

Also, the update sensor changed to “Up-to-date” eventually on its own.

3 Likes

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 :slight_smile: : 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 :wink: ).

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 :slight_smile:

I tried to update to 3.5 in HA, but it constantly fails. I use a Skyconnect stick for Thread.
Disconnecting from power did not change anything.

Anybody has any ideas?

Is it possible to use the Eve app, even if the socket is not part of an Apple ecosystem?

Did anybody come up with anything? I’ve got a couple of these plugs, and HA won’t stop prompting me for upgrades that never work.

I did not. HA still reminds me about the firmware update. But I have the same “problem” for two Reolink cameras, where the firmware update fails too.