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

mojomojoman · 2024-05-31T06:01:35Z

I'm getting a 403 when I try to login using the URL from Home Assistant. I am in Canada and using the latest commit in the 1.70 branch:

That is the problem a lot of us in North America have been having. Seems to be less of an issue overseas. I eventually got it to work but I'm not entirely sure what the secret sauce was or if it was just luck. If you want to try what I did then see my previous post HERE.

NOTE: Ignore the part of that post about my sensors being messed up as you'll see in a subsequent post that itchannel fixed that by updating the sensor.py in the 1.70 code and then all my sensor issues were fine.

In that post I did not specify what I modified in fordpass_new.py but it was this block of code at line 37:

region_lookup = {
    "UK&Europe": "1E8C7794-FF5F-49BC-9596-A1E0C86C5B19",
    "Australia": "5C80A6BB-CF0D-4A30-BDBF-FC804B5C1A98",
    "USA": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592",
    "Canada": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592"
}

I just did that so it lined up with const.py changes I made that were recommended by the previous poster I quoted.

Again, I have no idea if it was those code changes, or my changing my edge dev mode to emulate a mobile device or if it was sheer dumb luck that it worked that particular time. Sorry I wasn't more scientific and methodical with my changes. It could also just be the fact that I'd had the integration disabled for a few days before I tried again (maybe I was soft banned from when it was failing/retrying over and over.)

It seems they are using akamai and/or azure front door and probably web application firewalls now to screen incoming traffic. It's unclear if they are actively trying to block these kinds of 3rd party things or what but such abuse filtering/DDOS mitigation systems can be very touchy and picky about what traffic they accept from where and the user-agent strings and url formulations that they expect to see or the number of requests, etc. It might be very subtle changes that make it work. Overall though unless they make drastic changes to their mobile app it's just a matter of all of us figuring out the secret sauce since most mobile apps just use embedded mobile browser windows to do the logins and get OAUTH tokens so ultimately it should be pretty difficult for them to block it entirely. I think it'll take a lot of users in the trouble regions testing and reporting back as to what they changed to get it working before the devs can be sure what specifically that secret sauce is. All that while there's no guarantee that Ford isn't also making constant changes on their end.

danielbrunt57 · 2024-05-31T08:39:32Z

@serlinGi

I don't understand if I'm doing the right thing and if soon everything will stop again; I'm still using version 1.68 with the addition of the fordpass_new.py file for 1 week, with the old token files and everything works wonderfully. Do you think it's worth updating anyway? will there be new sensors?

If it ain't broke don't touch it!

danielbrunt57 · 2024-05-31T08:53:52Z

@dcshoes23

I'm getting a 403 when I try to login using the URL from Home Assistant. I am in Canada and using the latest commit in the 1.70 branch:

I'm in Canada also and I managed to get it to work with the following edits:
const.py

REGION_OPTIONS = ["UK&Europe", "Australia", "USA", "Canada"]
.
.
.
REGIONS = {
    "UK&Europe": {
        "region": "1E8C7794-FF5F-49BC-9596-A1E0C86C5B19",
        "locale": "EN-IE",
        "locale_short": "IE", #Temp fix 
        "locale_url": "https://login.ford.ie"
    },
    "Australia": {
        "region": "5C80A6BB-CF0D-4A30-BDBF-FC804B5C1A98",
        "locale": "EN-AU",
        "locale_short": "AUS",
        "locale_url": "https://login.ford.com.au"
    },
    "USA": {
        "region": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592", # ???
        "locale": "en-US",
        "locale_short": "USA",
        "locale_url": "https://login.ford.com" # ??? 
    },
    "Canada": {
        "region": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592",
        "locale": "en-CA",
        "locale_short": "CAN",
        "locale_url": "https://login.ford.com"
    }
}

In theory, "locale_url": "https://login.ford.ca" should work for us but .com worked for me when I tried it first.

fordpass_new.py (lines 37-42)

region_lookup = {
    "UK&Europe": "1E8C7794-FF5F-49BC-9596-A1E0C86C5B19",
    "Australia": "5C80A6BB-CF0D-4A30-BDBF-FC804B5C1A98",
    "Canada": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592",
    "USA": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592",
}

I downloaded the zip file for 1.70, extracted it, copied the fordpass folder into /config/custom_components/ (replace=yes), edited as above, restarted HA and then followed https://github.com/itchannel/fordpass-ha/wiki/Obtaining-Tokens-(As-of-25-05-2024) to get the magic fordapp://... token URL to enter when setting up the integration.

doronazl · 2024-05-31T11:27:24Z

what do i do if the link provided by the integration isnt a valid link ?
it sending me to login.ford.com.au which asks for email and password
here in thailand we use the phone number to login, not email

TerrorSource · 2024-05-31T15:22:44Z

I'm getting a 403 when I try to login using the URL from Home Assistant. I am in Canada and using the latest commit in the 1.70 branch:

That is the problem a lot of us in North America have been having. Seems to be less of an issue overseas. I eventually got it to work but I'm not entirely sure what the secret sauce was or if it was just luck. If you want to try what I did then see my previous post HERE.

NOTE: Ignore the part of that post about my sensors being messed up as you'll see in a subsequent post that itchannel fixed that by updating the sensor.py in the 1.70 code and then all my sensor issues were fine.

In that post I did not specify what I modified in fordpass_new.py but it was this block of code at line 37:
region_lookup = {
    "UK&Europe": "1E8C7794-FF5F-49BC-9596-A1E0C86C5B19",
    "Australia": "5C80A6BB-CF0D-4A30-BDBF-FC804B5C1A98",
    "USA": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592",
    "Canada": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592"
}
I just did that so it lined up with const.py changes I made that were recommended by the previous poster I quoted.

Again, I have no idea if it was those code changes, or my changing my edge dev mode to emulate a mobile device or if it was sheer dumb luck that it worked that particular time. Sorry I wasn't more scientific and methodical with my changes. It could also just be the fact that I'd had the integration disabled for a few days before I tried again (maybe I was soft banned from when it was failing/retrying over and over.)

It seems they are using akamai and/or azure front door and probably web application firewalls now to screen incoming traffic. It's unclear if they are actively trying to block these kinds of 3rd party things or what but such abuse filtering/DDOS mitigation systems can be very touchy and picky about what traffic they accept from where and the user-agent strings and url formulations that they expect to see or the number of requests, etc. It might be very subtle changes that make it work. Overall though unless they make drastic changes to their mobile app it's just a matter of all of us figuring out the secret sauce since most mobile apps just use embedded mobile browser windows to do the logins and get OAUTH tokens so ultimately it should be pretty difficult for them to block it entirely. I think it'll take a lot of users in the trouble regions testing and reporting back as to what they changed to get it working before the devs can be sure what specifically that secret sauce is. All that while there's no guarantee that Ford isn't also making constant changes on their end.

how did you get the region_lookup id's for that regions/countries?
Im from NL (Europe) but the plugin only uses IE (Ireland) for login, i want to try with the NL one.

SquidBytes · 2024-05-31T15:36:33Z

Just to clarify.
1.70 is, I believe, the planned next release - which will incorporate the new login flow.
It is still a work in progress and the reason some people are using it was to help @itchannel test.
@itchannel has been doing the heavy lifting with getting the login flow working, which will hopefully future proof this a bit.
I'm hoping to add in the FordConnect API to people who can take it advantage of it (not sure if this will be in 1.70 release at all)
But again, we both have limited time to contribute and manage things.

However, If 1.68 is currently working for you its recommend staying on it for now.
It seems like this initial issue has been resolved, and currently this is just the massive thread of people trying 1.70.

I'm going to open a new "issue" related to 1.70 specifically and provided its okay, probably close this one.
I've been trying to clear up the issues and I'm hoping upon 1.70 release essentially start with 0 issues for easier tracking.

michalk-k · 2024-05-31T16:13:57Z

Not sure what do you mean by this:

However, If 1.68 is currently working for you its recommend staying on it for now. It seems like this initial issue has been resolved (...)

I'm on v1.68 and the most recent data the integration has retrieved from Ford servers is from 23th May.
I'm patiently waiting for some update, but maybe I'm missing something

SquidBytes · 2024-05-31T16:54:47Z

Okay, I think I got confused. There was this comment on the fordpass_new.py for 1.69, which may have fixed this 1.68 issue.
So when I said

However, If 1.68 is currently working for you its recommend staying on it for now. It seems like this initial issue has been resolved (...)

I was really meaning 1.68 with modified fordpass_new from 1.69.

You just need to ensure you copy your token file prior to restarting HA.

dcshoes23 · 2024-05-31T19:49:01Z

@dcshoes23

I'm getting a 403 when I try to login using the URL from Home Assistant. I am in Canada and using the latest commit in the 1.70 branch:

I'm in Canada also and I managed to get it to work with the following edits: const.py
REGION_OPTIONS = ["UK&Europe", "Australia", "USA", "Canada"]
.
.
.
REGIONS = {
    "UK&Europe": {
        "region": "1E8C7794-FF5F-49BC-9596-A1E0C86C5B19",
        "locale": "EN-IE",
        "locale_short": "IE", #Temp fix 
        "locale_url": "https://login.ford.ie"
    },
    "Australia": {
        "region": "5C80A6BB-CF0D-4A30-BDBF-FC804B5C1A98",
        "locale": "EN-AU",
        "locale_short": "AUS",
        "locale_url": "https://login.ford.com.au"
    },
    "USA": {
        "region": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592", # ???
        "locale": "en-US",
        "locale_short": "USA",
        "locale_url": "https://login.ford.com" # ??? 
    },
    "Canada": {
        "region": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592",
        "locale": "en-CA",
        "locale_short": "CAN",
        "locale_url": "https://login.ford.com"
    }
}
In theory, "locale_url": "https://login.ford.ca" should work for us but .com worked for me when I tried it first.

fordpass_new.py (lines 37-42)
region_lookup = {
    "UK&Europe": "1E8C7794-FF5F-49BC-9596-A1E0C86C5B19",
    "Australia": "5C80A6BB-CF0D-4A30-BDBF-FC804B5C1A98",
    "Canada": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592",
    "USA": "71A3AD0A-CF46-4CCF-B473-FC7FE5BC4592",
}
I downloaded the zip file for 1.70, extracted it, copied the fordpass folder into /config/custom_components/ (replace=yes), edited as above, restarted HA and then followed https://github.com/itchannel/fordpass-ha/wiki/Obtaining-Tokens-(As-of-25-05-2024) to get the magic fordapp://... token URL to enter when setting up the integration.

Thanks, I made those changes, still had the same error using Brave browser. I then tried an incognito Chrome window and it worked!

michalk-k · 2024-05-31T21:27:48Z

I was really meaning 1.68 with modified fordpass_new from 1.69.

You just need to ensure you copy your token file prior to restarting HA.

Thank you.
I just did that. After HA restart it connected to Ford servers, and updated sensors to values valid at the time I went back home (about 8 hours ago). What is strange because the most recent records in HA logs show error communication with FordPass(...)Returning stale data... message. Also the refresh service doesn't work (while it doesn't show any error)

Edit: After further attempts to send service call, it refreshed car data.

sznandi77 · 2024-06-02T07:44:10Z

Hello!

The European login (IE), does not work from Hungary

in 1.70:

Hungary local:

Regions in const.py

"Hungary": {
"region": "4566605f-43a7-400a-946e-89cc9fdb0bd7",
"locale": "hu-HU",
"locale_short": "Hu", #Temp fix
"locale_url": "https://login.ford.hu"
},

in fordpass_new.py :

region_lookup = {

"Hungary": "4566605f-43a7-400a-946e-89cc9fdb0bd7",

elif self.region2 == "Hungary":
countryheader = "HUN"

At the moment, I've made it this far, but after copying the returned token: unknown error

I'll try to find out the reason as time permits!

michaeltryl · 2024-06-02T07:51:33Z

Hello!

The European login (IE), does not work from Hungary

in 1.70:

Hungary local:

Regions in const.py

"Hungary": { "region": "4566605f-43a7-400a-946e-89cc9fdb0bd7", "locale": "hu-HU", "locale_short": "Hu", #Temp fix "locale_url": "https://login.ford.hu" },

in fordpass_new.py :

region_lookup = {
"Hungary": "4566605f-43a7-400a-946e-89cc9fdb0bd7",
elif self.region2 == "Hungary": countryheader = "HUN"

At the moment, I've made it this far, but after copying the returned token: unknown error

I'll try to find out the reason as time permits!

You have to right click on the token and copy it.
Its is very long, so you cant see it all :)

sznandi77 · 2024-06-02T08:02:06Z

Hello!

I copied,token character chain, and paste to home assistant ford integration login page, and after click on the next button, the integrations answer unknow error.

BluThunder2k · 2024-06-06T20:56:31Z

Tried this on a US login and still get an error....

danktankk · 2024-06-08T12:49:50Z

Cant login either, US server

nexusis7 · 2024-06-11T14:14:23Z

is this plugin dead?

nytram-md · 2024-06-11T14:17:21Z

No, not when you use the workaround. All good since Thanks Martyn

…

________________________________ From: nexusis7 ***@***.***> Sent: Tuesday, June 11, 2024 5:14:54 PM To: itchannel/fordpass-ha ***@***.***> Cc: nytram-md ***@***.***>; Comment ***@***.***> Subject: Re: [itchannel/fordpass-ha] Can't login: 403 Client Error: Forbidden for url: https://login.ford.com (Issue #488) is this plugin dead? — Reply to this email directly, view it on GitHub<#488 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANHZVQETOTZ6KVBUSHLSS2LZG4A55AVCNFSM6AAAAABHLB227CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRQHA3TQNJYGI>. You are receiving this because you commented.Message ID: ***@***.***>

nexusis7 · 2024-06-11T14:19:17Z

No, not when you use the workaround. All good since Thanks Martyn
…

which workaround? can you provide the one that works please. i edited the const.py and newpass file, it didnt do the trick

pdecker414 · 2024-06-11T19:10:55Z

No, not when you use the workaround. All good since Thanks Martyn
…

which workaround? can you provide the one that works please. i edited the const.py and newpass file, it didnt do the trick
Try looking here. I followed the information and got mine working in NA
#509

nytram-md · 2024-06-11T19:41:35Z

I followed upgraded to 1.70 further up and then logged in at ford.com website and got the key from developer tab as per instructions 👍 Thanks Martyn

…

________________________________ From: pdecker414 ***@***.***> Sent: Tuesday, June 11, 2024 10:11:29 PM To: itchannel/fordpass-ha ***@***.***> Cc: nytram-md ***@***.***>; Comment ***@***.***> Subject: Re: [itchannel/fordpass-ha] Can't login: 403 Client Error: Forbidden for url: https://login.ford.com (Issue #488) No, not when you use the workaround. All good since Thanks Martyn … which workaround? can you provide the one that works please. i edited the const.py and newpass file, it didnt do the trick Try looking here. I followed the information and got mine working in NA #509<#509> — Reply to this email directly, view it on GitHub<#488 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANHZVQHGSODXBS46DK425ULZG5DWDAVCNFSM6AAAAABHLB227CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRRGQZTONZRGU>. You are receiving this because you commented.Message ID: ***@***.***>

BluThunder2k · 2024-06-11T20:01:25Z

No, not when you use the workaround. All good since Thanks Martyn
…
________________________________ From: nexusis7 @.> Sent: Tuesday, June 11, 2024 5:14:54 PM To: itchannel/fordpass-ha @.> Cc: nytram-md @.>; Comment @.> Subject: Re: [itchannel/fordpass-ha] Can't login: 403 Client Error: Forbidden for url: https://login.ford.com (Issue #488) is this plugin dead? — Reply to this email directly, view it on GitHub<#488 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANHZVQETOTZ6KVBUSHLSS2LZG4A55AVCNFSM6AAAAABHLB227CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRQHA3TQNJYGI. You are receiving this because you commented.Message ID: @.***>

I've tried the work around - are you talking the one with modifying the py file?

Also are you US?

pdecker414 · 2024-06-11T22:08:01Z

No, not when you use the workaround. All good since Thanks Martyn
…
________________________________ From: nexusis7 @.> Sent: Tuesday, June 11, 2024 5:14:54 PM To: itchannel/fordpass-ha _@**._> Cc: nytram-md _@.>; Comment @._> Subject: Re: [itchannel/fordpass-ha] Can't login: 403 Client Error: Forbidden for url: https://login.ford.com (Issue #488) is this plugin dead? — Reply to this email directly, view it on GitHub<#488 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANHZVQETOTZ6KVBUSHLSS2LZG4A55AVCNFSM6AAAAABHLB227CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRQHA3TQNJYGI. You are receiving this because you commented.Message ID: _@_.*>

I've tried the work around - are you talking the one with modifying the py file?

Also are you US?

I am in US and followed the instructions. Be sure you follow everything and you will need to get more files than just the py file. I pretty much got all 1.70 files and replaced ones I had on my system. Then followed instructions at listed above.

navarrolux · 2024-06-19T14:29:47Z

Hi all. I followed the process to install 1.70.
It is working great.
I am based in the US

JVTEAM · 2024-06-19T14:33:06Z

Is there a timeframe on pushing a non-workaround version to HACS? Just weighing whether I make the effort or not.

LarsTh86 · 2024-06-19T16:27:30Z

I tried more then one time. But the workaround doesn’t work for me in Germany. Also the provided URL doesn’t load.
For that reason, I am also interested in Version without workaround or a workaround which work.

SquidBytes · 2024-06-21T14:43:30Z

I haven't had any time to look into, update, or respond to anything, and I'm sure itchannel is also very busy.
I just got back from vacation, and I am very busy with work, home, and life things. I still plan on working on this and hopefully improving things where I can.

However, please keep in mind we are both working on this for free and in our, very limited, spare time.

JVTEAM · 2024-06-21T15:02:18Z

I haven't had any time to look into, update, or respond to anything, and I'm sure itchannel is also very busy. I just got back from vacation, and I am very busy with work, home, and life things. I still plan on working on this and hopefully improving things where I can.

However, please keep in mind we are both working on this for free and in our, very limited, spare time.

Not complaining at all. In awe of the work everyone does on this project. I was just asking if there was a general idea of when it might be done. 1 month, 6 months, a year?

BluThunder2k · 2024-06-23T17:10:28Z

So I decided to try this again. I removed the integration, rebooted, installed again from HACS with 1.68 and then unzipped the files from 1.70 overwriting everything. Went and added fordpass, picked US and followed the instructions again for gettign the token. It worked this time. Not sure if something on Ford's end changed from a few weeks back, but it sure didn't work before. If you've had failures before, try again, the procedure works for this US user.

itchannel pinned this issue May 7, 2024

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

Authentication error after HA Update #489

Closed

SquidBytes mentioned this issue May 31, 2024

Getting error showing truck image #480

Closed

mlewanca mentioned this issue Jun 6, 2024

1.70 Tests #509

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

EnDoubleU commented May 7, 2024 • edited

AlanJ500 commented May 7, 2024

clabern commented May 7, 2024

0sAND1s commented May 7, 2024 • edited

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

mojomojoman commented May 31, 2024 • edited

danielbrunt57 commented May 31, 2024 • edited

danielbrunt57 commented May 31, 2024 • edited

doronazl commented May 31, 2024

TerrorSource commented May 31, 2024

SquidBytes commented May 31, 2024 • edited

michalk-k commented May 31, 2024

SquidBytes commented May 31, 2024 • edited

dcshoes23 commented May 31, 2024

michalk-k commented May 31, 2024 • edited

sznandi77 commented Jun 2, 2024 • edited

michaeltryl commented Jun 2, 2024

sznandi77 commented Jun 2, 2024

BluThunder2k commented Jun 6, 2024

danktankk commented Jun 8, 2024

nexusis7 commented Jun 11, 2024

nytram-md commented Jun 11, 2024 via email

nexusis7 commented Jun 11, 2024 • edited

pdecker414 commented Jun 11, 2024 • edited

nytram-md commented Jun 11, 2024 via email

BluThunder2k commented Jun 11, 2024 • edited

pdecker414 commented Jun 11, 2024

navarrolux commented Jun 19, 2024 • edited

JVTEAM commented Jun 19, 2024

LarsTh86 commented Jun 19, 2024

SquidBytes commented Jun 21, 2024

JVTEAM commented Jun 21, 2024

BluThunder2k commented Jun 23, 2024

Picard16 commented May 7, 2024 •

edited

EnDoubleU commented May 7, 2024 •

edited

0sAND1s commented May 7, 2024 •

edited

mojomojoman commented May 31, 2024 •

edited

danielbrunt57 commented May 31, 2024 •

edited

danielbrunt57 commented May 31, 2024 •

edited

SquidBytes commented May 31, 2024 •

edited

SquidBytes commented May 31, 2024 •

edited

michalk-k commented May 31, 2024 •

edited

sznandi77 commented Jun 2, 2024 •

edited

nexusis7 commented Jun 11, 2024 •

edited

pdecker414 commented Jun 11, 2024 •

edited

BluThunder2k commented Jun 11, 2024 •

edited

navarrolux commented Jun 19, 2024 •

edited