Unlock Connector
Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.62 (Messages); Use Case F05 — Remotely Unlock Connector (Functional Block F. RemoteControl)
Overview
The CSMS sends UnlockConnectorRequest to ask the Charging Station to unlock a specific connector. Used to help an EV driver whose cable retention has malfunctioned. If a transaction is in progress on the connector, the CS finishes the transaction first.
IMPORTANT (from spec): This message is intended only for unlocking the cable retention lock on the connector — not for unlocking a connector access door. To remotely stop a transaction, use
RequestStopTransaction.
Sequence Diagram
CSMS ──── UnlockConnectorRequest ────▶ Charging Station
(evseId, connectorId)
CSMS ◀─── UnlockConnectorResponse ──── Charging Station
(status, statusInfo?)
Initiator
CSMS → Charging Station
Fields
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| evseId | integer | 1..1 | Required. EVSE for which a connector needs to be unlocked. |
| connectorId | integer | 1..1 | Required. Connector that needs to be unlocked. |
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| status | UnlockStatusEnumType | 1..1 | Required. Whether the CS has unlocked the connector. |
| statusInfo | StatusInfoType | 0..1 | Optional. Detailed status information. |
UnlockStatusEnumType values
Unlocked, UnlockFailed, OngoingAuthorizedTransaction, UnknownConnector.
Examples
{
"evseId": 1,
"connectorId": 1
}{
"status": "Unlocked"
}Schema
Source:
schemas/UnlockConnectorRequest.json,schemas/UnlockConnectorResponse.json(OCPP 2.0.1 FINAL)