RemoteStart fails while local RFID works

How it presents

Symptom

RemoteStart fails while local RFID works — CSMS RemoteStartTransaction rejected or times out though a badge starts fine. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F06.

Root causes (by observed frequency)

1. #1 CSMS sending wrong connectorId on RemoteStart

   Local RFID uses different path

2. #2 Charger rejecting RemoteStart while Charging/Finishing
3. #3 idTag used by RemoteStart not authorized for remote
4. #4 Policy: RemoteStart disabled in configuration

Diagnostic procedure

1. 1. Compare RemoteStart payload connectorId vs local success connector

   Expected: Same gun

   Tools: CSMS

2. 2. Check configuration keys enabling RemoteStart

   Expected: Enabled

   Tools: GetConfiguration

3. 3. Retry RemoteStart only from Available/Preparing

   Expected: Accepted

   Tools: CSMS

4. 4. Verify remote idTag privileges in CSMS

   Expected: Authorized for remote

   Tools: CSMS admin

5. 5. Capture Rejected reason codes for OEM/CSMS escalation

   Tools: logs

The fix

When local RFID works, RemoteStart failures are CSMS/config/state — not the reader coil.

1. Fix connectorId mapping on the CSMS RemoteStart path. Document readings and scrubbed photos for OCPP-F06 before closing the ticket.
2. Enable RemoteStart in configuration if intentionally off.
3. Use a privileged idTag and correct state before retrying.
4. Do not replace RFID hardware when local badge already works.
5. Document Accepted RemoteStart with a validation session.