OCPP 2.0.1 StatusNotification explained

In OCPP 2.0.1, StatusNotification still answers “what is this plug doing?” The map is simpler than 1.6: five connectorStatus values, plus an EVSE id.

OCPP 2.0.1 (OCA, 2020; IEC 63584) models a Charging Station → EVSE → Connector. Preparing / Charging / Finishing from 1.6 are reported as Occupied. Official specification download.

Index: 2.0.1 samples. Launch simulator.

When StatusNotification is triggered

  • After BootNotification is Accepted.
  • Cable in / out, session start / end, reservation, or a fault.
  • ChangeAvailability or TriggerMessage from the CSMS.

Sample message

Charging station → CSMS
JSON[
  2,
  "cf-st-201",
  "StatusNotification",
  {
    "timestamp": "2026-08-14T10:15:04.000Z",
    "connectorStatus": "Available",
    "evseId": 1,
    "connectorId": 1
  }
]
CSMS → charging station
JSON[
  3,
  "cf-st-201",
  {}
]

The five OCPP 2.0.1 connector statuses

connectorStatusPlain language
AvailableFree for a new driver.
OccupiedIn use — preparing, charging, suspended, or finishing.
ReservedHeld for a specific token.
UnavailableTaken out of service.
FaultedError — do not start a new session.

Chargeflux maps 1.6-style connector states onto these five when you run the OCPP 2.0.1 simulator. The 1.6 nine-state list stays on OCPP 1.6 connector status.

Related guides

FAQ

How many connector statuses does OCPP 2.0.1 have?

Five: Available, Occupied, Reserved, Unavailable, and Faulted. Preparing, Charging, and Finishing from 1.6 collapse into Occupied.

When is StatusNotification triggered in OCPP 2.0.1?

When an EVSE or connector changes state after boot, when a cable is plugged, when a session occupies the connector, and when the CSMS asks via TriggerMessage.

Last reviewed August 2026 · Chargeflux.io