ETL timing (over 45 min delay from unplugged)

[grahamr]

Before I fire in an actual issue - figured I would continue the discussion here instead of hijacking the Query thread. I have the json for the ETL file, and what i'm seeing is a fair "delay" for that entry coming back from the Ford api - for example:
2026-02-12_21-30-16.784_etl.json - Showing the following in the JSON - so about ~45 min for that ETL file to come down.

"energyTransferLogs": [ { "id": "", "deviceId": "", "eventType": "ChargeData", "chargerType": "AC_BASIC", "energyConsumed": 23.73727, "timeStamp": "2026-02-12T20:49:17Z", "preferredChargeAmount": 0, "targetSoc": 90, "plugDetails": { "plugInTime": "2026-02-12T18:14:20Z", "plugOutTime": "2026-02-12T20:48:14Z", "totalPluggedInTime": 9234, "plugInDte": 209.8, "totalDistanceAdded": 121.9 },

Given, in the past I have noticed the ford app shows the correct value, would it make sense to do something like this in an automation: "On plug disconnected, wait 5 min, then do a local refresh"

Of note, all the other stats seem fine in the UI - the "unplugged" sensor updates, trip data is flowing etc. its VERY rare we would have an in and out situation where a very short charge happened, but I'm trying to dashboard and automate this as much as I can to track it.

[marq24]

can you please enable the debug log and:

When you disconnect your car, you should see

... EV connect state changed to 'DISCONNECTED' -> triggering 'energy_transfer_logs' data update (will be started in 2.5min)

and then

... _ws_debounce_update_energy_transfer_logs(): started

and then 3 minutes later

... _ws_debounce_update_energy_transfer_logs(): starting the 'update_energy_transfer_logs_int()' update now

since that's the current default impl - that on a disconnect, the code will wait 3min = 180sec before the etl will be requested...

when this takes 45min on your device, then this await asyncio.sleep(180) will be an issue

[grahamr]

Interesting find today - The update to ETL took about 25 minutes to land, seemingly because of the delay with the "Disconnected" Status -
in the logs it shows the change to "Disconnected" right before firing off (as expected)
2026-02-17 12:55:09.133 INFO (MainThread) [custom_components.fordpass.fordpass_bridge] [Mustang Mach-E] ws(): this is a 'heartbeat': 2026-02-17T16:55:07Z ['customEvents[xev-key-off-route-efficiency-data]', 'updateTime'] 2026-02-17 12:55:09.134 DEBUG (MainThread) [custom_components.fordpass.fordpass_bridge] [Mustang Mach-E] ws(): EV connect state changed to 'DISCONNECTED' -> triggering 'energy_transfer_logs' data update (will be started in 2.5min) 2026-02-17 12:55:09.134 DEBUG (MainThread) [custom_components.fordpass.fordpass_bridge] [Mustang Mach-E] ws_connect(): received vehicle 'data' 2026-02-17 12:55:09.134 DEBUG (MainThread) [custom_components.fordpass.fordpass_bridge] [Mustang Mach-E] _ws_debounce_update_energy_transfer_logs(): started

But in my automation that is monitoring for "Connected -> Disconnected" it ran at 12:31 - I didn't have debugging running when the car was unplugged unfortunately, I only turned it on when I noticed it had been ~5 min from the unplug time.

[marq24]

technically the trigger is xevPlugChargerStatus will change from anything_random to DISCONNECTED... and this meta value (xevPlugChargerStatus) is also the source for the elVehPlug sensor...

[grahamr]

Thanks for that! I'll get debug enabled 2-3 minutes before I unplug tonight, and then toggle it off when my notification comes in. The iOS notification was a great way to see how long it actually is taking. On the whole 15-20 min isn't a big deal, I doubt I'll be out and back that fast, but it makes me curious 😃

[grahamr]

So for the last couple days I've been putting debug on and not having any issues and or forgetting and it's been fine. Naturally this evening it has not been fine, but I didn't have debug enabled when I disconnected. It's been about 3 hours since I unplugged, my charging disconnected automation fired as expected, and about 6 trips of different durations logged properly, but no last charge transfer

I have debugging on now, but I'm back plugged in for the night, so I'm going to shut off debug, update HA in hopes the reboot of the integration pulls the data 😃

Now I know better and will make sure to always run debugging for the next week or so to catch an anomaly.

[grahamr]

I ran debugging for a few days, caught one instance where it logged the disconnect but didn't update for 30 min, but it's been rock solid ever since.

I would say it's something odd on my end causing the issue.

I'm working on a PR for you that adds a button/service to manually force it - it's slow going over here.
Thanks for the support and addon.