FordPass 4.27.0 Update

[Shayne]

In addition for the first time the departure time didn’t work as well as my changing the preferred charge %. They are going backwards.

Just send a new departure schedule through Fordpass to the car should fix it right up no problems ???

Sponsored

 

[Shayne]

My car is scheduled to charge between noon and 4 pm HST daily. The pve system batteries are usually full by that time and the system is producing excess electrons.

I plugged the car in just before 3pm today when I got back from Kona. It stopped charging at 4 pm HST. This is what FordPass shows for when it’ll get to 80%

5:52 am tomorrow makes zero sense no matter how badly they’ve messed with time zone calculations. It’ll take a smidgen over 3 hours tomorrow to get to 80%.

I guess we know what they broke this time.

My charge started as per car time not what Fordpass said. They sent me a message it was completed at the time it started. Nope not finished just started to blink and still is? Give me more Ford software I can't get enough.

 

[Gullwingdmc]

Another bug in this update. The picture of the car is gone from the Apple Watch app. I reported that to the FordPass email. I don’t know if anyone checks that though.

 

[Shayne]

Another bug in this update. The picture of the car is gone from the Apple Watch app. I reported that to the FordPass email. I don’t know if anyone checks that though.

So now how will we find it in the parking lot with no visual reference of what it looks like?

Have not tried manipulating departure schedules through FP on this version. After over 6 months of it not working here I do not have great expectations.

 

[Fremont Kid]

Based on all reports Ford's software development team seems to not have a robust testing process. Come on Ford. Test, test, test, then test again! Never enough time to do the job right but always enough time to do the job again. Your customers should not be an essential part of your testing system.

 

[Kamuelaflyer]

4 PM HST Tues is 02:00 GMT Wed (actual charge finish time). Time zone offset -10 GMT. Double that so -20 GMT. 02:00 GMT - 20 = 06:00 HST Tues (05:52 is close). Seems the day matches GMT?

I could be wrong, but applying the GMT offset twice seems to be the pattern (times are handled by the server in GMT and corrected locally).

I thought about that but the predicted charge time isn’t off by enough from two years of using FordPass. Start to finish the charge will be about 3 hours and a minute or two. In the past FordPass would predict a charge time exceeding 4 hours by a lot. ?‍

We shall see sometime today.

 

[Gullwingdmc]

Based on all reports Ford's software development team seems to not have a robust testing process.

At least the FordPass team does not, the Sync team too. Hopefully they do more testing on the critical updates, like on drivetrain modules.

 

[83girl]

At least the FordPass team does not, the Sync team too. Hopefully they do more testing on the critical updates, like on drivetrain modules.

Everything is fine, nothing to see here....loading for 45 minutes........

 

[Rjk1726]

Lets see what this does.

Since the update it no longer predicts charging time on my ford level 2 charger properly. Also has been hit and miss with the departure time. Seems to have added bugs.

 

[Mrn]

I think you guys who where lucky enough to already get this update ARE the beta testers. Those of us who haven't received it yet are benefitting from your frustration?

 

[EELinneman]

Everything is fine, nothing to see here....loading for 45 minutes........

In the immortal words of Steve Jobs; You are holding it wrong. It cannot be Ford's software that is not working right. Just cannot possibly be.

 

[mach-e-waiting]

I stand corrected from my earlier post - the clock in the car is working fine with 4.27. Also I had a version 4.26 on another device and it worked perfectly. I noted also that the time to charge had the Minutes correct but not the Hour - indicating maybe the app has it's "own Time Zone". I guess we wait for an update to 4.27.0

 

[Shayne]

Since the update it no longer predicts charging time on my ford level 2 charger properly. Also has been hit and miss with the departure time. Seems to have added bugs.

Sending schedules through the phone worked on yours until recently? Or do you just set it once and stick with that? What exactly started to be hit and miss? I don't think the car cares too much about what fordpass version you have? The only accepted change it takes from the phone (server) is changes to the schedule which has not worked here for some time. All other communications the car sends.

Many here for along time say you need to set the departure schedules up in the cold car and trust what it says there. I can not trust the phone command did change the schedule in the car (even what the app displays can be not right). Need to check it and set it in the car. Fordpass departure schedule changes do not work here.

I'm am getting continuous partial response from FP now so have not even tried departure schedule communication on 427. @Ford Motor Company Bluetooth departure scheduling (both schedules) please! The server issues continue.

Good summer is coming and I don't need departure schedules or have to plug it in all the time. ?

 

[RickMachE]

I'm perplexed that Ford doesn't utilize the EA group to test the app. And, given the wide impact of changes, utilize it as different app. For example, Vanguard tested a new app for a long time, under a totally different name. So, if they broke a feature, one could still use the regular app.

As I come up on 2 years with Ford EVs, there are a handful of things that I shake my head at, that in 2 years they haven't fixed. This is top of the list, FordPass, and it's inability to be successfully updated and reliably interface with the vehicle.

But I put Communication above this as the #1 issue Ford has to fix. I was astonished that the Ford forum account actually communicated this week of the BlueCruise price increase. That type of communication, as well as direct communication to ALL owners, has to happen much, much more often and much, much quicker.

 

[pauljr]

I think what has happened in the app is that they are subtracting the user's UTC offset, for me in MN it is -5 for central time right now. The problem is they are subtracting the UTC offset from the user's local time and not UTC. So that is making things appear as charging would complete in the past. I guess if you know how many hours before or after UTC you are you can adjust in your head when the app thinks charging will start/finish. That is until the programmers get out an update to fix a silly mistake that should have been caught with some basic unit tests.

Sponsored