UnlockConnector

RemoteControl CSMS->CS OCPP 2.0.1

Sent by the CSMS to unlock a connector on a specific EVSE, allowing the cable to be removed.

Quick Reference

Required Fields

evseId integer

ID of the EVSE containing the connector to unlock

connectorId integer

ID of the connector to unlock

Example Payload

{
  "evseId": 1,
  "connectorId": 1
}

Example Full Frame

[
  2,
  "msg-001",
  "UnlockConnector",
  {
    "evseId": 1,
    "connectorId": 1
  }
]

Format: [MessageType, MessageId, Action, Payload]

Open in Builder Go to Validator

Overview

UnlockConnector instructs the Charging Station to release the mechanical lock on a connector, allowing the cable to be unplugged. This is typically used when a driver is unable to unlock the cable through normal means.

When to Send

When a driver reports being unable to unplug the cable
As part of a remote stop + unlock flow
For emergency cable release

Expected Response

status: Unlocked, UnlockFailed, or OngoingAuthorizedTransaction

OngoingAuthorizedTransaction means the connector cannot be unlocked while a transaction is in progress.

Usage Notes

Stop the transaction first with RequestStopTransaction before unlocking
Not all hardware supports remote unlock — some stations respond with UnlockFailed

Testing Tips

Test unlock during an active transaction (expect OngoingAuthorizedTransaction)
Test unlock on idle connector (expect Unlocked)
Test with hardware that does not support remote unlock (expect UnlockFailed)

Common Errors

`TypeConstraintViolation`

Cause: Only connectorId sent without evseId

Solution: In OCPP 2.0.1, both evseId and connectorId are required