Request the charger to send a specific OCPP message
POST/chargers/:id/actions/trigger-message
Sends an OCPP TriggerMessage command requesting the charger to initiate a specific OCPP message. Used for testing, diagnostics, and forcing status updates.
Use Cases:
- Request fresh meter values for real-time updates
- Force status updates for dashboard synchronization
- Test OCPP message handling and compliance
- Trigger diagnostics or firmware status messages
- Refresh heartbeat or boot notification data
Common Triggered Messages:
- BootNotification: Refresh charger metadata and capabilities
- StatusNotification: Get current connector status
- Heartbeat: Verify connectivity and refresh timestamp
- MeterValues: Request immediate meter value sample
- DiagnosticsStatusNotification: Check diagnostics upload progress
- FirmwareStatusNotification: Monitor firmware update status
Command Behavior:
- Charger sends requested message asynchronously
- Message may arrive several seconds after command accepted
- Not all chargers support all message types
- Some messages require specific charger states
- Optional connector parameter for connector-specific messages
Best Practices:
- Use for debugging and diagnostics, not production polling
- StatusNotification useful for real-time connector state refresh
- MeterValues triggers for immediate power/energy readings
- Verify charger supports the requested message type first
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 500
Standard success response for actions
Standard error response format
Standard error response format
Standard error response format
Standard error response format
Standard error response format