ClearCache
Empties the charge point's local authorization cache.
- Version
- OCPP 1.6
- Direction
- CSMS → Charge Point
- Feature profile
- Core
ClearCache also exists in OCPP 2.0.1, with a different payload. See the OCPP 2.0.1 version.
The authorization cache holds the results of previous Authorize calls so a charger can keep working while offline. ClearCache empties it.
This is not the same thing as the Local Authorization List, which is managed explicitly with SendLocalList. The cache fills itself; the list is pushed by the operator.
Request
No fields — the payload is an empty object {}.
[2, "19223201", "ClearCache", {}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | ClearCacheStatus | Required | Whether the cache was cleared. |
[3, "19223201", {
"status": "Accepted"
}]Values
ClearCacheStatus
| Value | Meaning |
|---|---|
Accepted | The cache was cleared. |
Rejected | The charge point could not clear the cache — commonly because caching is disabled. |
Implementation notes
A charger with AuthorizationCacheEnabled set to false will answer Rejected. That is correct behaviour, not a fault.
Clearing the cache on a charger that is currently offline removes its ability to authorize anyone until it reconnects. Sequence maintenance accordingly.