Day after my window sticker date from Kansas. Come from the age of setting up the engine by ignition points and balancing SU carbs. Widget seems a great idea and all doing great in fine tuning it. But will wait to be able to set up by following a walk through, with my limited programming experience.
Huh. Yes, what you put was fine. Troubleshooting via forum through the Scriptable app is a lot of layers of difficultStill same result, am I pasting in the code as you wish? Unsure if I can put two semicolon'd items into the same line? Or do you want console.log('data=' + data); on line 1254?
It’s never fun troubleshooting unless you’re right there! Still nothing with the changesHuh. Yes, what you put was fine. Troubleshooting via forum through the Scriptable app is a lot of layers of difficult
What @tonesto7 is doing in the script where it's failing for you is pretty straight-forward. It's just making a call to https://usapi.cv.ford.com/api/vehicles/v4/${vin}/status. By that point in the script, it thinks your login went fine.
Ok, try this. Put everything in the script back to the original from tonesto7. Then replace line 1243 with this:
'auth-token': '`${token}`',
I’m pretty sure that I can manipulate the zone lighting with the FordPass app and the ignition off.
Have you considered your phone may be haunted? ?It’s never fun troubleshooting unless you’re right there! Still nothing with the changes
Yeah, me too. Propower is the one that I can’t make go with ignition off
That’s interesting because I get an error through the FordPass app when trying to turn it on when the truck is off. My truck is a very early 2021 build and I got the update that “fixed” the zone lighting battery drain problem. I wonder if that has an impact?
That may well be due to the problems that AWS is experiencing this morning.I am CLEARLY not an intelligent person when it comes to widgets. I erased everything and started from scratch with new version. Now I'm getting this.
That's interesting... I bet it's because of the URL encoding when sending the data to ford for the token.Thanks to @WillB17 , it's safe to say that having either % or $ in your password (maybe both) won't work with the script right now. A quick and dirty way to get around this is to just change your password to have only letters and numbers in it. The script can probably be adapted to handle symbols, but I can't volunteer anyone to make a solution anytime soon. If I have time, I may poke at it to find a solution. @tonesto7 , if you're feeling generous, maybe you can noodle on it.
So it was the complicated password causing the issue that @WillB17 and I are having?Thanks to @WillB17 , it's safe to say that having either % or $ in your password (maybe both) won't work with the script right now. A quick and dirty way to get around this is to just change your password to have only letters and numbers in it. The script can probably be adapted to handle symbols, but I can't volunteer anyone to make a solution anytime soon. If I have time, I may poke at it to find a solution. @tonesto7 , if you're feeling generous, maybe you can noodle on it.
