Any coders willing to make a Mach-E app

[MrLoganRoss]

Hi. You can see my other thread on privacy and the Mache-E. In the F150 lightning forum as a result of a discussion on privacy someone developed their own app to bypass the restrictions of the Ford app requiring unnecessary access to data to use core vehicle functions. Unfortunately, I am not a coder, and I was wondering if anyone here had the skills to be able to look at what they did for the lightning, and potentially adapted for the Mache-E: https://www.f150lightningforum.com/forum/threads/lightningrod-better-charge-logs.16807/

Sponsored

 

[AtomicInternet]

https://www.codecademy.com/learn/paths/introduction-to-android-with-java

 

[AliRafiee]

I wonder how long before your Ford Pass account gets locked because a third party app is accessing it. Like some people and their charger apps.

 

[SpaceEVDriver]

https://www.macheforum.com/site/threads/my-winter-mustang-mach-e-project.13327/

 

[AliRafiee]

BTW, looks like he is sharing the code in github. All you need to do is change the background picture with a picture of a MME.

Someone also created an iOS widget in JavaScript to access all of that info.

Just googled FordPass widget and a ton showed up.

 

[tbrumleve]

Hi. You can see my other thread on privacy and the Mache-E. In the F150 lightning forum as a result of a discussion on privacy someone developed their own app to bypass the restrictions of the Ford app requiring unnecessary access to data to use core vehicle functions. Unfortunately, I am not a coder, and I was wondering if anyone here had the skills to be able to look at what they did for the lightning, and potentially adapted for the Mache-E: https://www.f150lightningforum.com/forum/threads/lightningrod-better-charge-logs.16807/

So, you want an app that accesses the API to do everything the FordPass app does? First off, you’ll probably run afoul of Ford and they’ll lock your account. They’ve done this for third party apps. IF that doesn’t happen, then expect months of development and tens of thousands of dollars to make it. Gotta reverse engineer the app, create a new app, programming, scripts, API calls.

It’s not worth anyone’s time, especially when v5 of the app is in development. That has taken months and they have full access to code and APIs. Most of what folks have made are more details information graphs from the OBD2 data.

 

[Jiji]

Hi. You can see my other thread on privacy and the Mache-E. In the F150 lightning forum as a result of a discussion on privacy someone developed their own app to bypass the restrictions of the Ford app requiring unnecessary access to data to use core vehicle functions. Unfortunately, I am not a coder, and I was wondering if anyone here had the skills to be able to look at what they did for the lightning, and potentially adapted for the Mache-E: https://www.f150lightningforum.com/forum/threads/lightningrod-better-charge-logs.16807/

Checkout TeslaFi and ElectraFi (for the Rivian R1S/R1T), these are possible because the Tesla API is excellent while the Rivian API is mediocre but useable and Ford’s contains even less useful data.

I made a TeslaFi clone for the Mach-E but in order to be useful you need to pull data from the ODBII port which presents a wide range of problems. I have since started driving an R1S and it encrypts the scan port data so only the Rivian API is available. This makes it easy for everyone to use as no hardware is required but there are still insurmountable issues for an iOS app making a server-hosted solution like TeslaFi/ElectraFi a requirement.

I use both every time I drive but In the end they are something only a parent could love and put up with. But I did learn how to write a modern SwiftUI iOS application which was the primary purpose of the exercises.

And since you are new I’ll share my Mach-E efficiency over the past year which really needs Ford (and Rivian) to step up their APIs to make possible wider distribution.

Or a trip in the Rivian version that includes weather data from Apple Weather:

 

[jpinFLX]

The ford architecture is not sustainable for custom app development beyond hobby grade.

 

[SpartanZack]

So FordPass is definitely trash, but I don't think using a custom app is going to solve the privacy issue, if it's still calling the Ford API?

What this really seems to accomplish is presenting the data in a better format, in an app that is less bloated and slow than Ford's app. But Ford still has all the vehicle information, and could be sharing it with insurance companies or whoever. The only real way around this is to pull the data directly from the car.

Creating an app is not particularly difficult, it's building a reliable and usable API that securely communicates with the car that is the hard part.

 

[rkmoray]

I will take a look at the links and see if I can put together a prototype.

 

[Art]

Hi. You can see my other thread on privacy and the Mache-E. In the F150 lightning forum as a result of a discussion on privacy someone developed their own app to bypass the restrictions of the Ford app requiring unnecessary access to data to use core vehicle functions. Unfortunately, I am not a coder, and I was wondering if anyone here had the skills to be able to look at what they did for the lightning, and potentially adapted for the Mache-E: https://www.f150lightningforum.com/forum/threads/lightningrod-better-charge-logs.16807/

I had a career in programming, so I wouldn't attempt hacking the Ford's software.
1. Ford's staff has enough problems insuring they don't tread on Apple carplay and Android apps.
2. Ford staff doesn't know about any hacks to their code and would quite likely damage the hack on an update.

Too summarize, it seems like a waste of time. I do like the idea of someone submitting a design to Ford. That might be a better path to the solution.

Sponsored