ClearChargingProfile
Removes charging profiles matching a filter. Omitting everything still clears everything.
- Version
- OCPP 2.0.1
- Direction
- CSMS → Charge Point
- Functional block
- Smart Charging
ClearChargingProfile also exists in OCPP 1.6, with a different payload. See the OCPP 1.6 version.
Same filter-based deletion as 1.6, with the criteria moved into a nested chargingProfileCriteria object.
Request
| Field | Type | Required | Description |
|---|---|---|---|
chargingProfileId | integer | Optional | A specific profile id to remove. |
chargingProfileCriteria | ClearChargingProfileType | Optional | evseId, chargingProfilePurpose and stackLevel filters. |
json
[2, "19223201", "ClearChargingProfile", {
"chargingProfileCriteria": {
"evseId": 1,
"chargingProfilePurpose": "TxProfile"
}
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | ClearChargingProfileStatusEnumType | Required | Accepted or Unknown. |
statusInfo | StatusInfoType | Optional | Reason code. |
json
[3, "19223201", {
"status": "Accepted"
}]Implementation notes
An empty request clears every profile on the station, including the ChargingStationMaxProfile protecting the supply. Always send a filter unless that is genuinely intended.
Unknown means nothing matched — usually harmless, since a TxProfile for an ended session is already gone.