Eve Energy (v3 with Thread) power usage readout possible?

Unfortunately doesn’t work for me. Perhaps there’s something wrong with IPv6 in my HA docker container.

In the HA logs I see “2022-11-23 09:00:53.634 ERROR (MainThread) [coap] Error received and ignored in this codepath: [Errno 101] Network unreachable”

Not sure how to proceed. I have a clue about IPV4, but not so much about IPv6. I’ve enabled IP v6 on the host (I think), and also on the Docker Daemon.

When I run “avahi-browse -r _hap._udp.”, I see the Eve devices pop up. But from the Linux host I cannot ping6 the address. Works perfectly on my Mac. Guess I have to dive into Ipv6 on my Raspberry Pi first :frowning:

I installed Home Assistant Operating System on a new Raspberry Pi (thus not using Docker). When I boot this, my Eve Energy also is discovered here. And here it works without any issue ! It doesn’t throw the [coap] Error received and ignored in this codepath: [Errno 101] Network unreachable” error.

Any thoughts on what I should enable on my Raspberry Pi (which has the default settings for IPv4 and IPv6) and/or the Docker environment to make this work ? (I don’t feel like migrating everything over to the HA OS).

1 Like

Trying to solve this very issue myself. I have HA-Core as a container on my UnRaid server and this discovers my Eve Energy plugs when I remove from Home but errors when trying to pair. Have found that ipv6 is configured but can’t route back whereas my Mac and other devices are fine.
Will report back if I resolve.

I took the long way around and reinstalled everything on another Pi with HA OS and use the node-red, mqtt, mariaDB and backup add-ons. Everything works out of the box wrt my Eve Energy devices.

That saved me tons of troubleshooting yet gave me the opportunity to test my backups :slight_smile:

2 Likes

If this is what required to use Eve products, than i don’t need them.

It is possible that this was all related to my specific Debian / Docker setup. So I wouldn’t discard using Eve products right away.

the thing is, I have bought 3 of Eve energy sockets. They report power only via Bluetooth. Over Thread they report nonsense values- I have kept them connected for 1 day, values didn’t change.

1 Like

I have a Homepod Mini and I paired my Eve Energy devices first via the Eve app. That way they use Thread to talk to each other. I then unpair them one by one from Homekit (through the Eve app) and consequently they will pop up in Home Assistant.

You do have added them to Homekit first, right ?

yes, added to homekit via Homepod mini first. Then disconnected and add into HA. They all report 5000W permanent power consumption

I had the same issue at first. After I rebooted the server and physically unplugged the devices, the readings came through. It took a while (15-something minutes), but the readings are good now.

1 Like

same for me. What server did you reboot? HomeKit Hub ?

I had mine connected to HomeKit, deleted it there. Then it popped right up in HA.
I got the same readings (5.000 W and so on). What worked for me, was to reboot HA and “Soft”-Reset the EVE Energy (Holding the button 'til it blinked red and released).

I now get all the reading correctly, BUT:

  • after a while, the first connection (if i want to switch the EVE on/off) takes around 5 secs. After that the switch is instant. (Maybe a sleep issue)
  • the data for Watt etc. is only updated every 5 mins, so it’s pretty useless for something that relies on a “live” status
  • Thread is not enabled

PS: I use this setup on my Pi4 without any further BT/Thread hardware addition to the Pi.

thanks, I followed your steps and reboot HA server. Then the readings started to normalize…

All good for now. Many thanks

1 Like

The readings are correct BUT it seems, the readout is sometimes plainly not availabe. So either it’s stuck at some wattage or it’s zero and doesn’t get an actual wattage… Maybe the reason is the not enabled thread… Don’t know for sure yet…
I’m afraid to enable Thread you have to add a Thread-Stick to the Pi… So for the moment i guess, it’s connecting directly to the Pi via BT and that, combined with going to sleep?, is not working flawlessly.

this is what is showing for my Eve Energy meter (Australian version)

I am happy with what I am seeing

Yes, it’s working (seeing almost the same data as you) :slight_smile:
Two things (at least for me) to keep im mind at the moment:

  • It updates only every 5 minutes - that makes it difficult to use for “live” things, as you could have a max. timeframe of +10min for data (+5 mins of not accurate data at each end of the 5min readout period)
  • Thread is not enabled (Thread capable is detected through HA)

But it works, you can switch it and get a general view of the used power and consumption.

following my earlier post,

I found that the readings drops out from HA regularly. If I re-start the service, it may work for a while then drops out again. Any one know of a fix ?

CleanShot 2023-02-05 at 13.14.30@2x

I have the same problem - yesterday two eve energy per thread connected to HA and get the consumption only 5000W displayed, so far nothing has changed there… how long does it normally take until the display shows the actual consumption? so the consumption measurement is unfortunately completely worthless…

It works for me right now with a slight delay.

  • if i switch it on via HA it takes about 5 secs to do so
  • power reading comes up after 30 seconds and displays the correct wattage
  • switching off takes around 3 secs, power reading follows 30 secs later to zero.
  • in the history I can afterwards see time and Watt with the correct values.

With me since the day before yesterday with both plugs no change - I have the one also again completely reset, has also not helped! I’m thinking straight whether I my Eve plug are connected by thread then gradually against Zigbee plugs from Aqara exchange where I do not have this problem … do not know more here!