Status Notification
Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.59 (Messages); Use Case G01 — Status Notification (Functional Block G. Availability)
Overview
The Charging Station sends StatusNotificationRequest to inform the CSMS about a change of connector status (Available, Occupied, Reserved, Unavailable, Faulted).
In OCPP 2.0.1, status reporting is much simpler than in 1.6 — the connector status enum has only five values, error reporting has been moved to NotifyEvent (Device Management Monitoring), and connector identity is split into evseId + connectorId.
NOTE (from spec): This message might be removed in a future version of OCPP — it will be replaced by Device Management Monitoring events.
Sequence Diagram
Charging Station ──── StatusNotificationRequest ────▶ CSMS
(timestamp, connectorStatus, evseId, connectorId)
Charging Station ◀─── StatusNotificationResponse ──── CSMS
Initiator
Charging Station → CSMS
Fields
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| timestamp | dateTime | 1..1 | Required. The time for which the status is reported. |
| connectorStatus | ConnectorStatusEnumType | 1..1 | Required. The current status of the Connector. |
| evseId | integer | 1..1 | Required. The id of the EVSE the connector belongs to. |
| connectorId | integer | 1..1 | Required. The id of the connector within the EVSE. |
No fields are defined.
ConnectorStatusEnumType values
Available— Connector is available for use.Occupied— Connector is in use (any state where a transaction is or could be ongoing).Reserved— Connector is reserved for a specific user.Unavailable— Connector is not available (e.g. set unavailable byChangeAvailability, firmware update, etc.).Faulted— Connector has a fault.
Examples
{
"timestamp": "2026-04-27T12:34:56Z",
"connectorStatus": "Available",
"evseId": 1,
"connectorId": 1
}{}Schema
Source:
schemas/StatusNotificationRequest.json,schemas/StatusNotificationResponse.json(OCPP 2.0.1 FINAL)