For many months I was getting and error when trying to update my Emporia Vue 2 from the Home Assistant Settins screen. I just kept skipping because it was still working fine.
Yesterday I had some time to dig and found out the reason for the updating issue was a breaking change which required “platform: esphome” to be added to the YAML under OTA.
After that I hit install assuming that would bring the device up to date, which I think it did.
Today I noticed that the power readings were “unavailable”. Checking the logs of the EmporiaVue, there are a lot of “Failed to read from sensor due to I2C error 3” entries.
Looking online a bunch of people have had the same problem. Most solved it with adjusting the frequency and adding a timeout.
I tried that but I’m still getting the same issue.
Has anyone else run into this? Any other solutions?
Just following up on this issue. It’s still spitting out loads of I2C errors.
I did notice in the logs the “Frequency: 200000 Hz” even though in my YAML I have it set to 400kHz.
Is that a recovery thing to lower it, or are my yaml changes not being saved/uploaded?
Latest logs. I removed 90% of the I2C error 3 entries for clarity.
I’m newly seeing “I2C error 3” errors too. My vue2 returns nan/Unknown for every circuit power sensor that previously worked. I haven’t run updates on my Gen 2 Vue since setting it up (2 years ago?), but the symptoms appeared when I accidentally flashed a different device build onto the vue by using the wrong IP address and subsequently re-flashed the correct build with the esphome CLI (version 2025.5.2).
The logs do show the correct frequency being set from yaml, but nothing I’ve tried works (it was set to 200 kHz, I’ve attempted 400 per the 50, 100, 200). I also tried adding a timeout (was not previously set) of 1ms and 11ms.
Searching for solutions I’ve found the issue that cropped up with the 2024.10 release[1], and that it could also be hardware failure[2]. Because the issue is directly correlated with my first attempt to re-flash the config since well before 2024.10, I didn’t think hardware failure was likely. But it’s not looking good - I reverted my esphome to 2024.9 and re-flashed the config with frequency: 200kHz and i2c still fails. So maybe the re-flash triggered hardware failure?!
Interesting. I saw those older threads about hardware failure as well. At the bottom of that thread the post says they fixed it by using the web flasher.
I originally flashed my Vue that way, and only flashed it via the ESPHome Builder a few times before I started getting the error from the missing ota “platform: esphome” entry. Didn’t bother correcting it for over a year. But now this.
I’m going to try removing the Vue from inside my panel, and manually reflash with https://web.esphome.io/.
I have a newly flashed and installed getting this issue as well. I’ve played with the i2c settings a bit but mostly blind checks with no success. Following
Funny enough, I just re-flashed mine and now it’s working fine.
The only error showing in the logs now is [16:57:22][W][emporia_vue:066]: Detected 1 missing reading(s), data may not be accurate!
Interestingly the frequency is now showing at 400000 Hz, which wasn’t being saved before.