home-assistant/core · error · UpdateFailed
coordinator_connection_error
coordinator_connection_error
Error message
Error while establishing connection with BSB-LAN device at {host} What it means
Raised by the bsblan coordinator when a refresh raises BSBLANConnectionError (re-raised from the per-circuit loop or caught on the outer sensor fetch). It becomes UpdateFailed with translation key `coordinator_connection_error` and the host placeholder, marking bsblan entities unavailable until the device answers again. Unlike setup-time NotReady, the entry stays loaded and retries each scan interval.
Source
Thrown at homeassistant/components/bsblan/coordinator.py:140
raise
except BSBLANError as err:
raise UpdateFailed(
translation_domain=DOMAIN,
translation_key="coordinator_state_error",
translation_placeholders={
"host": host,
"circuit": str(circuit),
},
) from err
sensor = await self.client.sensor(include=SENSOR_INCLUDE)
except BSBLANAuthError as err:
raise ConfigEntryAuthFailed(
translation_domain=DOMAIN,
translation_key="coordinator_auth_error",
) from err
except BSBLANConnectionError as err:
raise UpdateFailed(
translation_domain=DOMAIN,
translation_key="coordinator_connection_error",
translation_placeholders={"host": host},
) from err
# Fetch DHW state separately - device may not support hot water
dhw: HotWaterState | None = None
try:
dhw = await self.client.hot_water_state(include=DHW_STATE_INCLUDE)
except BSBLANError:
# Preserve last known DHW state if available (entity may depend on it)
if self.data:
dhw = self.data.dhw
LOGGER.debug(
"DHW (Domestic Hot Water) state not available on device at %s",
self.config_entry.data[CONF_HOST],
)
View on GitHub (pinned to 58a3fdb3ea)
Solutions
- Verify reachability of the device web UI from the HA host; fix IP/reservation if changed.
- Wait for the next coordinator interval — entities recover automatically once the device answers.
- Stabilize the network (Wi-Fi signal, static IP) if the error recurs daily.
- Power-cycle the BSB-LAN board if its web UI is hung.
Defensive patterns
Strategy: retry
Prevention
- Use a static IP or DHCP reservation for the BSB-LAN device.
- Don't build automations that fail hard on entity unavailability — condition on state first.
- The coordinator retries each interval; avoid manual reload storms during brief outages.
When it happens
Trigger: Any scheduled or manual coordinator refresh while the device is powered off, unreachable on the network, or the HTTP connection is refused/reset during `client.state()` or `client.sensor()`.
Common situations: Device reboot, Wi-Fi dropouts, router/DHCP changes, device in sleep mode, or nightly router maintenance windows.
Related errors
- Connection failed during update for zone {self.state.zn}
- setup_connection_error
- coordinator_state_error
- coordinator_auth_error
- Unable find multi-factor auth module: {mfa_module_id}
AI-assisted analysis of home-assistant/core@58a3fdb3ea (2026-08-14).
Data as JSON: /api/errors/b8f20c2b4ced8330.
Report an issue: GitHub.