home-assistant/core · error · HomeAssistantError

command_error_not_found

Error message

command_error_not_found

What it means

Produced by the braviatv coordinator's error-catching decorator: the wrapped coordinator method raised BraviaNotFound from the underlying bravia_tv library, meaning the TV's HTTP API answered but the requested command/endpoint does not exist for this device. Re-raised as HomeAssistantError with translation_key 'command_error_not_found' and the device title as placeholder.

Source

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

type BraviaTVConfigEntry = ConfigEntry[BraviaTVCoordinator]


def catch_braviatv_errors[_BraviaTVCoordinatorT: BraviaTVCoordinator, **_P](
    func: Callable[Concatenate[_BraviaTVCoordinatorT, _P], Awaitable[None]],
) -> Callable[Concatenate[_BraviaTVCoordinatorT, _P], Coroutine[Any, Any, None]]:
    """Catch Bravia errors."""

    @wraps(func)
    async def wrapper(
        self: _BraviaTVCoordinatorT,
        *args: _P.args,
        **kwargs: _P.kwargs,
    ) -> None:
        """Catch Bravia errors and log message."""
        try:
            await func(self, *args, **kwargs)
        except BraviaNotFound as err:
            raise HomeAssistantError(
                translation_domain=DOMAIN,
                translation_key="command_error_not_found",
                translation_placeholders={
                    "device": self.config_entry.title,
                },
            ) from err
        except (BraviaConnectionError, BraviaConnectionTimeout, BraviaTurnedOff) as err:
            raise HomeAssistantError(
                translation_domain=DOMAIN,
                translation_key="command_error_offline",
                translation_placeholders={
                    "device": self.config_entry.title,
                },
            ) from err
        except BraviaError as err:
            raise HomeAssistantError(
                translation_domain=DOMAIN,
                translation_key="command_error",

View on GitHub (pinned to 58a3fdb3ea)

Solutions

1. Identify which command triggered it from the automation/log context and stop using that command on this TV.
2. Update the TV firmware (Settings > System > Software Update) so the API exposes the endpoint.
3. Reinstall the missing app or re-add the input in the TV, then reload the integration.
4. Update Home Assistant / bravia_tv library — newer releases map model-specific command sets.

try:
    await coordinator.async_send_command(cmd)
except HomeAssistantError as err:
    if err.translation_key == "command_error_not_found":
        _LOGGER.debug("command %s unsupported on %s", cmd, entry.title)

When it happens

Trigger: Sending a command (channel, input, app launch, setting) the specific TV model/firmware does not support — e.g. an app URI or input that isn't present, a command only available on newer Android TV firmware. Any coordinator update/action hitting a 404-style 'not found' from the TV maps here.

Common situations: Model differences (commands valid on one Bravia generation missing on another), app uninstalled so its endpoint 404s, older firmware lacking an API the integration calls.

Related errors

• Unable to deactivate the owner
• Unable find multi-factor auth module: {mfa_module_id}
• update_error
• Failed to communicate with device.
• Failed to connect

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