home-assistant/core · error · ConfigEntryAuthFailed
ConfigEntryAuthFailed
Error message
ConfigEntryAuthFailed
What it means
Error "ConfigEntryAuthFailed" thrown in home-assistant/core.
Source
Thrown at homeassistant/components/brunt/coordinator.py:81
@override
async def _async_update_data(self) -> dict[str | None, Thing]:
"""Fetch data from the Brunt endpoint for all Things.
Error 403 is the API response for any kind of
authentication error (failed password or email)
Error 401 is the API response for things that are not
part of the account, could happen when a device is
deleted from the account.
"""
try:
async with timeout(10):
things = await self.bapi.async_get_things(force=True)
return {thing.serial: thing for thing in things}
except ServerDisconnectedError as err:
raise UpdateFailed(f"Error communicating with API: {err}") from err
except ClientResponseError as err:
if err.status == 403:
raise ConfigEntryAuthFailed from err
if err.status == 401:
_LOGGER.warning("Device not found, will reload Brunt integration")
await self.hass.config_entries.async_reload(self.config_entry.entry_id)
raise UpdateFailed from err
View on GitHub (pinned to 58a3fdb3ea)
Solutions
- Verify the Brunt account username and password are still valid and reconfigure the integration with correct credentials.
- Log in to the Brunt app to confirm the account is not locked or the password changed.
- Re-authenticate via the integration's reauth flow when prompted.
Example fix
The Brunt API returned HTTP 403, meaning the stored credentials are rejected. Reauthenticate with a valid Brunt account username and password via the config entry's reauth flow.
When it happens
Trigger: Thrown at homeassistant/components/brunt/coordinator.py:81 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of home-assistant/core@58a3fdb3ea (2026-08-14).
Data as JSON: /api/errors/4eec425ea360b6b8.
Report an issue: GitHub.