This is the meters endpoint call in _async_get_meters() here. It fails before even reaching the usage data request. The 424 Failed Dependency points to that ConEd's backend is not returning meter asset IDs, so the Opower API doesn;t know what to do. This appears to be a server-side issue on ConEd's end, but I do not know much more.
Request: GET https://cned.opower.com/ei/edge/apis/cws-real-time-ami-v1/cws/cned/accounts/3d205211-dcf6-11f0-ba90-0200170e78f8/meters
Response (HTTP 424):
{
"error": {
"details": "An invalid response was received from EDAP API. No meter asset ID returned. (<redacted uuid>)"
}
}
This is the meters endpoint call in
_async_get_meters()here. It fails before even reaching the usage data request. The424 Failed Dependencypoints to that ConEd's backend is not returning meter asset IDs, so the Opower API doesn;t know what to do. This appears to be a server-side issue on ConEd's end, but I do not know much more.Request:
GET https://cned.opower.com/ei/edge/apis/cws-real-time-ami-v1/cws/cned/accounts/3d205211-dcf6-11f0-ba90-0200170e78f8/metersResponse (HTTP 424):
{ "error": { "details": "An invalid response was received from EDAP API. No meter asset ID returned. (<redacted uuid>)" } }