UnlockConnector
Releases the cable lock on a connector, for a driver whose cable is stuck.
- Version
- OCPP 1.6
- Direction
- CSMS → Charge Point
- Feature profile
- Core
UnlockConnector also exists in OCPP 2.0.1, with a different payload. See the OCPP 2.0.1 version.
UnlockConnector exists for one support scenario: a driver cannot retrieve their cable. It releases the physical lock on a socket.
It is explicitly not a way to stop charging. The spec is clear that it should not be used to end a session — that is RemoteStopTransaction's job.
Request
| Field | Type | Required | Description |
|---|---|---|---|
connectorId | integer | Required | The connector to unlock. Must be greater than 0. |
[2, "19223201", "UnlockConnector", {
"connectorId": 1
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | UnlockStatus | Required | Result of the unlock attempt. |
[3, "19223201", {
"status": "Unlocked"
}]Values
UnlockStatus
| Value | Meaning |
|---|---|
Unlocked | The connector is now unlocked. |
UnlockFailed | The unlock was attempted and failed — usually a mechanical fault. |
NotSupported | The connector has no lock, as on a tethered cable. |
Implementation notes
`NotSupported` is normal for tethered chargers. A cable attached permanently to the unit has nothing to unlock. Treating this as a fault produces support tickets for working hardware.
If a transaction is running, the charge point should stop it before unlocking — expect a StopTransaction with reason: "UnlockCommand".
UnlockFailed usually means a physically jammed latch, and is one of the few OCPP responses that reliably requires a site visit.