Enphase Envoy Battery reporting

“Consommation d’energie totale” is the consumption by the House also known as total-consumption.

“Lifetime net energy consumption” is balance of energy to and from the grid.

See the picture in this paragraph in the docs.

Difference between those is what the solar panels and batteries add.

For the dashboard you need 2 values, one for grid import and 1 for grid export. None of these 2 will work.

You can try splitting the “Lifetime net energy consumption” using the concept in the docs or correct lifetime balanced net energy consumption as described in this issue.

Thx for answer and sorry for delayed, I prepare now all Helper on my YAML Code

it s better for and also ask people for help :slight_smile:

And pehaps later i cand give the code to antoher people who have also the same problem

I dont have “balanced” Value

Here is my new Code, if you can please check :slight_smile: will be nice

If you have net-consumption CT installed then the balanced ones are disabled by default. You can enable these.

Hi @catsmanac ok thx for support

Just to clarify: does the Cloud API that provides data to the Enphase app apply smoothing to the values?

As you can see in the screenshot, sometimes the current net power consumption shows negative values—which could be interpreted as power export—but that’s not actually possible in those moments.

This discrepancy seems to cause differences later in the Cloud API data.

Please see my screenshot for reference.

No idea what data manipulation the cloud api does nor what data the Envoy is reporting to the cloud.

That value come directly from the Envoy. So it’s something the Envoy is picking up or wrongly reporting.

The export spikes seems to coincide with the spikes in the encharge energy puissance and battery charge/discharge power. You may want to check times on that to confirm

I dont understand why the value on the API cloud are correct but not for local API …

The measurements for the local API and the cloud API are performed using the same CT …

In my opinion, it has software processing/smoothing code so that users do not see export errors at night…

EDIT: here we can see also 'That “Balanced net power consumption” and Envoy xxxx “Current net power consumption” Give exactly the same mistake

See at time 10:30

EDIT2:

Here we can see that, for example, on 24 October, Enphase was having a lot of trouble with the measurements… Yesterday the values were wrong, and this morning I see that they have been corrected as if by magic…

That’s the most asked question about Enphase data. You should really ask Enphase. Their local API is poorly documented and no details how data is collected. Let alone it changes between firmware versions without notice or explanation. Details how the their cloud gets data and processed er not known either.

Their cloud api may hit delays in receiving and processing and look different when you have another look at a later time.

see also 'That “Balanced net power consumption” and Envoy xxxx “Current net power consumption” Give exactly the same mistake

That data comes from the same report source. If you see it always it can even be some issue with your installation.

One option is to use the HA filter integration to filter spikes if you have these often.

If you have multi phase installation check if this happens on all phases or on a specific one?

Hi i just activated the L1/L2/L3, then i can check it and give you feednack

You never see this kind of negativ value ?

For Enphase Value
it s seams that some another people have the same Problem…

Take a look here, Current Power Consumption is not matching real world · Issue #153265 · home-assistant/core · GitHub. That reports something similar in relation to batteries. Might be the same.

I will ask Enphase support, but Enphase in my country is not really good … sometimes no answer …
Is it possible to tell me what are the endpoints you are using for Current net power consumption and Balanced net power consumption

Balanced net power consumption: /production.json?details=1 / production / type = ‘eim’ / wNow

Current net power consumption: /ivp/meters/readings / [1] /activePower

Accessing IQ Gateway local APIs and local UI using token

1 Like