home-assistant/core · error · UpdateFailed

update_error_not_found

Error message

update_error_not_found

What it means

UpdateFailed with translation_key update_error_not_found (coordinator.py:198), rendered as 'Error updating data for {device}: the Bravia API service is stuck'. Raised when the poll loop (_async_update_data) hits BraviaNotFound more than 10 consecutive times; the first 10 are silently skipped (skipped_updates counter) because the API service is assumed to be reloading.

Source

Thrown at homeassistant/components/braviatv/coordinator.py:198

                self.system_info = await self.client.get_system_info()

            if self.is_on is False:
                return

            if not self.source_map:
                await self.async_update_sources()
            await self.async_update_volume()
            await self.async_update_playing()
        except BraviaNotFound as err:
            if self.skipped_updates < 10:
                self.connected = False
                self.skipped_updates += 1
                _LOGGER.debug(
                    "Update for %s skipped: the Bravia API service is reloading",
                    self.config_entry.title,
                )
                return
            raise UpdateFailed(
                translation_domain=DOMAIN,
                translation_key="update_error_not_found",
                translation_placeholders={
                    "device": self.config_entry.title,
                },
            ) from err
        except BraviaConnectionError, BraviaConnectionTimeout, BraviaTurnedOff:
            self.is_on = False
            self.connected = False
            _LOGGER.debug(
                "Update for %s skipped: the TV is turned off", self.config_entry.title
            )
        except BraviaError as err:
            self.is_on = False
            self.connected = False
            raise UpdateFailed(
                translation_domain=DOMAIN,
                translation_key="update_error",

View on GitHub (pinned to 58a3fdb3ea)

Solutions

1. Wait for the TV to fully finish booting/updating, then reload the braviatv config entry — the counter resets on reload.
2. Power-cycle the TV (unplug ~30s) if the API service is genuinely stuck after a firmware update.
3. Check for firmware updates on the TV and apply them; known Sony bugs wedge the IP Control service.
4. If it recurs, increase the coordinator update interval so the 10-skip grace period covers the boot window.

When it happens

Trigger: The TV's internal Bravia API service returns 'not found' for every poll (get_system_info, sources, volume, playing) for more than 10 consecutive coordinator updates — typically right after the TV boots/reboots or after a firmware update while the API service is still initializing or wedged.

Common situations: TV rebooting or firmware updating when HA polls; TV stuck in a half-booted state where networking is up but the Sony API is not; polling interval so short the 10-update grace window passes before the TV finishes booting.

Related errors

• update_error
• Unable find multi-factor auth module: {mfa_module_id}
• Error communicating with API: {err}
• {err}
• update_error

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