ReportChargingProfiles

Delivers the installed charging profiles requested by GetChargingProfiles.

Version: OCPP 2.0.1
Direction: Charge Point → CSMS
Functional block: Smart Charging

The reply channel for GetChargingProfiles. Large sets are split across messages, with tbc marking that more are coming.

Request

Field	Type	Required	Description
`requestId`	integer	Required	Matches the GetChargingProfiles request.
`chargingLimitSource`	ChargingLimitSourceEnumType	Required	Where these profiles came from: `EMS`, `Other`, `SO` or `CSO`.
`chargingProfile`	ChargingProfileType[]	Required	The profiles.
`evseId`	integer	Required	The EVSE they apply to.
`tbc`	boolean	Optional	True when more parts follow.

json

[2, "19223201", "ReportChargingProfiles", {
  "requestId": 701,
  "chargingLimitSource": "CSO",
  "evseId": 1,
  "chargingProfile": [{
    "id": 100,
    "stackLevel": 0,
    "chargingProfilePurpose": "TxDefaultProfile",
    "chargingProfileKind": "Absolute",
    "chargingSchedule": [{ "id": 1, "chargingRateUnit": "A",
      "chargingSchedulePeriod": [{ "startPeriod": 0, "limit": 32.0 }] }]
  }]
}]

Response

No fields — the payload is an empty object {}.

json

[3, "19223201", {}]

Implementation notes

Accumulate until tbc is false, as with NotifyReport.

chargingLimitSource tells you whether a profile came from you (CSO) or from an external energy management system (EMS) — profiles you did not install are not bugs.