Bogus Enphase Values?

[rigid fog]

My metrics today are absolutely bananas. I have a separate, albeit more primitive, "Real Time Usage" number from my electricity provider that confirms that today's energy usage is normal - but...

• Is there any way I can determine what caused this wild data?
• Is there any way I can exclude this data from reporting? It'll mess up my work to start building daily/monthly power usage.

[limber grove]

You can adjust the data over the dev tools > statistics

At worst you can add a negative value to eliminate this

[rigid fog]

Great news, thanks.

This sort of seems, at first blush, like a weekly/monthly/Ltd value got loaded suddenly. Odd.

[trail rose]

Your Enphase system has been running for some time before you included it in Home Assistant, didn't it? Because this looks like the initial value read by HA was the system's current state for the energy produced and energy consumed being greater than 0. As HorstExplorer said, you can fix this initial value in Developer tools -> STATISTICS. Just overwrite those large initial values by 0 and future readings will automatically be offset with the corrected values.

[grizzled berry]

That might not work as after correction to 0 the next lifetime value will be in the same ballpark and still produce the peak. Using lifetime value for energy dash is recommended for Enphase, as todays value has been reported with issues in some situations. You could try using the daily value in the energy dash and see if the issue shows or not.

Sounds like the Energy dashboard is lacking a detection of very first value to ignore?

[rigid fog]

Yes that's correct. Installed by the previous owner.

[rigid fog]

Hm, I'll look into this

[trail rose]

It is not the energy dashboard that needs this detection. It is the recorder and/or the integration. Fixing the initial value will work, as the [state] column will still have the lifetime value (as supplied by the Enphase integration), but the [sum] column will be the corrected value. i.e. the initial [sum] value will be 0, the 2nd entry will be 0 + (state(1) - state(0)), where 0 is our corrected initial value, the [sum] value of the 1st row: sum(0). The third entry will be sum(1) + (state(2) - state(1)), etc.

Every integration that produces an ever-growing value has this same issue. f.e. zigbee plugs that keep track of energy usage, water meters, smart p1 meters. all produce an initial peak value when the meter was not reset at the same time it reads the initial value into HA. It would be nice to have this fixed in the recorder, but on the other hand it's only an easy, single time needed fix to correct it.

Most people don't even notice it, as they usually integrate only 'fresh' (newly bought) meters into their HA systems and thus the initial value will be (close to) zero anyway.

[grizzled berry]

Thanks for the thorough explanation. I'll add it to the enphase integration docs in a future update.

[grizzled berry]

Would this work the same way with a single step when prior data is present? Just got an issue reported where for some envoy models the lifetime value that reset to zero each ~1.2MWh is now reporting the total value again. Result a large step change. If we let them correct the very first value to the last low value it would work evenly well? From your descriptions it seems so, right?

[rigid fog]

I was mulling this over and I realized there's an alleged spike in use every day or so that's also probably a false value.

[rigid fog]

For instance, today

[trail rose]

You did add the "Lifetime Energy Consumption" and the "Lifetime Energy Production" sensors in the Energy dashboard, i.e. not the "Today's Energy Consumption/Production" sensors? Because those last ones are known to reset at weird times and thereby potentially can cause odd, daily returning, spikes. Production starts only when the voltage output by your panels exceeds some threshold, and all values output throughout the night time are suppressed, i.e. a peak at 00:00 for the consumption plus one in the first sunny hour for the production could very well be a symptom of you using those daily resetting sensors.

[trail rose]

Yes, you can also fix a peak (or a low) in between two discontinuous data sets using the same method: The 'state' will still show the values from the both data sets, the 'sum' however can be fixed to continue the series over the both sets. In fact, I once imported my energy readings from the time I used Domoticz before I used Home Assistant into the statistics table (in the homeassistant db) with timestamps before I had HA running. I had to fix a single entry in both the consumption and the production statistics and from then on I could see my old Domoticz data in HA's dashboard, combined with the values recorded by HA.
It isn't completely flawless though, because Domoticz only stores its energy information on a daily basis. My pre-HA energy data thus shows as one single 'measurement' each day. But hey, I don't care, because I realistically never need to see my usage per hour from over a year in the past... Most of the times I only use that old data to compare monthly or even yearly usage/production.