Repairs

Home Assistant keeps track of issues which should be brought to the user's attention. These issues can be created by integrations or by Home Assistant itself. Issues can either be fixable via a RepairsFlow or by linking to a website with information on how the user can solve it themselves.

Creating an issue

from homeassistant.helpers import issue_registry as ir

ir.async_create_issue(
    hass,
    DOMAIN,
    "manual_migration",
    breaks_in_ha_version="2022.9.0",
    is_fixable=False,
    severity=ir.IssueSeverity.ERROR,
    translation_key="manual_migration",
)

Attribute	Type	Default	Description
domain	string		Domain raising the issue
issue_id	string		An identifier for the issue, must be unique within domain
breaks_in_ha_version	string	None	The version in which the issue is breaking
data	dict	None	Arbitrary data, not shown to the user
is_fixable	boolean		True if the issue can be automatically fixed
is_persistent	boolean		True if the issue should persists across restarts of Home Assistant
issue_domain	string	None	Set by integrations creating issues on behalf of other integrations
learn_more_url	string	None	URL where the user can find more details about an issue
severity	IssueSeverity		Severity of the issue
translation_key	str		Translation key with a brief explanation of the issue
translation_placeholders	dict	None	Placeholders which will be injected in the translation

Severity of an issue

To better understand which severity level to choose, see the list below.

IssueSeverity	Description
CRITICAL	Considered reserved, only used for true panic
ERROR	Something is currently broken and needs immediate attention
WARNING	Something breaks in the future (e.g., API shutdown) and needs attention

Fixing an issue

If an issue has the is_fixable issue set to True, the user will be allowed to fix the issue. An issue which is successfully fixed will be removed from the issue registry. If an automatic repair is possible, it should be implemented using a RepairsFlow.

Offering an automatic repair

Create a new platform file in your integration folder called repairs.py and add code according to the pattern below.

import voluptuous as vol

from homeassistant.components.repairs import RepairsFlow, RepairsFlowResult
from homeassistant.core import HomeAssistant


class Issue1RepairFlow(RepairsFlow):
    """Handler for an issue fixing flow."""

    async def async_step_init(
        self, user_input: dict[str, str] | None = None
    ) -> RepairsFlowResult:
        """Handle the first step of a fix flow."""

        return await (self.async_step_confirm())

    async def async_step_confirm(
        self, user_input: dict[str, str] | None = None
    ) -> RepairsFlowResult:
        """Handle the confirm step of a fix flow."""
        if user_input is not None:
            return self.async_create_entry(title="", data={})

        return self.async_show_form(step_id="confirm", data_schema=vol.Schema({}))


async def async_create_fix_flow(
    hass: HomeAssistant,
    issue_id: str,
    data: dict[str, str | int | float | None] | None, # the arbitrary issue data
) -> RepairsFlow:
    """Create flow."""
    if issue_id == "issue_1":
        return Issue1RepairFlow()

[!NOTE] The flow manager creates the RepairsFlow and passes the attributes data and issue_id from the instigating issue. These should not be passed to the RepairsFlow in any implementations of async_create_fix_flow as these will be overridden by the flow manager.

Issues that can be repaired via entry/options/subentry reconfiguration or other repair flows.

Repair flows can forward issue fixes to config, options, subentry, or even different repair flows:

import voluptuous as vol

from homeassistant import data_entry_flow
from homeassistant.components.repairs import FlowType, RepairsFlow, RepairsFlowResult
from homeassistant.config_entries import (
    SOURCE_RECONFIGURE,
    SubentryFlowContext,
    SubentryFlowResult,
)
from homeassistant.core import HomeAssistant

class Issue1RepairFlow(RepairsFlow):
    """Handler for an issue fixing flow."""

    async def async_step_init(
        self, user_input: dict[str, str] | None = None
    ) -> RepairsFlowResult:
        return await (self.async_step_confirm())

    async def async_step_confirm(
        self, user_input: dict[str, str] | None = None
    ) -> RepairsFlowResult:
        """Handle the confirm step of a fix flow."""
        if user_input is not None:
            next_flow: SubentryFlowResult = (
                await self.hass.config_entries.subentries.async_init(
                    (self.data["entry_id"], "subentry_type"),
                    context=SubentryFlowContext(
                        subentry_id=self.data["subentry_id"],
                        source=SOURCE_RECONFIGURE,
                    ),
                )
            )
            return self.async_abort(
                title="", data={},
                next_flow=(
                    FlowType.CONFIG_SUBENTRIES_FLOW,
                    next_flow["flow_id"]
                )
            )

        return self.async_show_form(
            step_id="confirm",
            data_schema=vol.Schema({})
        )

If using next_flow in the repair flow's async_abort it will be the responsibility of the developer to delete the issue from the registry once the repair (i.e. config entry reconfigured) has been made.

Example next_flow options flow

next_flow: ConfigFlowResult = (
    await self.hass.config_entries.options.async_init(
        self.data["entry_id"]
    )
)
return self.async_create_entry(
    title="", data={},
    next_flow=(
        FlowType.OPTIONS_FLOW,
        next_flow["flow_id"]
    )
)

Example next_flow repair flow

from homeassistant import data_entry_flow
from homeassistant.components.repairs import (
    FlowType,
    RepairsFlow,
    RepairsFlowResult,
    RepairsFlowManager,
    async_get
)

async def async_step_confirm(
    self, user_input: dict[str, str] | None = None
) -> RepairsFlowResult:
    """Handle the confirm step of a fix flow."""
    if user_input is not None:
        repairs_flow_handler:  RepairsFlowManager = async_get(self.hass)
        next_flow: RepairsFlowResult = await repairs_flow_handler.async_init(
            # The domain of the integration containing the
            # "fixable issue" with corresponding fix flow
            DOMAIN, 
            context = {
                "issue_id": "example_issue_id"
            }
        )
        
        return self.async_create_entry(
            title="", data={},
            next_flow=(
                FlowType.REPAIRS_FLOW,
                next_flow["flow_id"]
            )
        )

[!TIP] The RepairsFlowManager expects context to contain the issue_id in async_init as shown in the code snippet above. The prior behavior of passing issue_id via data (e.g. data={"issue_id": "example_issue_id"}) will still work but will generate usage warnings in the logs to prompt developers to shift to using context to be consistent with other data entry flows.

The next_flow argument in async_abort or async_create_entry expects a tuple: tuple[homeassistant.components.repairs.FlowType, str].

Issue life cycle

Issue persistence

An issue will be kept in the issue registry until it's removed by the integration that created it or by the user fixing it.

The is_persistent flag controls if an issue should be shown to the user after a restart of Home Assistant:

• If the is_persistent flag is set on the issue, the issue will be shown again to the user after a restart. Use this for issues that can only be detected when they occur (update failed, unknown action in automation).
• If the is_persistent flag is not set on the issue, the issue will not be shown again to the user after a restart until it's created again by its integration. Use this for issues that can be checked for, like low disk space.

Ignored issues

It's possible for the user to "ignore" issues. An ignored issue is ignored until it's explicitly deleted - either by the integration or by the user successfully walking through its repair flow - and then created again. Ignoring an issue takes effect across restarts of Home Assistant regardless of issue persistence.

Deleting an issue

Integrations typically don't need to delete issues, but it may be useful in some cases.

from homeassistant.helpers import issue_registry as ir

ir.async_delete_issue(hass, DOMAIN, "manual_migration")

Repair flows using next_flow

Integration repair flows using next_flow in RepairsFlow.async_abort will have to delete an issue once the repair is completed as the RepairsFlow.async_abort will not remove the issue from the registry (note that RepairFlow.async_create_issue will always remove the issue from the registry). Issues can be deleted in config_flow.py or in the integration's async_setup_entry:

async def async_step_reconfigure(
    self, user_input: dict[str, Any] | None = None
) -> ConfigFlowResult:
    """Config entry reconfigure."""
    if user_input is not None:
        ...
        if success:
            ir.async_delete_issue(
                self.hass,
                DOMAIN,
                "url_invalid",
            )
            return self.async_update_reload_and_abort(
                self._get_reconfigure_entry(),
                data=data,
            )