home-assistant/core · error · ConfigEntryNotReady

Could not fetch integration list

Error message

Could not fetch integration list

What it means

Raised as ConfigEntryNotReady when client.get_integrations(Environment.NEXT) fails with HomeassistantAnalyticsConnectionError during setup of the analytics_insights integration. The Home Assistant Analytics insights web service (analytics.next.home-assistant.io) could not be reached, so the first fetch of the integration list failed and setup will be retried.

Source

Thrown at homeassistant/components/analytics_insights/__init__.py:42

@dataclass(frozen=True)
class AnalyticsInsightsData:
    """Analytics data class."""

    coordinator: HomeassistantAnalyticsDataUpdateCoordinator
    names: dict[str, str]


async def async_setup_entry(
    hass: HomeAssistant, entry: AnalyticsInsightsConfigEntry
) -> bool:
    """Set up Homeassistant Analytics from a config entry."""
    client = HomeassistantAnalyticsClient(session=async_get_clientsession(hass))

    try:
        integrations = await client.get_integrations(Environment.NEXT)
    except HomeassistantAnalyticsConnectionError as ex:
        raise ConfigEntryNotReady("Could not fetch integration list") from ex

    names = {}
    for integration in entry.options[CONF_TRACKED_INTEGRATIONS]:
        if integration not in integrations:
            names[integration] = integration
            continue
        names[integration] = integrations[integration].title

    coordinator = HomeassistantAnalyticsDataUpdateCoordinator(hass, entry, client)

    await coordinator.async_config_entry_first_refresh()

    entry.runtime_data = AnalyticsInsightsData(coordinator=coordinator, names=names)

    await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)

    return True

View on GitHub (pinned to 58a3fdb3ea)

Solutions

1. Verify outbound HTTPS to https://analytics.next.home-assistant.io from the HA host.
2. Wait for automatic retry — ConfigEntryNotReady schedules re-setup with backoff.
3. If a firewall blocks it, allowlist the analytics domain or remove the integration if the network policy forbids it.
4. Check the chained exception (__cause__) in logs for the precise network failure.

except ConfigEntryNotReady: allow backoff retries; check connectivity if it persists past ~10 minutes.

When it happens

Trigger: async_setup_entry constructs HomeassistantAnalyticsClient and immediately calls get_integrations(Environment.NEXT); any connection error (DNS, TLS, timeout, HTTP 5xx) from that call maps to HomeassistantAnalyticsConnectionError.

Common situations: No internet on the HA host at setup time, the analytics insights service being down, or corporate firewalls/DNS filters blocking analytics.next.home-assistant.io.

Related errors

• supervisor_not_ready
• {exc}
• {error_message}
• Error connecting to {host}:{port}
• Error communicating with Homeassistant Analytics

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