Skip to main content

Send direct OCPP RemoteStartTransaction command

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

Sends a raw OCPP RemoteStartTransaction command directly to the charger, bypassing all GridLink policies, authorization checks, and session management. For testing and emergency use only.

When to Use:

  • Protocol Testing: Verify OCPP command handling and charger compliance
  • Emergency Bypass: Start charging when policy system is unavailable
  • Debugging: Isolate charger behavior from GridLink logic
  • Integration Testing: Test OCPP flows independently

What Gets Bypassed:

  • ❌ Authorization and ID tag validation
  • ❌ Policy evaluation (load limits, reservations, access rules)
  • ❌ Session creation in GridLink database
  • ❌ Event publishing and webhook notifications
  • ❌ Charging profile validation
  • ❌ Load balancing and power management

What Still Happens:

  • ✅ OCPP command sent to charger hardware
  • ✅ Charger performs local authorization (if configured)
  • ✅ Charger creates local transaction
  • ✅ Meter values sent to GridLink
  • ✅ Basic OCPP message flow preserved

Risks:

  • Sessions started this way have no GridLink transaction record initially
  • Billing and reporting may be incomplete or inaccurate
  • Load balancing and power limits not enforced
  • Policy violations possible (unauthorized users, exceeded limits)
  • Session state reconciliation may fail
danger

WARNING: This endpoint bypasses ALL GridLink safety checks, policies, and session management. Use ONLY for controlled testing or emergency situations. For production use, ALWAYS use /actions/remote-start.

warning

Sessions started via this endpoint may not appear in GridLink dashboards initially. They will be reconciled when the charger sends StartTransaction confirmation.

Request​

Responses​

Standard success response for actions