home-assistant/core · warning · HomeAssistantError
unknown_issue_id
Error message
unknown_issue_id
What it means
A HomeAssistantError with translation key 'unknown_issue_id' raised in async_create_fix_flow when the repairs subsystem asks the Anthropic integration to create a fix flow for an issue_id other than the one it knows ('model_deprecated'). The integration is only registered to repair deprecated-model issues; any other id is rejected.
Source
Thrown at homeassistant/components/anthropic/repairs.py:211
def _format_subentry_type(self, subentry_type: str) -> str:
"""Return a user-friendly subentry type label."""
if subentry_type == "conversation":
return "Conversation agent"
if subentry_type in ("ai_task", "ai_task_data"):
return "AI task"
return subentry_type
async def async_create_fix_flow(
hass: HomeAssistant,
issue_id: str,
data: dict[str, str | int | float | None] | None,
) -> RepairsFlow:
"""Create flow."""
if issue_id == "model_deprecated":
return ModelDeprecatedRepairFlow()
raise HomeAssistantError(
translation_domain=DOMAIN, translation_key="unknown_issue_id"
)
View on GitHub (pinned to 58a3fdb3ea)
Solutions
- Update Home Assistant core so the integration registering the issue and the one repairing it match
- Ignore/dismiss the orphaned repair item if it refers to a no-longer-existing issue
- Restart Home Assistant to re-sync registered repairs
Defensive patterns
Strategy: validation
Validate before calling
SUPPORTED_ISSUE_IDS = {"model_deprecated"}
def issue_supported(issue_id: str) -> bool:
return issue_id in SUPPORTED_ISSUE_IDS Try / catch
if issue_id == "model_deprecated":
return ModelDeprecatedRepairFlow()
raise HomeAssistantError(translation_domain=DOMAIN, translation_key="unknown_issue_id") Prevention
- Keep issue registry ids in sync with async_create_fix_flow's accepted ids when authoring repairs
- Register repairs only for issues your integration creates
When it happens
Trigger: Home Assistant core calling async_create_fix_flow(hass, issue_id, ...) with an issue id not matching 'model_deprecated' — typically an issue registered by an older/newer version of the integration, or a manually created custom repair issue routed to this domain.
Common situations: Version skew after upgrading/downgrading the integration where issue ids changed; leftover repair issues in .storage from a previous release.
Related errors
AI-assisted analysis of home-assistant/core@58a3fdb3ea (2026-08-14).
Data as JSON: /api/errors/3e9205a3ff57fcf6.
Report an issue: GitHub.