Persist active transaction ID's

[filmackay]

Description

When Home Assistant restarts or the OCPP integration is reloads while an EV is actively charging, the integration loses its in-memory tracking of the active transaction_id.

When subsequently attempting to stop the charge session via the HA switch entity after a reboot/reload, the integration sends a StopTransaction without the recognized active session ID.

Because OCPP 1.6 does not feature a native API for the Central System to query the charger for an active transactionId upon WebSocket reconnection, HA remains unable to control or cleanly end the session until the physical cable is disconnected or a charger reset is issued.

Is this a general issue for all chargers, or something specific to Wallbox?

Describe the solution you'd like

Persist active transaction_id states per connector to disk (e.g., using Home Assistant's RestoreEntity or Store helper in .storage) whenever a StartTransaction or status change occurs.

Upon integration startup/reboot:

1. Load stored active transaction_id mappings from .storage.
2. If the connector reports active charging (StatusNotification = Charging or SuspendedEV), restore the active transaction_id into the runtime session state.
3. Allow RemoteStopTransaction and local switch toggles to cleanly match and end the active session using the restored ID.

Describe alternatives you've considered

• Soft Reset: Calling the charger reset button clears the Finishing state on the wallbox, but interrupts charging unnecessarily.
• Cable Disconnect: Unplugging the EV manually clears the local session, but prevents automated/headless control when HA reboots mid-charge.

Additional context

Tested on a single-connector wallbox (Wallbox Pulsar Plus / PLP2-0-2-4, firmware 6.13.6) running OCPP 1.6 J.

---

[mfuchs1984]

An active transaction id can technically be recovered from received metervalues, so persisting should not be necessary. A persisted transaction might be stale when starting again.

[filmackay]

Good point - do you think use the transaction_id on the first metervalues after startup?

[mfuchs1984]

Looks like this is already implemented

ocpp/custom_components/ocpp/ocppv16.py

Line 1668 in e6a95c5

if transaction_id and not tx_ended and (recorded_tx == 0 and active_tx == 0):

[filmackay]

Right you are!

Looks like this was a while ago too - I wonder how mine got into a bad state when rebooting HA mid-charge 🤔