ConnectorLockFailure: what it means and what to do
"Failure to lock or unlock connector" (OCPP 1.6, §7.6). If the lock fails at the start, OCPP 2.0.1 says the charging station shall not start charging (OCPP 2.0.1, G05).
What it means
The code covers both directions.
A lock that will not engage stops a session from starting. A lock that will not release leaves the driver unable to unplug after the session.
The retention lock holds an inserted plug in the socket, both to prevent unplugging under load and to prevent cable theft (OCPP 2.0.1 Appendices, §3.2.17). Not every connector has one: in OCPP 1.6 a charger without a connector lock answers UnlockConnector with NotSupported (OCPP 1.6, §7.46), and in OCPP 2.0.1 a connector with no lock or a manual lock should answer with the error NotSupported (OCPP 2.0.1, F05).
In OCPP 2.0.1
StatusNotification carries no error code in OCPP 2.0.1 (OCPP 2.0.1, §1.59.1).
Instead, the charging station sends a NotifyEvent for the ConnectorPlugRetentionLock component with variable Problem set to true, and does not start the transaction. The specification adds that a lock failure can also be reported when unlocking fails (OCPP 2.0.1, G05).
The same component can report Tries, the retries taken on the last attempt, and Tripped, for example a blown stall-protection fuse (OCPP 2.0.1 Appendices, §3.2.17).
UnlockConnector behaves differently between versions. In OCPP 1.6, if a transaction is in progress on that connector, the charger shall finish the transaction first (OCPP 1.6, §5.18). In OCPP 2.0.1 it shall not unlock or stop the transaction, and answers OngoingAuthorizedTransaction. Its other answers are Unlocked, UnlockFailed and UnknownConnector (OCPP 2.0.1, F05, §3.83).
Likely causes
Tension on the cable.
The specification names it as the usual reason a connector does not unlock (OCPP 2.0.1, F05).
Beyond that, OCPP lists no causes. The detail is in vendorErrorCode and info (OCPP 1.6, §6.47) or, in OCPP 2.0.1, in the lock's Tries and Tripped variables.
First three checks
1.
Lock or unlock? A fault right after plug-in is a lock failure; a fault after the session stopped is an unlock failure.
2.
One connector or several? Note how often it repeats on the same connector; the manufacturer will ask.
3.
In OCPP 2.0.1, read the ConnectorPlugRetentionLock Tries and Tripped variables (OCPP 2.0.1 Appendices, §3.2.17).
What to do
What to tell the customer
"The charger couldn't lock the cable, so it didn't start charging.
Please unplug, plug the cable back in fully and try again. If it still doesn't work, we'll check it remotely."
A detection rule to start from
On ConnectorLockFailure (in OCPP 2.0.1, ConnectorPlugRetentionLock Problem = true): if an UnlockConnector returned UnlockFailed, open a high-priority ticket; if the events repeat on the same connector, open a ticket with the manufacturer.
Sources
- Open Charge Alliance (2017). Open Charge Point Protocol 1.6, edition 2 (opens in a new tab). §5.18 Unlock Connector, §6.47 StatusNotification.req, §7.6 ChargePointErrorCode, §7.46 UnlockStatus; accessed 2026-10-22.
- Open Charge Alliance (2025). OCPP 2.0.1 Edition 4, Part 2 – Specification (opens in a new tab). §1.59.1 StatusNotificationRequest, §3.83 UnlockStatusEnumType, F05 Remotely Unlock Connector (incl. F05.FR.02, F05.FR.07), G05 Lock Failure; accessed 2026-10-22.
- Open Charge Alliance (2025). OCPP 2.0.1 Part 2 – Appendices, v1.5 (opens in a new tab). §3.2.17 ConnectorPlugRetentionLock; accessed 2026-10-22.
Talk to us about your chargers
- Tell us about your network.
- Meet a Kinethra specialist.
- Get your chargers live on Kinethra.
- 40,000+ chargers onlineOn the Kinethra platform.
- OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
- No commission on charging revenueKinethra takes none.
We use your details to answer your request. See our Privacy Policy for details.