Reset

{
  "type": "Soft"
}

[
  2,
  "msg-001",
  "Reset",
  {
    "type": "Soft"
  }
]

Overview

The Reset command instructs the Charge Point to reboot. This is useful for applying configuration changes, recovering from errors, or performing maintenance.

When to Send

• After firmware update
• After critical configuration changes
• To recover from error states
• For scheduled maintenance
• To clear caches or temporary state

Reset Types

Soft Reset:

• Graceful shutdown and restart
• Stops active transactions with proper StopTransaction messages
• Saves state before rebooting
• Waits for safe shutdown point
• Preferred for normal operations

Hard Reset:

• Immediate forced reboot
• May interrupt active transactions
• Similar to pulling power plug
• Use only when soft reset fails or emergency situations

Expected Response

The CP responds with:

• status: Accepted or Rejected

What Happens After Acceptance

1. CP sends response immediately
2. CP stops accepting new transactions
3. For Soft: CP gracefully stops active transactions
4. For Hard: CP immediately reboots
5. CP reboots
6. CP sends BootNotification after restart

Usage Notes

• Accepted response doesn’t mean reset completed, just initiated
• Active transactions may be interrupted (especially Hard reset)
• CP sends new BootNotification after reboot
• Some CPs may delay Soft reset until transactions complete

Best Practices

1. Prefer Soft - Use Soft reset unless necessary
2. Check transactions - Verify no critical transactions before reset
3. Notify users - Warn users before resetting (if possible)
4. Monitor reboot - Watch for BootNotification after reset
5. Transaction handling - Active sessions may need reconciliation after Hard reset

Testing Tips

• Test Soft reset with no active transactions
• Test Soft reset with active transaction
• Test Hard reset
• Test rejection scenarios (if implemented)
• Verify BootNotification after reset
• Check transaction state after reset