RemoteStopTransaction
Asks the charge point to stop a running session by transaction id.
- Version
- OCPP 1.6
- Direction
- CSMS → Charge Point
- Feature profile
- Core
The counterpart to RemoteStartTransaction. It identifies the session by transactionId rather than by connector, so the CSMS must know the id — which it does, because it assigned it.
As with the remote start, Accepted means the request was taken, not that the session has ended.
Request
| Field | Type | Required | Description |
|---|---|---|---|
transactionId | integer | Required | The transaction to stop, as assigned in the StartTransaction response. |
json
[2, "19223201", "RemoteStopTransaction", {
"transactionId": 8814
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | RemoteStartStopStatus | Required | Whether the charge point will attempt the stop. |
json
[3, "19223201", {
"status": "Accepted"
}]Implementation notes
The session has ended when StopTransaction arrives, with reason: "Remote". Until then it is still running.
A transactionId the charger does not recognise gets Rejected. This happens routinely when the CSMS and charger disagree about which sessions are open after a reconnect.
Stopping a session does not unlock the connector on every model. UnlockConnector is a separate message for a reason.