Set Monitoring Level
Source: OCPP 2.0.1 Part 2 — Specification (Edition 2, 2022-12-15) — Section 1.54 (Messages); Use Case N05 — Set Monitoring Level (Functional Block N. Diagnostics)
Overview
The CSMS sends SetMonitoringLevelRequest to configure the severity threshold below which the Charging Station reports monitoring events. Only events with severity ≤ severity are sent.
The severity scale runs 0–9:
| Level | Meaning |
|---|---|
| 0 | Danger — lives potentially in danger; urgent action required. |
| 1 | Hardware Failure — CS unable to operate due to hardware issues. |
| 2 | System Failure — CS unable to operate due to software / minor hardware issues. |
| 3 | Critical — critical error, action required. |
| 4 | Error — non-urgent error, action required. |
| 5 | Alert — alert event (default for monitoring events). |
| 6 | Warning — action may be required. |
| 7 | Notice — unusual event, no immediate action. |
| 8 | Informational — regular operational event. |
| 9 | Debug — useful for developers; not for operations. |
Sequence Diagram
CSMS ──── SetMonitoringLevelRequest ────▶ Charging Station
(severity)
CSMS ◀─── SetMonitoringLevelResponse ──── Charging Station
(status, statusInfo?)
Initiator
CSMS → Charging Station
Fields
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| severity | integer (0..9) | 1..1 | Required. Only events with severity ≤ this value will be reported. |
| Field Name | Field Type | Card. | Description |
|---|---|---|---|
| status | GenericStatusEnumType | 1..1 | Required. Whether the CS could accept the request. |
| statusInfo | StatusInfoType | 0..1 | Optional. Detailed status information. |
GenericStatusEnumType values
Accepted, Rejected.
Examples
{
"severity": 4
}{
"status": "Accepted"
}Schema
Source:
schemas/SetMonitoringLevelRequest.json,schemas/SetMonitoringLevelResponse.json(OCPP 2.0.1 FINAL)