TriggerMessage

RemoteControl CSMS->CS OCPP 2.0.1

Sent by the CSMS to request the Charging Station to send a specific message. Useful for diagnostics, status checks, and forcing reports.

Quick Reference

Required Fields

requestedMessage MessageTriggerEnumType

Message type to trigger: BootNotification, LogStatusNotification, FirmwareStatusNotification, Heartbeat, MeterValues, SignChargingStationCertificate, SignV2GCertificate, StatusNotification, TransactionEvent, SignCombinedCertificate, PublishFirmwareStatusNotification

Optional Fields

evse EVSEType

Target EVSE for messages that are EVSE-specific (e.g., StatusNotification, MeterValues)

Example Payload

{
  "requestedMessage": "StatusNotification",
  "evse": {
    "id": 1,
    "connectorId": 1
  }
}

Example Full Frame

[
  2,
  "msg-001",
  "TriggerMessage",
  {
    "requestedMessage": "StatusNotification",
    "evse": {
      "id": 1,
      "connectorId": 1
    }
  }
]

Format: [MessageType, MessageId, Action, Payload]

Open in Builder Go to Validator

Overview

TriggerMessage lets the CSMS force the Charging Station to send a specific message on demand. This is extremely useful for diagnostics, validating integrations, and refreshing stale data.

When to Send

To refresh the status of an EVSE in the CSMS
To request an immediate firmware status update
To force a new BootNotification (e.g., after provisioning changes)
To request meter values for billing reconciliation

Expected Response

status: Accepted or Rejected (or NotImplemented)

After Accepted, the requested message will arrive asynchronously.

Key Differences from OCPP 1.6J

DiagnosticsStatusNotification is now LogStatusNotification
New triggers: SignChargingStationCertificate, SignV2GCertificate, PublishFirmwareStatusNotification
evse object replaces flat connectorId

Testing Tips

Trigger StatusNotification to verify the station reports its current status
Trigger Heartbeat to test that the Charging Station is responsive
Trigger MeterValues during an active session to get immediate readings

Common Errors

`TypeConstraintViolation`

Cause: requestedMessage uses a value not in MessageTriggerEnumType

Solution: Use one of the valid enum values. Note that DiagnosticsStatusNotification from 1.6J is replaced by LogStatusNotification.