An ALTERNATIVE to Fordpass integration is born (read only)

[marq24]

I am quite happy to share with you the news, that I have finished the initial steps to release a first version of my FordConnect Query Integration for HA...

https://github.com/marq24/ha-fordconnect-query

Comparison / need help with the decision ?

You can find a brief comparison between both integrations here: https://github.com/marq24/ha-fordpass/blob/main/doc/FORDPASS_VS_FORDCONNECT.md

[N3rdix]

Read-only would be fine for me, but I didn't get the difference fully.
The Ford API used is not the same, right? Are you planning to further maintain both integrations then, as you mentioned it's unsure when this one will break?

Grüße und Danke für deinen Einsatz

[marq24]

The Ford API used is not the same, right?

That's correct - the API endpoint(s) are completely different - but at least the 'metrics' object have plenty of similarities...

Are you planning to further maintain both integrations then,

My plan is to maintain both. Specially since currently both Integrations have a "common" base [even if the code is currently copied] - but I wanted to have a initial working version asap, in order to get feedback - specially about your user experience "how to obtain a access token".

With the FordConnect Query integration, nobody have to deal with browser developer tools and all this complicated stuff. All services & portals are maintained by Ford. Of course we don't know how long this API access will be available either (since there was more or less the same available 1.5 years ago) - so we will see.

For me personal this is now the 2`nd backup implementation I have to access my car's SOC (and that's the most important value. So at the end of the day I am happy that it worked.

Also this new Ford API have also some documentation - so instead of build guessing, there might be now some additional hint's... [even if this might be a bit late] :-D

... as you mentioned it's unsure when this one will break?

Indeed I have no clue, what Ford might invent in the future to prevent that the FordPass HA Integration will continue to work... So having this new Integration will not hurt. [and in the last 24h I have learned plenty of stuff about oAuth Handling in HA]

[N3rdix]

Just gave it a try and ran both integrations in parallel for a short time, so you convinced me to switch to the new query-integration 🥇

It provides all data I need with my 2020 Mustang GT and the setup via developer account/official API makes me feel more confident that this won't break too often 😆

Thanks for the efforts

[SammyDog3]

Works perfectly with my 2025 Escape PHEV. It pulls the EV and the ICE data, for now at least. Thank you very much for doing this!

[grahamr]

I've gone pretty deep into building out a dashboard for my 1 week old Mach-E using the R/W integration, and one thing I'm finding is some values, like EV Last Charging Session seem to be "slow" to update - I will get positional data, trip data, other stats but this one value seems delayed. The App itself will show a completed charge session, so I know the data is "somewhere". With a move to the new query integration would that (potentially) be faster?
Right now i'm using that data, combined with trip data to build an automated dashboard showing trip and charge details, and I know that both entries reset when the "next" one comes along, so pulling that data out in a timely fashion is key.

[marq24]

First I just can recommend to give you a little bit more time - 1 week is really a short period of time. If you miss data (or wonder about when which sensor updates...

Just enable the data-dump function (via the integration options) in order to check, if you can find the data you are missing in the JSON data... Since you mention, the FordPass App will show this data - the Fordpass Integration will use the same data-source - so you should be able to find it in the logged JSON data...

Switching to FordConnect Query will IMHO does not change... FordConnect will request every x minutes the data from the backend - FordPass will get the data pushed as soon as the backend receive a change.

[grahamr]

Thanks - that's what I figured. The trip data is nearly instant - within seconds of hitting the stop button. It's that "last charging" value that's tricky at the moment.

For more context I've got an automation firing off when the value updates, which pushes the data via a webhook to n8n, which writes to a database.

I'll give it a bit more time to see what pattern I can find. I did sign up for a developer account, and may try running both integrations side by side just to compare data.

Long term I do like the idea of the read only integration just for "support" aspects.

[grahamr]

Thanks for that write up and the localized api endpoints. I have both integrations running now 😃