New Vue 3 install, not getting any voltage readings

[mattster98]

Freshly flashed Vue 3 and working in general, but not sending any voltage readings. Tried the dev and vue3 branch. Probably should have tested with the stock firmware before flashing to rule out any DOA issues.

Config below:

esphome:
  name: emporia-vue-3-1
  friendly_name: Emporia Vue 3 #1

# Enable Home Assistant API
api:
  encryption:
    key: "xxxxxxx"

ota:
  - platform: esphome
    password: "xxxxxxx"

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Emporia-Vue-3-1 Fallback Hotspot"
    password: "xxxxxxx"

captive_portal:
  
substitutions:
  display_name: EmpVu3-1

external_components:
  - source: github://emporia-vue-local/esphome@vue3
    components:
      - emporia_vue
      
esp32:
  board: esp32dev
  framework:
    type: esp-idf
    version: recommended

preferences:
  # the default of 1min is far too short--flash chip is rated
  # for approx 100k writes.
  flash_write_interval: "48h"   

logger:
  logs:
    sensor: DEBUG

i2c:
  sda: 5
  scl: 18
  scan: false
  frequency: 200kHz  # recommended range is 50-200kHz
  timeout: 13000ms # max value
  id: i2c_a

switch:
  - platform: restart
    name: Restart  

time:
  - platform: sntp
    id: sntp_time    

# these are called references in YAML. They allow you to reuse
# this configuration in each sensor, while only defining it once
.defaultfilters:
  - &throttle_avg
    # average all raw readings together over a 5 second span before publishing
    throttle_average: 5s
  - &throttle_time
    # only send the most recent measurement every 60 seconds
    throttle: 60s  
  - &moving_avg
    # we capture a new sample every 0.24 seconds, so the time can
    # be calculated from the number of samples as n * 0.24.
    sliding_window_moving_average:
      # we average over the past 2.88 seconds
      window_size: 24
      # we push a new value every 1.44 seconds
      send_every: 12
  - &invert
    # invert and filter out any values below 0.
    lambda: 'return max(-x, 0.0f);'
  - &pos
    # filter out any values below 0.
    lambda: 'return max(x, 0.0f);'
  - &abs
    # take the absolute value of the value
    lambda: 'return abs(x);'

sensor:
  - platform: emporia_vue
    i2c_id: i2c_a
    phases:
      - id: phase_a  # Verify that this specific phase/leg is connected to correct input wire color on device listed below
        input: BLACK  # Vue device wire color
        calibration: 0.022  # 0.022 is used as the default as starting point but may need adjusted to ensure accuracy
        # To calculate new calibration value use the formula <in-use calibration value> * <accurate voltage> / <reporting voltage>
        voltage:
          name: "Phase A Voltage"
          filters: [*throttle_avg, *pos]
        frequency:
          name: "Phase A Frequency"
          filters: [*throttle_avg, *pos]
      - id: phase_b  # Verify that this specific phase/leg is connected to correct input wire color on device listed below
        input: RED  # Vue device wire color
        calibration: 0.022  # 0.022 is used as the default as starting point but may need adjusted to ensure accuracy
        # To calculate new calibration value use the formula <in-use calibration value> * <accurate voltage> / <reporting voltage>
        voltage:
          name: "Phase B Voltage"
          filters: [*throttle_avg, *pos]
        phase_angle:
          name: "Phase B Phase Angle"
          filters: [*throttle_avg, *pos]
    ct_clamps:
      - phase_id: phase_a
        input: "A"  # Verify the CT going to this device input also matches the phase/leg
        power:
          id: phase_a_power
          filters: [*pos]
      - phase_id: phase_b
        input: "B"  # Verify the CT going to this device input also matches the phase/leg
        power:
          id: phase_b_power
          filters: [*pos]
  

[mattster98]

Here's what I'm getting in debug:
[21:14:21][D][sensor:094]: 'phase_a_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:21][D][sensor:094]: 'phase_b_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:22][D][sensor:094]: 'phase_a_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:22][D][sensor:094]: 'phase_b_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:22][D][sensor:094]: 'phase_a_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:22][D][sensor:094]: 'phase_b_power': Sending state 317.71600 W with 1 decimals of accuracy
[21:14:23][D][sensor:094]: 'phase_a_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:23][D][sensor:094]: 'phase_b_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:23][D][sensor:094]: 'phase_a_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:23][D][sensor:094]: 'phase_b_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:23][D][sensor:094]: 'Phase B Phase Angle': Sending state nan ° with 0 decimals of accuracy
[21:14:24][D][sensor:094]: 'Phase A Frequency': Sending state inf Hz with 1 decimals of accuracy
[21:14:24][D][sensor:094]: 'phase_a_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:24][D][sensor:094]: 'phase_b_power': Sending state 97.77600 W with 1 decimals of accuracy
[21:14:24][D][sensor:094]: 'phase_a_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:24][D][sensor:094]: 'phase_b_power': Sending state 0.00000 W with 1 decimals of accuracy
[21:14:24][D][sensor:094]: 'Phase A Voltage': Sending state 0.00000 V with 1 decimals of accuracy
[21:14:25][D][sensor:094]: 'Phase B Voltage': Sending state 0.00000 V with 1 decimals of accuracy

[DeathBlade]

No Idea if this will be of any help but your config is pretty close to mine with only a few differences in the filters for both voltage and power on the clamps.

For the filter under voltage I am using filters: [*pos, *pos] and for the clamps I am using filters: [*moving_avg, *pos]

may be work giving a shot

[DeathBlade]

Hmm, it is possible that caused some issue. I found my factory image and ill attach it here since i don't know off hand where else there is a factory image. Just in the off chance you want to give it a shot.
emporiavue3-factory.zip

[mattster98]

OK - got my replacement and confirmed it works OK. Going to push the factory image back to my original unit that is acting up. Got a quick pointer to an esptool command line for this? I'm feeling a little unsure and don't want to make things worse.

[mattster98]

In the original Vue 3 support thread there's a full factory bin dump that @digiblur took, which is about 8MB, so that seems like the right thing to push. Looking at trying a command line like this:

esptool.exe --chip esp32 --port COM5 --baud 115200 write_flash -z 0x0000 c:\Users\matt\Downloads\emporia_vue_gen3_oem_untouched\emporia_vue_gen3_oem_untouched.bin

[mattster98]

Pushing a factory image has been "working" in general.. I can go through all the steps to add the Vue 3 to the emporia app, but it will never connect to the cloud. I'm assuming there's some sort of way for them to know I've reflashed it. I examined the .bin and the MAC address from the device the firmware was downloaded from appears in the bin code, so I'm trying to hexedit that and see if that helps.

[mattster98]

Must be some other places that uniquely tie the firmware to the hardware that I can't see. The serial number has a prefix then the MAC address of the ESP. I'm guessing that, along with the "Check Code" on that label is involved somehow. I get to where the unit is doing the three flashes (trying to reach the cloud) but never gets farther.