Power readings are way higher than reality

[catatung]

Hey everybody--

I recently flashed a vue2 with the ESP32 firmware and have added it to a homeassistant instance (running HAOS on a proxmox VM if it matters) -- I was able to pull in the entities however, the values are incorrect.

The software pulled in POWER and DAILY ENERGY for each circuit. However, after comparing with a standalone current clamp meter, I found a huge disparity in some. Two examples are below:

Circuit 6 current clamp meter reading: 12.10A
HA reports 2670W
2670W / 117.6V = 22.70A

Circuit 12 current clamp meter reading: 0.750A
HA reports 98.9W
98.9W / 117.6 = 0.84A

One is way off, the other is close. I switched the current clamp jacks and got the same readings, so I have ruled out issue of a bad CT sensor. In searching I read about assigning the correct phase for each circuit in configuration, but both phases read 117.6v, so I didn't bother to get to that just yet, since it wouldn't be the problem here as both are identical.

Does anybody have any ideas what I could do to fix this or tests I could perform to nail down what the cause of these inaccuracies are? I've read that the native reporting of current is off, and that it should be mathematically computed within HA to get the correct data, but before I even get to that, I'm seeing the wrong values. Is there some other data available via JSON/esp32home that HA did not pull in that I should be using to calculate the wattage/current draw?

Thanks for any help
Randy

[flaviut]

both phases read 117.6v, so I didn't bother to get to that just yet, since it wouldn't be the problem here as both are identical

The RMS voltage may be identical, but the phases are definitely not! Current & voltage is measured by the vue thousands of times a second, while your multimeter only measures a long-term average.

Please update your & come back if you're still have trouble.

[catatung]

Hi Flaviut,

That file I found/showed to you was from the download diagnostics link. It sent a text file to my browser. Image is attached so you can see them.

Since this is a HAOS installation, I do not have the linux command line shell which I am most familiar with for finding and editing configuration files. When I originally flashed the unit, I used a vue2.yaml file to generate the firmware which had numerous references to phase association for all of the circuits. Is there a different place you recommend I can look to check if the phase information is set correctly? It appears either the file "download diagnostics" sent me is incomplete, or the initial flashing process paid no regard to the phase information in the vue2.yaml file.

Otherwise I guess, if there are no other ideas, I could try flashing again. Though I would still like to find out how I can confirm from the HA/ESP32Home interface if the phase information ported over as expected.

Thanks for any ideas or suggestions
Randy

[flaviut]

Is there a different place you recommend I can look to check if the phase information is set

There is no way to do this. This is the closest you can get.

The only way to confirm is to reflash the config.

Once you've checked the phases in the config match the phases in your panel, and you've reflashed the Vue, please let me know if the data still looks wrong. Also make sure that your multiply values in filters: [ *moving_avg, *pos, multiply: 2 ] are correct. Step 9 in the Vue manual has instructions.

[catatung]

Hi Flaviut,

I took myself back to basics today and took some time to RTFM -- and figured out what I had done wrong, my mistake was staring at me the whole time!

I had made a temporary plug for the unit so I could power it up at my computer desk and flash the firmware. After examining the documentation, I joined the blue and white wires for connection to neutral, and joined the red and black wires for connection to hot. I wired these to an electrical outlet plug, and plugged it into my Variac (for some added isolation via the transformer windings)

Once I was done flashing the firmware, I brought it down to the panel and out of convenience just plugged in the cable I had created at the desk, forgetting that the two phases need to be connected separately inside the panel!

I am going to assume this is my problem -- I will get some time soon to disconnect my plug connection and attach it correctly inside the panel, taking note of the phases on each breaker. I will then update my .yaml file and create the .bin firmware file, and reflash the unit. I'll let you know how everything is once I've done that. I am thinking this will solve my problems.

Thanks for pushing me in the direction of the phase management and helping me to realize my mistake! :)

Randy

[catatung]

I've wired the 4 pin connector correctly now to my panel -- I now have different readings for Phase A and Phase B voltage, as you previously indicated would absolutely be the case.

I've mapped out which circuits are on which phases, and before looking into modifying my configuration to reflash the unit, I reviewed my previous YAML file which I used to create the firmware BIN file which was flashed to the unit. I found this:

- { phase_id: phase_a, input:  "6", power: { name:  "Circuit 6 Power", id:  cir6, filters: [ *moving_avg, *pos, multiply: 2 ] } }
- { phase_id: phase_a, input: "12", power: { name: "Circuit 12 Power", id: cir12, filters: [ *moving_avg, *pos, multiply: 2 ] } }

I believe this is my problem - the multiplier is set to 2 on the two specific circuits that I am seeing the implausible current draw. I believe this was a starting point configuration file from following instructions when I initially flashed the unit, however I didn't take any time to review the configuration file, because I read that future changes could be easily made and not require grounding the GPIO to flash the unit.

I went to update my config file, starting with validating the .YAML file which I know I used previously. I received this message when running "esphome ./vue2.yaml config"

INFO Reading configuration ./vue2.yaml...
Failed config

esphome: None

  'platform' is a required option for [esphome].
  name: emporiavue2

I know I used this file previously when I flashed via the windows utility. Now that it is on my network, I am on Linux, and receiving this message. Do you have any idea why? I'm considering pulling the unit back and grounding the GPIO and flashing it the way I initially did, but doing it from Linux would be so much easier.

As always thanks for any help!
Randy

[flaviut]

Maybe try updating your esphome version--I just updated emporia-vue-local/esphome to the febuary edition a few hours ago. If that doesn't work, try clearing caches and so on.

The issue sounds like it's in the configuration step, which comes before the compilation & the flashing steps.