Revert "Revert "Remove AC Current sensor, no correct readings""

[mnederlof]

I think you were right to remove it the first time 😄

My assumption is that this value is only used, if the inverter is used to charge a battery. In my setup it is always 0, but as the name in the file says, it is acCurrentInmA (so inbound).

One var that might be a nice to have, it the leadingVArs, which is the reactive power in the inverter while producing power.
My assumption is, that laggingVArs is the value for reactive power while in charging mode

Maybe if somebody shares their file with a battery setup, it might shed some more light on those assumptions 😇

Reverts #181

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mnederlof]

One could also argue, that we could add the joulesProduced value to provide a more precise production for the current day. (as you can convert joules to a wh value)

(and since there is also a joulesUsed value, it further strengthens my assumption that the acCurrentInmA is for charging mode, or at least the output is used for both the inverter and the battery inverter module)

[vincentwolsink]

For my setup (Envoy Standard with IQ8 inverters, no battery) this sensor actually provides data.

[vincentwolsink]

Although on lower production the value isn't what I would expect. Currently my Production is between 1-3 W and the AC Current value stays on 0,074 A (which should be around 17 W). Maybe this has to do with power usage of the inverter mainboard itself (although I would kinda expect that the logic works on DC)

[mnederlof]

oh wow, for me the graph flatlines, but lets see what it does today 😇

[vincentwolsink]

About the naming, I think the last part of acCurrentInmA stands for "in milliamperes" stating the unit. Same for all the other ones like acFrequencyINmHz etc. Since there is no outSomething.

[mnederlof]

That could be as well obviously, as it is a guess 😄

Anyway, the joulesProduced can be used (in collaboration with duration), to calculate the watts->now value (with more precision)

So, i think we can ignore it for now 😇