home-assistant/core · error · ConfigEntryNotReady
ConfigEntryNotReady
Error message
ConfigEntryNotReady
What it means
Error "ConfigEntryNotReady" thrown in home-assistant/core.
Source
Thrown at homeassistant/components/bryant_evolution/__init__.py:74
config_entry_id=entry.entry_id,
identifiers={(DOMAIN, names.system_device_uid(sam_uid, sys_id))},
via_device_id=sam_device.id,
manufacturer="Bryant",
name=f"System {sys_id}",
)
# Create a client for every zone.
entry.runtime_data = {}
for sz in entry.data[CONF_SYSTEM_ZONE]:
try:
client = await BryantEvolutionLocalClient.get_client(
sz[0], sz[1], entry.data[CONF_FILENAME]
)
if not await _can_reach_device(client):
raise ConfigEntryNotReady
entry.runtime_data[tuple(sz)] = client
except FileNotFoundError as f:
raise ConfigEntryNotReady from f
await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
return True
async def async_unload_entry(
hass: HomeAssistant, entry: BryantEvolutionConfigEntry
) -> bool:
"""Unload a config entry."""
return await hass.config_entries.async_unload_platforms(entry, PLATFORMS)
View on GitHub (pinned to 58a3fdb3ea)
Solutions
- Verify the Bryant Evolution thermostat system is powered on and reachable on the network/serial connection.
- Check that the configured filename/device path for the Evolution connection is correct and accessible.
- Confirm the device is responsive, then reload the integration; setup will retry automatically.
Example fix
The Bryant Evolution system cannot be reached or its serial device file is missing. Confirm the equipment is connected and powered and that the serial device path in the configuration exists, then reload the integration; setup retries automatically.
When it happens
Trigger: Thrown at homeassistant/components/bryant_evolution/__init__.py:74 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of home-assistant/core@58a3fdb3ea (2026-08-14).
Data as JSON: /api/errors/63e0bf304ca07ce1.
Report an issue: GitHub.