Anyone else getting i2c error 3 after updating esphome version?

[derekyle]

All the sudden, I'm getting NaN responses from all sensors on the vue2 and the following error:

" Failed to read from sensor due to I2C error 3"

appears over and over in the logs. I saw one other person with this error in a now closed issue, but no update on if/how they fixed it. This seems to have appeared suddenly, but I believe it started occurring after the most recent version update of ESPhome. It was running for a few weeks without issue before that.

Is anyone else getting an error after any recent updates?

I have tried power cycling the vue2 as well as clearing the build cache and rebuilding/reinstalling the firmware, but still getting the error. I also tried adjusting the i2c frequency down to 150khz, 100, 50, and back to 200, but also no change. Any help would be appreciated.

I'm currently running esphome v 2022.12.3 and home assistant core version 2023.1.4. Not sure if the version of anything except esphome should make a difference.

[flaviut]

Error 3 is "Timeout".

I'm not sure what's wrong. You can always downgrade and see if that works. Maybe check and/or reflow some solder joints if you have the equipment for that.

[derekyle]

I'm surprised no one else is having this issue. I am now on my 3rd Vue2 and just like before, it worked perfectly at first. And then this time, just a few days after installing it just all the sudden started returning the i2c error 3 again for every sensor. Power cycling doesn't fix it, left it off for a few minutes then reconnected the power. I'm going to post my config below just in case I have something weird. It just seems so bizarre that I would have this problem with 3 units. I'm beginning to wonder if something is up with my power and it is getting a surge or something. But power is pretty stable and wiring is good here. So I'm really at a loss.

esphome:
  name: emporiavue2

external_components:
  - source: github://emporia-vue-local/esphome@dev
    components: [ emporia_vue ]

esp32:
  board: esp32dev
  framework:
    type: esp-idf
    version: recommended

api:
  encryption:
    key: !secret encryption_key

ota:
  password: !secret commmon_ota_password

logger:
  baud_rate: 0

preferences:
  flash_write_interval: "48h"

i2c:
  sda: 21
  scl: 22
  scan: false
  frequency: 200kHz  # recommended range is 50-200kHz
  id: i2c_a
time:
  - platform: sntp
    id: my_time

.defaultfilters:
  - &moving_avg
    sliding_window_moving_average:
      window_size: 6
      send_every: 6
  - &invert
    # invert and filter out any values below 0.
    lambda: 'return max(-x, 0.0f);'
  - &pos
    lambda: 'return max(x, 0.0f);'
  - &abs
    lambda: 'return abs(x);'
  - &neg
    lambda: 'return min(x, 0.0f);'

sensor:
  - platform: emporia_vue
    i2c_id: i2c_a
    phases:
      - id: phase_a 
        input: RED  
        calibration: 0.021355  # 0.022 is used as the default as starting point but may need adjusted to ensure accuracy
      
        voltage:
          name: "Phase A Voltage"
          filters: [*moving_avg, *pos]
      - id: phase_b  
        input: BLACK  
        calibration: 0.023102  
        voltage:
          name: "Phase B Voltage"
          filters: [*moving_avg, *pos]
    ct_clamps:
      - phase_id: phase_a
        input: "A" 
        power:
          name: "Phase A Power"
          id: phase_a_power
          device_class: power
          filters: [*moving_avg, *pos]
      - phase_id: phase_b
        input: "B" 
        power:
          name: "Phase B Power"
          id: phase_b_power
          device_class: power
          filters: [*moving_avg, *pos]
      - { phase_id: phase_a, input:  "1", power: { name: "HVAC Power A", id:  cir1, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_b, input:  "2", power: { name: "HVAC Power B", id:  cir2, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_b, input:  "3", power: { name: "Kitchen Power", id:  cir3, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_a, input:  "4", power: { name: "Microwave Power", id:  cir4, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_a, input:  "5", power: { name: "Bathroom Plugs Power", id:  cir5, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_b, input:  "6", power: { name: "Bedroom Plugs Power", id:  cir6, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_a, input:  "7", power: { name: "HVAC Blower A", id:  cir7, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_b, input:  "8", power: { name: "Main Lights/HVAC Blower B", id:  cir8, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_a, input:  "9", power: { name: "Fridge Power", id:  cir9, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_b, input: "10", power: { name: "Server/Laundry Power", id: cir10, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_b, input: "11", power: { name: "Garage Power", id: cir11, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_a, input: "12", power: { name: "Office/South Kitchen Plugs Power", id: cir12, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_a, input: "13", power: { name: "Dishwasher Power", id: cir13, filters: [ *moving_avg, *pos ] } }
      - { phase_id: phase_b, input: "14", power: { name: "Disposal Power", id: cir14, filters: [ *moving_avg, *pos ] } }
 

  - platform: template
    name: "Total Power"
    lambda: return id(phase_a_power).state + id(phase_b_power).state;
    update_interval: 2.88s
    id: total_power
    unit_of_measurement: "W"
    
  - platform: template
    name: "HVAC Blower"
    lambda: return id(cir7).state * 2;
    update_interval: 2.88s
    id: hvac_blower_power
    unit_of_measurement: "W"

  - platform: template
    name: "HVAC Compressor"
    lambda: return id(cir1).state + id(cir2).state;
    update_interval: 2.88s
    id: hvac_compressor_power
    unit_of_measurement: "W"
  
  - platform: template
    name: "Main Lights"
    lambda: return id(cir8).state - id(cir7).state;
    update_interval: 2.88s
    id: main_lights_power
    unit_of_measurement: "W"
  
  - platform: template
    name: "Balance Power"
    lambda: return id(phase_a_power).state + id(phase_b_power).state - id(cir14).state - id(cir13).state - id(cir12).state - id(cir11).state - id(cir10).state - id(cir9).state - id(cir8).state - id(cir7).state - id(cir6).state - id(cir5).state - id(cir4).state - id(cir3).state - id(cir2).state - id(cir1).state;
    update_interval: 2.88s
    id: balance_power
    unit_of_measurement: "W"
  
  - platform: template
    name: "HVAC Power"
    lambda: return id(hvac_blower_power).state + id(cir1).state + id(cir2).state;
    update_interval: 2.88s
    id: total_hvac_power
    unit_of_measurement: "W"

  - platform: total_daily_energy
    name: "Total Daily Energy"
    power_id: total_power
    accuracy_decimals: 0
  - { power_id:  cir3, platform: total_daily_energy, accuracy_decimals: 0, name:  "Kitchen Daily Energy" }
  - { power_id:  cir4, platform: total_daily_energy, accuracy_decimals: 0, name:  "Microwave Daily Energy" }
  - { power_id:  cir5, platform: total_daily_energy, accuracy_decimals: 0, name:  "Bathroom Plugs Daily Energy" }
  - { power_id:  cir6, platform: total_daily_energy, accuracy_decimals: 0, name:  "Bedroom Daily Energy" }
  - { power_id:  main_lights_power, platform: total_daily_energy, accuracy_decimals: 0, name:  "Main Lights Daily Energy" }
  - { power_id:  cir9, platform: total_daily_energy, accuracy_decimals: 0, name:  "Fridge Daily Energy" }
  - { power_id: cir10, platform: total_daily_energy, accuracy_decimals: 0, name: "Server/Laundry Daily Energy" }
  - { power_id: cir11, platform: total_daily_energy, accuracy_decimals: 0, name: "Garage Daily Energy" }
  - { power_id: cir12, platform: total_daily_energy, accuracy_decimals: 0, name: "Office/Kitchen Plugs Daily Energy" }
  - { power_id: cir13, platform: total_daily_energy, accuracy_decimals: 0, name: "Dishwasher Daily Energy" }
  - { power_id: cir14, platform: total_daily_energy, accuracy_decimals: 0, name: "Disposal Daily Energy" }
  - { power_id:  hvac_blower_power, platform: total_daily_energy, accuracy_decimals: 0, name:  "HVAC Blower Daily Energy" }
  - { power_id: hvac_compressor_power, platform: total_daily_energy, accuracy_decimals: 0, name: "HVAC Compressor Daily Energy" }
  - { power_id: total_hvac_power, platform: total_daily_energy, accuracy_decimals: 0, name: "HVAC Daily Energy" }
 

[derekyle]

Just updating this issue with more that I have done in case anyone has ideas. I have now gone through 3 Emporia Vue units. Each one working for for a few days and then suddenly starting to throw timeout errors. Below is the output of verbose debugging:

[10:55:57][E][emporia_vue:048]: Failed to read from sensor due to I2C error 3
[10:55:57][V][component:204]: Component emporia_vue.sensor took a long time for an operation (1.00 s).
[10:55:57][V][component:205]: Components should block for at most 20-30ms.

That set of errors repeats over and over presumably once for each of the active 16 CT clamps. It does not appear that it has anything to do with Home Assistant or ESPhome updates because the other 2 units that failed, failed at random times without having updated or changed anything. Power cycling has not fixed it. Clearing esphome cache did not. I have also completely removed the esphome device and recreated it, started from a fresh config file, tried different frequencies for the i2c component. And then lastly, I re-flashed a unit back to the original emporia vue firmware, and surprisingly, it works fine. Then after flashing it again, back to the esphome firmware, it still doesn't work. Very strange.

[flaviut]

@clowrey there are two 3.3V regulators, 3.3V_WiFi, which is exposed on the programming header, and a 3.3V_Analog, which is what the MCU & analog switches are powered by. U2 is the regulator for the analog circuitry.

[clowrey]

Awesome you found the problem! Emporia should hire you as their tech support/repair 😝 wonder if they got a bad batch of regulators..

[Veers01]

I will order the part and test the repair on my unit too. I don't have the equipment to diagnose the problem but I'm sure able to do this kind on repair.

[derekyle]

Awesome, thanks for figuring that out. Could you post a picture of the circuit board and highlight which part you had to replace? That would be very helpful for me or anyone else to fix one in the future.

[flaviut]

Sure, I've replied in a top-level component so it doesn't get buried: #108 (comment)

[Veers01]

Same here with ESPHome 2023.6.5. I have the error on all my sensor on emporia. Try to update to 2023.7.0, same error:

[10:59:15][E][emporia_vue:048]: Failed to read from sensor due to I2C error 3
[10:59:15][W][component:204]: Component emporia_vue.sensor took a long time for an operation (1.00 s).
[10:59:15][W][component:205]: Components should block for at most 20-30ms.

I don't know when this append, I have neglects my system for the past months. :(

[flaviut]

If you are in the USA & would like to mail me your device to test, please email me at the email address in my github profile. I'll send it back to you once I've figured out what's wrong.

[flaviut]

For @derekyle's device, the problem was a hardware fault. Replacing U2 with a NCV8730ASN330T1G solved the issue and hopefully the better specs mean that the issue will not come up again.

Diagnosis

Connect the Vue to 5V power (VCC_5V0)

With a multimeter, measure the voltage between these two points (the shield, which is ground, and one side of R43, which is connected to the output of U2)

If you see 3.3V, then U2 is likely fine. If you see more or less than 3.3 volts, then the U2 regulator may be the problem.

Repair

Desolder and remove U2 from the rear of the board:

Replace it with NCV8730ASN330T1G, or another comparable part.

(cc @Veers01)

[madsciencetist]

Just chiming in to add that I had this problem, and this solved it. I had the same I2C errors, saw that the U2 regulator was outputting 5V instead of 3.3V, and removed it. I connected the VCC_3V3_WIFI pin to what had been the U2 output, saw that the bus got properly energized with 3.3V and the I2C errors went away. I assumed that was a low-reliability fix, removed that jumper I had added and instead put a NCV8730ASN330T1G where U2 had been. Working well.

[Aston77]

I am running into this problem oddly enough after I had the vue working and had to swap the phases my red & black wires were connected to.

Testing with a multimeter I and seeing 3.289v at R43, but the looking at the tolerances of the NCV8730ASN330T1G being 1% as I understand it that reading should still be in range.

I also reflashed using web.esphome.io with no notable benefit.

The oddest thing was it was working, but just swapping the red & black wires was enough to generate ongoing "i2c error 3" issues

Any thoughts on what I could try that might narrow down the issue?

[wingrunr21]

I wanted to pop in here and add that I also got the I2C error on 2 new gen5 Vue 2s. In both instances, the U2 regulator was fine (verified with a multimeter). It ended up being an issue flashing new units from the HASS add-on for ESPHome.

In both cases, a flashed Vue from the add-on wouldn't connect to wifi without being connected to the AC plug and would spew I2C error 3. I ended up solving it by choosing the manual install from the add-on and using web.esphome.io to perform the flash. After that, worked great (even connected to wifi when connected to the USB <> Serial adapter via 5v).

My hunch is that the add-on isn't properly prepping the ESP32 for the install. ESPHome Web has an explicit "erasing" step which seems to not happen via the add-on (or at least, the UI doesn't reflect this). Either way, with the exact same config, I couldn't get them to flash until I used web.esphome.io

[mutilator]

esphome/issues#6335

Issue in the esp home tracker was created as well

[genehand]

Fix/workaround in esphome/issues#6335 (comment) 👍

[jpborjas]

The fix/Workaround above, fixed it for me!

[Glob0x17]

Thanks a lot ! you save me :D

[agoode]

I've proposed #317 to update the README with the new settings.