UnlockConnector
Releases the cable lock on a connector, for a driver whose cable is stuck.
- Version
- OCPP 2.0.1
- Direction
- CSMS → Charge Point
- Functional block
- Remote Control
UnlockConnector also exists in OCPP 1.6, with a different payload. See the OCPP 1.6 version.
Same support scenario as 1.6, addressed by EVSE and connector. Still explicitly not a way to stop charging.
Request
| Field | Type | Required | Description |
|---|---|---|---|
evseId | integer | Required | The EVSE. |
connectorId | integer | Required | The connector within that EVSE. |
json
[2, "19223201", "UnlockConnector", {
"evseId": 1,
"connectorId": 1
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | UnlockStatusEnumType | Required | Result of the unlock attempt. |
statusInfo | StatusInfoType | Optional | Reason code. |
json
[3, "19223201", {
"status": "Unlocked"
}]Values
UnlockStatusEnumType
| Value | Meaning |
|---|---|
Unlocked | The connector is unlocked. |
UnlockFailed | The attempt failed, usually a mechanical fault. |
OngoingAuthorizedTransaction | Refused: an authorized transaction is running. |
UnknownConnector | No such connector on this station. |
Implementation notes
`NotSupported` is gone; two new statuses replace it. OngoingAuthorizedTransaction is a refusal rather than a failure — stop the transaction first. UnknownConnector means your EVSE/connector addressing is wrong.
Tethered stations have nothing to unlock, and answer UnlockFailed rather than the 1.6 NotSupported.