TriggerMessage
Asks the station to send a specific message now rather than on its own schedule.
- Version
- OCPP 2.0.1
- Direction
- CSMS → Charge Point
- Functional block
- Remote Control
TriggerMessage also exists in OCPP 1.6, with a different payload. See the OCPP 1.6 version.
Same idea as 1.6, with a longer list of triggerable messages reflecting 2.0.1's larger message set.
Request
| Field | Type | Required | Description |
|---|---|---|---|
requestedMessage | MessageTriggerEnumType | Required | Which message to request. |
evse | EVSEType | Optional | Which EVSE and connector, for per-EVSE messages. |
json
[2, "19223201", "TriggerMessage", {
"requestedMessage": "StatusNotification",
"evse": { "id": 1, "connectorId": 1 }
}]Response
| Field | Type | Required | Description |
|---|---|---|---|
status | TriggerMessageStatusEnumType | Required | Whether the station will send it. |
statusInfo | StatusInfoType | Optional | Reason code. |
json
[3, "19223201", {
"status": "Accepted"
}]Values
MessageTriggerEnumType
| Value | Meaning |
|---|---|
BootNotification | Sent with reason: "Triggered". |
Heartbeat | A heartbeat. |
StatusNotification | Connector status. |
MeterValues | A meter sample. |
TransactionEvent | A transaction event. |
LogStatusNotification | Log upload status. |
FirmwareStatusNotification | Firmware update status. |
SignChargingStationCertificate | Trigger a SignCertificate for the station certificate. |
SignV2GCertificate | Trigger a SignCertificate for the V2G certificate. |
PublishFirmwareStatusNotification | Local firmware publishing status. |
TriggerMessageStatusEnumType
| Value | Meaning |
|---|---|
Accepted | The station will send it. |
Rejected | It will not. |
NotImplemented | This particular message cannot be triggered on this station. |
Implementation notes
The triggered message arrives as a separate request. Accepted only means it is coming.
Triggering StatusNotification on every connector is the standard way to resynchronise after a CSMS restart.