Can't login: 403 Client Error: Forbidden for url: https://login.ford.com #488

frankie-boy-hgv · 2024-05-07T13:52:42Z

2024-05-07 15:47:24.506 WARNING (MainThread) [custom_components.fordpass] 403 Client Error: Forbidden for url: https://login.ford.com/xxxxxxxxxxxxxxxxxxx/B2C_1A_SignInSignUp_EN-GB/SelfAsserted?tx=StateProperties=xxxxxxxxxxxxxxxxxxx&p=B2C_1A_SignInSignUp_en-AU
2024-05-07 15:47:24.506 WARNING (MainThread) [custom_components.fordpass] Error communicating with FordPass for xxxxxxxxxxxxxxxxxxx
2024-05-07 15:47:24.506 WARNING (MainThread) [custom_components.fordpass] Returning Stale data to prevent unavaliable status
2024-05-07 15:47:24.507 ERROR (MainThread) [custom_components.fordpass] Error fetching fordpass data: Error communicating with FordPass for xxxxxxxxxxxxxxxxxxx

Ford changed things again?

JVTEAM · 2024-05-07T13:55:40Z

Same issue here. Thought it was because I upgrade the Core, but it seems just bad timing.

frankie-boy-hgv · 2024-05-07T13:57:58Z

Same here, right after updating to 2024.5.2 (from 2024.5.1)

JVTEAM · 2024-05-07T13:59:22Z

Same here, right after updating to 2024.5.2 (from 2024.5.1)

Ok, so it is core related.

keller1982 · 2024-05-07T14:04:18Z

Seems like it.

I didn't change the core, I still have 2024.4.2 and I have the same error.

400HPMustang · 2024-05-07T14:44:49Z

Same issue on 2024.5.1

JanosBerke · 2024-05-07T16:13:20Z

Hi,

It is the same here, Ford must have changed something.

D0NY3NK0 · 2024-05-07T17:05:41Z

Same issue here.

AndreiGavriliu · 2024-05-07T17:36:10Z

Same here. I thought I got banned or something

Picard16 · 2024-05-07T18:06:55Z

Same here in Germany with my Kuga.
Last successful sync was yesterday, 2024-05-06, at 16:20 CEST Europe.

EnDoubleU · 2024-05-07T18:15:38Z

Since 2024.5.2 the FordPass integration cannot initalize anymore. Logfile says: "Error fetching fordpass data: Error communicating with FordPass for vin number"
And since 16:10:07 of today (may 7) the "403 Client Error: Forbidden for url: https://login.ford.com/..." error.

AlanJ500 · 2024-05-07T18:41:06Z

Issue isn't core, it's on Fords side for this one. Maybe it will resolve itself? Or maybe some tweaks will need to be made.

clabern · 2024-05-07T18:41:34Z

Same issue here, started around 9:31AM eastern.

0sAND1s · 2024-05-07T19:04:40Z

Hi! The error I get in the log starting today is below. Thanks for any idea.

[139683214187072] 403 Client Error: Forbidden for url: https://login.ford.com/GUID-REMOVED/B2C_1A_SignInSignUp_EN-GB/SelfAsserted?tx=StateProperties=eyJUSUQiOiIxY2ZkMGNhZS1iMWQ1LTQ3ZTQtYTc1Yi1jNjMwZDUyOTEyOGIifQ&p=B2C_1A_SignInSignUp_en-AU

alessandro1898 · 2024-05-07T19:06:50Z

Same issue for me in Italy with a Ford Puma. Can't login.

bmwhitetx · 2024-05-07T20:20:00Z

Have not updated anything HA related in a month. On Core 2024.4.3. Got this error today. Can't be HA related.

dizzybro · 2024-05-07T23:12:07Z

Same here, can't login as of 5-7-2024

itchannel · 2024-05-07T23:39:15Z

Looks like an API change to the login flow. Will try and take a look later today. In the meantime I recommend people disable the integration in HA until I can fix it :)

domolys · 2024-05-08T03:22:33Z

Still running core 2024.1.6 and having the same issue

scotty1395 · 2024-05-08T05:15:51Z

Working again for me in Australia. Entities became available about 90 minutes ago without a HA restart.

frankie-boy-hgv · 2024-05-08T07:46:14Z

Not working here yet.

0sAND1s · 2024-05-08T08:50:00Z

I also noticed that the official FORDPASS app now shows some details that were previously unavailable/removed:

charging details (charging power, time, energy added, etc)
charging history
charging times & places
leaving time
So it may seem that the API was changed on the FORD side.

itchannel · 2024-05-08T10:37:14Z

Initial looks it seems Ford have enabled Akamai Bot Manager in a fairly aggressive mode to prevent people calling the API Login from tools other than Fords own app.

This probably isn't going to be a quick fix. It does look like they have officially launched their developer api that people could use but only available in Northern America and severely limited so I'm unable to test or implement that.

Will keep playing and seeing if there's away round it.

AlanJ500 · 2024-05-08T12:35:55Z

@itchannel The new FordPass Connect API in the developer program does have feature parity according to the Ford team in charge of it. The only difference is that anyone who wants to use it must register their FordPass account to use it and prevent lockouts.

The Ford team has been attempting to reach out to you to get this functional / supported.

ve6rah · 2024-05-08T14:30:08Z

You say only available in North America, in fact the website specifies only available in the US, so not even Canada!
That said, if I have to create a developer account to get things working, I'm willing to do that, but if it's not even going to work in my country, that's severely disappointing! And less than a week after I bought my truck!

If the Ford team is really trying to reach out to you though, absolutely take this opportunity! That's exactly what we've been waiting for! Anything they can do to help make this official would go a very long way to helping all of us.

AlanJ500 · 2024-05-08T14:33:28Z

^ The Ford team is. I don't speak for them, however my interactions with the team is that they do want to enable this type of functionality but also balance security concerns and legal concerns. The developer program is new, which is why it's US only right now. I am sure that will change over time.

mclever · 2024-05-08T14:48:03Z

I signed up for a dev account, put n/a for company, and was poking around. From https://developer.ford.com/use-cases/connect-ford-to-daily-tracking-apps it says that the FordConnect API is available globally except for China. You can connect your dev account to Fordpass account and get API creds.

400HPMustang · 2024-05-08T14:50:06Z

You can connect your dev account to Fordpass account and get API creds.

Are you able to log in to the fordpass integration with those creds or does it require a different login URL?

ve6rah · 2024-05-08T14:50:20Z

I signed up for a dev account, put n/a for company, and was poking around. From https://developer.ford.com/use-cases/connect-ford-to-daily-tracking-apps it says that the FordConnect API is available globally except for China. You can connect your dev account to Fordpass account and get API creds.

That's the tracking API only, that doesn't include things like unlocking or locking, remote start, etc. Scroll to the bottom of that page that you linked and will show the actual connect API separate and listed as USA only

Dangeryeen · 2024-09-27T00:56:39Z

This is what I did: Install version 1.68 (but don't set anything up), then go to 'Developer tools' in Home Assistant, perform the following "action" with these settings and button. This will trigger an offer to update to version 1.70. Restart HA and ignore the prompt to update back to 1.68.

I can't even get fordpass to show under targets, everything is to update, not sure what I'm doing wrong.

Installed 1.68 on hacs, restarted, went to dev actions to update and 'fordpass' won't show under anything

ve6rah · 2024-11-27T00:15:08Z

So this repository was last updated back in May, and the experimental 1.70 branch never was pushed to this repository. The official instructions on how to install 1.70 no longer work either as you can't get the token through that link anymore.

Is this whole project simply abandonware at this point?

I'm not trying to criticize the authors at all. I get it that Ford is not playing nice, and are making our lives difficult, however I'm wondering if there's even any work still happening on this, or if I just need to give up and realize that Fords can no longer be integrated into HA?

benk016 · 2024-11-27T00:18:17Z

I was able to use the method from 1.70 just last week. But Ford locked my account within 12 hours of setting it up again.

ve6rah · 2024-11-27T00:19:59Z

Just now the link only gives me a 403 error when trying to log in, developer tools no longer shows a code.

itchannel · 2024-11-27T00:22:01Z

The 1.70 branch does work as it's what I am actively using and a lot of other users are as well. The issue and why I haven't pushed it to main is Ford are changing things a lot and have even dropped support for the semi working official API. We have been trying in the background to get open dialogue with Ford but it's been an uphill struggle and not expecting anything anytime soon.

Unfortunately with these blockers I don't want to release the new version and then have a lot of people banned. So for now use 1.70 at your own risk.

@benk016 If you are getting 403 please try a different browser or your account is banned/not setup correctly.

ve6rah · 2024-11-27T00:33:38Z

I was using 1.70 until 2 days ago as well. with a secondary disposable account and then I got the "suspicious activity, reset your password" email. I reset my password, and then logged in again in my browser successfully. However today I couldn't get the new token.

That said, I'm now trying to login again through the website, and it's just spinning. No error message, just never completes. Just tried my main account too on the main website, and it's not loading either, so maybe the Ford servers are having issues. I'll have to try again later.

I do appreciate all you've done here, I really do! I'm just trying to gauge where we're at, the project seems at a stand still, and I get that based on Ford's actions.

ve6rah · 2024-11-27T00:56:30Z

@itchannel well, I managed to get the token in firefox, but when I enter it into HA I just get "an unknown error occurred"
2 log entries in HA core:

This error originated from a custom integration.

Logger: py.warnings
Source: custom_components/fordpass/fordpass_new.py:108
integration: fordpass (documentation, issues)
First occurred: 17:53:03 (1 occurrences)
Last logged: 17:53:03

/usr/local/lib/python3.12/site-packages/urllib3/connectionpool.py:1064: InsecureRequestWarning: Unverified HTTPS request is being made to host 'login.ford.com'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings warnings.warn(

and

Logger: aiohttp.server
Source: /usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py:448
First occurred: 17:53:04 (1 occurrences)
Last logged: 17:53:04

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_protocol.py", line 477, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_app.py", line 567, in _handle
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 92, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 210, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 26, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 86, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 242, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 32, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/http.py", line 73, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 81, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 222, in post
    return await super().post(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 74, in wrapper
    return await method(view, request, data, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 122, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in async_configure
    result = await self._async_configure(flow_id, user_input)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 414, in _async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 517, in _async_handle_step
    result: _FlowResultT = await getattr(flow, method)(user_input)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/fordpass/config_flow.py", line 171, in async_step_token
    info = await validate_token(self.hass, user_input)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/fordpass/config_flow.py", line 64, in validate_token
    results = await hass.async_add_executor_job(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/fordpass/fordpass_new.py", line 116, in generate_tokens
    return self.generate_fulltokens(req.json())
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/fordpass/fordpass_new.py", line 119, in generate_fulltokens
    data = {"idpToken": token["access_token"]}
                        ~~~~~^^^^^^^^^^^^^^^^
KeyError: 'access_token'

mojomojoman · 2024-11-28T13:25:52Z

Yeah they recently started locking accounts and forcing you to verify and change password if you're polling over a certain amount of time. I got locked repeatedly a while back but mine is now set to 930 seconds and I haven't been locked out once since. [image: image.png]

…

On Tue, Nov 26, 2024 at 6:18 PM benk016 ***@***.***> wrote: I was able to use the method from 1.70 just last week. But Ford locked my account within 12 hours of setting it up again. — Reply to this email directly, view it on GitHub <#488 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQAZQIXGSQSQ44TPYP5E3BL2CUFWRAVCNFSM6AAAAABHLB227CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBSGMZDIOJZGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

patrickvorgers · 2024-11-28T13:51:57Z

I recently encountered an issue where my token was no longer accepted. This caused my account to be locked due to the reload mechanism in the Home Assistant integration, which retries more times than allowed by Ford, ultimately resulting in the lockout.

I spoke with someone from the FordPass helpdesk, who mentioned that the limit is 250 calls per day. To prevent this issue from happening again, I created an automation that checks whether the FordPass integration is in error and disables the integration if needed.

You need to install the Spook integration to be able to disable an integration.

alias: "Home Assistant: Ford Pass integration error"
description: >-
  Disable the Ford Pass integration when it is in error. This to prevent that
  the account will be disabled (max 250 calls per day)
triggers:
  - trigger: event
    event_type: system_log_event
    event_data:
      name: custom_components.fordpass
      level: ERROR
    alias: Log event that Ford Pass is in error
conditions: []
actions:
  - action: homeassistant.disable_config_entry
    data:
      config_entry_id: 29f10c1e71d10b79535be6d8fa412940
mode: single

In the configuration.yaml you have to enable events

# Create events on system log items
system_log:
  fire_event: true

ve6rah · 2024-11-28T17:05:59Z

So I've confirmed my account is not locked. I have no problem logging in normally through the website.

But when I try to enter my token into the fordpass integration (1.70) it just won't take it "Unknown error occurred" and the log messages as posted above.

Anyone with any ideas?

ve6rah · 2024-11-28T23:50:38Z

Update: DO NOT USE FIREFOX TO GET THE TOKEN. The token Firefox gave must have been invalid somehow as it gave me the "unknown error" But once I switched to chrome and got the token there I was successful.

Also, Brave wouldn't get a token at all, even with all protections disabled.

doczong · 2024-12-03T23:09:04Z

Looks like all was well here for months, and then my account got locked out as above (#488 (comment)) and I had to reset my password on the ford site, but I was indeed able to get in, but it is not accepting any token now from Firefox or Edge (same token).

Edit, eventually got it working after numerous, repeated, and same attempts. Edge eventually worked, but I had to use USA, whereas my location, Canada is not working.

advisorgee · 2024-12-31T22:24:58Z

Just noticed this had gone down today, and looking at the logs; it looks like the SSO URL no longer exists; https://sso.ci.ford.com.

benk016 · 2024-12-31T22:53:30Z

Just noticed this had gone down today, and looking at the logs; it looks like the SSO URL no longer exists; https://sso.ci.ford.com.

Still working normally for me here.

advisorgee · 2025-01-04T21:49:48Z

had to remove the integration, restart HA, then reinstall the integration and then follow the procedure to get my token.

danielbrunt57 · 2025-01-06T10:02:18Z

Are we all talking about the original branch (v1.68) or the v1.70 branch?

ve6rah · 2025-01-06T10:03:52Z

Are we all talking about this original version 1.68 or the alternate version 1.70?

1.68 does not work at all. There is no way to get it working as is. The only version that somewhat works is 1.70, however the developer has decided not to publish that one officially so you have to download it manually to get it to work.

danielbrunt57 · 2025-01-06T10:40:10Z

I've installed 1.68 via HACS, deleted custom_components/fordpass/, downloaded v1.70.zip and copied its custom_components/fordpass to my config/custom_components/, restarted HA, verified manifest.json says "version": "0.1.70", then went about installing the integration. I get the URL to open to login, log in and locate the header:

fordapp://userauthorized/?code=eyJraWQiOiJHS2R2ZTVaVXEtNjBlRVpsTHRINHpiR3JfY1JoU05mWEJXVDZBYUtKTUlvIiwidmVyIjoiMS4wIiwiemlwIjoiRGVmbGF0ZSIsInNlciI6IjEuMCJ9.m7CzEYCqRZspW-M-Ycn9QSGzyyIMXIjtAsz5K4JxrdOEyYGvNUAGuoo9v7mFN_61VhGsf9nEpBS5AkMd87yWVdrpQhlL8jF2MhSINjv1dhdbFzTNf0kHgCyUqpq86a2kuAyuFCLyqBK6XJgmKae1mEkcgkM2y_ly9bimjAzxh1a_NzdDTTnmd-tnUhrgL9Hzzn7igZ_un-EZjWwSrWnhgVqBM96Vg6qhPfP9rTEfoSm1uR_6HcqyzEeO_A8nJsbVWaohfqUikS1LcZ9xw9NNL5U3T5Dr8OfVn0MVzRDD0z3YkalozO1W2xlEzBHTPC5WnsVMnmqNnohhjFq2r_ZVGw._2lcMJh4KqXrPdAi.WXM6TUEB0cWgzBxaxdbNM2lh2MCG1jTrnwhjWv6I4fUdHaOHoij1tzA1N54qPGnkwFCAIX0IQNgrWxvIjkFuvOtuqWzOJGxS2mXE9KjPh5LX7n014mUml47YojGvSKMlx0uFdC-q5U33CP6zFQ5uanqhtN9b-XaJwMFZ13i23b8bcoZecCzs5wlN8KpRL4BiLHYjjfXg58SmFnCr1Phznii_vi1bwC5wENf-wCtazn5VJABSH1Ak-TsHPGnChHhMXqF2iorln70abngsg-mEqQgofJxAVMdtT4YW37HmlcAA3XRXzznQG7dUPc9Mg49ofm8es6aF4irAZvyKwiIIkc66IXjXBA7m5emwFgiIS7qsscBA8HPmNUMh0aWWw5K_iEthxcRwbpPd2J_4Zs7fTxXXdEyguDbKYuIQrqh17717P_bLWCc39GlRwFjjW3PR22NxdXVdgmxZzHCI6F_THc6Y8c8yDDjH3sj9axykWo7cc8OL3nuhqRSaRDM4g6l5U9EATiENtgVEK31u8BR6JknWGywx56T65kg47Ii15QBgvo8k_15aBwQKxAj_4gS9JMF2cF083jEAh6D4s7D_HWUAlSmWnE1eNnGt0VYvKqN8H3ic1ydwgzdKcxbhIqiobciC2FbZljEgu5-7O2ImDLzIsACVtNMBExvQ4gv4muM-HpFkDDp4rFyDgOB-PrFoqtrS4v2J_vq1QtgnNYbIDypmT9Qfd4WS71L3Gx1nKaVcgaV3cL_lceoE42jWCZATrzDuBgsP7A.vwMetYBhzZDH276er4abeg

and paste:

eyJraWQiOiJHS2R2ZTVaVXEtNjBlRVpsTHRINHpiR3JfY1JoU05mWEJXVDZBYUtKTUlvIiwidmVyIjoiMS4wIiwiemlwIjoiRGVmbGF0ZSIsInNlciI6IjEuMCJ9.m7CzEYCqRZspW-M-Ycn9QSGzyyIMXIjtAsz5K4JxrdOEyYGvNUAGuoo9v7mFN_61VhGsf9nEpBS5AkMd87yWVdrpQhlL8jF2MhSINjv1dhdbFzTNf0kHgCyUqpq86a2kuAyuFCLyqBK6XJgmKae1mEkcgkM2y_ly9bimjAzxh1a_NzdDTTnmd-tnUhrgL9Hzzn7igZ_un-EZjWwSrWnhgVqBM96Vg6qhPfP9rTEfoSm1uR_6HcqyzEeO_A8nJsbVWaohfqUikS1LcZ9xw9NNL5U3T5Dr8OfVn0MVzRDD0z3YkalozO1W2xlEzBHTPC5WnsVMnmqNnohhjFq2r_ZVGw._2lcMJh4KqXrPdAi.WXM6TUEB0cWgzBxaxdbNM2lh2MCG1jTrnwhjWv6I4fUdHaOHoij1tzA1N54qPGnkwFCAIX0IQNgrWxvIjkFuvOtuqWzOJGxS2mXE9KjPh5LX7n014mUml47YojGvSKMlx0uFdC-q5U33CP6zFQ5uanqhtN9b-XaJwMFZ13i23b8bcoZecCzs5wlN8KpRL4BiLHYjjfXg58SmFnCr1Phznii_vi1bwC5wENf-wCtazn5VJABSH1Ak-TsHPGnChHhMXqF2iorln70abngsg-mEqQgofJxAVMdtT4YW37HmlcAA3XRXzznQG7dUPc9Mg49ofm8es6aF4irAZvyKwiIIkc66IXjXBA7m5emwFgiIS7qsscBA8HPmNUMh0aWWw5K_iEthxcRwbpPd2J_4Zs7fTxXXdEyguDbKYuIQrqh17717P_bLWCc39GlRwFjjW3PR22NxdXVdgmxZzHCI6F_THc6Y8c8yDDjH3sj9axykWo7cc8OL3nuhqRSaRDM4g6l5U9EATiENtgVEK31u8BR6JknWGywx56T65kg47Ii15QBgvo8k_15aBwQKxAj_4gS9JMF2cF083jEAh6D4s7D_HWUAlSmWnE1eNnGt0VYvKqN8H3ic1ydwgzdKcxbhIqiobciC2FbZljEgu5-7O2ImDLzIsACVtNMBExvQ4gv4muM-HpFkDDp4rFyDgOB-PrFoqtrS4v2J_vq1QtgnNYbIDypmT9Qfd4WS71L3Gx1nKaVcgaV3cL_lceoE42jWCZATrzDuBgsP7A.vwMetYBhzZDH276er4abeg

into the config setup but it says token is invalid. I've tried both Canada and USA...

ve6rah · 2025-01-06T10:42:09Z

I've installed 1.68 via HACS, deleted custom_components/fordpass/, downloaded v1.70.zip and copied its custom_components/fordpass to my config/custom_components/, restarted HA, verified manifest.json says "version": "0.1.70", then went about installing the integration. I get the URL to open to login, log in and locate the header:

fordapp://userauthorized/?code=eyJraWQiOiJHS2R2ZTVaVXEtNjBlRVpsTHRINHpiR3JfY1JoU05mWEJXVDZBYUtKTUlvIiwidmVyIjoiMS4wIiwiemlwIjoiRGVmbGF0ZSIsInNlciI6IjEuMCJ9.m7CzEYCqRZspW-M-Ycn9QSGzyyIMXIjtAsz5K4JxrdOEyYGvNUAGuoo9v7mFN_61VhGsf9nEpBS5AkMd87yWVdrpQhlL8jF2MhSINjv1dhdbFzTNf0kHgCyUqpq86a2kuAyuFCLyqBK6XJgmKae1mEkcgkM2y_ly9bimjAzxh1a_NzdDTTnmd-tnUhrgL9Hzzn7igZ_un-EZjWwSrWnhgVqBM96Vg6qhPfP9rTEfoSm1uR_6HcqyzEeO_A8nJsbVWaohfqUikS1LcZ9xw9NNL5U3T5Dr8OfVn0MVzRDD0z3YkalozO1W2xlEzBHTPC5WnsVMnmqNnohhjFq2r_ZVGw._2lcMJh4KqXrPdAi.WXM6TUEB0cWgzBxaxdbNM2lh2MCG1jTrnwhjWv6I4fUdHaOHoij1tzA1N54qPGnkwFCAIX0IQNgrWxvIjkFuvOtuqWzOJGxS2mXE9KjPh5LX7n014mUml47YojGvSKMlx0uFdC-q5U33CP6zFQ5uanqhtN9b-XaJwMFZ13i23b8bcoZecCzs5wlN8KpRL4BiLHYjjfXg58SmFnCr1Phznii_vi1bwC5wENf-wCtazn5VJABSH1Ak-TsHPGnChHhMXqF2iorln70abngsg-mEqQgofJxAVMdtT4YW37HmlcAA3XRXzznQG7dUPc9Mg49ofm8es6aF4irAZvyKwiIIkc66IXjXBA7m5emwFgiIS7qsscBA8HPmNUMh0aWWw5K_iEthxcRwbpPd2J_4Zs7fTxXXdEyguDbKYuIQrqh17717P_bLWCc39GlRwFjjW3PR22NxdXVdgmxZzHCI6F_THc6Y8c8yDDjH3sj9axykWo7cc8OL3nuhqRSaRDM4g6l5U9EATiENtgVEK31u8BR6JknWGywx56T65kg47Ii15QBgvo8k_15aBwQKxAj_4gS9JMF2cF083jEAh6D4s7D_HWUAlSmWnE1eNnGt0VYvKqN8H3ic1ydwgzdKcxbhIqiobciC2FbZljEgu5-7O2ImDLzIsACVtNMBExvQ4gv4muM-HpFkDDp4rFyDgOB-PrFoqtrS4v2J_vq1QtgnNYbIDypmT9Qfd4WS71L3Gx1nKaVcgaV3cL_lceoE42jWCZATrzDuBgsP7A.vwMetYBhzZDH276er4abeg

and paste:

eyJraWQiOiJHS2R2ZTVaVXEtNjBlRVpsTHRINHpiR3JfY1JoU05mWEJXVDZBYUtKTUlvIiwidmVyIjoiMS4wIiwiemlwIjoiRGVmbGF0ZSIsInNlciI6IjEuMCJ9.m7CzEYCqRZspW-M-Ycn9QSGzyyIMXIjtAsz5K4JxrdOEyYGvNUAGuoo9v7mFN_61VhGsf9nEpBS5AkMd87yWVdrpQhlL8jF2MhSINjv1dhdbFzTNf0kHgCyUqpq86a2kuAyuFCLyqBK6XJgmKae1mEkcgkM2y_ly9bimjAzxh1a_NzdDTTnmd-tnUhrgL9Hzzn7igZ_un-EZjWwSrWnhgVqBM96Vg6qhPfP9rTEfoSm1uR_6HcqyzEeO_A8nJsbVWaohfqUikS1LcZ9xw9NNL5U3T5Dr8OfVn0MVzRDD0z3YkalozO1W2xlEzBHTPC5WnsVMnmqNnohhjFq2r_ZVGw._2lcMJh4KqXrPdAi.WXM6TUEB0cWgzBxaxdbNM2lh2MCG1jTrnwhjWv6I4fUdHaOHoij1tzA1N54qPGnkwFCAIX0IQNgrWxvIjkFuvOtuqWzOJGxS2mXE9KjPh5LX7n014mUml47YojGvSKMlx0uFdC-q5U33CP6zFQ5uanqhtN9b-XaJwMFZ13i23b8bcoZecCzs5wlN8KpRL4BiLHYjjfXg58SmFnCr1Phznii_vi1bwC5wENf-wCtazn5VJABSH1Ak-TsHPGnChHhMXqF2iorln70abngsg-mEqQgofJxAVMdtT4YW37HmlcAA3XRXzznQG7dUPc9Mg49ofm8es6aF4irAZvyKwiIIkc66IXjXBA7m5emwFgiIS7qsscBA8HPmNUMh0aWWw5K_iEthxcRwbpPd2J_4Zs7fTxXXdEyguDbKYuIQrqh17717P_bLWCc39GlRwFjjW3PR22NxdXVdgmxZzHCI6F_THc6Y8c8yDDjH3sj9axykWo7cc8OL3nuhqRSaRDM4g6l5U9EATiENtgVEK31u8BR6JknWGywx56T65kg47Ii15QBgvo8k_15aBwQKxAj_4gS9JMF2cF083jEAh6D4s7D_HWUAlSmWnE1eNnGt0VYvKqN8H3ic1ydwgzdKcxbhIqiobciC2FbZljEgu5-7O2ImDLzIsACVtNMBExvQ4gv4muM-HpFkDDp4rFyDgOB-PrFoqtrS4v2J_vq1QtgnNYbIDypmT9Qfd4WS71L3Gx1nKaVcgaV3cL_lceoE42jWCZATrzDuBgsP7A.vwMetYBhzZDH276er4abeg

into the config setup but it says token is invalid. I've tried both Canada and USA...

Use a different browser. Only Chrome works to get the proper token. Any token copied from Firefox will not work.

danielbrunt57 · 2025-01-06T10:54:13Z

I first used Edge but then tried Chrome (same token). I also tried modifying the login URL (using Chrome) to https://login.ford.ca/4566605f-43a7-400a-946e-89cc9fdb0bd7/B2C_1A_SignInSignUp_en-CA/oauth2/v2.0/authorize?redirect_uri=fordapp://userauthorized&response_type=code&max_age=3600&code_challenge=HGgDcduf9KYkhqCDkwE3x29ZhamwUcDMTeRx3zmZNx4&code_challenge_method=S256&scope=%2009852200-05fd-41f6-8c21-d36d3497dc64%20openid&client_id=09852200-05fd-41f6-8c21-d36d3497dc64&ui_locales=en-CA&language_code=en-CA&country_code=CAN&ford_application_id=71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592 and got a different token but still does not work.

danielbrunt57 · 2025-01-06T10:57:34Z

Note: it was working a while ago but then I started getting something like invalid token (I think) so I deleted everything but am retrying it again now...

jonepet · 2025-01-06T11:02:07Z

I've installed 1.68 via HACS, deleted custom_components/fordpass/, downloaded v1.70.zip and copied its custom_components/fordpass to my config/custom_components/, restarted HA, verified manifest.json says "version": "0.1.70", then went about installing the integration. I get the URL to open to login, log in and locate the header:
fordapp://userauthorized/?code=
and paste:
into the config setup but it says token is invalid. I've tried both Canada and USA...
Use a different browser. Only Chrome works to get the proper token. Any token copied from Firefox will not work.

Please do not paste this URL in public. It contains a one-time code giving unlimited access to your account without a password.

You are supposed to paste the full URL, not just the code. Last time I logged in it worked on login.ford.com.

danielbrunt57 · 2025-01-06T11:06:09Z

Please do not paste this URL in public. It contains a one-time code giving unlimited access to your account without a password.

No worries! I've been IT tech support for 35+ years and am not that naive. I modified the token characters in a couple of places before posting it!

You are supposed to paste the full URL, not just the code. Last time I logged in it worked on login.ford.com.

Thanks, I'll try the full fordapp:// URL...

danielbrunt57 · 2025-01-06T11:09:08Z

That worked!

danielbrunt57 · 2025-01-06T11:12:32Z

I've set the polling interval to 3600 (once per hour)

djlevin · 2025-01-07T02:35:20Z

So I followed the instructions, and my location header token URL doesn't start with fordapp:// it starts with https://www.account.ford.com/etc/...

Anyone done this recently? Does this look familiar at all?

djlevin · 2025-01-07T06:43:48Z

Ok, that happens when instead of reading carefully, cutting the URL from the first line in the HA config dialog, and pasting that into your browser, you just navigate to fordpass.com and try to do the rest. If you do go to the URL provided by HA, as directed, then the rest is easy and works.

itchannel pinned this issue May 7, 2024

frankie-boy-hgv mentioned this issue May 8, 2024

Authentication error after HA Update #489

Closed

TheLizard mentioned this issue Oct 11, 2024

How do we install the 1.70 version in HACS? #540

Closed

This was referenced Jan 9, 2025

Device tracker is no longer working as HA have changed the way they handle their "async_forward_entry_setup" calls in 2025.1 #556

Closed

Can't install V1.70 #557

Open

Can't login: 403 Client Error: Forbidden for url: https://login.ford.com #488

Can't login: 403 Client Error: Forbidden for url: https://login.ford.com #488

Comments

frankie-boy-hgv commented May 7, 2024

JVTEAM commented May 7, 2024

frankie-boy-hgv commented May 7, 2024

JVTEAM commented May 7, 2024

keller1982 commented May 7, 2024

400HPMustang commented May 7, 2024

JanosBerke commented May 7, 2024

D0NY3NK0 commented May 7, 2024

AndreiGavriliu commented May 7, 2024

Picard16 commented May 7, 2024 • edited Loading

EnDoubleU commented May 7, 2024 • edited Loading

AlanJ500 commented May 7, 2024

clabern commented May 7, 2024

0sAND1s commented May 7, 2024 • edited Loading

alessandro1898 commented May 7, 2024

bmwhitetx commented May 7, 2024

dizzybro commented May 7, 2024

itchannel commented May 7, 2024

domolys commented May 8, 2024

scotty1395 commented May 8, 2024

frankie-boy-hgv commented May 8, 2024

0sAND1s commented May 8, 2024

itchannel commented May 8, 2024

AlanJ500 commented May 8, 2024

ve6rah commented May 8, 2024

AlanJ500 commented May 8, 2024

mclever commented May 8, 2024

400HPMustang commented May 8, 2024

ve6rah commented May 8, 2024

Dangeryeen commented Sep 27, 2024

ve6rah commented Nov 27, 2024

benk016 commented Nov 27, 2024

ve6rah commented Nov 27, 2024

itchannel commented Nov 27, 2024

ve6rah commented Nov 27, 2024

ve6rah commented Nov 27, 2024

mojomojoman commented Nov 28, 2024 via email

patrickvorgers commented Nov 28, 2024

ve6rah commented Nov 28, 2024

ve6rah commented Nov 28, 2024

doczong commented Dec 3, 2024 • edited Loading

advisorgee commented Dec 31, 2024

benk016 commented Dec 31, 2024

advisorgee commented Jan 4, 2025

danielbrunt57 commented Jan 6, 2025 • edited Loading

ve6rah commented Jan 6, 2025

danielbrunt57 commented Jan 6, 2025 • edited Loading

ve6rah commented Jan 6, 2025

danielbrunt57 commented Jan 6, 2025 • edited Loading

danielbrunt57 commented Jan 6, 2025

jonepet commented Jan 6, 2025

danielbrunt57 commented Jan 6, 2025

danielbrunt57 commented Jan 6, 2025

danielbrunt57 commented Jan 6, 2025

djlevin commented Jan 7, 2025

djlevin commented Jan 7, 2025

Picard16 commented May 7, 2024 •

edited

Loading

EnDoubleU commented May 7, 2024 •

edited

Loading

0sAND1s commented May 7, 2024 •

edited

Loading

doczong commented Dec 3, 2024 •

edited

Loading

danielbrunt57 commented Jan 6, 2025 •

edited

Loading

danielbrunt57 commented Jan 6, 2025 •

edited

Loading

danielbrunt57 commented Jan 6, 2025 •

edited

Loading