What causes "notify_request_failed" in home-assistant/core?

Retry the notification once connectivity is confirmed.

home-assistant/core · error · HomeAssistantError

notify_request_failed

Error message

notify_request_failed

What it means

Raised by BringTodoListEntity.async_send_message when coordinator.bring.notify() raises BringRequestException, i.e. the push-notification HTTP request to Bring's servers failed. This is the generic transport/HTTP failure path (auth failures and missing-argument have separate keys).

Source

Thrown at homeassistant/components/bring/todo.py:252

            raise HomeAssistantError(
                translation_domain=DOMAIN,
                translation_key="todo_delete_item_failed",
                translation_placeholders={"count": str(len(uids))},
            ) from e

        await self.coordinator.async_refresh()

    async def async_send_message(
        self,
        message: BringNotificationType,
        item: str | None = None,
    ) -> None:
        """Send a push notification to members of a shared bring list."""

        try:
            await self.coordinator.bring.notify(self._list_uuid, message, item or None)
        except BringRequestException as e:
            raise HomeAssistantError(
                translation_domain=DOMAIN,
                translation_key="notify_request_failed",
            ) from e
        except ValueError as e:
            raise ServiceValidationError(
                translation_domain=DOMAIN,
                translation_key="notify_missing_argument",
                translation_placeholders={"field": "item"},
            ) from e

View on GitHub (pinned to 58a3fdb3ea)

Solutions

Retry the notification once connectivity is confirmed.
Reload/re-authenticate the Bring integration if failures persist.
Guard automations with a connectivity/binary_sensor condition so notifications are not attempted offline.
Check the underlying exception in logs for HTTP status detail.

Defensive patterns

Strategy: retry

Try / catch

try:
    await todo_list.async_send_message(message, item)
except HomeAssistantError as err:
    if err.translation_key == "notify_request_failed":
        raise HomeAssistantErrorRetryLater from err  # transient network failure
    raise

Prevention

Gate notification automations on a connectivity condition so they never fire while offline.
Reload the Bring integration after network outages to restore the session.
Log chained exceptions to distinguish auth from transport failures quickly.

When it happens

Trigger: Calling a notify-style service on a Bring To-do entity (e.g. 'Going shopping' / 'arriving' notifications) while the Bring API request fails: bad HTTP status, timeout, invalid session cookie.

Common situations: Sending 'Going to the store' pings during a Bring outage, after token expiry, or to a list with no other members (some endpoints reject), from automations that fire when WAN is down.

Related errors

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