home-assistant/core · error · ConfigEntryNotReady

Unable to connect to Abode: {ex}

Error message

Unable to connect to Abode: {ex}

What it means

Wrapped as ConfigEntryNotReady when the Abode client constructor raises any non-auth failure: AbodeException, requests ConnectTimeout, or HTTPError. Home Assistant will mark the entry as setup-retry and back off, retrying automatically rather than failing permanently.

Source

Thrown at homeassistant/components/abode/__init__.py:101

    # Configure abode library to use config directory for storing data
    jaraco.abode.config.paths.override(user_data=Path(hass.config.path("Abode")))

    # For previous config entries where unique_id is None
    if entry.unique_id is None:
        hass.config_entries.async_update_entry(
            entry, unique_id=entry.data[CONF_USERNAME]
        )

    try:
        abode = await hass.async_add_executor_job(
            Abode, username, password, True, True, True
        )

    except AbodeAuthenticationException as ex:
        raise ConfigEntryAuthFailed(f"Invalid credentials: {ex}") from ex

    except (AbodeException, ConnectTimeout, HTTPError) as ex:
        raise ConfigEntryNotReady(f"Unable to connect to Abode: {ex}") from ex

    entry.runtime_data = AbodeSystem(abode, polling)

    await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)

    await setup_hass_events(hass, entry)
    await hass.async_add_executor_job(setup_abode_events, hass, entry)

    return True


def _shutdown_client(abode: Abode) -> None:
    """Shutdown client."""
    abode.events.stop()
    abode.logout()


async def async_unload_entry(hass: HomeAssistant, entry: AbodeConfigEntry) -> bool:

View on GitHub (pinned to 58a3fdb3ea)

Solutions

1. Wait for Home Assistant's automatic retry (ConfigEntryNotReady backs off and retries) — often transient
2. Check https://status.goabode.com and Abode app for cloud issues
3. Verify outbound HTTPS to goabode.com from the host (DNS, firewall, proxy)
4. If it persists with valid credentials, capture a debug log of the Abode exception detail and report it

except (AbodeException, ConnectTimeout, HTTPError) as ex:
    raise ConfigEntryNotReady(f"Unable to connect to Abode: {ex}") from ex
# Home Assistant backs off and retries automatically

When it happens

Trigger: Abode(username, password, True, True, True) raises AbodeException (library-level API error) or the underlying HTTP request times out or returns an HTTP error status during login/initial fetch.

Common situations: Abode cloud API outage or rate limiting, local network/DNS problems blocking goabode.com, transient 5xx responses, or an expired TLS interception cert on the network.

Related errors

• Invalid credentials: {ex}
• Credential is already linked to a user
• current_conditions_update_error
• forecast_update_error
• Timed out connecting to august api

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