BootNotification rejected — wrong chargePointModel

How it presents

Symptom

BootNotification rejected — wrong chargePointModel / identity after board swap or clone config, leaving the charger offline to CSMS. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F08.

Root causes (by observed frequency)

1. #1 chargePointModel/vendor mismatch vs CSMS whitelist

   Common after control-board swap

2. #2 Duplicate chargePointIdentity already registered
3. #3 Firmware reporting unexpected model string
4. #4 CSMS environment pointing at staging whitelist

Diagnostic procedure

1. 1. Read BootNotification.conf status and current identity fields

   Expected: Rejected reason

   Tools: CSMS

2. 2. Compare HMI identity to commissioning sheet

   Expected: Exact match

   Tools: HMI, sheet

3. 3. Remove/rename duplicate identity collisions in CSMS

   Expected: Unique ID

   Tools: CSMS admin

4. 4. Correct model/vendor strings per OEM after board swap

   Expected: Accepted Boot

   Tools: OEM tool

5. 5. Reboot once after identity correction; confirm Accepted

   Tools: CSMS

The fix

Rejected BootNotification is identity/whitelist — fix config, don’t RMA power modules.

1. Stop swapping boards without rewriting chargePointIdentity.
2. Align model/vendor strings with the CSMS whitelist. Document readings and scrubbed photos for OCPP-F08 before closing the ticket.
3. Resolve duplicate identity collisions before more reboots.
4. Obtain Accepted BootNotification before chasing session faults.
5. Update the commissioning sheet with the live identity. Document readings and scrubbed photos for OCPP-F08 before closing the ticket.