GetConfiguration key unknown storm

How it presents

Symptom

GetConfiguration key unknown storm — CSMS polls unsupported keys, filling logs and sometimes slowing the charger’s OCPP task. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on OCPP-F12.

Root causes (by observed frequency)

1. #1 CSMS profile expects OCPP keys the firmware does not implement

   Noise ≠ hardware fail

2. #2 Wrong OCPP version assumed by CSMS
3. #3 Custom keys left enabled after OEM change
4. #4 Monitoring tool spamming GetConfiguration

Diagnostic procedure

1. 1. Sample unknown key names from CSMS/charger logs

   Expected: Which keys

   Tools: logs

2. 2. Confirm negotiated OCPP version

   Expected: 1.6 vs 2.0.1 match

   Tools: CSMS

3. 3. Disable unsupported key polling in CSMS templates

   Expected: Storm stops

   Tools: CSMS admin

4. 4. Update FW only if OEM lists those keys as newly supported

   Tools: OEM notes

5. 5. Confirm session performance recovers after poll reduction

   Tools: field

The fix

UnknownKey storms are CSMS template noise — fix polling, not power stages.

1. Trim CSMS configuration polls to keys the firmware supports.
2. Align OCPP version expectations. Document readings and scrubbed photos for OCPP-F12 before closing the ticket.
3. Do not RMA controllers for UnknownKey spam alone. Document readings and scrubbed photos for OCPP-F12 before closing the ticket.
4. Upgrade FW only with a release note that adds the keys.
5. Recheck logs for a quiet GetConfiguration pattern. Document readings and scrubbed photos for OCPP-F12 before closing the ticket.