StatusNotifications 2.0.1
π StatusNotification: OCPP 1.6 vs 2.0.1
Purpose: The StatusNotification message informs the backend system about the current status of a connector (e.g. Available, Charging, Faulted).
π§Ύ Key Differences
Feature OCPP 1.6 OCPP 2.0.1
Message Direction Charge Point β CSMS EVSE β CSMS
Context Sent per connector Sent per EVSE (new structure)
Connector Structure connectorId (flat model) Hierarchical: evseId + connectorId
Status Values Fixed enums Expanded enums + more granular statuses
Timestamp Optional Mandatory (more precise tracking) Extensibility Limited Highly extensible with richer diagnostics
β
Example Use Cases
OCPP 1.6: Suitable for simpler infrastructures with basic status reporting.
OCPP 2.0.1: Better for smart charging, richer diagnostics, and advanced monitoring in complex EVSE deployments.
2.0.1 Status Notification
{
"timestamp":"2025-05-14T13:31:50.629Z",
"connectorStatus":"Faulted",
"evseId":1,
"connectorId":1
},
Attributes
timestamp string
The Date and Time of the message
connectorStatus string
Status reported by the connector
evseId string
The Id of the EVSE
connectorId string
The Id of the connector
1.6 Status Notification
{
"timestamp":"2025-05-14T13:31:50.629Z",
"status":"Faulted",
"errorCode":"NoError",
"evseId":1,
"connectorId":1
},
Attributes
timestamp string
The Date and Time of the message
Status string
Status reported by the connector
errorCode string
Reported vendor error code
evseId string
The Id of the EVSE
connectorId string
The Id of the connector
Updated 3 days ago