ChangeAvailability
Takes a connector, or a whole charge point, in or out of service.
- Version
- OCPP 1.6
- Direction
- CSMS → Charge Point
- Feature profile
- Core
ChangeAvailability also exists in OCPP 2.0.1, with a different payload. See the OCPP 2.0.1 version.
ChangeAvailability is how an operator marks hardware as unavailable without powering it down — for maintenance, for a decommissioned socket, or to drain a station before service.
Setting connectorId: 0 applies to the entire charge point and every connector on it.
Request
| Field | Type | Required | Description |
|---|---|---|---|
connectorId | integer | Required | Connector to change. 0 means the whole charge point. |
type | AvailabilityType | Required | Operative to bring into service, Inoperative to take out. |
[2, "19223201", "ChangeAvailability", {
"connectorId": 1,
"type": "Inoperative"
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | AvailabilityStatus | Required | Whether the change took effect immediately. |
[3, "19223201", {
"status": "Scheduled"
}]Values
AvailabilityType
| Value | Meaning |
|---|---|
Operative | In service and available. |
Inoperative | Out of service. |
AvailabilityStatus
| Value | Meaning |
|---|---|
Accepted | The change took effect immediately. |
Rejected | The charge point refused the change. |
Scheduled | A transaction is running. The change applies once it ends. |
Implementation notes
`Scheduled` is not `Accepted`. It means a session is in progress and the connector will become unavailable later. A CSMS that treats the two identically will show a connector as out of service while it is still charging a car.
The change must survive a reboot. A charger that comes back Operative after being set Inoperative is non-conformant, and produces sessions on hardware that was supposed to be locked out.
Expect a StatusNotification with status Unavailable to follow once the change actually applies.