The EVSE DirectorySubscribe

Blink

Field hub — common codes, ownership boundaries, and links into the fault database.

Blink IQ 200 AC pedestals/wall units dominate these tickets. Ownership is the station enclosure (relay, RFID, boot/firmware) plus Blink network reachability — not a DC power cabinet. Pedestal owns GFCI/relay, connector, and local controller. CPO/Blink network owns auth backend. Site owns PE and feeder. A “station offline” ticket is often cellular/Wi-Fi or CSMS — not a dead power board.

When this OEM shows up

Common calls: network offline (app/CSMS red), RFID intermittent, relay welded after high-cycle use, boot loop after OTA. Confirm whether the stall has AC power and a live Blink backhaul before condemning the relay. Photograph LEDs and capture OTA version before you force another update.

How faults present

Ranked failure patterns

  1. Blink network offline — Modem/Ethernet/DNS/TLS before board RMA. Entry: /entries/blink-blk-iq-net-blink-network-offline.

  2. RFID intermittent — Reader seating, harness, moisture. Entry: /entries/blink-blk-iq-rfid-rfid-intermittent. Related: /entries/protocol-rfid-01-rfid-reader-no-uid, /entries/protocol-ocpp-f03-authorize-rejected-invalid-idtag.

  3. IQ200 relay welded — Stuck closed/open after cycling; prove with known-good EV and measure contactor side. Entry: /entries/blink-blk-iq-relay-iq200-relay-welded.

  4. Boot loop after update — Preserve version; do not keep force-updating. Entry: /entries/blink-blk-iq-boot-boot-loop-after-update. Stuck Faulted after reboot: /entries/protocol-ocpp-f01-statusnotification-stuck-faulted-after-reboot.

Logs / tools

Blink portal / CSMS screenshots, OTA version, LED photos, DMM on relay/output, RFID test card, modem link lights, PE continuity.

Escalate when

  • Electrician: Supply/breaker issues, welded relay needing licensed swap per site policy, shared parking-lot circuit trips.
  • Network/Blink ops: Prolonged offline with good local power; identity/URL after board swap; bad OTA cohort; auth-only failures.
  • OEM: Confirmed relay/board/boot-loop hardware with version package.

Do not swap relays for network-offline tickets.

Field checklist

  1. Confirm AC present at the pedestal and breaker not tripped.
  2. Is the complaint offline, auth, or no energy after authorize?
  3. Photo LEDs + capture OTA/firmware version before another update.
  4. Pull Blink/CSMS timeline for Heartbeat gaps vs Authorize rejects.
  5. RFID test with known-good credential; reseat reader harness if intermittent.
  6. If relay suspected: known-good EV, measure output side per site LOTO rules.
  7. Do not swap the relay for a network-offline ticket.

Persistent GFCI/ground after dry known-good cable still belongs with PE verification (/entries/protocol-gnd-01-ground-continuity-fail-at-dispenser) before OEM board talk.

Models

Fault index (4)

BLK-IQ-RELAYBlink · IQ 200 · AC Level 2Free sample

IQ200 relay welded

Blink IQ200 reports a welded or stuck main relay, or fails its weld-detect self-check, typically right after a hard fault-current event or years of high-cycle depot duty. The stall latches Faulted and stays there — FreeVend and app-initiated sessions are both blocked — while neighboring pedestals on the same pad usually keep working normally, which helps rule out a site-wide power event.

3 confirmed
BLK-IQ-NETBlink · IQ 200 · AC Level 2 solo+

Blink network offline

Blink IQ shows the pedestal offline in the Cloud portal while the physical unit may still illuminate normally and even a…

2 confirmed
BLK-IQ-RFIDBlink · IQ 200 · AC Level 2 solo+

RFID intermittent

Blink IQ's RFID reader works intermittently: some taps produce a beep with no Authorize response, other cards fail consi…

2 confirmed
BLK-IQ-BOOTBlink · IQ 200 · AC Level 2 solo+

Boot loop after update

Blink IQ200 boot-loops immediately after a firmware update: the power LED cycles repeatedly, the unit never reaches Avai…

1 confirmed