home-assistant/core · warning · ConfigEntryNotReady

No devices were found on the websocket, perhaps you don't ha

Error message

No devices were found on the websocket, perhaps you don't have any devices on this account?

What it means

Raised as a ConfigEntryNotReady by the Anova integration when api.create_websocket() throws NoDevicesFound. The WebSocket connection to Anova's cloud succeeded at the API level, but the account returned zero paired devices, so there is nothing to coordinate. Home Assistant will retry setup later, which is intentional: devices added to the account afterwards can still be picked up.

Source

Thrown at homeassistant/components/anova/__init__.py:45

    """Set up Anova from a config entry."""
    api = AnovaApi(
        aiohttp_client.async_get_clientsession(hass),
        entry.data[CONF_USERNAME],
        entry.data[CONF_PASSWORD],
    )
    try:
        await api.authenticate()
    except InvalidLogin as err:
        _LOGGER.error(
            "Login was incorrect - please log back in through the config flow. %s", err
        )
        return False
    assert api.jwt
    try:
        await api.create_websocket()
    except NoDevicesFound as err:
        # Can later setup successfully and spawn a repair.
        raise ConfigEntryNotReady(
            "No devices were found on the websocket, perhaps you"
            " don't have any devices on this account?"
        ) from err
    except WebsocketFailure as err:
        raise ConfigEntryNotReady("Failed connecting to the websocket.") from err
    # Create a coordinator per device, if the device is offline, no data will be on the
    # websocket, and the coordinator should auto mark as unavailable. But as long as
    # the websocket successfully connected, config entry should setup.
    devices: list[APCWifiDevice] = []
    if TYPE_CHECKING:
        # api.websocket_handler can't be None after successfully creating the
        # websocket client
        assert api.websocket_handler is not None
    devices = list(api.websocket_handler.devices.values())
    coordinators = [AnovaCoordinator(hass, entry, device) for device in devices]
    entry.runtime_data = AnovaData(api_jwt=api.jwt, coordinators=coordinators, api=api)
    await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
    return True

View on GitHub (pinned to 58a3fdb3ea)

Solutions

1. Open the Anova app and confirm at least one WiFi cooker is paired with the same account used in the Home Assistant config flow
2. Verify the credentials in the config flow match the account that owns the devices (re-run reauth if unsure)
3. Once the device shows in the app, let Home Assistant retry setup (ConfigEntryNotReady retries automatically) or reload the config entry

try:
    await api.create_websocket()
except NoDevicesFound as err:
    # transient/account state: surface as retryable setup failure
    raise ConfigEntryNotReady(...) from err

When it happens

Trigger: Calling await api.create_websocket() after successful authenticate() when the Anova account has no WiFi-enabled precision cookers registered; e.g. the cooker was never linked in the Anova app, was unpaired, or belongs to a different account than the one used in the config flow.

Common situations: User logs in with the wrong Anova account (e.g. app account vs. web account), received a new device but has not paired it in the Anova app yet, or deleted/removed all devices from the account after setting up the integration.

Related errors

• Failed connecting to the websocket.
• Key data not returned from device
• Unknown error
• wake-engine-missing
• setup_connection_error

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