-
|
I have two Emporia Vue 2s. I went through this process on the one I have in the garage and everything is working flawlessly. That was a few days ago. I just went through this process again for the one in the house and I am getting "Failed to read from sensor due to I2C error 3" repeatedly. I've done as much troubleshooting as I can. I have even deleted the device from ESPHome, created a new one, copied the contents of the yaml file from the garage which is working, only modified what was needed to make it unique (host name and such) and tried again but am still getting the error. I deleted and created again, this time just copy/pasting the starter code which is provided here and again just changed the minimum items to get it working. still get the same error. i do not recall any updates occurring between when I did this to the Vue in the garage and now. I also made a small tweak to the garage yaml and installed it OTA to the garage Vue and it is still working fine. The garage Vue is setup to use MQTT. I originally tried that with the house Vue but it gives the same I2C error. i am tempted to upload the yaml config i had for the house Vue to the garage and see if it works. I assume that if it does, there must be something different about the hardware between the two Vues i own. Anyone have any ideas? I did see there were a couple other discussions with similar issues, but they seemed to be related to an update and I did not see a resolution for any of them that I have not already tried. Here is the log file from my attempt at using the starter code
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
|
I have fixed it. I don't know specifically which step fixed it, but I will detail what I did. A little history first though. I am very new to Home Assistant and ESPHome. When I setup the Garage Vue, I did not know that I could push the yaml/firmware installation to the chip over a USB programmer via the ESPHome webportal. So with the Garage Vue I started off by downloading the .bin file from ESPHome using the Manual Install option and selecting the Legacy format. Next I connecting my USB Programmer to the Vue and used esptool.py to create backups and install the firmware. It worked great. With the House Vue, I had learned I could push the yaml/firmware directly to the device over USB from the ESPHome dashboard. This seemed much easier and that's what I did. It appeared to have worked, it showed up in ESPHome, I could see the log files over Wifi, I could push new configurations OTA. But as my previous post stated, none of the sensors would work and I was getting I2C errors. I tried removing the device from ESP Home and creating a new one with a different name and re-installing via the dashboard but it did not help. Ultimately this is what I did to fix it. Basically I tried to recreate the steps i did with the Garage Vue.
I was just re-reading the installation guide and notice it says to use esptool.py to install the yaml file. I wonder if that is what went wrong with my original install. Maybe the ESPHome dashboard cannot handle this install correctly for some reason? Regardless, it is working now :) p.s. - I thought I spoke too soon... after I saw that the logs did not contain an I2C errors and I saw numbers being displayed for Phase A and B, I came here and wrote/posted the above message. I sit back down to start configuring my sensors and such and discover that all the regular sensors are reporting 0 or very close to 0. Phase A and B seem correct, but all the power use is being listed under Balance Power. After some swearing I remember someone else had this problem and it was because their CTs were "backwards" and they had to change the *pos entries to *invert (or flip the CTs around, either or). replacing *pos to *invert in the sensor entries worked for me. |
Beta Was this translation helpful? Give feedback.
-
|
It shouldn't really matter how exactly you do the flashing, but I'm glad flashing in a different way worked! Not really sure what went wrong here. |
Beta Was this translation helpful? Give feedback.
-
|
I have had the same issue with 3 separate Vue 2 units. In all 3 cases the units started out working and then suddenly, usually in the middle of the day at some random time, they just stopped reporting and the logs show the same i2c errors. I have not tried flashing via USB except for the original flash. It doesn't seem like it would be the problem because mine stopped working without any change. But maybe there is some problem or data loss that doesn't get fixed with a wifi flash. I will attempt a USB erase and reflash. Thanks for posting your solution. |
Beta Was this translation helpful? Give feedback.
-
|
Are you tried to reflash via USB? Is it working? Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I tried reflashing two units and still having the same problem. I also tried flashing them back to the original firmware. And they seem to work fine on the Vue app. But after flashing back to the esphome firmware, they are back to throwing the errors (at least on one of the units. I haven't had a chance to reflash the other unit back to esphome yet). |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if this helps, but I remember when I was researching setting up my Vues for ESPHome I saw that it was suggested to delete/comment out any lines for ports that do not have a Current Transformer (CT) connected. If I recall correctly, it was said that some people would get I2C errors if a CT was not plugged into the port. I did not experience that personally, but I still removed those lines for any ports I was not using. For me, the constant fluctuation on the unused ports was creating problems with my reporting because those unused ports will have values bouncing all over from 0 to like 80w sometimes. It would only be for one or two readings, but through a day it was enough to throw off my readings. |
Beta Was this translation helpful? Give feedback.
-
I can't see how this could be case--the Vue fetches the data for all the sensors on every update, there actually isn't a way to limit the data. The config only restricts which readings are actually reported to HomeAssistant. Although perhaps there is a timing issue? |
Beta Was this translation helpful? Give feedback.
-
|
Hey, I'm going to close this discussion--I'd like to keep all conversations on this issue in one place: #108 |
Beta Was this translation helpful? Give feedback.
I have fixed it.
I don't know specifically which step fixed it, but I will detail what I did.
A little history first though. I am very new to Home Assistant and ESPHome. When I setup the Garage Vue, I did not know that I could push the yaml/firmware installation to the chip over a USB programmer via the ESPHome webportal. So with the Garage Vue I started off by downloading the .bin file from ESPHome using the Manual Install option and selecting the Legacy format. Next I connecting my USB Programmer to the Vue and used esptool.py to create backups and install the firmware. It worked great.
With the House Vue, I had learned I could push the yaml/firmware directly to the device over USB from…