EVE Energy 3.5.0 producing duplicate device in Google Home

[jolly crescent]

Just an FYI. When I updated one of my EVE Energy plugs through Home Assistant, I got a notification from Google Home that a new device was added to my home. Looking at Google Home, I can now see a duplicate device. The OG device is still present and works properly but the new duplicate one doesn't let you control the plug at all. Also in Home Assistant, the identify configuration shows a (1) next to it. Not sure what to make of that. Gonna hold off on updating my other one for now.

[honest agate]

Are there any controls on the new device main page?

[jolly crescent]

Nope

[finite oxide]

Skipped this update myself as it didn’t match what the eve release notes indicated to be the latest. Also, non of my other apps (eve app, apple home app) indicated that there was a new update available. Maybe incorrect firmware being offered in home assistant?

[livid marsh]

This is the correct fw update

[pulsar grove]

Same issue here.

[livid marsh]

The Eve 3.5.0 update bumps the device to Matter 1.3 with official energy measurement support. You will have to manually cleanup the orphaned entities for the old custom clusters.

Why Google displays a new device is maybe a Google issue ?
What happens if you cleanup the orphaned entities ?

[pulsar grove]

I don’t use Google - but I already cleaned up the orphaned HA entity entries and repaired the power tiles.

I have only 5 plugs. Pretty annoying though if you have a house full of them.

[livid marsh]

Yeah, it is what it is, sorry.
Let's be glad that Eve provides the update to Matter 1.3, so we can get rid of the old custom clusters with inefficient polling of the energy values.

[pulsar grove]

True.

[finite oxide]

@livid marsh just out of curiosity, why is only home assistant offering the update? is it because the other platforms/apps arent up to speed yet or?

[livid marsh]

Yeah, we are checking DCL more regularly. I'm pretty sure Apple will follow later this week as well

[finite oxide]

awesome, good to know. Thanks for the clarification!

Apple home just now notified me about the update, so slow! 😉

[pulsar grove]

@livid marsh Has Thread been updated too? Which version is the firmware providing?

[livid marsh]

I'm pretty sure it includes Thread 1.3 in the base firmware

[pulsar grove]

Also my assumption. It would be really great though if the root node information would contain the Matter and Thread versions provided.

[livid marsh]

Yeah, but there is no clear version here. Manufacturers use intermediate libraries which are based on some snapshot version of either Matter SDK or Thread sdk/libraries. I agree it would help if they conform to at least which base version was used. Currently its a mess and the only way to somewhat detect which Matter version a product is running is checking the certification info

[pulsar grove]

Really? I didn’t know that. Thanks for providing that insight! I always thought that the vendors would rely on major release versions. I wonder how a certification can be done at all for a (buggy) snapshot version.
Anyway, it really seems to be a mess currently.

[ebon mulch]

https://csa-iot.org/csa_product/eve-energy-2/ confirming that firmware 3.5.0 for eve energy is matter 1.3 certified
Edit: And https://www.threadgroup.org/Certified-Products , yes Thread 1.3 as of Jul '24, so that should have made it into the Aug '24 firmware that is 3.5.0.
Quite a bit of a release cycle though...

[novel rampart]

Is this out for the US plug as well? Home Assistant notified me, but so far nothing from the Eve app so it might be a staged rollout

[honest agate]

Google side of this will get cleaned up soon. It's the energy monitoring sensor that is not fully supported yet

[pulsar grove]

A bit off topic, but Eve released the 3.5.0 firmware update for Eve Weather yesterday. Installing it OTA via HA is a lottery kind of thing. I tried it 10-15 times already running into timeouts at different percentages. The closest I got was 95% completion. I already rebooted the device and HA, I put the device close to its hub, etc., but no success. Pretty frustrating that the OTA update process doesn’t seem to be robust at all.

[barren quarry]

I’ve been having the same issues with trying to update the Eve Weather

(For now I added it to Apple Home and am trying to update it that way instead)

[livid marsh]

As soon as ANY apple border router is involved, you need to do updates using Apple, not HA.

OTA updates from within HA will only work reliable when (solely) using OTBR based border routers

[pulsar grove]

I don’t use Apple border routers but the OTBR addon. I meanwhile was able to successfully install the 3.5.0 firmware by starting the update directly in the node of the HA Matter server addon.

[livid marsh]

OK, in that case ensure that the signal is strong and dont update multiple devices at once.

It should be robust (but can take a long time) if the signal is strong.

[pulsar grove]

I had even turned the signal power to high via Eve App before updating. It was only one device.

[livid marsh]

hmm, crazy and the ZBT-1 is connected using extension cable to the usb port ?
No other interference source nearby ? wifi not overlapping ?

I have updated dozens of devices already using HA otbr without a single glitch, ever.

[teal skiff]

I'm having the same issue. Updating 2 Eve Energy's when they had the 3.5 update released, worked perfectly, but the Eve Weather just won't update. Tried multiple times. Gets to 40, 50 , 60% and then just stops.

[livid marsh]

OK, well the special thing about it is that is a battery powered device

I'll see if I can update a Ee weather tonorrow to test it out

[pulsar grove]

Yes, my ZBT-1 is connected via USB extension cable. And my Thread mesh is generally rock solid. I also run 6 Eve Energy plugs, that I have recently updated to 3.5.0 via the standard HA update function. All 6 devices successfully on the first try without any glitch. I also had checked the Eve Weather connection to the closest Eve Energy hub -which is just 3 meters away- via the Eve App. It showed "Excellent" signal quality in both directions. And I had 2.4GHz Wifi temporarily deactivated during the update.

[stuck condor]

Same symptoms here, Energy outlets worked just fine but not the weather. Managed to get it to max 70% before it stops.

[teal skiff]

I, gallingly, got to 93% with one attempt. So close!

[pulsar grove]

Try to start the update directly in the Eve Weather node of Matter server. Worked for some people:
https://community.home-assistant.io/t/eve-weather-ota-update-from-3-3-0-to-3-5-0-running-into-timeouts/883435/15

[teal skiff]

Did you have any luck?

[pulsar grove]

There seems to be an issue with an outdated Matter OTA chip provider app for Linux used by HA. Compiling an actual version solved this guy's issue with updating Eve Weather: https://www.reddit.com/r/EveHome/comments/1kap78s/comment/mq2iqb0

[teal skiff]

Just updated to 2025.5. I was, probably erroneously, hoping this would be fixed.

It's not

[livid marsh]

It's not that black and white - although we needed to update it, we have seen that eve weather just has issues pulling through the update. Its a matter of keep retrying. The updated ota provider helps but its not the golden solution. Ironically enough the update its trying to install is actually bringing an improved thread connection to prevent this issue in the first place so a bit of a chicken and the egg situation.

We'll publish a new Matter server beta today or tomorrow and if all is fine, it will be released as stable version next week

[pulsar grove]

Thanks for the insights and the update!

[teal skiff]

Likewise, thanks for the explanation. I guessed it may not be so straight forward.

[pulsar grove]

Any news on the Matter server?

[livid marsh]

Thanks for the reminder. I just published 7.1.0 of the matter server

[teal skiff]

@livid marsh How long will it take to get through the system before it's actually available as an update?

[ebon mulch]

Looks like it turned into 8.0 though?

[livid marsh]

Yeah

[pulsar grove]

The HA matter_server addon is still 7.0.1.

[dapper plinth]

Not yet public. Open pull request to update. https://github.com/home-assistant/addons/pull/4025

[latent sentinel]

@jolly crescent , As for the extra device created in Google Home: this isn't an Eve issue, but a Google problem. Google Home has a known problem when it encounters a Matter endpoint that isn't implemented - in those circumstances, rather than simply ignoring the non-implemented endpoint types (which is what Apple and others do), Google Home creates a "dummy" device for the endpoint which serves no purpose. I've also observed that Google Home does this with Matter Generic Switch endpoints, Matter Mode Select endpoints, and the various control types in Chapter 6 of the Matter Device Library Specification. Try one of the Inovelli Matter switches and you'll see lots of these useless icons.

In the case of the Eve Energy plugs, after the update to firmware 3.5.0 (Matter 1.3), the device now includes Endpoint 2 which is an Energy Sensor endpoint to report energy usage. Google Home doesn't support the Energy Sensor endpoint type, and so you get one of these dummy endpoints.

This creation of dummy endpoints ends up cluttering the UI with useless icons and obscuring the ones that actually can be used - its hard to imagine a much worse approach to handling non-implemented endpoint types.

As a work-around, I've found its better to pair only to Home Assistant and then export only the working entities from Home Assistant back to Google Home using this Add-on: https://github.com/t0bst4r/home-assistant-matter-hub which acts as a Matter bridge from Home Assistant to Google Home. My preferred way of doing this is to label the entities I want to bridge using the Home Assistant Labels function (I use the label "Expose Using Matter") and then in the matter-hub addon, export entities by label using that label.

[dapper plinth]

@latent sentinel like the label idea. Already use matter hub.

[jolly crescent]

Yeah I came to this same conclusion recently. Not a great way to handle this I agree. Been trying to figure out the best way to raise the issue with Google. Also something interesting I found with this is the firmware got updated on one of my devices automatically a day after I had manually updated the other with HA. I'm assuming it's Google that did that but not quite sure.

Question for @livid marsh will the HA Matter Server ever update Matter device firmware automatically or is it all manual?

[upbeat adder]

This is already a known issues within Google - see earlier post: #1360076297119727697 message

[teal skiff]

Matter server updated to 8.0.0. So far updating Eve Weather is still failing. Anybody else had any luck?

[dapper plinth]

Seems pretty clear that main culprit is the eve 3.30 firmware on this weather not being able to keep a stable connection long enough to complete the 3.5 update. Other things (matter OTA update, moving closer to thread BR, etc...) help but the core issue remains the core issue.

[jolly crescent]

not seeing a source for that statement. @honest agate how do you know Google will get this cleaned up soon?

[livid marsh]

That is indeed the issue - the 3.5 update fixes the very issue it runs into while OTA updating, so bit of a chicken and the egg. Just keep retrying is the only advice I can give now.

[teal skiff]

I must have tried 50 times now!

[livid marsh]

Ok, I’ll reach out to Eve if they have more suggestions