FordPass - Scriptable Widget V2022.XX (iOS, iPad, MacOS)

[Neil4Real]

Sorry for so many updates to the widget today!
I'm trying to get all the bugs fixed as I find them... I think I'm done for now.
The current release is 2022.10.13.4

Is this worth trying to get working on the current Scriptable release or is it better to wait until the beta is released publicly?

Sponsored

 

[Ravensfan1996]

Sorry for so many updates to the widget today!
I'm trying to get all the bugs fixed as I find them... I think I'm done for now.
The current release is 2022.10.13.4

SO both my scripts disappeared a few days ago on my iPad and iPhone. Do i just follow The instructions again on the first page of this post to get them back?

 

[Shayne]

? Which battery level/status?

 

[Carlos J. Marrero]

 

[tonesto7]

? Which battery level/status?

that's the LVB

 

[tonesto7]

use the widget tool to update and try again

 

[tonesto7]

Is this worth trying to get working on the current Scriptable release or is it better to wait until the beta is released publicly?

the public or beta releases work fine

 

[JohnFoxeSheets]

Sorry for so many updates to the widget today!
I'm trying to get all the bugs fixed as I find them... I think I'm done for now.
The current release is 2022.10.13.4

I echo others in thanking you for your hard work on this! If you ever move this to a paid platform, you'll have my subscription ?.

One quick question: do you think you'll be able to get OTA info working again? Or had Ford made that infeasible? Thanks!!

 

[Logal727]

So is the OTA Status info gone?

 

[JohnFoxeSheets]

So is the OTA Status info gone?

Yup

 

[tonesto7]

So is the OTA Status info gone?

I had to remove it. When I first added this the token used by Fordpass also allowed authentication on the digitalservice.ford.com API's used by the Ford Website.

Then a couple of months ago ford started locking down their stuff for the Fordpass and Web separately. So I had to maintain getting two tokens just to provide the OTA data and sync info.
Now they've locked the token process down pretty well by adding a unique fma_verifier cookie to the login process to get a particular token version required to access the OTA info and it's just too hard to capture using Scriptable at the moment.

I'm all good with the added security but they need to allow authorized access to the API they created which is technically the same one we use for Ford Pass.

Ford Developer Marketplace | FordConnect

It has all of the calls available except the one to get your token

 

[Logal727]

I had to remove it. When I first added this the token used by Fordpass also allowed authentication on the digitalservice.ford.com API's used by the Ford Website.

Then a couple of months ago ford started locking down their stuff for the Fordpass and Web separately. So I had to maintain getting two tokens just to provide the OTA data and sync info.
Now they've locked the token process down pretty well by adding a unique fma_verifier cookie to the login process to get a particular token version required to access the OTA info and it's just too hard to capture using Scriptable at the moment.

I'm all good with the added security but they need to allow authorized access to the API they created which is technically the same one we use for Ford Pass.

Ford Developer Marketplace | FordConnect

It has all of the calls available except the one to get your token

Thank you, wasn't complaining was just curious about the status. I appreciate all your work on getting this back and running!

 

[Carlos J. Marrero]

use the widget tool to update and try again

Resolved. Thanks

 

[JeffGo]

I had to remove it. When I first added this the token used by Fordpass also allowed authentication on the digitalservice.ford.com API's used by the Ford Website.

Then a couple of months ago ford started locking down their stuff for the Fordpass and Web separately. So I had to maintain getting two tokens just to provide the OTA data and sync info.
Now they've locked the token process down pretty well by adding a unique fma_verifier cookie to the login process to get a particular token version required to access the OTA info and it's just too hard to capture using Scriptable at the moment.

I'm all good with the added security but they need to allow authorized access to the API they created which is technically the same one we use for Ford Pass.

Ford Developer Marketplace | FordConnect

It has all of the calls available except the one to get your token

I recall a notice I got about a month or two ago from Ford about 3rd party access, something about not sharing your login info. I also had to give up (again) on the homebridge plugin as it kept failing login. I haven't checked the Alexa skill in a while though.

 

[Bayviews88]

I reset my login information in the app. After setting up the widget again on my iPhone and logging into FordPass I’m getting the following error.

Sponsored