home-assistant/core · error · ConfigEntryAuthFailed

setup_authentication_exception

Error message

setup_authentication_exception

What it means

ConfigEntryAuthFailed with translation_key setup_authentication_exception (bring/coordinator.py:102), rendered as 'Authentication failed for {email}, check your email and password'. Raised when load_lists() raises BringAuthException during a coordinator update; it starts the reauth flow for the config entry using the account email (self.bring.mail) as the placeholder.

Source

Thrown at homeassistant/components/bring/coordinator.py:102

    @override
    async def _async_update_data(self) -> dict[str, BringData]:
        """Fetch the latest data from bring."""

        try:
            self.lists = (await self.bring.load_lists()).lists
        except BringRequestException as e:
            raise UpdateFailed(
                translation_domain=DOMAIN,
                translation_key="setup_request_exception",
            ) from e
        except BringParseException as e:
            raise UpdateFailed(
                translation_domain=DOMAIN,
                translation_key="setup_parse_exception",
            ) from e
        except BringAuthException as e:
            raise ConfigEntryAuthFailed(
                translation_domain=DOMAIN,
                translation_key="setup_authentication_exception",
                translation_placeholders={CONF_EMAIL: self.bring.mail},
            ) from e

        if self.previous_lists - (
            current_lists := {lst.listUuid for lst in self.lists}
        ):
            self._purge_deleted_lists()
        new_lists = current_lists - self.previous_lists
        self.previous_lists = current_lists

        list_dict: dict[str, BringData] = {}
        for lst in self.lists:
            if (
                (ctx := set(self.async_contexts()))
                and lst.listUuid not in ctx
                and lst.listUuid not in new_lists

View on GitHub (pinned to 58a3fdb3ea)

Solutions

1. Open the HA notification / config entry and complete the reauth flow with the current email and password.
2. If the password was changed in the Bring! app, use the new one in the reauth prompt.
3. Confirm the account is not locked and can log in inside the Bring! mobile app.
4. After successful reauth, the coordinator resumes polling automatically.

When it happens

Trigger: The Bring! session token expires or is revoked (password changed, account logged out everywhere, token invalidated server-side) so load_lists() returns 401/403 → BringAuthException → ConfigEntryAuthFailed, which triggers HA's re-authentication flow.

Common situations: User changed their Bring! password in the app; Bring! invalidated old sessions after a security change; multiple HA instances or reinstalls invalidating each other's tokens; email typo fixed later on the account side.

Understand the failure class

• Authentication and authorization failures — expired tokens, bad credentials, and missing scopes.

Related errors

• Unable to deactivate the owner
• Authentication failed, please reauthenticate.
• invalid_api_key
• authentication_failed
• setup_auth_error

AI-assisted analysis of home-assistant/core@58a3fdb3ea (2026-08-14). Data as JSON: /api/errors/cc5ecb2330171aa8. Report an issue: GitHub.