home-assistant/core · error · UpdateFailed

data_update_failed

data_update_failed

Error message

data_update_failed

What it means

The blebox DataUpdateCoordinator wraps device errors: when self.box.async_update_data() raises a python-blebox Error (anything other than UnauthorizedRequest) during a poll, _async_update_data raises UpdateFailed with translation key 'data_update_failed' and the underlying error text. This is Home Assistant's standard mechanism to mark the coordinator fetch as failed; entities go unavailable and the message appears in diagnostics/logs.

Source

Thrown at homeassistant/components/blebox/coordinator.py:49

        """Initialize the coordinator."""
        super().__init__(
            hass,
            _LOGGER,
            config_entry=config_entry,
            name=DOMAIN,
            update_interval=timedelta(seconds=5),
        )
        self.box = box

    @override
    async def _async_update_data(self) -> None:
        """Fetch data from the BleBox device."""
        try:
            await self.box.async_update_data()
        except UnauthorizedRequest as err:
            raise ConfigEntryAuthFailed from err
        except Error as err:
            raise UpdateFailed(
                translation_domain=DOMAIN,
                translation_key="data_update_failed",
                translation_placeholders={"error": str(err)},
            ) from err

View on GitHub (pinned to 58a3fdb3ea)

Solutions

1. Verify the device is reachable: open its configured host/IP in a browser or curl the /api endpoint.
2. If the IP changed, set a DHCP reservation or update the config entry host.
3. Check that nothing intercepts port 80 traffic to the device (captive portals, proxies).
4. If reachable but still failing, enable debug logging for blebox to capture the underlying Error text and report to the integration.

from homeassistant.helpers.update_coordinator import UpdateFailed

# Coordinator retries automatically with backoff; in custom code:
try:
    await coordinator.async_config_entry_first_refresh()
except ConfigEntryNotReady:
    # device unreachable at setup; HA will retry setup
    raise

When it happens

Trigger: Any periodic 5-second coordinator refresh where the BleBox device HTTP API fails: device powered off/unreachable on the network, timeouts, malformed responses, or transient blebox gateway errors. UnauthorizedRequest is handled separately as ConfigEntryAuthFailed and does not produce this error.

Common situations: BleBox device dropped off Wi-Fi; IP changed after DHCP renewal; device firmware rebooting; flaky 2.4 GHz network; device behind a reverse proxy that returns unexpected payloads.

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/efa54b261f32cdc0. Report an issue: GitHub.