Stop a charging session (with policy evaluation)
POST/chargers/:id/actions/remote-stop
Stops an active charging session using GridLink's full workflow with proper session finalization and state reconciliation. This is the recommended way to stop charging.
Use Cases:
- Stop charging remotely via mobile app or dashboard
- End sessions when vehicles reach target charge level
- Terminate sessions for time-based billing periods
- Emergency stop for safety or grid load management
- Stop sessions as part of automated fleet workflows
What Happens:
- Session Lookup: Identifies active session by transaction ID or charger/connector
- OCPP Command: Sends RemoteStopTransaction to charger
- Session Finalization: Waits for StopTransaction confirmation from charger
- Metrics Calculation: Calculates final energy, cost, duration
- Event Publishing: Emits session stop events for webhooks/integrations
- State Reconciliation: Updates connector availability and session status
Stop Behavior:
- Charger ends power delivery to vehicle
- Cable remains locked until physically removed (depends on charger)
- Final meter values recorded for billing
- Session marked as completed in GridLink database
- Command queues if charger offline
Best Practices:
- Use transaction ID when available for precise targeting
- Allow 5-10 seconds for graceful stop completion
- Monitor webhooks for stop confirmation
- Verify final energy values for billing accuracy
info
This endpoint ensures proper session finalization and state reconciliation. It updates GridLink database, calculates metrics, and publishes events.
tip
For testing or protocol debugging, use the OCPP Direct endpoint (/ocpp/remote-stop). For production use, always use this managed endpoint.
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