Replies: 4 comments 6 replies
-
Yup! The current numbers are way off. Not sure why, and I'm not sure if it's possible at all to fix them. What you can do is create a set of computed fields that divide the power by that phase's voltage. Something similar to this perhaps?
|
Beta Was this translation helpful? Give feedback.
-
Allright, this bothered me enough to start to think about it and after a bit of playing I have a solution which gives reasonable numbers for me: I took a few assumptions here, leaving it for you @flaviut to judge if they make sense:
Then if you use real_current=measured_current/10/((2.2/used_phase_calibration)/100)/5.5 I get quite close for the sample values I took from my running system. One is within a percent and the other one is within 10% (but I don't fully trust my phase calibration numbers just yet, voltages seem bit too far). Following are the numbers I used and a screenshot of the excel sheet for the calc: Code for config:
Can somebody confirm if these numbers also work for them? |
Beta Was this translation helpful? Give feedback.
-
For me adding |
Beta Was this translation helpful? Give feedback.
-
Has this been fixed recently?
Here are the results that I get:
The current readings seem to make sense. Edit: just saw this PR which has been merged: #90 According to the readings, it is the apparent current. |
Beta Was this translation helpful? Give feedback.
-
First off, thanks for the esphome module for vue2, really nice and works like a charm.
I was trying to see if I could get the measured amperages out by using ct_clamps: input: current as configurable, but the numbers returned are not reasonable (123v, 2kw power, 897A?). I can see in the code there's a bit of magic (https://github.com/emporia-vue-local/esphome/blob/emporia-vue-2022.4.0/esphome/components/emporia_vue/emporia_vue.cpp#L118) to get corrected numbers for power. Any chance of a fix for current (in A)?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions