ChangeAvailability rejected while charging

How it presents

Symptom

ChangeAvailability rejected while charging — ops tries to set Inoperative mid-session and charger correctly rejects, or rejects even when idle due to state desync. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F13.

Root causes (by observed frequency)

1. #1 CSMS sending ChangeAvailability during Active/Charging

   Expected reject

2. #2 Charger state machine thinks still Charging after stop
3. #3 Wrong connectorId targeted
4. #4 OEM requiring local finish before Inoperative

Diagnostic procedure

1. 1. Check connector status at reject time

   Expected: Charging vs Available

   Tools: CSMS

2. 2. Stop session cleanly; retry ChangeAvailability

   Expected: Accepted when idle

   Tools: CSMS

3. 3. Verify connectorId in the ChangeAvailability call

   Expected: Correct gun

   Tools: CSMS

4. 4. If idle but still rejecting, capture status machine and OEM reset

   Tools: OEM

5. 5. Train ops not to force Inoperative mid-charge without Stop

   Tools: runbook

The fix

Most ChangeAvailability rejects are state/timing — stop first, then mark Inoperative.

1. Stop the transaction before setting Inoperative. Document readings and scrubbed photos for OCPP-F13 before closing the ticket.
2. Target the correct connectorId. Document readings and scrubbed photos for OCPP-F13 before closing the ticket.
3. Clear stuck Charging state with OEM procedure if needed.
4. Update ops runbooks to avoid mid-session availability fights.
5. Confirm Accepted ChangeAvailability and physical unavailability.