-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
Component/s: Cloud Integrations
-
None
The data returned from the Enphase API for site-level data can change over time, as individual devices report their data at different schedules. For example, a request to
/api/v4/systems/{systemId}/telemetry/production_micro
for a specific time range (close to "now") might return data like
{
"system_id": 123,
"granularity": "day",
"total_devices": 16,
"start_at": 1754335500,
"end_at": 1754336625,
"items": "intervals",
"intervals": [
{
"end_at": 1754335800,
"devices_reporting": 16,
"powr": 2436,
"enwh": 203
},
{
"end_at": 1754336100,
"devices_reporting": 15,
"powr": 2676,
"enwh": 223
},
{
"end_at": 1754336400,
"devices_reporting": 7,
"powr": 1968,
"enwh": 164
}
],
Note the devices_reporting values that decrease over time. After some time has passed, the same API query can report different results:
{
"system_id": 123,
"granularity": "day",
"total_devices": 16,
"start_at": 1754335500,
"end_at": 1754358300,
"items": "intervals",
"intervals": [
{
"end_at": 1754335800,
"devices_reporting": 16,
"powr": 2436,
"enwh": 203
},
{
"end_at": 1754336100,
"devices_reporting": 16,
"powr": 2688,
"enwh": 224
},
{
"end_at": 1754336400,
"devices_reporting": 16,
"powr": 2880,
"enwh": 240
},
The last 2 results changed. The Cloud Integration poll task does not take this phenomenon into consideration, which can cause it to capture "incomplete" data over time.
