Skip to main content

Send direct OCPP RemoteStopTransaction command

POST 
/chargers/:id/ocpp/remote-stop

Sends a raw OCPP RemoteStopTransaction command directly to the charger, bypassing GridLink session finalization and state reconciliation. For testing and emergency use only.

When to Use:

  • Protocol Testing: Verify OCPP command handling
  • Emergency Stop: Force stop when GridLink session management unavailable
  • Debugging: Isolate charger stop behavior from GridLink logic
  • Recovery: Stop orphaned transactions without GridLink session record

What Gets Bypassed:

  • ❌ Session finalization in GridLink database
  • ❌ Final metrics calculation (energy, cost, duration)
  • ❌ Event publishing and webhook notifications
  • ❌ State reconciliation and cleanup
  • ❌ Billing record finalization

What Still Happens:

  • ✅ OCPP command sent to charger
  • ✅ Charger stops power delivery
  • ✅ Charger sends StopTransaction confirmation
  • ✅ Basic OCPP message flow preserved
  • ✅ Connector released (depends on charger)

Risks:

  • Sessions may remain in "active" state in GridLink database
  • Final energy values not recorded for billing
  • Metrics and analytics incomplete
  • Dashboard may show stale session state
  • Manual cleanup or reconciliation may be required
danger

WARNING: This endpoint bypasses session finalization and state reconciliation. Use ONLY for testing or emergency situations. For production use, ALWAYS use /actions/remote-stop.

warning

Sessions stopped via this endpoint may not be properly finalized in GridLink. Manual reconciliation may be needed for accurate billing and reporting.

Request​

Responses​

Standard success response for actions