DataTransfer vendorId rejected

How it presents

Symptom

DataTransfer vendorId rejected — OEM vendor messages fail while core OCPP profile still works, breaking advanced diagnostics or PnC helpers. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F10.

Root causes (by observed frequency)

1. #1 CSMS not allowing that vendorId/messageId

   Profile mismatch

2. #2 Charger firmware expecting a newer vendor schema
3. #3 Typos in custom DataTransfer integrations
4. #4 Security policy blocking vendor payloads

Diagnostic procedure

1. 1. Capture DataTransfer.conf status and vendorId/messageId

   Expected: Rejected vs UnknownVendorId

   Tools: CSMS

2. 2. Confirm CSMS vendor allowlist for this OEM

   Expected: Vendor permitted

   Tools: CSMS admin

3. 3. Align charger FW with CSMS vendor schema notes

   Expected: Compatible pair

   Tools: OEM release notes

4. 4. Retest a single known vendor message

   Expected: Accepted

   Tools: CSMS

5. 5. Fall back to standard StatusNotification diagnostics meanwhile

   Tools: field

The fix

Vendor DataTransfer rejects are CSMS/OEM profile issues — keep using core OCPP for triage.

1. Enable the OEM vendorId on the CSMS if policy allows. Document readings and scrubbed photos for OCPP-F10 before closing the ticket.
2. Upgrade/align firmware and CSMS schema together. Document readings and scrubbed photos for OCPP-F10 before closing the ticket.
3. Fix integration typos in messageId. Document readings and scrubbed photos for OCPP-F10 before closing the ticket.
4. Do not treat vendor DataTransfer rejects as DC hardware faults.
5. Document Accepted DataTransfer for the ops runbook. Document readings and scrubbed photos for OCPP-F10 before closing the ticket.