NotifyMonitoringReport
Delivers the list of installed monitors requested by GetMonitoringReport.
- Version
- OCPP 2.0.1
- Direction
- Charge Point → CSMS
- Functional block
- Diagnostics
Split across parts with seqNo and tbc, like NotifyReport and NotifyEvent.
Request
| Field | Type | Required | Description |
|---|---|---|---|
requestId | integer | Required | Matches the GetMonitoringReport request. |
generatedAt | dateTime | Required | When this part was generated. |
seqNo | integer | Required | Part number. |
monitor | MonitoringDataType[] | Optional | The monitors, with their component, variable and settings. |
tbc | boolean | Optional | True when more parts follow. |
json
[2, "19223201", "NotifyMonitoringReport", {
"requestId": 901,
"generatedAt": "2026-09-09T10:50:00Z",
"seqNo": 0,
"monitor": [{
"component": { "name": "TemperatureSensor", "evse": { "id": 1 } },
"variable": { "name": "Temperature" },
"variableMonitoring": [{ "id": 55, "transaction": false, "value": 80.0, "type": "UpperThreshold", "severity": 4 }]
}]
}]Response
No fields — the payload is an empty object {}.
json
[3, "19223201", {}]Implementation notes
This is how you recover monitor ids when the CSMS has lost its own record of them.