car status not updated after charging session started

[ari197]

so I have a HA automation script that takes into account the current electricity price and the car's battery SoC and determine if it's beneficial to charge.

this morning at 11:07 the script got triggered and started charging, however if you looked in HA, the states didn't get updated, as such that on 12:07 the script got triggered again (because the status of the car is not charging)

here is the log from the GW for both event :

2025-06-10 09:06:33,434 [INFO]: Job "Check for new messages (trigger: interval[0:01:00], next run at: 2025-06-10 09:07:33 UTC)" executed successfully - apscheduler.executors.default
2025-06-10 09:07:00,816 [INFO]: Setting charging current limit to MAX - handlers.vehicle
2025-06-10 09:07:00,857 [INFO]: Charging will be started - handlers.vehicle
2025-06-10 09:07:10,509 [INFO]: Setting refresh mode to force due to after command execution on topic drivetrain/chargeCurrentLimit/set - vehicle
2025-06-10 09:07:10,566 [INFO]: Setting refresh mode to periodic due to restoring of previous refresh mode after a FORCE execution - vehicle
2025-06-10 09:07:10,567 [INFO]: Updating vehicle status - handlers.vehicle
2025-06-10 09:07:14,152 [INFO]: Updating charging status - handlers.vehicle
2025-06-10 09:07:17,510 [INFO]: Updating scheduled battery heating status - handlers.vehicle
2025-06-10 09:07:17,584 [INFO]: Refreshing vehicle status succeeded... - handlers.vehicle
2025-06-10 09:07:17,793 [INFO]: Refreshing ABRP status succeeded... - handlers.vehicle
2025-06-10 09:07:17,793 [INFO]: Sending HA discovery messages for LSJxxxxxxxxxxxxxx (Force: False) - handlers.vehicle
2025-06-10 09:07:33,037 [INFO]: Running job "Check for new messages (trigger: interval[0:01:00], next run at: 2025-06-10 09:08:33 UTC)" (scheduled at 2025-06-10 09:07:33.034700+00:00) - apscheduler.executors.defau
lt
2025-06-10 09:07:33,436 [INFO]: 2 messages received - handlers.message

... other non relevant logs ...

2025-06-10 10:06:33,416 [INFO]: 2 messages received - handlers.message
2025-06-10 10:06:33,417 [INFO]: Job "Check for new messages (trigger: interval[0:01:00], next run at: 2025-06-10 10:07:33 UTC)" executed successfully - apscheduler.executors.default
2025-06-10 10:07:00,802 [INFO]: Setting charging current limit to MAX - handlers.vehicle
2025-06-10 10:07:00,843 [INFO]: Charging will be started - handlers.vehicle
2025-06-10 10:07:07,417 [INFO]: Setting refresh mode to force due to after command execution on topic drivetrain/charging/set - vehicle
2025-06-10 10:07:07,621 [INFO]: Setting refresh mode to periodic due to restoring of previous refresh mode after a FORCE execution - vehicle
2025-06-10 10:07:07,622 [INFO]: Updating vehicle status - handlers.vehicle
2025-06-10 10:07:20,515 [INFO]: Updating charging status - handlers.vehicle
2025-06-10 10:07:27,077 [INFO]: Setting charging query interval in vehicle handler for VIN LSJxxxxxxxxxxxxxx to 0:09:42 - vehicle
2025-06-10 10:07:27,077 [INFO]: Updating scheduled battery heating status - handlers.vehicle
2025-06-10 10:07:27,154 [INFO]: Refreshing vehicle status succeeded... - handlers.vehicle
2025-06-10 10:07:27,379 [INFO]: Refreshing ABRP status succeeded... - handlers.vehicle
2025-06-10 10:07:27,380 [INFO]: Sending HA discovery messages for LSJxxxxxxxxxxxxxx (Force: False) - handlers.vehicle
2025-06-10 10:07:27,562 [INFO]: Charging will be stopped - handlers.vehicle
2025-06-10 10:07:27,574 [INFO]: Charging will be stopped - handlers.vehicle

here is the log from home-assistant GUI :

[elmr91]

I noticed the same.
I worked around by forcing a refresh 30s after starting charge.

[nanomad]

We're addressing this with two changes coming in the next release:

1. Polling phase visibility (refresh/pollingPhase)

A new MQTT topic that publishes which sub-phase of the periodic polling the gateway is currently in. Possible values:

• off — refresh mode is OFF
• force — one-shot forced refresh
• charging_detection — one-shot charging detection refresh (see below)
• error_recovery — retrying after a failed refresh
• charging — polling at a computed charging interval
• active — HV battery is active, polling at the active interval
• after_shutdown — grace period after car shutdown, polling frequently to detect charger connection
• inactive — car is inactive, polling at the inactive interval (e.g. once per day)

This will also appear as a diagnostic sensor in Home Assistant.

2. New charging_detection refresh mode

A new one-shot refresh mode (like force) that can be set via refresh/mode/set. When triggered, it:

1. Resets the "last car shutdown" timestamp to now
2. Performs a single immediate refresh
3. Reverts to the previous refresh mode

If the previous mode was periodic, the gateway will then naturally enter the after_shutdown grace period — polling every ~120s for ~600s — which is the window designed to detect a charger being plugged in. If charging is detected during this window, the gateway automatically transitions to the charging polling interval.

For your use case: after your HA automation sends the "start charging" command, you can publish charging_detection to the refresh/mode/set topic. This ensures the gateway keeps polling frequently for the next ~10 minutes to pick up the charging state change, rather than falling back to the inactive (24h) interval.