EV Energy Consumption (last trip) - value incorrect?

[alexwhittemore]

This pretty clearly isn't an issue with the integration since the data comes unmodified from the API, but I wonder if anyone else has noticed that the entity "EV Energy Consumption (last trip) is consistently low? I made a trip efficiency calculator in HA using that data, and it appears to report low. In fact, it appears to report data consistent with the energy consumed by the drivetrain only and not HVAC or accessories. That is, on my drive this morning, "EV Energy Consumption (last trip) read 81% of the value calculated from OBDII "available energy" before and after the trip, while the infotainment system said "80% used for driving." I wrote it up here:
https://www.alexwhittemore.com/home-assistant-and-mach-e-trip-efficiency-calculation/

Mostly a curiosity but if anyone has ideas on how to accurately calculate the TOTAL consumption I'd love to hear them!

[grahamr]

This is fascinating- thanks for diving in with OBD data. I have a 2025 and unfortunately can't pull that data due to the encryption on the port.

I've been using these stats in an automated trip logger, and one thing I noticed is that I def have a delta in the charged energy vs consumed - i haven't had a chance to really dig into the "why" there, but the assumption its drivetrain only seems plausible.

Whats unfortunate is that this is one of the few endpoints that isn't in the proper public API so we cant even easily "ask ford". It also means any OBD based tracking apps on a phone will equally under report - also interesting.

[alexwhittemore]

I have a 2025 and unfortunately can't pull that data due to the encryption on the port

That's very surprising, are you sure it's true? The whole point of anything available via OBDII is that it's explicitly made available for diagnostic use. The "energy remaining" PID in the 2024 isn't there by accient - it's not like someone reverse engineered the communication between two other modules to get it. Now, not all the same PIDs might be present, or currently known to app developers, but I don't think that has anything to do with TRON in 2025/26 cars.

But in any event, it doesn't matter, you can also get it via HA-Fordpass, right from the Ford app API. Again no guarantees it's available for all model years, but in my setup it's at "sensor.fordpass_YOURVIN_elveh.batteryEnergyRemaining"

Tell me more about your automated trip logger! I was thinking of trying to make one myself using a Home Assistant automation to log details to some external database at each trip-end for offline post-processing/searching/analytics/etc, but haven't fleshed it out yet.

[grahamr]

Ah yeah, the one that's not in the proper API is energytransferlogentry which I'm using as well.

My automation is:

• Trip or charge state changes
• Webhook fires to N8n with the data
• N8n parses and writes the trip entry
• If its a charge, it parses it to see if its home or away
• if the charge is home, its logged
• if the charge is away, its sends a telegram message
• telegram reply is parsed by n8n and if 0 it logs as free, if i reply with an amount it logs the per kwh charge cost and then replies with a summary.

This is all written into postgres, and is supplemented by 2 other n8n automations that scrape our power utility for the rate, as well as our fuel regulator for the "weekly" price (checked daily in the event they use a legislation to change mid week)

Grafana charts my trip costs, charging costs, and highlights home vs away trips.

I can do everything with the ford connect query integration except for the charge data.

[grahamr]

Re OBD, I know I could see a few values, but not the battery SOH and some other things I was after so I returned my dongle.
Also from what I read ABRP isnt working with 25+ vehicles over obd either. That may have changed though.