TriggerMessage

Asks the charge point to send a specific message now, rather than waiting for its schedule.

Version: OCPP 1.6
Direction: CSMS → Charge Point
Feature profile: Remote Trigger

TriggerMessage also exists in OCPP 2.0.1, with a different payload. See the OCPP 2.0.1 version.

TriggerMessage is the diagnostic poke. Instead of waiting for the next heartbeat or meter sample, the CSMS asks for one immediately.

It is the correct way to resynchronise after a CSMS restart: trigger StatusNotification on every connector and you have current state without waiting.

Request

Field	Type	Required	Description
`requestedMessage`	MessageTrigger	Required	Which message to request.
`connectorId`	integer	Optional	Which connector it applies to, for messages that are per-connector.

json

[2, "19223201", "TriggerMessage", {
  "requestedMessage": "StatusNotification",
  "connectorId": 1
}]

Response

Field	Type	Required	Description
`status`	TriggerMessageStatus	Required	Whether the charge point will send the requested message.

json

[3, "19223201", {
  "status": "Accepted"
}]

Values

MessageTrigger

Value	Meaning
`BootNotification`	Ask for a fresh BootNotification.
`Heartbeat`	Ask for a Heartbeat.
`StatusNotification`	Ask for connector status.
`MeterValues`	Ask for a meter sample.
`FirmwareStatusNotification`	Ask for firmware update status.
`DiagnosticsStatusNotification`	Ask for diagnostics upload status.

TriggerMessageStatus

Value	Meaning
`Accepted`	The charge point will send the message.
`Rejected`	The charge point will not send it.
`NotImplemented`	The charge point does not support triggering this particular message.

Implementation notes

The triggered message arrives as a separate request, not in this response. Accepted only means it is coming.

NotImplemented is per-message: a charger may support triggering Heartbeat but not MeterValues. Probe rather than assume.

Triggering BootNotification does not reset the charge point. It only asks for the message.