home-assistant/core · error · UpdateFailed

Unable to connect to the Arve device

Error message

Unable to connect to the Arve device

What it means

UpdateFailed('Unable to connect to the Arve device') raised by the Arve coordinator when pyarve raises ArveConnectionError during get_devices()/device_sensor_data()/get_sensor_info(). It marks the poll as failed and entities unavailable; recovery is automatic on the next successful poll.

Source

Thrown at homeassistant/components/arve/coordinator.py:62

            self.config_entry.data[CONF_CLIENT_SECRET],
            session=async_get_clientsession(hass),
        )

    @override
    async def _async_update_data(self) -> dict[str, ArveDeviceInfo]:
        """Fetch data from API endpoint."""
        try:
            self.devices = await self.arve.get_devices()

            response_data = {
                sn: ArveDeviceInfo(
                    await self.arve.device_sensor_data(sn),
                    await self.arve.get_sensor_info(sn),
                )
                for sn in self.devices.sn
            }
        except ArveConnectionError as err:
            raise UpdateFailed("Unable to connect to the Arve device") from err
        except ArveError as err:
            raise UpdateFailed("Unknown error occurred") from err

        return response_data

View on GitHub (pinned to 58a3fdb3ea)

Solutions

  1. Check connectivity to the Arve API from the HA host (DNS, firewall, proxy).
  2. Confirm the Arve service status / hub is online.
  3. Wait for the coordinator retry; if it never recovers, reload the integration to rebuild the API client.
Defensive patterns

Strategy: retry

Try / catch

Catch ArveConnectionError separately from ArveError (integration pattern): connection errors map to a specific UpdateFailed and rely on coordinator retry; generic errors get their own message plus the chained cause for diagnosis.

Prevention

When it happens

Trigger: Any coordinator refresh where the Arve cloud/local API connection fails at the HTTP layer: server unreachable, connection reset, or DNS failure for the Arve endpoint.

Common situations: Arve cloud outage, local Arve hub offline, firewall blocking outbound API traffic, intermittent Wi-Fi on the host running Home Assistant.

Related errors


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