Ford Vehicle Data shows your Ford vehicle’s data in Homey: lock status,
doors/windows, location (home/work/away), fuel, oil, tire pressure, 12V
battery, ignition status and warning lights. Use this to build your own
Flows, for example a notification when your car arrives home but isn’t
locked.
WHAT DOES THIS APP NOT DO?
This app CANNOT control your car. No locking/unlocking, no remote start,
no climate control, no charging, no horn or lights. All communication
with Ford is read-only.
WHAT DO YOU NEED?
A Homey (Pro).
A Ford account with a vehicle that works with FordPass/FordConnect.
Your OWN, free Ford Developer account with your own registered
application (a Client ID + Client Secret). This is required: the app
never uses a shared key, every installation uses its own Ford
registration. This is a deliberate, permanent design choice - not a
temporary limitation.
Go to: More → Apps → Ford Vehicle Data → settings (gear icon).
Enter your Client ID and Client Secret (from step 1) and click Save.
Restart the app: Apps → Ford Vehicle Data → Restart.
(Required - new settings don’t take effect without a restart.)
STEP 3 - PAIR YOUR VEHICLE
Go to Devices → + → select Ford Vehicle Data → select “Ford Vehicle”.
You’ll be sent to Ford’s login page. Log in with your non-developer account and select your car.
Click “Allow” at the bottom of the page.
You’ll return to Homey, where you can confirm the vehicle that was found.
One Ford login gives access to exactly one vehicle. If you have
multiple cars, just repeat the pairing process for each one.
After pairing it might take a few minutes for all available information to show up, give it some time.
WHAT DATA DO YOU GET?
Lock status, per-door/window open or closed, hood
Location: home / work / away / unknown (never the exact coordinates)
Fuel level and remaining range (petrol/diesel vehicles only)
Oil life (a Ford-calculated estimate, not a physical measurement)
Tire pressure per wheel, plus warnings
12V battery level and voltage
Ignition status (off/on/accessory/start)
Warning lights (check engine, ABS, airbag, brake, traction control)
and a general “other notifications” field
Whether Ford’s data is up to date, and how old it is
A data point only appears once your specific car actually reports it to
Ford - not every model/trim level provides everything.
IMPORTANT THINGS TO KNOW
Ford’s data is not real-time. There’s a delay between what your car
reports to Ford and what Ford makes available. Homey then reads the
latest status from Ford every 60 seconds (default, cannot be set lower).
If the app can’t reach Ford for a while, the device becomes
“unavailable” - this recovers automatically once Ford is reachable again.
Trying to pair the same vehicle twice gives a clear message - that’s
not an error.
Do NOT try to log in to Ford repeatedly in quick succession if
something goes wrong during pairing. Ford enforces a limit on login
attempts; too many attempts in a short time can trigger a temporary
block. If that happens, wait 30-60 minutes and try again.
PRIVACY
Your Client ID/Secret are stored only locally on your own Homey -
never shared with the developer or other users.
Your vehicle’s VIN is masked internally, never logged or shown in
plain text.
Exact GPS coordinates are never shown - only the derived
home/work/away status.
TROUBLESHOOTING
“This Ford vehicle is already paired with Homey”
→ You’re trying to pair a car that’s already paired. Remove the
existing device first, or select a different car at Ford.
Device becomes “unavailable” with a message that you need to log in
again
→ Ford revoked access. Remove the device and pair again.
Device temporarily becomes “unavailable” (“Ford data temporarily
unreachable”)
→ A temporary issue on Ford’s side. Recovers automatically, no
action needed.
An expected data point is missing
→ Your car apparently doesn’t report that data point to Ford. Not a
bug.
Long, unclear error message from Ford during pairing
→ Check that your Client ID/Secret were entered correctly and that
you restarted the app after saving the settings (step 2.5).
Pairing fails with “AADB2C90085: The service has encountered an
internal error” (especially on a Transit Courier / E-Transit Courier)
→ This error comes directly from Ford’s own servers, not from this
app. The Transit Courier is the one Ford model that does NOT have
a built-in FordPass Connect modem as standard - it needs a
separate aftermarket modem, activated and connected, before any
third-party app (including this one) can read its data. Check in
the FordPass app whether your vehicle shows as “Connected”. If it
doesn’t, this isn’t something this app (or Homey) can work around.
I’ve installed (at least homey did it) the update. I can read the PHEV battery status. All data I can see are correct, compared to the data obtained from my Ford app.
I programmed a quick test to see if my Ford’s presence and plugin is recognised. Excellent.
Now I have to connect My car into the “Slim Laden Thuis & Auto” app.
Creating a new Client Secret and waiting for it to become active
Checking the Client ID and Client Secret
The strange thing is that the vehicle itself is successfully discovered, so authentication appears to work up to the point where the vehicle is selected. The error seems to occur when the pairing is finalized / the token is exchanged.
My Ford Developer account and the Ford account used for the vehicle are not necessarily the same account. The Courier is registered to my father’s Ford account, and my Ford account has been invited/shared access to the vehicle. I’m also going to test pairing directly with his primary Ford account.
Is AADB2C90085 a known issue with the current OAuth/token exchange in v1.1.1, or is there anything else in the Ford Developer configuration I should check?
Restarted the Ford Vehicle Data app and immediately tried to connect my Ford again. The connection still fails. This diagnostic report was created immediately after the failed connection attempt.
Pairing fails with “AADB2C90085: The service has encountered an
internal error” (especially on a Transit Courier / E-Transit Courier)
→ This error comes directly from Ford’s own servers, not from this
app. The Transit Courier is the one Ford model that does NOT have
a built-in FordPass Connect modem as standard - it needs a
separate aftermarket modem, activated and connected, before any
third-party app (including this one) can read its data. Check in
the FordPass app whether your vehicle shows as “Connected”. If it
doesn’t, this isn’t something this app (or Homey) can work around.
Hi, thanks for the Ford Vehicle Data app, it works great with my Ford Puma Gen-E. One request: could you set the device class to car and enable energy.electricCar: true in the driver? That would make the vehicle show up in Homey’s Energy tab with its battery level, the same way other EV apps (like the Fiat 500e one) do. Thanks!
Thanks for the suggestion — good news, this is now implemented!
As of v1.1.2, the device will automatically set itself to device class “car” with energy.electricCar enabled as soon as it detects that your vehicle actually reports EV battery data. Concretely, two new capabilities were added alongside the existing ones: measure_battery and ev_charging_state (Homey’s own standard capabilities, required for the Energy tab). The moment those appear on your device, it should show up in Homey’s Energy tab with its battery level, the same way you described for the Fiat 500e app.
A few things worth knowing:
This only affects EV/PHEV vehicles. Since this app also supports regular petrol/diesel Fords, non-electric vehicles are untouched — they never get these capabilities and stay as a regular sensor device.
It applies automatically to your already-paired Puma Gen-E too — no need to remove and re-add it. It should pick this up on its next data refresh (within a minute) after you update.
This requires Homey firmware 12.4.5 or newer (that’s a Homey platform requirement for the ev_charging_state capability, not something I can change). If you’re on an older firmware and don’t see it, that’s likely why.
I don’t have an EV to test this against myself, so this is implemented based on Ford’s and Homey’s official documentation but not yet verified live against a real Puma Gen-E. I’d really appreciate it if you could confirm whether it shows up correctly in your Energy tab once you’re on the new version — and let me know if the battery percentage/charging state look right.
I’ve just pushed this to the test channel on Athom. Could you install the test version of the app (Ford Vehicle Data | Homey) and let me know how it goes? If anything looks off, screenshots are very welcome.
