OCPP 1.6 connector status explained

Connector status is what the charger reports in StatusNotification: is this plug free, charging, or faulted. Maps and support tools usually paint from these frames, not from the last StartTransaction.

Edition 2 defines nine statuses. There is no EVSE object in 1.6 — only a Charge Point and numbered connectors. connectorId 0 is the station as a whole. Outlets start at 1. Names are in the official 1.6 spec. See also the 1.6J sample list.

When StatusNotification is triggered

• After BootNotification is Accepted — one report per connector (often Available).
• When a cable is plugged or unplugged.
• When authorization succeeds and the connector moves to Preparing.
• When energy starts (Charging) or pauses (SuspendedEV / SuspendedEVSE).
• When a session ends (Finishing, then Available).
• When a fault appears or clears.
• When the CSMS sends ChangeAvailability or TriggerMessage for StatusNotification.

StatusNotification sample message

JSON[
  2,
  "a7k2-st-01",
  "StatusNotification",
  {
    "connectorId": 1,
    "status": "Available",
    "errorCode": "NoError",
    "timestamp": "2026-08-14T10:15:04.000Z"
  }
]

JSON[
  3,
  "a7k2-st-01",
  {}
]

The success reply is an empty object. The useful data is on the CALL. errorCode is still required even when nothing is wrong — use NoError.

The nine OCPP 1.6 connector statuses

Sample: Preparing then Charging

JSON[
  2,
  "a7k2-st-02",
  "StatusNotification",
  {
    "connectorId": 1,
    "status": "Preparing",
    "errorCode": "NoError",
    "timestamp": "2026-08-14T10:15:50.000Z"
  }
]

JSON[
  2,
  "a7k2-st-03",
  "StatusNotification",
  {
    "connectorId": 1,
    "status": "Charging",
    "errorCode": "NoError",
    "timestamp": "2026-08-14T10:16:02.000Z"
  }
]

These status frames sit next to Authorize / StartTransaction — they do not replace them. Billing still needs the transaction pair and MeterValues.

Sample: a fault

JSON[
  2,
  "a7k2-st-err",
  "StatusNotification",
  {
    "connectorId": 1,
    "status": "Faulted",
    "errorCode": "OverCurrentFailure",
    "info": "Input current exceeded configured limit",
    "timestamp": "2026-08-14T10:18:44.000Z"
  }
]

Common error codes include NoError, ConnectorLockFailure, GroundFailure, OverVoltage, UnderVoltage, HighTemperature, and OtherError. Do not invent codes — CSMS filters depend on the official list.

How Chargeflux keeps status aligned

The OCPP 1.6 simulator moves each connector through a simplified path that stays aligned with the frames it emits:

Available → Preparing → Charging → Finishing → Available

You cannot start a second transaction on a busy connector, or charge a Faulted / Unavailable plug. When a control is disabled, the UI says why. That is deliberate: a virtual charge point should not emit impossible combinations.

Related

• OCPP 1.6J sample messages — Every core message, when it fires, and a full session sample.
• BootNotification — The charger introduces itself. Heartbeat keeps the line alive.
• Charging session messages — Authorize, StartTransaction, MeterValues, and StopTransaction.
• RemoteStartTransaction — How the office starts or stops a session from the CSMS.

• 2.0.1 StatusNotification uses five statuses and an EVSE id
• Launch simulator

FAQ

Last reviewed August 2026 · Chargeflux.io