Card not accepted: ReaderFailure and LocalListConflict
ReaderFailure: "Failure with idTag reader". LocalListConflict: the server's authorization data conflicts with the charger's Local Authorization List (OCPP 1.6, §7.6), reported on connector 0 (OCPP 1.6, §3.5.2).
What it means
Both are OCPP 1.6 error codes.
A reader failure is about the idTag reader itself; a list conflict is a mismatch between the server's data and the list stored in the charger.
Likely causes
For the reader, OCPP gives no causes: the code only says the idTag reader failed (OCPP 1.6, §7.6).
Any detail is in the optional vendorErrorCode and info fields (OCPP 1.6, §6.47).
For a conflict, the specification gives the case: the validity the server reports for an idTag, for instance in StartTransaction.conf, does not match the charger's Local Authorization List (OCPP 1.6, §3.5.2).
First three checks
1.
Any successful Authorize since the fault? Do other cards work?
2.
For a conflict, compare GetLocalListVersion with the server's record (OCPP 1.6, §5.10).
3.
Check the idTag's current status on the server.
What to do
What to tell the customer
"The card reader on this charger isn't working.
We can start your session remotely while we arrange a repair."
A detection rule to start from
On LocalListConflict: send the full list if allowed, and open a ticket only if the conflict comes back after the charger accepted the full list.
Sources
- Open Charge Alliance (2017). Open Charge Point Protocol 1.6, edition 2 (opens in a new tab). §3.5.2 Local Authorization List, §5.10 Get Local List Version, §5.11 Remote Start Transaction, §5.15 Send Local List, §6.47 StatusNotification.req, §7.6 ChargePointErrorCode; accessed 2026-10-22.
Talk to us about your chargers
- Tell us about your network.
- Meet a Kinethra specialist.
- Get your chargers live on Kinethra.
- 40,000+ chargers onlineOn the Kinethra platform.
- OCPP 1.6 and 2.0.1Kinethra works with OCPP chargers from any manufacturer.
- No commission on charging revenueKinethra takes none.
We use your details to answer your request. See our Privacy Policy for details.