Reset
Reboots the charge point, either gracefully (Soft) or immediately (Hard).
- Version
- OCPP 1.6
- Direction
- CSMS → Charge Point
- Feature profile
- Core
Reset also exists in OCPP 2.0.1, with a different payload. See the OCPP 2.0.1 version.
Reset is the remote reboot. Soft asks the charge point to shut down cleanly — finish what it is doing, stop transactions properly, then restart. Hard restarts immediately, as though power had been cycled.
Either way the charger sends BootNotification when it comes back.
Request
| Field | Type | Required | Description |
|---|---|---|---|
type | ResetType | Required | Soft for a graceful restart, Hard for an immediate one. |
[2, "19223201", "Reset", {
"type": "Soft"
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | ResetStatus | Required | Whether the charge point will perform the reset. |
[3, "19223201", {
"status": "Accepted"
}]Values
ResetType
| Value | Meaning |
|---|---|
Soft | Graceful restart. Running transactions are stopped properly first. |
Hard | Immediate restart, equivalent to a power cycle. |
ResetStatus
| Value | Meaning |
|---|---|
Accepted | The reset will be performed. |
Rejected | The charge point refused. |
Implementation notes
A Soft reset should produce a StopTransaction with `reason: "SoftReset"` for any running session; a Hard reset should produce one with `reason: "HardReset"` — sent before the reboot if possible, or queued and delivered afterwards. Chargers that simply vanish leave orphaned transactions the CSMS has to time out.
Use Reset to apply a configuration change that returned RebootRequired.
Repeated Hard resets on a station with an active session are a common cause of meter-reading gaps in billing data.