Ask for the email in the reauth flow, and add a reconfigure step

[AboveColin]

What broke

Reconfiguring the Fitdays entry on my dev instance showed "Unexpected error." Three receipts:

• home-assistant.log — ERROR [custom_components.fitdays.config_flow] Unexpected Fitdays error during login: email and password are required
• the entry's stored data — {'email': None, 'password_hash': None, 'refresh_token': None, 'token': SET, 'uid': SET}
• fitdays/client.py:109 — if not email or not password: raise FitdaysValidationError("email and password are required")

async_step_reauth_confirm asked only for the password and reused the email stored on the entry. With no email on the entry it passed "" to FitdaysClient.login, the client raised FitdaysValidationError before contacting the cloud, and the except FitdaysError branch mapped it to the unknown key, which strings.json renders as "Unexpected error." The entry could not be recovered from the UI at all.

There was also no async_step_reconfigure, so the entry could not be pointed at fresh credentials.

What changed

• The reauth form asks for the email too, prefilled from the entry when it has one.
• FitdaysValidationError maps to invalid_auth. Blank input is a form problem, not an outage.
• New async_step_reconfigure taking email, password and country. It aborts with account_mismatch when the returned uid differs from the entry's unique_id, because reconfigure repairs one account's entry and a second account belongs in its own entry.
• _credentials_schema() builds the one form all three steps use.
• strings.json and translations/en.json gain the reconfigure step and the reconfigure_successful and account_mismatch aborts.

Verified on ha-dev

HA 2026.8.3, podman container ha-dev on nix1, running this branch's files.

• the entry reports supports_reconfigure: true
• POST /api/config/config_entries/flow with the entry id returns step_id: reconfigure with fields email (required), password (password selector), country (optional, default NL)
• submitting a blank email, the exact input that produced "Unexpected error.", returns errors {"base": "invalid_auth"} on both the reconfigure and the reauth step
• grep -c 'Unexpected Fitdays error' on the log after those submits: 0

The successful-login path is not exercised, because the dev entry holds an expired hand-seeded token with no credentials and I have no Fitdays account credentials to hand.

Independent of #3; branched from main.

🤖 Generated with Claude Code

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 0b3faa7b-a573-4f97-9efb-4dc86ce7fbbf

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}