Looks like a great app and I was waiting for an app like this. But I have troubles signing up for developer account. Maybe something went wrong in the process of creating an account. I login with email and password and auth app. That seems to work but I keep getting an overview page with the available api’s. I am able to view more after signin which I thought I did. No logout button either. Any ideas?
Hi,
First of all, @Ziglar THANK YOU SO MUCH for this app! I was waiting so long for a Ford Connect app.
Till now I used Home Assistant to connect my Ford EV to Homey, which worked ok-ish.
I don’t want to rely on third party domotica controllers and wanted a native Homey app. I even tried to make self an app, but didn’t succeed.
Now I’m testing your app and want to rebuild my current flows. But for my purpose I’m missing on flow card: AND > EV is charging. I know I can do that with a logic card, but a native card for this is cleaner. Is it possible for you to add this card? (Skoda app has this as well)
Many thanks again @Ziglar
Hi @Ziglar,
Unfortunately, the issue is still not resolved, even after following your suggestions.
I completely deleted my previous Ford Developer app registration and created a brand-new application with a new Client ID and Client Secret.
Ford initially displayed a message stating that the application was not ready and that I needed to wait 2 hours.
After waiting more than 2 hours, I completely reinstalled the Ford Vehicle Data app on Homey, entered the new credentials and tried pairing again.
Unfortunately, I still receive exactly the same error:
AADB2C90085: The service has encountered an internal error. Please reauthenticate and try again.
Correlation ID: db3fded1-c56a-40c9-9206-2525b5f03d30
Timestamp: 2026-10-13 12:14:49Z
Important clarification about when the error occurs:
-
Ford authentication itself appears to work.
-
The Ford E-Transit Courier is successfully discovered and displayed in the list of available vehicles.
-
I can select the E-Transit Courier without any problems.
Regarding your earlier suggestion about the FordPass Connect modem:
The vehicle is a 2026 Ford E-Transit Courier, not the older Transit Courier mentioned in Ford’s 2020 press release.
The official Ford app works correctly and provides access to:
-
Battery state of charge (SOC)
-
Remaining driving range
-
Vehicle location
-
Odometer reading
-
Remote climate control
-
Vehicle status and warnings
This strongly suggests that the vehicle has an active modem and connected services.
Tests already performed:
-
Two completely separate Homey installations
-
Different Windows PCs and an iPhone
-
Different browsers and network connections
-
With and without VPN
-
The vehicle owner’s primary Ford account
-
A completely new Ford Developer app registration
-
New Client ID and Client Secret
-
Waiting more than 2 hours for Ford’s application activation
-
Completely reinstalling the Homey app
All tests result in the same AADB2C90085 error after selecting the vehicle.
Since the official Ford app works correctly and the error occurs only after selecting the vehicle, I wonder whether this could be related to the FordConnect Query API’s authorization or vehicle-specific access permissions rather than the vehicle’s connectivity.
Do you have any further suggestions, or would you recommend escalating this directly to Ford Developer Support?
Thank you again for your time and help!
Kind regards,
John
@Alexandre_Ladra and @BasPost , both your suggestions are now live in v1.1.3
Hi, I’ve tried setting it up a couple of times but keep ending at a blank page with the text “Cannot GET /oath2/callback”
When I have selected my vehicle and confirms for what I presume is the last step before the car is added correct in homey.
Have you entered the correct address in step 1.3 ?
Yes, and Ive checked everything several times, everything was according to manual.
so ive delete4d everything on ford developer, and installed again and now im “online”
Hi @Ziglar ,
It seems that my EV location at home is not regconized. In the insights it shows distance at home 0km and when I’m from home, it alsp shows de distance. So it works somehow. Only the card does not.
I’m experiencing the same issue as others, encountering error “0085” despite following all troubleshooting steps. I’ve also performed a diagnostic with reference 8a12f6a4-28a9-45e6-b86e-7d1432aa412a. Any assistance would be greatly appreciated.
the mistake that John made was that he copied the enire json format value into the client id field. you should only copy the ID and Client secret as text values.
your log shows that the Client ID and Client Secret were not entered properly
Warning: Trying to access `Homey.env.CLIENT_ID` but the environment variable has not been set!
Warning: Trying to access `Homey.env.CLIENT_SECRET` but the environment variable has not been set!
kindly make sure that ONLY the ID is there and only the client secret without any additional characters.
also make sure to restart the app after you save the 2 values.
After a certain amount of time the app cannot accurate tell if the car is actually at home, the last update was indeed at home, but it changes from “at home” to unknown if too much time has passed since the last update.
Thank you, that was it. Pasted the secret to an editor and probably added sim ekstras:-)
