System off to save battery

[ProximusAl]

No....The widget I use is using a script from scriptable...here:

https://www.macheforum.com/site/threads/fordpass-scriptable-widget-v2022-xx-ios-ipad-macos.14658/

Although, I guess what you use is similar.

Sponsored

 

[RickMachE]

If you think about it, it's common sense. If you use an app that pulls data from the servers, which query the car to get the data, you're waking up the car and using battery. Same as walking by with the fob or PaaK.

 

[tonesto7]

Iirc that bulletin was pointed out in the iOS widget thread. There was little, if any response.

Because there is nothing really to respond to. Why would this affect some and not others?
I have the home assistant integration and my widget running, and never seen this issue after replacing my battery a month ago (It's been bad since I bought my truck, the freeze plugs were slightly raised and one of the cells was bad).

Odds are that your LVB is not well like thousands of others.

The whole point behind polling the server is to eliminate waking the car. Why would it wake some and not others?

 

[Carsinmyblood]

I got that screen last week.

I assumed I walked away from the car with the Acc on. I'm now thinking that isn't the problem.

 

[Flydivesurf]

Odds are that your LVB is not well like thousands of others.

I don’t use the widget. I see no advantage in doing so and my lvb battery is fine. That part of your response regarding why the author of the iOS widget hasn’t responded is a non sequitur.

 

[tonesto7]

I don’t use the widget. I see no advantage in doing so and my lvb battery is fine. That part of your response regarding why the author of the iOS widget hasn’t responded is a non sequitur.

Well, since I am the widget author it felt pretty damn relevant to me.
My apologies for offending your intellect since you are clearly more knowledgable than I

 

[tonesto7]

If you think about it, it's common sense. If you use an app that pulls data from the servers, which query the car to get the data, you're waking up the car and using battery. Same as walking by with the fob or PaaK.

Just so everyone understands. Polling Ford does not trigger a vehicle poll. It requires a special command to request the vehicle wake up.

 

[RickMachE]

Just so everyone understands. Polling Ford does not trigger a vehicle poll. It requires a special command to request the vehicle wake up.

I'm not a software engineer, but when my FordPass app shows 12 hour old info, and I refresh it to get new info, it's pretty clearly getting that from my car, no?

 

[tonesto7]

I'm not a software engineer, but when my FordPass app shows 12 hour old info, and I refresh it to get new info, it's pretty clearly getting that from my car, no?

Yes, you are correct that when you pull down to refresh in FP, it sends the wake command to the vehicle, as I mentioned above.

 

[tonesto7]

If your mach-e is anything like my F150 it wakes up quite a bit. I can hear it clicking all the time even when the fob is in the house.
I also catch my CMR doing scans while parked in my driveway on my cameras all the time at night. The night vision IR filters on the cams make the cars light up inside because the CMR uses IR.
I think there are bugs in certain software versions that prevent vehicles from fully going to sleep.

Maybe in some cases, Ford API users are abusing the wake command which could easily be fixed by adding a rate limit to wake commands to once every 30 minutes.

 

[737flyer]

OK, so just another update on my second test so far.....

This time, after fully charging my LVB, I made one significant difference. I was hoping it wouldn't be this, but so far.....the "System off to save battery" has not returned.

The only difference this time.....was I removed the Scriptable widget from my iPad. I know, I know...this is only supposed to query the Ford Server data, but it can wake the car using the "Request Refresh" button in the widget.

I only removed the widget, I haven't uninstalled Scriptable or the script, just haven't used it.

As much as I don't want it to be this, so far, by not having the scriptable widget displaying on my iPad, I have not had the return of this screen.

So, as I say...this is just my findings....if any of you above want to do the same test, then fully charge your LVB, and try removing the scriptable widget from your devices.

Obviously, if this changes in any way, I shall come back and update the thread, but just thought I'd update people on my findings.....

I love the widget, and did use it quite a bit, but for now, I'll run for another few weeks without it just to see if that screen returns.....

Some of you above may not even use the widget....in which case, the cause may be something else.

I didn’t have the widget installed and I’m still getting the message. It’s not the widget.

 

[ARK]

I get this message pretty frequently. Never had any problems, and it disappears very quickly after start up.

My best guess is I am more likely to get it if it has been a few days since I have driven the vehicle, or sometimes I notice at night that the driver display is randomly on with a dark screen - I think the screen probably times out at some point.

If you think about what the message says, it is odd that it appears when you turn the vehicle on. It seems appropriate to appear if you have been sitting in the car in accessory mode or the like and doing nothing for a while, but I've never seen it in that circumstance (but I also don't really hang out in my car in accessory mode, like some people do waiting for kids, etc.).

 

[Mach-Lee]

If your mach-e is anything like my F150 it wakes up quite a bit. I can hear it clicking all the time even when the fob is in the house.
I also catch my CMR doing scans while parked in my driveway on my cameras all the time at night. The night vision IR filters on the cams make the cars light up inside because the CMR uses IR.
I think there are bugs in certain software versions that prevent vehicles from fully going to sleep.

Maybe in some cases, Ford API users are abusing the wake command which could easily be fixed by adding a rate limit to wake commands to once every 30 minutes.

It definitely seems that only some vehicles are affected, perhaps due to different gateway module software versions. Due to bugs, polling the sever might end up sending a message to the vehicle, even though it doesn't refresh status. I think you are assuming because no new data is received that the vehicle isn't being woken up, which might be false. What I'm saying is maybe the server pings the vehicle every time you poll, but doesn't update JSON file you get as output.

Either way, I think adding an advisory message somewhere to the effect of "This widget may cause 12V drain on some vehicles, if you notice a low 12V battery increase polling interval to every 30 minutes or longer." would be helpful.

The CMR coming on can be due to a couple things, if it picks up your PAAK or fob nearby that may trigger it. This can be due to differences in signal strength (walking around in your house could affect the RSSI, so car thinks your are moving towards it). Disabling welcome lighting really quieted down my car since it's no longer constantly checking for the key. Waking up at random times could also be due to polling.

 

[tonesto7]

Due to bugs, polling the sever might end up sending a message to the vehicle, even though it doesn't refresh status. I think you are assuming because no new data is received that the vehicle isn't being woken up, which might be false. What I'm saying is maybe the server pings the vehicle every time you poll, but doesn't update the JSON file you get as output.

While I'm open to the possibility of this occurring it is not behavior I've seen before.
I can try to add so customization to the time between polling of the data.

If users truly suspect this is the case then just delete the widgets from your home screen and leave the script installed. The widgets themselves are what drives the timing of the polling.
One way to check to see how often your vehicle is actually being woke up is to open the Script interface and leave it open. It polls the servers every 30 seconds. Pay attention to the Last Check-Date. If that's updating frequently then the vehicle is sending in data way more than it should.

 

[Flydivesurf]

Well, since I am the widget author it felt pretty damn relevant to me.
My apologies for offending your intellect since you are clearly more knowledgable than I

I was referring to the iOS widget thread when the question was first presented to you there following Ford publishing the SSM. There was silence there for some time. Whatever, using the widget can cause problems for some cars.

Sponsored