StopTransaction id mismatch

How it presents

Symptom

StopTransaction id mismatch — stop fails or CSMS alarms because transactionId/idTag does not match the open transaction. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F11.

Root causes (by observed frequency)

1. #1 Charger and CSMS disagree on transactionId after reconnect

   Half-open session

2. #2 Second Start without clean Stop leaving orphan transactions
3. #3 Clock/idTag change mid-session confusing Stop
4. #4 CSMS bug on reconnect replay

Diagnostic procedure

1. 1. List open transactions for that chargeBoxId in CSMS

   Expected: Orphans?

   Tools: CSMS

2. 2. Compare charger local transactionId vs CSMS

   Expected: Match or mismatch

   Tools: HMI/CSMS

3. 3. Perform OEM/CSMS guided orphan cleanup

   Expected: No open ghosts

   Tools: admin

4. 4. Reproduce a clean start→stop with stable websocket

   Expected: Clean StopTransaction.conf

   Tools: test

5. 5. Escalate if mismatch persists on stable path

   Tools: both vendors

The fix

StopTransaction mismatches are session-state/CSMS sync — clean orphans first.

1. Clear orphan transactions before blaming connector hardware.
2. Stabilize reconnect/NAT so Start/Stop stay paired. Document readings and scrubbed photos for OCPP-F11 before closing the ticket.
3. Avoid double-starts without a confirmed Stop. Document readings and scrubbed photos for OCPP-F11 before closing the ticket.
4. Use OEM tools to resync transaction state if provided. Document readings and scrubbed photos for OCPP-F11 before closing the ticket.
5. Validate a full start/stop with matching IDs in CSMS. Document readings and scrubbed photos for OCPP-F11 before closing the ticket.