home-assistant/core · error · UpdateFailed

Unknown error occurred

Error message

Unknown error occurred

What it means

UpdateFailed('Unknown error occurred') raised by the Arve coordinator when pyarve raises a generic ArveError that is not ArveConnectionError (e.g. malformed response, unexpected payload, or library-level failure). It is a catch-all: the chained exception (raise ... from err) carries the real cause.

Source

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

        )

    @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. Enable debug logging for homeassistant.components.arve and inspect the chained ArveError for the concrete cause.
  2. Update pyarve to the latest version (dependencies can lag API changes).
  3. Verify all serial numbers returned by get_devices still exist in your Arve account.
  4. Reload or re-create the config entry after fixing the underlying issue.
Defensive patterns

Strategy: try-catch

Try / catch

Catch ArveError (after ArveConnectionError) and always chain with 'from err' plus debug logging so the underlying library exception is preserved for diagnosis.

Prevention

When it happens

Trigger: get_devices() returns an unexpected payload shape, device_sensor_data(sn) or get_sensor_info(sn) raise a non-connection ArveError for a serial number that is listed but unreachable/misbehaving.

Common situations: Arve API contract change breaking pyarve parsing; device removed on the Arve side but still in the devices.sn list; pyarve version mismatch with the deployed API.

Related errors


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