? Scriptable FordPass Widget (iOS, iPad, MacOS)

[generaltso]

Thanks for the info.
Oil life is basically irrelevant with EV's right? I ask because I have limited space in the widget and if I need to put charging status and plug status I would like to eliminate oil if it's not useful

Yup, oil life is useless so that can go.

Sponsored

 

[Texas-E]

Thanks for the info.
Oil life is basically irrelevant with EV's right? I ask because I have limited space in the widget and if I need to put charging status and plug status I would like to eliminate oil if it's not useful

If you are able to display the low voltage battery with one decimal place (e.g., 12.4V), that would be awesome! The low voltage batteries in the Mach-E are rather small, and quite a few of us keep an eye on that.

 

[tonesto7]

If you are able to display the low voltage battery with one decimal place (e.g., 12.4V), that would be awesome! The low voltage batteries in the Mach-E are rather small, and quite a few of us keep an eye on that.

I like the decimal point as well. I’m not certain it returns the number as a float value. I will check and see though

 

[Jiji]

Thanks for the info.
Oil life is basically irrelevant with EV's right? I ask because I have limited space in the widget and if I need to put charging status and plug status I would like to eliminate oil if it's not useful

I suppose oil is used for cooling and lubrication but it isn’t a consumable in the way it is in an ICE vehicle so carries little information.

The only other EV specific data might be charging start/stop times. Looking at the original screen shot on page 1 the frunk status is in the the door data (as hood) and might fit as a sixth ‘door’.

And if it were me I would report the TPMS data as integers and not waste space with tenths.

 

[Chudsaviet]

Approved by me (c).
I have quickly looked through the code.
From the first sight, it looks like it does not send our sensitive information to anywhere but Ford.
The code itself looks pretty good too.

 

[Jiji]

I like the decimal point as well. I’m not certain it returns the number as a float value. I will check and see though

I don't see any sort of LV battery data that is a voltage in the FordPass data. There is the field 'battery' which has two entries, 'batteryHealth' and 'batteryStatusActual':

'battery': {
'batteryHealth': {'value': 'STATUS_LOW', 'timestamp': '11-23-2021 21:48:04'},
'batteryStatusActual': {'value': 15, 'status': 'CURRENT', 'timestamp': '12-13-2021 23:49:29'}
}

Not sure what STATUS_LOW means for 'batteryHealth' and I don't think the value 15 for 'batteryStatusActual' makes sense as a voltage as the field is tagged a status and 15V would be worry me tremendously so I will assume it is an enumeration for different battery statuses. But I could be wrong here.

I'll go plug in and see if anything updates.

 

[tonesto7]

I suppose oil is used for cooling and lubrication but it isn’t a consumable in the way it is in an ICE vehicle so carries little information.

The only other EV specific data might be charging start/stop times. Looking at the original screen shot on page 1 the frunk status is in the the door data (as hood) and might fit as a sixth ‘door’.

And if it were me I would report the TPMS data as integers and not waste space with tenths.

I doubt I can fit that charge start/stop on the medium widget.

I have plans to replace the menu system and build a sort of interface using the UITable. That way I can simulate a sort of limited app interface. If I can get items arranged the way I like it might become a sort of FP app

 

[tonesto7]

Approved by me (c).
I have quickly looked through the code.
From the first sight, it looks like it does not send our sensitive information to anywhere but Ford.
The code itself looks pretty good too.

I appreciate the compliment on the code... I think it looks like unorganized crap

I need to restructure some stuff, before I add a UI to it and the code reaches 4000+ lines of code

 

[tonesto7]

I don't see any sort of LV battery data that is a voltage in the FordPass data. There is the field 'battery' which has two entries, 'batteryHealth' and 'batteryStatusActual':

'battery': {
'batteryHealth': {'value': 'STATUS_LOW', 'timestamp': '11-23-2021 21:48:04'},
'batteryStatusActual': {'value': 15, 'status': 'CURRENT', 'timestamp': '12-13-2021 23:49:29'}
}

Not sure what STATUS_LOW means for 'batteryHealth' and I don't think the value 15 for 'batteryStatusActual' makes sense as a voltage as the field is tagged a status and 15V would be worry me tremendously so I will assume it is an enumeration for different battery statuses. But I could be wrong here.

I'll go plug in and see if anything updates.

The batteryStatusActual is the voltage... I wonder if your LVB is constantly being topped off by your HVB?
Did you ever have a low battery back on November 23rd?

 

[Mach-Lee]

If you are able to display the low voltage battery with one decimal place (e.g., 12.4V), that would be awesome! The low voltage batteries in the Mach-E are rather small, and quite a few of us keep an eye on that.

I like the decimal point as well. I’m not certain it returns the number as a float value. I will check and see though

No, it's only reported to the nearest volt (integer) in the API, not very useful that way.

 

[Mach-Lee]

I don't see any sort of LV battery data that is a voltage in the FordPass data. There is the field 'battery' which has two entries, 'batteryHealth' and 'batteryStatusActual':

'battery': {
'batteryHealth': {'value': 'STATUS_LOW', 'timestamp': '11-23-2021 21:48:04'},
'batteryStatusActual': {'value': 15, 'status': 'CURRENT', 'timestamp': '12-13-2021 23:49:29'}
}

Not sure what STATUS_LOW means for 'batteryHealth' and I don't think the value 15 for 'batteryStatusActual' makes sense as a voltage as the field is tagged a status and 15V would be worry me tremendously so I will assume it is an enumeration for different battery statuses. But I could be wrong here.

I'll go plug in and see if anything updates.

15V is normal at times when it's charging it up, especially in colder temps. The low status makes sense, because it's charging at a high voltage to recover from a low SoC.

 

[tonesto7]

No, it's only reported to the nearest volt (integer) in the API, not very useful that way.

It's definitely useful in mine because it keeps dying in my truck (I'm waiting for ford to get back to me with a fix)
I'm adding more tales to the widget for things like lvb battery low, firmware updating, deep sleep mode. etc

 

[Mach-Lee]

It's definitely useful in mine because it keeps dying in my truck (I'm waiting for ford to get back to me with a fix)
I'm adding more tales to the widget for things like lvb battery low, firmware updating, deep sleep mode. etc

Almost the entire useful range of the battery is between 12.0 and 13.0V. If it just says 12V it could be at 25% SoC or 100% SoC but you wouldn't be able to tell the difference without the extra decimal place.

 

[Jiji]

The batteryStatusActual is the voltage... I wonder if your LVB is constantly being topped off by your HVB?
Did you ever have a low battery back on November 23rd?

I completely missed that old timestamp, only Ford knows why that is there when the car is driven daily. Just ran FordPass and it says it was last updated 3 hours ago.

This is the problem with FordPass data is it only gets updated when you start a trip or an event occurs. I gave up on it as I could not rely on it being current.

 

[tonesto7]

I completely missed that old timestamp, only Ford knows why that is there when the car is driven daily. Just ran FordPass and it says it was last updated 3 hours ago.

This is the problem with FordPass data is it only gets updated when you start a trip or an event occurs. I gave up on it as I could not rely on it being current.

I hear you on the FP app... I hate that damn thing (my 10 year old could make a more reliable app)

Sponsored