Enphase Envoy Shows incorrect Lifetime Production values about core HOT 6 CLOSED

@home-assistant close

from core.

Hey there @bdraco, @cgarwood, @dgomes, @joostlek, @catsmanac, mind taking a look at this issue as it has been labeled with an integration (enphase_envoy) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

enphase_envoy documentation
enphase_envoy source
_{^{(message by IssueLinks)}}

from core.

Hi @suedeyoung, so your solar installation has been running for some years and you now are adding it to Home Assistant?

The numbers differ quite a bit as you are indicating. History at the very first start may take some time to show as expected.

To rule-out other issues can you share the diagnostics file from the HA Envoy integration page here?

from core.

Hey there!

Yes, that is correct. We had it installed back in 2021 and have been looking at trying out Home Assistant, so we added them to the energy tab.

Here's the file that it downloaded on my end:

config_entry-enphase_envoy-2d42629786b78ae971d1c569efc93110.json

from core.

Looking at your file and your remark earlier:

The system doesn't have a consumption module (the solar panel company didn't tell me until after installation that it's an extra charge for some reason to install it, so I am waiting on them..)

It seems to be the other way around. If you look in the file for "/ivp/meters": you'll find:

          "state": "disabled",
          "measurementType": "production",

and

          "state": "enabled",
          "measurementType": "net-consumption",

These are the current transformer (CT) clamps. The Envoy reports that a net-consumption one is installed and configured. The net-consumption CT sits on the grid lines somewhere between where they enter the house and the main panel.

The production CT typically sits on the lines from the solar to the panel. But these are reported as disabled and won't report solar production data, if they even are installed.

If this is an known and expected configuration see below, if not, something might not be configured as needed. You need to determine if, how many and where you have CT installed and if that matches the Envoy configuration.

If the configuration is as expected, no production CT and a net-consumption CT, then HA integration uses the data in the "/production.json?details=1": section of the file. And more specifically this section:

          {
            "type": "inverters",
            "activeCount": 40,
            "readingTime": 1716297287,
            "wNow": 1778,
            "whLifetime": 220893
          },

The whLifetime value is what is used for Lifetime Energy Production, the 0.221 MWh you see. The value is reported by the Envoy.

So why is this number so different from the Enphase App/Website. We don't know the details, but have reports from users of Envoy-metered without installed and configured CT clamps that the whLifetime value cycles to zero roughly every 1.19 Mwh. The app value of 46.7 is 39 of those cycles and ~0.280 MWh left, pretty close to the reported value. So I wouldn't be surprised this is going on.

Long story short:

• observe what lifetime energy production is doing, it might wrap around 1.19 MWh. Think the energy dash can handle it and will report hour and day values. If not we can find a workaround for it.
• Check what your current transformer situation needs to be and if it is accurate. Envoy-metered without CT has it's own features based on which firmware the Envoy runs.

from core.

Hey Catsmanac,

Thanks for getting back to me. I have confirmed with them that it should be a production module that is installed and not the consumption module. They said they would look into it some more and get back to me, so hopefully, we will get that side of things sorted out soon.

from core.