# \[APP\]\[Pro\] Ford Vehicle Data - Your Ford's status, always within reach **URL:** \ **Category:** Apps\ **Tags:** app, homey-pro\ **Created:** [September 6, 2026, 12:27pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236 "2026-09-06T12:27:47Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [September 6, 2026, 12:27pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/1 "2026-09-06T12:27:47Z")
> [Ford Vehicle Data | Homey](https://homey.app/a/com.ziglar.fordvehicledata) =============================================== ## WHAT DOES THIS APP DO? 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. ## STEP 1 - CREATE A FORD DEVELOPER APPLICATION 1. Create an account on the Ford Developer Portal. 2. Register a new application there for the “FordConnect Query API”. ( [https://developer.ford.com/developer-eu/application](https://developer.ford.com/developer-eu/application) ) 3. Fill in EXACTLY the following as the redirect/callback URL (do not change it): 4. Save the Client ID and Client Secret you receive from Ford. 5. It can take up to 2 hours before new Ford credentials become active. If it doesn’t work the first time, try again a bit later. ## STEP 2 - INSTALL THE APP 1. Navigate to [Ford Vehicle Data | Homey](https://homey.app/a/com.ziglar.fordvehicledata) . 2. Install the app as usual. 3. Go to: More → Apps → Ford Vehicle Data → settings (gear icon). 4. Enter your Client ID and Client Secret (from step 1) and click Save. 5. Restart the app: Apps → Ford Vehicle Data → Restart. (Required - new settings don’t take effect without a restart.) ## STEP 3 - PAIR YOUR VEHICLE 1. Go to Devices → + → select Ford Vehicle Data → select “Ford Vehicle”. 2. You’ll be sent to Ford’s login page. Log in with your non-developer account and select your car. 3. Click “Allow” at the bottom of the page. 4. You’ll return to Homey, where you can confirm the vehicle that was found. 5. 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. ---
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [September 7, 2026, 6:40am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/2 "2026-09-07T06:40:12Z")
Looking for a few testers , send me a private message trough this community of you are interested. ---
**Author:** ![Marco\_Schilder](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/marco_schilder/32/120715_2.png) [@Marco\_Schilder](https://community.homey.app/u/Marco_Schilder)\ **Post date:** [September 7, 2026, 7:58am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/3 "2026-09-07T07:58:13Z")
I want to test it ---
**Author:** ![Tim\_de\_Jongh](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tim_de_jongh/32/154651_2.png) [@Tim\_de\_Jongh](https://community.homey.app/u/Tim_de_Jongh)\ **Post date:** [September 7, 2026, 2:47pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/4 "2026-09-07T14:47:16Z")
I want to test it in the Netherlands as well. ---
**Author:** ![Joy\_Bulters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joy_bulters/32/129226_2.png) [@Joy\_Bulters](https://community.homey.app/u/Joy_Bulters)\ **Post date:** [September 16, 2026, 6:40pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/5 "2026-09-16T18:40:24Z")
Vrijwilliger ! ---
**Author:** ![Joy\_Bulters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joy_bulters/32/129226_2.png) [@Joy\_Bulters](https://community.homey.app/u/Joy_Bulters)\ **Post date:** [September 17, 2026, 10:04am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/6 "2026-09-17T10:04:33Z")
De installatie ging vlekkeloos dankzij de goede handleiding. Ik mis alleen de gegevens over de rijaccu. Ik denkdat ik nogmaals bij ford moet inloggen om alle gegevens te krijgen. ---
**Author:** ![FocalFossa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/focalfossa/32/171899_2.png) [@FocalFossa](https://community.homey.app/u/FocalFossa)\ **Post date:** [September 17, 2026, 12:59pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/7 "2026-09-17T12:59:40Z")
Ik wil ook wel testen, voor mij zou ik ook de PHEV/EV accu status willen kunnen uitlezen ---
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [September 17, 2026, 1:21pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/8 "2026-09-17T13:21:19Z")
The app is now live, you can follow the manual to install the published version. ---
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [September 18, 2026, 7:19am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/9 "2026-09-18T07:19:36Z")
Update 1.1.1 for EV is now live ---
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [September 18, 2026, 11:40am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/10 "2026-09-18T11:40:14Z")
Update the app to version 1.1.1 ---
**Author:** ![Joy\_Bulters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joy_bulters/32/129226_2.png) [@Joy\_Bulters](https://community.homey.app/u/Joy_Bulters)\ **Post date:** [September 18, 2026, 11:49am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/11 "2026-09-18T11:49:57Z")
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. So far so good. ---
**Author:** ![Joy\_Bulters](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/joy_bulters/32/129226_2.png) [@Joy\_Bulters](https://community.homey.app/u/Joy_Bulters)\ **Post date:** [September 18, 2026, 11:52am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/12 "2026-09-18T11:52:40Z")
Gewoon de instructie van Ziglar volgen en het werkt. ---
**Author:** ![John\_Janssens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_janssens/32/48716_2.png) [@John\_Janssens](https://community.homey.app/u/John_Janssens)\ **Post date:** [September 29, 2026, 7:08pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/15 "2026-09-29T19:08:22Z")
Hi Ziglar, I’m having an issue pairing a **Ford E-Transit Courier** with Ford Vehicle Data **v1.1.1**. The pairing process gets quite far: - I created my own Ford Developer application for the FordConnect Query API. - Client ID and Client Secret are entered in the Homey app. - I restarted the Ford Vehicle Data app after saving the credentials. - The credentials have been active for more than 2 hours. - The Ford login itself works. - My E-Transit Courier is successfully found and shown in the vehicle selection screen. - I can select the Courier and press Continue. However, immediately after pressing Continue, the pairing fails with: AADB2C90085: The service has encountered an internal error. Please reauthenticate and try again. Example from my latest attempt: Correlation ID: 68084025-ad98-4e34-8ad0-1e26c3d22fde Timestamp: 2026-09-29 16:41:03Z I have already tried: - Restarting the Ford Vehicle Data app - Re-authenticating - PC and iPhone - With and without VPN - 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? ---
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [October 1, 2026, 6:16am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/16 "2026-10-01T06:16:36Z")
Hello John, quick question: Did you select All available data categories in the first screen when creating the api? and did you select all fuel types when creating the app ---
**Author:** ![John\_Janssens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_janssens/32/48716_2.png) [@John\_Janssens](https://community.homey.app/u/John_Janssens)\ **Post date:** [October 1, 2026, 6:38am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/17 "2026-10-01T06:38:26Z")
Hi Ziglar, Yes, I checked it again: - **All available data categories** are selected. - **All fuel types** are selected when creating the app. So unfortunately that doesn’t seem to be the cause. The E-Transit Courier is found correctly during pairing and I can select it. The error only appears after I press **Continue** : `AADB2C90085: The service has encountered an internal error. Please reauthenticate and try again.` I’m using Ford Vehicle Data **v1.1.1**. Is there anything else I can check, or would a diagnostic log from Homey help? ---
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [October 1, 2026, 6:46am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/19 "2026-10-01T06:46:12Z")
yes. restart the app, try to connect, then immediately create the report and send me the id please. i’ll check if there is anything in there tonight. ---
**Author:** ![John\_Janssens](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_janssens/32/48716_2.png) [@John\_Janssens](https://community.homey.app/u/John_Janssens)\ **Post date:** [October 1, 2026, 6:53am UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/20 "2026-10-01T06:53:11Z")
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. e61a3dd0-7a38-4a35-9c13-4dc64c1101ac ---
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [October 3, 2026, 1:07pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/21 "2026-10-03T13:07:17Z")
Added to original forum post: - 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. ---
**Author:** ![Alexandre\_Ladra](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/alexandre_ladra/32/177367_2.png) [@Alexandre\_Ladra](https://community.homey.app/u/Alexandre_Ladra)\ **Post date:** [October 3, 2026, 6:17pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/22 "2026-10-03T18:17:09Z")
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! 🙂 ---
**Author:** ![Ziglar](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ziglar/32/1009_2.png) [@Ziglar](https://community.homey.app/u/Ziglar)\ **Post date:** [October 9, 2026, 4:28pm UTC](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236/23 "2026-10-09T16:28:42Z")
Hi, 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](https://homey.app/a/com.ziglar.fordvehicledata/test/)) and let me know how it goes? If anything looks off, screenshots are very welcome. [Next page](https://community.homey.app/t/app-pro-ford-vehicle-data-your-fords-status-always-within-reach/159236.md?page=2)