Comments (315)
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 :)
from fordpass-ha.
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.
from fordpass-ha.
@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.
from fordpass-ha.
I've done some testing and it looks like as a few people have worked out that only added security measures have been enabled for "login.ford.com" and not for local endpoints i.e. "login.ford.ie" so I can roll out a temporary fix for those users so it uses the correct endpoint depending on your region set in HA.
Long term I'd love to properly implement the new Ford API that has now been publically released, I do have an account and oauth codes. However anything I do results in 500 errors which makes me think it is still restricted to USA members only. I am working with @SquidBytes and hope to have a more permanent fix soon.
from fordpass-ha.
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.
from fordpass-ha.
Did the same in Denmark. Changed the url to login.ford.dk and lang to DA-DK. Integration now works again.
Can you tell me exactly what you did? I assume edit /custom_components/fordpass/fordpass_new.py and change FORD_LOGIN_URL = "https://login.ford.com"? Anything else?
Thanks :)
fordpass_new.py
L46: "UK&Europe": "DA-DK",
L50: "UK&Europe": "DNK",
L63: FORD_LOGIN_URL = "https://login.ford.dk"
Also change following, not sure if needed:
L151: "Origin": "https://login.ford.dk",
L267: url1 = f"https://login.ford.dk/ *****************
from fordpass-ha.
Do any of these workarounds work for people in the US?
from fordpass-ha.
Pushed a Beta version that just changes the login endpoint to use an alternative one for now. This is only as temporary measure and have reached out to Ford about potentially supporting their new official API. However region restrictions and limited functionality for now it seems.
from fordpass-ha.
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
from fordpass-ha.
@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.How do you know they've been trying to reach out? Do you have a point of contact?
I do, I cant say how I know due to an NDA but just that they have. I do have a point of contact however I would rather not post it in here for all to see. I can DM it.
My email & discord are on my profile. I'll also pass along to itchannel
from fordpass-ha.
Hi,
It is the same here, Ford must have changed something.
from fordpass-ha.
Same here in Germany with my Kuga.
Last successful sync was yesterday, 2024-05-06, at 16:20 CEST Europe.
from fordpass-ha.
For me the integration started working again if I change all the variables related to locale and the ford_application_id parameter to the same as in the URL provided by ford website (in my language).
The integration seems to be mixing australia and GB and US when used in EU&Europe mode. In my case replaced AUS => NOR, login.ford.com => login.ford.no, en-GB => nb-NO, 5C80A6BB-CF0D-4A30-BDBF-FC804B5C1A98 => 260ea066-aa5e-4344-995d-b8a3d7dd0fca
Maybe the issue is about each country having their own settings?
from fordpass-ha.
Thanks @kernest - worked a treat after a restart :) Didn't test start/lock/unlock but all the sensors are there and updated :)
from fordpass-ha.
Waiting for a USA fix as well. Attempting to change the short code, and control codes don't resolve the issue like in the other countries.
from fordpass-ha.
Has anyone else got this working in the UK? If so, what changes did you make to your
fordpass_new.py
file? Thanks
I have this working with the previously mentioned changes as per the below. i fully rebooted the HA and it came straight back online.
44 "UK&Europe": "EN-IE",
50 "UK&Europe": "IE",
63 FORD_LOGIN_URL = "https://login.ford.ie"
from fordpass-ha.
from fordpass-ha.
Same issue here.
Can confirm that login now works with 1.68 Beta. I am situated in Croatia.
from fordpass-ha.
Just switched to beta and it seems to be functioning for me now (US based) as well.
Still seems like moving to new FordPass Connect API is best option and Ford "approved".
from fordpass-ha.
Same issue here. Thought it was because I upgrade the Core, but it seems just bad timing.
from fordpass-ha.
Same here, right after updating to 2024.5.2 (from 2024.5.1)
from fordpass-ha.
Same here, right after updating to 2024.5.2 (from 2024.5.1)
Ok, so it is core related.
from fordpass-ha.
Seems like it.
I didn't change the core, I still have 2024.4.2 and I have the same error.
from fordpass-ha.
Same issue on 2024.5.1
from fordpass-ha.
Same issue here.
from fordpass-ha.
Same here. I thought I got banned or something
from fordpass-ha.
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.
from fordpass-ha.
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.
from fordpass-ha.
Same issue here, started around 9:31AM eastern.
from fordpass-ha.
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
from fordpass-ha.
Same issue for me in Italy with a Ford Puma. Can't login.
from fordpass-ha.
Have not updated anything HA related in a month. On Core 2024.4.3. Got this error today. Can't be HA related.
from fordpass-ha.
Same here, can't login as of 5-7-2024
from fordpass-ha.
Still running core 2024.1.6 and having the same issue
from fordpass-ha.
Working again for me in Australia. Entities became available about 90 minutes ago without a HA restart.
from fordpass-ha.
Not working here yet.
from fordpass-ha.
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.
from fordpass-ha.
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.
from fordpass-ha.
^ 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.
from fordpass-ha.
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?
from fordpass-ha.
@jonepet that appears to be a simple change. in my HA instance my integration shows as cloud dependent so not sure I can test that out myself. Any tips there?
from fordpass-ha.
@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.
How do you know they've been trying to reach out?
Do you have a point of contact?
from fordpass-ha.
For me the integration started working again if I change all the variables related to locale and the ford_application_id parameter to the same as in the URL provided by ford website (in my language).
The integration seems to be mixing australia and GB and US when used in EU&Europe mode. In my case replaced AUS => NOR, login.ford.com => login.ford.no, en-GB => nb-NO, 5C80A6BB-CF0D-4A30-BDBF-FC804B5C1A98 => 260ea066-aa5e-4344-995d-b8a3d7dd0fca
Maybe the issue is about each country having their own settings?
Did the same in Denmark.
Changed the url to login.ford.dk and lang to DA-DK.
Integration now works again.
from fordpass-ha.
Did the same in Denmark. Changed the url to login.ford.dk and lang to DA-DK. Integration now works again.
Can you tell me exactly what you did? I assume edit /custom_components/fordpass/fordpass_new.py and change FORD_LOGIN_URL = "https://login.ford.com"? Anything else?
Thanks :)
from fordpass-ha.
L46: "UK&Europe": "DA-DK",
L50: "UK&Europe": "DNK",
L63: FORD_LOGIN_URL = "https://login.ford.dk"
Thank you @kernest ist works also in Germany with this changes in the fordpass_new.py:
L46: "UK&Europe": "DE-DE",
L50: "UK&Europe": "DE",
L63: FORD_LOGIN_URL = "https://login.ford.de"
the other lines in don´t change. And with this changes I can login und the sensors are back.
from fordpass-ha.
Did the same in Denmark. Changed the url to login.ford.dk and lang to DA-DK. Integration now works again.
Can you tell me exactly what you did? I assume edit /custom_components/fordpass/fordpass_new.py and change FORD_LOGIN_URL = "https://login.ford.com"? Anything else?
Thanks :)fordpass_new.py
L46: "UK&Europe": "DA-DK", L50: "UK&Europe": "DNK", L63: FORD_LOGIN_URL = "https://login.ford.dk"
Also change following, not sure if needed: L151: "Origin": "https://login.ford.dk", L267: url1 = f"https://login.ford.dk/ *****************
Works with Dutch settings! Awesome, thnx!
NL-NL
NL
login.ford.nl
I changed all 5 lines.
from fordpass-ha.
@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.How do you know they've been trying to reach out? Do you have a point of contact?
I do, I cant say how I know due to an NDA but just that they have. I do have a point of contact however I would rather not post it in here for all to see. I can DM it.
from fordpass-ha.
I'd be interested if anyone found an angle on this solution for North America. Most of the references seem correct by default for us. I did find a few EN-AU references in the url strings but replacing them doesn't seem to change anything
from fordpass-ha.
Ok in France too ! FR-FR and login.ford.fr ;)
from fordpass-ha.
Doesn't work for Canada afaict - tried CA as the locale_short_lookup and EN-CA for the locale_lookup as well as login.ford.ca for the FORD_LOGIN_URL. It looks like they haven't rolled this out worldwide - only to North America - so if you redirect yourself to the non-NA endpoints it'll work for you.
from fordpass-ha.
Did the same in Denmark. Changed the url to login.ford.dk and lang to DA-DK. Integration now works again.
Can you tell me exactly what you did? I assume edit /custom_components/fordpass/fordpass_new.py and change FORD_LOGIN_URL = "https://login.ford.com"? Anything else?
Thanks :)fordpass_new.py
L46: "UK&Europe": "DA-DK", L50: "UK&Europe": "DNK", L63: FORD_LOGIN_URL = "https://login.ford.dk"
Also change following, not sure if needed: L151: "Origin": "https://login.ford.dk", L267: url1 = f"https://login.ford.dk/ *****************
Line 267 needs localization everywhere and works after a restart :) Thanks a ton!!!!
from fordpass-ha.
Necessary updates to make it work in Czechia:
locale_lookup = {
"UK&Europe": "cs-CZ",
...
locale_short_lookup = {
"UK&Europe": "CZ",
...
FORD_LOGIN_URL = "https://login.ford.cz"
from fordpass-ha.
The codes should be USA and en-US, but keep in mind there are several places in the fordpass_new.py where the lookup tables are not used, but instead hard codes into the URLs.
I would also suspect the problem could be they have changed the application ID also, as I had to change it too for it to work. It is also possible the application ID for the app and the website is different, but with GDPR it is possible they are removing data sparing between the different regions so this has to be correct to work. The application ID I get on ford.com is not the same as for ford.no.
from fordpass-ha.
Germany: I changed L44: "DE-DE" (not L46 in my file for whatever reason), L50: "DE", L63: "...de", L151: "...de", L267: "...de".
When I tried to add the FordPass integration again (I disabled it after the errors appeared), I got no Login-Error anymore, but I got the error in a popup: "No vehicles on account or all are configured already" and the integration was not activated.
Of course my car is still in the FordPass app on my smartphone.
Thanks in advance for any ideas!
Update 09.05.24 11:00 CEST: Updated to 1.68-Beta
from fordpass-ha.
I highly suspect they made a change to the North America servers that broke this. It only broke for everyone else because of the hard-coded URL's, and fixing that manually is allowing connections again because those systems haven't had the change yet.
from fordpass-ha.
Germany:
L44: "UK&Europe": "DE-DE",
L63: FORD_LOGIN_URL = "https://login.ford.de"
L147: urlp = f"{FORD_LOGIN_URL}/4566605f-43a7-400a-946e-89cc9fdb0bd7/B2C_1A_SignInSignUp_{self.country_code}/SelfAsserted?tx={transId}&p=B2C_1A_SignInSignUp_de-DE"
from fordpass-ha.
for ITALY:
L44: it-IT
L50: IT
L63: https://login.ford.it
for now is OK
Thanks 👍
from fordpass-ha.
for ITALY: L44: it-IT L50: IT L63: https://login.ford.it
for now is OK
Thanks 👍
now I've this warning
This error originated from a custom integration.
Logger: py.warnings
Source: custom_components/fordpass/__init__.py:32
integration: Fordpass (documentation, issues)
First occurred: 21:57:32 (1 occurrences)
Last logged: 21:57:32
/config/custom_components/fordpass/fordpass_new.py:278: SyntaxWarning: invalid escape sequence '\s' ibm_url = re.findall('data-ibm-login-url="(.*)"\s', response.text)[0]
from fordpass-ha.
Has anyone got the changes needed for the UK?
from fordpass-ha.
Has anyone got the changes needed for the UK?
What have you got in "fordpass_new.py" file ?
44 "UK&Europe": "EN-GB",
50 "UK&Europe": "GB",
63 FORD_LOGIN_URL = "https://login.ford.com"
????
from fordpass-ha.
Ireland Working:
44 "EN-IE"
50 "IE"
63 "https://login.ford.ie"
from fordpass-ha.
Exactly as you write it. But no joy with the integration...
from fordpass-ha.
Was wondering if there was a .co.uk alternate that might work?
from fordpass-ha.
Exactly as you write it. But no joy with the integration...
Perhaps try:
from fordpass-ha.
from fordpass-ha.
for SPAIN
L44: es-ES
L50: ES
L63: https://login.ford.es/
Thanks
from fordpass-ha.
So changed to ford.co.uk (two places 63&L51) but still getting error:
Error fetching fordpass data: Error communicating with FordPass for 6FPPXX
from fordpass-ha.
Try GBR instead of GB
from fordpass-ha.
So changed to ford.co.uk (two places 63&L51) but still getting error:
Error fetching fordpass data: Error communicating with FordPass for 6FPPXX
en-GB , not EN-GB
try
from fordpass-ha.
These were there in the original file, I didn't change them; should I?
from fordpass-ha.
Try GBR instead of GB
Still nothing.. Same error..
from fordpass-ha.
These were there in the original file, I didn't change them; should I?
in your link posted the language_code is "en-GB" (for line 44), you already tried?
from fordpass-ha.
Try:
L44 en-GB
L50 GBR
from fordpass-ha.
Try:
L44 en-GB
L50 GBR
Double checked, now have the below, but still same error.
from fordpass-ha.
You reboot homeassistant?
from fordpass-ha.
I've done some testing and it looks like as a few people have worked out that only added security measures have been enabled for "login.ford.com" and not for local endpoints i.e. "login.ford.ie" so I can roll out a temporary fix for those users so it uses the correct endpoint depending on your region set in HA.
Long term I'd love to properly implement the new Ford API that has now been publically released, I do have an account and oauth codes. However anything I do results in 500 errors which makes me think it is still restricted to USA members only. I am working with @SquidBytes and hope to have a more permanent fix soon.
It is restricted to US only at the moment.
from fordpass-ha.
You reboot homeassistant?
Of course, each time making changes. Only thing I've not tried is integration removal and re-installation... Not sure I can find the token and don't fancy going though that again...lol
from fordpass-ha.
and not for local endpoints i.e. "login.ford.ie"
I've tried uk but still no joy...
from fordpass-ha.
Try:
L44 en-GB
L50 GBR
Also change this line from
FORD_LOGIN_URL = "https://login.ford.com"
to
FORD_LOGIN_URL = "https://login.ford.co.uk"
from fordpass-ha.
Also change this line from
from fordpass-ha.
from fordpass-ha.
It's worth changing the Origin header, although might not make a difference.
from fordpass-ha.
might not make a difference
Confirmed, makes no difference. Still not working... 😢
from fordpass-ha.
Has anyone else got this working in the UK? If so, what changes did you make to your fordpass_new.py
file?
Thanks
from fordpass-ha.
I'm in US and got mine to work by setting to Australias settings
Line 46 to
EN-AU
Line 52 to
AUS
Line 63 to
https://login.ford.com.au
from fordpass-ha.
I'm in US and got mine to work by setting to Australias settings
Line 46 to EN-AU
Line 52 to AUS
Line 63 to https://login.ford.com.au
This worked for me, however none of the entities are loading / updating. So Pretty useless at this point.
from fordpass-ha.
I was able to control, but didn't check sensors. I might have changed that other ID too I can check later for sure
Just checked sensors and they refreshed so I must have changed that ID too
from fordpass-ha.
I have this working with the previously mentioned
Hi, just tried this, even though I'm in the UK, and it works. Many thanks. Pete
from fordpass-ha.
Has anyone else got this working in the UK? If so, what changes did you make to your
fordpass_new.py
file? ThanksI have this working with the previously mentioned changes as per the below. i fully rebooted the HA and it came straight back online.
44 "UK&Europe": "EN-IE", 50 "UK&Europe": "IE", 63 FORD_LOGIN_URL = "https://login.ford.ie"
Worked for me as well. Came up straight after a full reboot. Many thanks!!
from fordpass-ha.
Pushed a Beta version that just changes the login endpoint to use an alternative one for now. This is only as temporary measure and have reached out to Ford about potentially supporting their new official API. However region restrictions and limited functionality for now it seems.
Awesome, still working 😀. So no need to add locales for every country?
from fordpass-ha.
Pushed a Beta version that just changes the login endpoint to use an alternative one for now. This is only as temporary measure and have reached out to Ford about potentially supporting their new official API. However region restrictions and limited functionality for now it seems.
Awesome, still working 😀. So no need to add locales for every country?
Not for now. Problem is countries seem to be hit and miss which got the new security enabled. So for now I've just changed it to use login endpoints I know work from people who have posted feedback.
Happy to add more country specific ones if anyone wants to try endpoints in their own country :) I've also moved the region dictionary to const.py for easier editing/access.
from fordpass-ha.
Pushed a Beta version that just changes the login endpoint to use an alternative one for now. This is only as temporary measure and have reached out to Ford about potentially supporting their new official API. However region restrictions and limited functionality for now it seems.
Awesome, still working 😀. So no need to add locales for every country?
Not for now. Problem is countries seem to be hit and miss which got the new security enabled. So for now I've just changed it to use login endpoints I know work from people who have posted feedback.
Happy to add more country specific ones if anyone wants to try endpoints in their own country :) I've also moved the region dictionary to const.py for easier editing/access.
Yep, saw that. If the fix wouldn't help for the Netherlands, modifying the code would be much easier 💪
from fordpass-ha.
Germany: I changed L44: "DE-DE" (not L46 in my file for whatever reason), L50: "DE", L63: "...de", L151: "...de", L267: "...de". When I tried to add the FordPass integration again (I disabled it after the errors appeared), I got no Login-Error anymore, but I got the error in a popup: "No vehicles on account or all are configured already" and the integration was not activated. Of course my car is still in the FordPass app on my smartphone. Thanks in advance for any ideas! Update 09.05.24 11:00 CEST: Updated to 1.68-Beta
Thank you @itchannel for providing an update so fast!! 🏆
I am not quite sure, if this/my issue ist off-topic here, but after updating to 1.68-Beta, I'm still facing the problem that my car is not found after trying to install the integration (again) and login, what is obviously working, with 1.68-Beta. My car is still in the FordPass app but is not "found" in my Ford-account by the integration or is "already configured" in the integration as the error message said.
Is it possible that there are still configuration remnants somewhere in the installation that make the integration think the car is already configured, which I have to delete manually first?
I would very much appreciate your help. 💐
from fordpass-ha.
Germany: I changed L44: "DE-DE" (not L46 in my file for whatever reason), L50: "DE", L63: "...de", L151: "...de", L267: "...de". When I tried to add the FordPass integration again (I disabled it after the errors appeared), I got no Login-Error anymore, but I got the error in a popup: "No vehicles on account or all are configured already" and the integration was not activated. Of course my car is still in the FordPass app on my smartphone. Thanks in advance for any ideas! Update 09.05.24 11:00 CEST: Updated to 1.68-Beta
Thank you @itchannel for providing an update so fast!! 🏆 I am not quite sure, if this/my issue ist off-topic here, but after updating to 1.68-Beta, I'm still facing the problem that my car is not found after trying to install the integration (again) and login, what is obviously working, with 1.68-Beta. My car is still in the FordPass app but is not "found" in my Ford-account by the integration or is "already configured" in the integration as the error message said. Is it possible that there are still configuration remnants somewhere in the installation that make the integration think the car is already configured, which I have to delete manually first?
I would very much appreciate your help. 💐
Has it previously worked for you ok?
I'd recommend deleting the integration. Then giving your HA a full restart then re-adding it.
I've just tested on my dev instance and vehicles are showing up ok when adding the integration so must be something cached or broken on your instance.
from fordpass-ha.
Germany: I changed L44: "DE-DE" (not L46 in my file for whatever reason), L50: "DE", L63: "...de", L151: "...de", L267: "...de". When I tried to add the FordPass integration again (I disabled it after the errors appeared), I got no Login-Error anymore, but I got the error in a popup: "No vehicles on account or all are configured already" and the integration was not activated. Of course my car is still in the FordPass app on my smartphone. Thanks in advance for any ideas! Update 09.05.24 11:00 CEST: Updated to 1.68-Beta
Thank you @itchannel for providing an update so fast!! 🏆 I am not quite sure, if this/my issue ist off-topic here, but after updating to 1.68-Beta, I'm still facing the problem that my car is not found after trying to install the integration (again) and login, what is obviously working, with 1.68-Beta. My car is still in the FordPass app but is not "found" in my Ford-account by the integration or is "already configured" in the integration as the error message said. Is it possible that there are still configuration remnants somewhere in the installation that make the integration think the car is already configured, which I have to delete manually first?
I would very much appreciate your help. 💐Has it previously worked for you ok?
I'd recommend deleting the integration. Then giving your HA a full restart then re-adding it.
I've just tested on my dev instance and vehicles are showing up ok when adding the integration so must be something cached or broken on your instance.
Thanks for you quick reply!
Yes, it worked perfect before this login-issue. Then I disabled the integration and the problem started with my try to install the integration again after the login-issue was "solved".
I completely deleted the integration yesterday (before the beta release) and installed it again (with restarting the whole system in between) 🤷♂️. I will try the procedure again with the beta now and report the result.
from fordpass-ha.
Can confirm that login now works with 1.68 Beta. I am situated in Croatia.
login works with 1.68 from Germany...
switching to the BETA Channel is always a bit tricky...
- enable beta - wait a short while
- select "any" other release that is not on top of the list - wait a short while
- select the 1.68 beta - wait a short while...
- now install it
- restart HA
from fordpass-ha.
Im in the UK and changed to Australia and all OK. Nothing working changing to .co.uk or en-GB, etc.
Not tried the beta, does anyone know the correct set up for the UK ?
from fordpass-ha.
Germany: I changed L44: "DE-DE" (not L46 in my file for whatever reason), L50: "DE", L63: "...de", L151: "...de", L267: "...de". When I tried to add the FordPass integration again (I disabled it after the errors appeared), I got no Login-Error anymore, but I got the error in a popup: "No vehicles on account or all are configured already" and the integration was not activated. Of course my car is still in the FordPass app on my smartphone. Thanks in advance for any ideas! Update 09.05.24 11:00 CEST: Updated to 1.68-Beta
Thank you @itchannel for providing an update so fast!! 🏆 I am not quite sure, if this/my issue ist off-topic here, but after updating to 1.68-Beta, I'm still facing the problem that my car is not found after trying to install the integration (again) and login, what is obviously working, with 1.68-Beta. My car is still in the FordPass app but is not "found" in my Ford-account by the integration or is "already configured" in the integration as the error message said. Is it possible that there are still configuration remnants somewhere in the installation that make the integration think the car is already configured, which I have to delete manually first?
I would very much appreciate your help. 💐Has it previously worked for you ok?
I'd recommend deleting the integration. Then giving your HA a full restart then re-adding it.
I've just tested on my dev instance and vehicles are showing up ok when adding the integration so must be something cached or broken on your instance.Thanks for you quick reply! Yes, it worked perfect before this login-issue. Then I disabled the integration and the problem started with my try to install the integration again after the login-issue was "solved". I completely deleted the integration yesterday (before the beta release) and installed it again (with restarting the whole system in between) 🤷♂️. I will try the procedure again with the beta now and report the result.
OK, after breakfast, I was just about to reinstall it when I saw that I could now activate the integration - and what can I say: everything works perfectly (again).
Now, of course, I'm wondering whether I simply overlooked the fact that the integration only needed to be reactivated (and not reinstalled/added again) and I overlooked the fact that it was still only deactivated. 🤔
If yes: Sorry about the confusion. 🫣
from fordpass-ha.
Still not working with 1-68Beta.
I changed the config and it's working now
I'm in France
from fordpass-ha.
Can confirm beta fixes the issue here, Netherlands
from fordpass-ha.
Related Issues (20)
- sensor.fordpass_fuel Does not update anymore HOT 2
- Creditals not working after reinstalling integration HOT 6
- Question surrounding what I can do when the Alarm is triggered HOT 4
- Lots of tinkering to get token, then KeyError. HOT 3
- Invalid Credentials HOT 2
- 1.70 click on website opens fordpass app HOT 6
- Email about API from Ford HOT 1
- 1.70 Tests HOT 75
- Using phone number instead of email to login the new workflow? HOT 5
- 1.70 HOT 2
- ? sensor.fordpass_tirepressure Attribute Unit of Measure HOT 1
- SOURCE_TYPE_GPS was used from fordpass, this is a deprecated constant which will be removed in HA Core 2025.1. Use SourceType.GPS instead, please report it to the author of the 'fordpass' custom integration
- v1.70 has a typo in the generate_url at line 216 HOT 1
- FordPass- Home assisant - Invalid Credentials HOT 16
- Fuel percentage wrong HOT 3
- Home Assistant 2024.7 logs warning messages about async_forward_entry_setup HOT 3
- 2023 PHEV Escape battery sensors
- Corrupted fordpass_token.txt file HOT 7
- Can't Login Invalid Credentials HOT 7
- Enhancement: SOC sensor HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fordpass-ha.