Enphase V4 Automatic Upload - Now 1 hour generation reporting

As of 11/15/2024 I have my Enphase Automatic Upload configuration displaying generation data in hourly buckets, delivered only hourly and averaged generation values across the hour versus 5 minute increments that update every 15 minutes. The consumption data still is in 5 minute increments. I have not made any configuration changes and my Enphase Enlighten Manager and Tesla Powerwall data do not exhibit this behavior. The daily totals are inline with Enlighten and Tesla. Please review these two daily production views for context. @bankstownbloke I would appreciate any insights here as these new data are ugly.

Prior data view 5 minute increments delivered in 15-minute increments:
https://pvoutput.org/intraday.jsp?id=45323&sid=70647&dt=20241114

New data view in hourly reporting with flattened data averaged across each hour (consumption data looks like normal 5 minute increments):
https://pvoutput.org/intraday.jsp?id=45323&sid=70647&dt=20241116

Note that this system is also sending Eagle net data which may be overwriting your Enphase data.

I do not see a configuration in PVOutput for Eagle Net. Please point me in the right direction to disable this if it is active. I don’t recall ever having used Eagle Net. I did previously use a Raspberry PI with the Tesla Powerwall integration service, but that’s long since gone.

Are you referring to the API Access key that’s enabled under Account Settings?

@bankstownbloke - I have removed the Eagle net API on Rainforest Eagle portal but still having the same problem. Now seeing a similar behavior with consumption data, though less of lengthy delay.

@bankstownbloke - please look at my data today (and the last 3). The data is totally messed up.

Today, I’ve had no data since 8:05am Pacific. I’m not sure what to do here. My Enphase data looks normal. Are others with the Enphase configuration having problems like I am?
https://pvoutput.org/intraday.jsp?id=45323&sid=70647

The raw responses from Enphase are reporting the same power data for the entire hour (see below), so this would be a change/problem on the Enphase side.

A potential workaround is to use a PVOutput rule under the ‘Automatic Uploads’ section.

power = -1

This will ignore power values from Enphase and calculate them from the energy value provided.

e.g. 3:50PM to 4:35PM on 2024-11-24

        {
        "end_at": 1732492200,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732492500,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732492800,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732493100,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732493400,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732493700,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732494000,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732494300,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732494600,
        "devices_reporting": 18,
        "powr": 288,
        "enwh": 24
    },
    {
        "end_at": 1732494900,
        "devices_reporting": 17,
        "powr": 288,
        "enwh": 24
    }

Thank you. Just made the change. Hoping that this fixes the problem.

I contacted Enphase and they actually responded within 30 minutes. They reset my polling configuration to 5 minutes. I also used your suggestion of the 'Automatic Uploads’ rule of power = -1. Not sure which change made the difference. Data is looking as of 11:30am PT.

Note the rule is case sensitive and should be power = -1 rather than Power = -1. The ‘TEST’ link on the left shows the result of the rule on a range of values.

@bankstownbloke you can mark this as problem fixed. Thanks for your insights on this.