ReservationStatusUpdate
Tells the CSMS that a reservation expired or became unusable.
- Version
- OCPP 2.0.1
- Direction
- Charge Point → CSMS
- Functional block
- Reservation
New in 2.0.1, and it closes a real 1.6 gap. In 1.6 a reservation could lapse silently, leaving the CSMS believing a connector was held when it was not.
Now the station reports it.
Request
| Field | Type | Required | Description |
|---|---|---|---|
reservationId | integer | Required | The reservation concerned. |
reservationUpdateStatus | ReservationUpdateStatusEnumType | Required | What happened to it. |
json
[2, "19223201", "ReservationStatusUpdate", {
"reservationId": 77,
"reservationUpdateStatus": "Expired"
}]Response
No fields — the payload is an empty object {}.
json
[3, "19223201", {}]Values
ReservationUpdateStatusEnumType
| Value | Meaning |
|---|---|
Expired | The reservation passed its expiry time. |
Removed | The reservation was removed at the station. |
Implementation notes
Handle this, or your reservation state drifts out of sync exactly as it did in 1.6 — the message only helps if the CSMS acts on it.