-
-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.70 Tests #509
Comments
i've made a PR for version 1.70 to let the plugin create an URL for NL users. |
Hi, i'm try to change only part from const.py
worked for now , i'm try to open a PR |
hi, login.ford.de/4566605f-43a7-400a-946e-89cc9fdb0bd7 or this is the whole link when I log in normally at ford: If it is neither of these, how can I find out the region ID? Regions in const.py
in fordpass_new.py :
would like to try the German login because it is very slow and does not always respond |
Hello! In the US here and tried to follow the instructions but getting a "unknown error occurred" when I enter in my token from the developer tools in my browser.
Maybe something in the token not being expected is causing the error? DM me if you want me to share anything more confidential. Or of course if there is anything I can retry let me know. |
Can I confirm the token you are entering into the box starts with fordpass:// |
Leave the region id as the uk/Europe one, just change the country codes. Also that login string you showed isn't for the fordpass app so the token won't work. It needs to have a callback_url as fordpass://token |
Yes, i can confirm that. Just for fun I tried entering just the token and not the full URL and I got a validation error. (a different error than I am seeing) |
It took me a couple of attempts, but I was successfully able to get the token and add my vehicle to HA for the US region. |
I had to delete my original vehicle device to get it to work. New region config doesn't line up with the old and I didn't see a way to change that on the existing device.
|
Another error I am seeing:
|
I just tested 1.70 in Germany. The page did not load properly when I selected Europe/UK. Then, I tried North Ameriaca an everything worked properly, except that all text messages appeared in dutch language! But the integration seems to be OK now. |
Tested with North America and Canada. Link does not load. It seems that it wants to open the App. |
I've copied the files over and am trying to get the token to work with a US login. I get the developer tool string - but mine is "fordapp://userauthorized/?code=" and the string. I get unknown error occurred as another did above. No where in the network tab on the URL I am given has "fordpass". Anyone have any suggestions? I as well have the " KeyError: 'access_token' " entry in my logs (with all the other entries matching what's been posted above). |
If I try with my European login I get a link for the token that won't load in Chrome if I set it to European. But if in ha I put it to USA I get a link that loads but then I get the error user not known in dev tools. This is what I get if I set Europe in ha with 1.7 This is what I get if I set it to USA in ha. I'm not an IT guy so just tried for what I know and wanted to Share so it maybe can help. Thanks for your efforts. Great work. |
My sensors don't seem to update unless I manually reload the integration (had not updated in a week) |
This solved my issue: |
OK, tryied your solution, but ... i received this error |
I seem to have the same issue. Its not updating. |
I'm getting this same error. I tried rebuilding the POST request directly in a python interpreter to see what the response code and text were. I got a 400 response, and the following text: |
Same here. |
1.70 works for three days in row. Netherlands. |
I'm getting this same error. I tried rebuilding the POST request directly in a python interpreter to see what the response code and text were. I got a 400 response, and the following text:
Update: I tried the login process from a different browser (Chrome) and it worked. I had been using Firefox before. |
Working fin on my end "Canada" Script to reload /refresh Data is also good :-) |
Maybe we need to add also Belgium (be-fr) .be for it to work for me, (i've tryied to just update the login link copied, with .be, but it didn't work |
Have you tried using a different browser? Firefox wouldn't work for me, but Chrome did. You can also try using a private browsing/incognito window or clearing cookies/cache. |
I was able to get the token without any problems. I just noticed that not all sensors are updated for a longer period of time There are three warnings in the logs: 1: |
Just wanted to add my experience here, as well: Just got 1.70 going, and I've tested both locking and remote starting. The functionality for both works, but reporting back to HA doesn't seem to. I have the unlocking issue reported above, and my ignition status doesn't update once the car is started (though it does show in the FordPass app as started). EDIT: I did test the ignition after setting it to 30, and that status didn't change. I do notice that fordpass_remoteStartStatus is updating to Active when the vehicle is remote started, though (and I noticed this prior to doing this refresh test as well). |
Just a note, I was running 1.68 fine until I noticed the last update to my odometer, fuel remaining, unlock not working. Last update on the mileage was June 21st. Figuring my token probably finally expired, I deleted the integration and manually updated to 1.70. Had the same issues with Firefox noted above so I used Chrome. Added the token/vehicle back no issues. All/Some the data being pulled from the API is old state data that 1.68 was showing. I think the outside temperature may be accurate, but most of it is at a point in time from 7 days ago. It is not throwing any errors. Using Canada as my endpoint. Update: Things that are as of right now on Canada endpoint updating: Outside temperature, Messages, Oil %, Battery. Things not updating: Odometer, fuel tank - haven't checked unlock/lock or alarm status since I updated to 1.70. |
Followed the instructions. In Uk but understand not working so using USA. When trying to sign in understand the login should still spin, mine completes and advise 'We do not recognize this email and password. Please try again' Any advice appreciated. Not seen this issue mentioned. |
Anyone any idea with a challenge I got? Don't get the code |
In case anyone is having trouble with the dev tools and such, you can install this Chrome extension and it will show you the redirects in a nicer way. https://chromewebstore.google.com/detail/redirect-path/aomidfkchockcldhbkggjokdkkebmdll |
I can second that. Also Brave Browser did not work for me. But Chrome did. |
@kurtSejr which country have you chosen? from the 404 I recon an URL is generated that does not exist (anymore) |
I have chosen UK&Europe, I'm in Denmark. |
If I select "Netherlands" it works for me :-) |
1.70 branch works fine for me! Thanks :) |
@Prekzz Could you enable the debug log and provide it? |
@TheLizard i can't, this is the initial setup so the plugin is not loaded yet. I manually installed the plugin in home-assistant (ssh and do a git pull in the correct folders), because i could'nt do it in de HACS gui because that errored with the message that the repo already exists (on the default master branch). |
I've updated to 1.70 and it works for me... BUT the function 'fordpass.refresh_status' is not working well. |
More and more frequently I am having to generate a new token to keep 1.70 working. The only way I know to do this is to delete the device (car) and then rebuild it from scratch. Beyond that I don't know how to get the login box to reappear. Am I missing something? There has to be a way to redo the token without deleting the device right? |
Yes, you can redo the token by just going though the login process again like you going to add a new device. It will say no new vehicles found but still update the token fixing your old one. Also, you likely are running into #524 so you can also open the tokens.txt file and delete the last character (or 2) without generating a new token. |
Thanks! Got me working again. It seems so obvious now that I can update the token that way. I had already deleted the token file so it just generated a new one. I will take a look at #524 to see what I need to do in the future. |
Hey there, I wanted to download then 1.70 version but I just can't do it. |
Try this: #488 (comment) |
Thanks for the reply. That worked for me but while doing everything I get an error message: I was trying the Netherlands way as UK&Europe wouldn't open anything on any of the browsers (Safari, Firefox and Chrome) |
Installed 1.70 today, things went pretty well. All functionality seems to work except for starting and stopping ignition. On initial installation, it will start the vehicle the first time, but any subsequent attempt to start / stop the vehicle fails. Locking / Unlocking the doors, and all other data continues to work. I removed the integration, deleted the old config, reinstalled the integration and the same exact issue happens again. In the logs when trying to start the vehicle, I see this:
Any suggestions? |
It's been working great for me in the US, no accounts locks on secondary account with refresh set to every 15 min. |
Same for me. |
Thanks for the replies. Apparently, some kind of race condition or spam of the command must be occurring because when I try to use the FordPass app directly after it fails with Home Assistant, I get an error that states that there were too many remote start requests, and I'll need to start the car manually to reset. I'll try to mess around with it some more this weekend and make sure my refresh timer is set to 15m. |
I am in Australia and have successfully obtained a token and had the integration working fine. I add a second vehicle by repeating all the steps again for the same account, obtaining a new token and all worked great. I left the update frequency at 900 (15mins) and all worked great for a couple of days and then the integration failed with both integrations showing "Failed setup". I can delete them and go through the installation again and it works fine fin a day or so then fails again. Happy to provide more details if someone can point me to the procedure for getting said details. Thanks |
Hello ! |
This is an Issue thread for people who are trying/testing out branch 1.70
Relevant question and answers:
Q: Do I switch to 1.70 now?
Q: Will 1.70 have new sensors?
Q: Is 1.70 the new API?
FordConnect API
into this integration for users who can take advantage of it. See the 1.70 README for more information.Q: If I want to switch to 1.70, how do I do so?
Q: Is there an update time-frame/timeline/estimation/status/progress?
Relevant Wiki's
The text was updated successfully, but these errors were encountered: