RequestStartTransaction

Asks the station to start a session. The 2.0.1 name for RemoteStartTransaction.

Version: OCPP 2.0.1
Direction: CSMS → Charge Point
Functional block: Remote Control

Renamed from 1.6's RemoteStartTransaction, and it now carries a remoteStartId the CSMS chooses. That id comes back in the resulting TransactionEvent, which is how you correlate a start request with the session it produced — something 1.6 left you to guess at.

As in 1.6, Accepted means the station will try, not that charging has begun.

Request

Field	Type	Required	Description
`idToken`	IdTokenType	Required	The token to charge the session against.
`remoteStartId`	integer	Required	Correlation id, returned in `transactionInfo.remoteStartId`.
`evseId`	integer	Optional	Which EVSE. Omit to let the station choose.
`groupIdToken`	IdTokenType	Optional	Group token, where the station needs it to authorize.
`chargingProfile`	ChargingProfileType	Optional	A TxProfile to apply to the resulting session.

json

[2, "19223201", "RequestStartTransaction", {
  "evseId": 1,
  "remoteStartId": 90210,
  "idToken": { "idToken": "04A1B2C3D4E580", "type": "ISO14443" }
}]

Response

Field	Type	Required	Description
`status`	RequestStartStopStatusEnumType	Required	Whether the station will attempt the start.
`statusInfo`	StatusInfoType	Optional	Reason code.
`transactionId`	string	Optional	The transaction id, when the station can supply it immediately.

json

[3, "19223201", {
  "status": "Accepted",
  "transactionId": "a1b2c3d4-0002"
}]

Values

RequestStartStopStatusEnumType

Value	Meaning
`Accepted`	The station will attempt it.
`Rejected`	The station will not.

Implementation notes

Use `remoteStartId` rather than timing. Matching a start request to a session by guessing which TransactionEvent arrived next is how apps attribute a session to the wrong user on a busy station.

Accepted is still only an acknowledgement. The session exists when a TransactionEvent with eventType: "Started" arrives.