Renault Kamereon API returning Account Pending TFA Verification. Is anyone else seeing this?

[iSenne]

Following up on #30025 (where Renault broke third-party auth with an API key change), I wanted to flag what looks like the next step in that rollout: two-factor authentication enforcement.

This morning I noticed a new error in my EVCC logs that I hadn't seen before:

[lp-1  ] ERROR charger soc: Get "https://api-wired-prod-1-euw1.wrd-aws.com/...": Account Pending TFA Verification
[lp-1  ] ERROR vehicle range: Get "https://api-wired-prod-1-euw1.wrd-aws.com/...": Account Pending TFA Verification
[lp-1  ] ERROR climater: Get "https://api-wired-prod-1-euw1.wrd-aws.com/...": Account Pending TFA Verification

This is different from the Invalid LoginID errors in #30025, authentication itself seems to succeed, but the API then rejects all car-adapter calls with this TFA status message. In my case the errors were intermittent and eventually went away on their own, so it may be that Renault is prompting for TFA verification in the background and temporarily blocking API access until it's confirmed. Errors are back, they just stopped for ~30 minutes. Got errors between 12:39 - 13:05 and after 13:36

My setup (for reference):

• Vehicle: Renault Scenic E-Tech
• EVCC: Kubernetes deployment
• Charger: OCPP (Wallbox Pulsar Max)

What I observed during the error window:

• OCPP charging itself kept working fine — charge profiles were accepted, meter values reported normally
• The errors appeared consistently every ~20 seconds (EVCC's poll interval), with no backoff

What I'm not sure about:

• Whether this is rolling out account by account, or whether it's triggered by something specific (new login, app update, etc.)
• Whether it resolves itself once TFA is completed in the My Renault app, or whether something else is needed

In #30025, @rubinho76 already asked "Wollte Renault nicht auch 2FA aktivieren?" — this might be the answer to that question showing up in practice.

Are others seeing this error? Particularly curious whether it affects all Renault models/accounts or just specific ones.

[felix-schwarz]

I'm seeing the same error (Account Pending TFA Verification) for a Twingo E-Tech.

[LeonSol]

Probably you have accept some new documents in your Renault-App.

[felix-schwarz]

Unfortunately that's not it. The Renault app continues to work, but I haven't yet tried to log out and in again. Maybe they require 2FA setup after token expiration.

[iSenne]

@LeonSol I thought so too, but I don't see anything in the app. Not even after logging out and logging back in.

[gr0mit1]

same error here in .uk but the Renault app carries on working. Kelec also broken.

[ttil1962]

Same error here in .de with a R5-etech

[poohnet]

Same here - a few days ago our ID.4 stopped working with evcc and now our Zoe as well :-(
Re-login to the Renault app indeed resulted in a TFA code being sent via E-Mail.

[iSenne]

I logged into the app on may 19, I also got a TFA code via email

[tih2010]

Same here.

[iSenne]

Just reconnected my vehicle, now it's a guest vehicle. After selecting my car from the list, it just starts charging and cannot stop at the configured SoC limit, because it cannot read the charge percentage ☹️

[iSenne]

Made a (massively vibe coded) fix for my local app, seems to work

https://gitlab.com/isenne/renault-test/-/commit/63d52352d0dfb9f49bb39030a9021352d12771ea

Don't know if I have time to make a fix and PR for EVCC though

[iSenne]

I've burnt some codex tokens, and maybe found a fix (I have limited go experience)

https://github.com/iSenne/evcc/tree/codex/renault-tfa

Cannot test it at the moment, because Error: Account Temporarily Locked Out: Account temporarily locked out 🫣. I did get TFA emails, so will test it when I have access again (or maybe someone else can test it)

[iSenne]

I've opened a PR

[tih2010]

That sounds interesting - how do you get around codes sent by email?