CSMS rate-limits StatusNotification

How it presents

Symptom

CSMS rate-limits StatusNotification — after a reconnect storm the CSMS throttles, chargers appear offline/Faulted in UI despite healthy hardware. protocol field note: keep evidence scrubbed and prove the ranked cause before module RMA on NET-C06.

Root causes (by observed frequency)

1. #1 Mass reconnect storm after site power blip

   CSMS protecting itself

2. #2 Charger retry loop too aggressive
3. #3 CSMS misconfigured rate limit too low for pad size
4. #4 Monitoring tool amplifying status storms

Diagnostic procedure

1. 1. Check CSMS rate-limit / HTTP 429 / throttle logs

   Expected: Throttle evidence

   Tools: CSMS admin

2. 2. Correlate with site power or modem reconnect event

   Expected: Storm start

   Tools: timeline

3. 3. Backoff charger reconnects per OEM if configurable

   Expected: Slower retries

   Tools: HMI

4. 4. Ask CSMS to raise limits or stagger pad reconnects

   Expected: Accepts statuses

   Tools: CSMS

5. 5. Confirm StatusNotifications flow after quiet period

   Tools: CSMS

The fix

Rate-limit Soft-offlines are CSMS/ops storms — stagger reconnects, don’t RMA modules.

1. Wait out or stagger reconnects instead of power-cycling every stall.
2. Tune charger retry backoff if OEM provides it. Document readings and scrubbed photos for NET-C06 before closing the ticket.
3. Resize CSMS rate limits for the pad’s stall count. Document readings and scrubbed photos for NET-C06 before closing the ticket.
4. Stop third-party pollers that amplify storms. Document readings and scrubbed photos for NET-C06 before closing the ticket.
5. Validate steady StatusNotification flow before closing the ticket.