home-assistant/core · error · UpdateFailed

setup_request_exception

Error message

setup_request_exception

What it means

UpdateFailed with translation_key setup_request_exception (bring/coordinator.py:92), rendered as 'Failed to connect to server, try again later'. Raised in the list DataUpdateCoordinator's _async_update_data when bring.load_lists() raises BringRequestException — an HTTP/network-level failure talking to the Bring! cloud API.

Source

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

        """Initialize the Bring data coordinator."""
        super().__init__(
            hass,
            _LOGGER,
            config_entry=config_entry,
            name=DOMAIN,
            update_interval=timedelta(seconds=90),
        )
        self.bring = bring
        self.previous_lists: set[str] = set()

    @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}
        ):

View on GitHub (pinned to 58a3fdb3ea)

Solutions

1. Check general internet connectivity from the HA host and that api.getbring.com resolves.
2. Wait and let the coordinator retry — Bring! backend blips usually resolve within minutes.
3. Check Bring! status/social channels for an outage if only this integration fails.
4. If behind a proxy/SSL-inspecting firewall, exempt the Bring! API endpoints.

When it happens

Trigger: Every ~90s poll calls load_lists(); a network outage, DNS failure, or Bring! cloud 5xx/timeouts raise BringRequestException from the bring-client library, which the coordinator converts to UpdateFailed so entities go unavailable and the coordinator schedules a retry.

Common situations: Internet outage or firewall blocking api.getbring.com; Bring! backend downtime (the message explicitly says 'try again later'); HA host losing connectivity (Wi-Fi drop, container DNS issues); SSL interception breaking the TLS session.

Related errors

• Unable find multi-factor auth module: {mfa_module_id}
• update_error
• Failed to communicate with device.
• Failed to connect
• Airtouch connection issue

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