Electrafi Charging Data Issues

[DeanB1452]

Has anyone had any issues with their charging data on Electrafi? Since March, it has been missing components of the charge data. I submitted a ticket with Electrafi right away and got a response that they were looking into it, but only crickets for the last month and no responses to my inquiries.

Sponsored

 

[godfodder0901]

Has anyone had any issues with their charging data on Electrafi? Since March, it has been missing components of the charge data. I submitted a ticket with Electrafi right away and got a response that they were looking into it, but only crickets for the last month and no responses to my inquiries.

Rivian changed some API endpoints. Other services are having the same issues.

 

[pogiant]

that's pure electrafi issue, rivian api endpoints haven't changed and rivian uses websockets for streaming charging data. You can evaluate https://rivolt.dev/signup I created as electrafi+abrp alternative, it has electrafi import option with charging enrichment, so you can have this data backfilled.

 

[godfodder0901]

that's pure electrafi issue, rivian api endpoints haven't changed and rivian uses websockets for streaming charging data. You can evaluate https://rivolt.dev/signup I created as electrafi+abrp alternative, it has electrafi import option with charging enrichment, so you can have this data backfilled.

Based on some communication with the devs of the Home Assistant integration for Rivian I was under the impression that Rivian renamed getLiveSessionData to getLiveSessionHistory on their GraphQL API.
And:

the getLiveSessionHistory is not a replacement for the previous getLiveSessionData. Rivian is migrating/has migrated to a new encoded data structure for some commands/queries.

 

[pogiant]

Based on some communication with the devs of the Home Assistant integration for Rivian I was under the impression that Rivian renamed getLiveSessionData to getLiveSessionHistory on their GraphQL API.
And:

That rename doesn't quite match what I'm seeing. getLiveSessionHistory does exist and is stable - I use it myself for session-start metadata (IsRivianCharger, startTime). But it's not a drop-in replacement for getLiveSessionData: it returns populated telemetry only for DC fast sessions, and zeros out AC/L1/L2. So if you swap one name for the other you'll appear to "work" on DC and silently lose everything else.

Live charging telemetry isn't a REST endpoint for a long time now - it flows over the WebSocket ChargingSession subscription. That stream pushes powerKW, totalChargedEnergy, timeElapsed/Remaining, price, vehicleChargerState, plus a chartData SoC/power series, and crucially it's populated for every session type including home AC.

My read on the ElectraFi outage in late March: getLiveSessionData stopped producing any data, their query was hardcoded to it, and they haven't migrated to the subscription. Anyone still polling REST for live telemetry will keep getting empty rows until they move to the WebSocket path. The REST getLiveSessionHistory call is fine to keep around, but only as a metadata enrichment - not as the telemetry source.

Sponsored