Remote Control

Remote Control lets the CSMS drive the charger directly — starting and stopping transactions, unlocking the connector, changing availability, and requesting messages on demand. This is the OCPP 2.0.1 RemoteControl functional block, and the Remote Trigger profile plus core remote messages in OCPP 1.6.

Start and stop a transaction remotely

The CSMS can start and stop charging without the driver presenting a token. This is used when charging is triggered by an external system such as a mobile app or a management portal.

sequenceDiagram
    participant CSMS as Your CSMS
    participant CS as Enua Charging Station
    CSMS->>CS: RequestStartTransaction {idToken, remoteStartId}
    CS-->>CSMS: Response {status: Accepted}
    Note over CS: When preconditions are met,<br/>the charger starts the transaction
    CS->>CSMS: TransactionEvent(Started) / StartTransaction

Request start

• OCPP 2.0.1
• OCPP 1.6

[
  2,
  "19223201",
  "RequestStartTransaction",
  {
    "idToken": {
      "idToken": "<token>",
      "type": "Central"
    },
    "remoteStartId": 1234
  }
]

The charger responds with Accepted if it can start a transaction, otherwise Rejected:

[
  3,
  "681bbb0e-df67-5b23-90ed-a221fa345c12",
  {
    "status": "Accepted"
  }
]

Request stop

• OCPP 2.0.1
• OCPP 1.6

[
  2,
  "681bbb0e-df67-5b23-90ed-a221fa345c12",
  "RequestStopTransaction",
  {
    "transactionId": "a3e1b9c4-..."
  }
]

Note

Whether a remote start must be authorized first is controlled by AuthCtrlr.AuthorizeRemoteStart (2.0.1) / AuthorizeRemoteTxRequests (1.6). See Supported Configuration Keys.

Unlock connector

Asks the charger to release the connector lock. If a transaction is ongoing, the charger may deny the request; stop the transaction first if you need to force the connector open.

• OCPP 2.0.1
• OCPP 1.6

[
  2,
  "1efde99b-37ab-4f7b-b95d-c78432c3dacc",
  "UnlockConnector",
  {
    "evseId": 1,
    "connectorId": 1
  }
]

Response values:

Value	Description
Unlocked	Connector has been unlocked.
UnlockFailed	Failed to unlock the connector.
OngoingAuthorizedTransaction	Not unlocked because an authorized transaction is still ongoing.
UnknownConnector	The specified connector is not known by the Charging Station.

Note

The Permalock feature can keep the connector permanently locked, in which case an unlock request will not release it. See Custom Extensions → Permalock.

Change availability

The CSMS can change whether the charger accepts charging. A Charging Station is Operative when it is charging or ready to charge, and Inoperative when it does not allow charging. This can be used to implement, for example, a queue system.

• OCPP 2.0.1
• OCPP 1.6

[
  2,
  "681bbb0e-df67-5b23-90ed-a221fa345c12",
  "ChangeAvailability",
  {
    "operationalStatus": "Operative",
    "evse": { "id": 1 }
  }
]

Response values:

Value	Description
Accepted	Request has been accepted and will be executed.
Rejected	Request has not been accepted and will not be executed.
Scheduled	Request accepted; will be executed when transactions in progress have finished.

Trigger message

TriggerMessage instructs the charger to send a specific message immediately. Enua supports triggering the following messages:

• OCPP 2.0.1
• OCPP 1.6

Value	Description
BootNotification	Trigger a BootNotification.
Heartbeat	Trigger a Heartbeat.
StatusNotification	Trigger a StatusNotification.
TransactionEvent	Trigger a TransactionEvent.

[
  2,
  "12345",
  "TriggerMessage",
  {
    "requestedMessage": "StatusNotification",
    "evse": { "id": 1 }
  }
]

Warning

Only the messages listed above can be triggered. Requesting any other message (for example MeterValues, FirmwareStatusNotification, or a certificate-signing message) returns a NotImplemented error. This is a deliberate deviation from the standard's full trigger list — see Deviations from the Standard. The exact set may vary by charger model.