home-assistant/core · error · UpdateFailed
Service {self._service_id} was unrecognised
Error message
Service {self._service_id} was unrecognised What it means
UpdateFailed(f'Service {service_id} was unrecognised') raised by the aussie_broadband coordinator when the aussiebb library raises UnrecognisedServiceType during get_usage. It means the service id stored in the config entry maps to a plan type the library cannot parse usage for (or the service no longer exists on the account).
Source
Thrown at homeassistant/components/aussie_broadband/coordinator.py:61
) -> None:
"""Initialize Atag coordinator."""
super().__init__(
hass,
_LOGGER,
config_entry=config_entry,
name=f"Aussie Broadband {service_id}",
update_interval=timedelta(minutes=DEFAULT_UPDATE_INTERVAL),
)
self._client = client
self._service_id = service_id
@override
async def _async_update_data(self) -> dict[str, Any]:
"""Update data via library."""
try:
return await self._client.get_usage(self._service_id)
except UnrecognisedServiceType as err:
raise UpdateFailed(f"Service {self._service_id} was unrecognised") from err
View on GitHub (pinned to 58a3fdb3ea)
Solutions
- Update the aussiebb python library / Home Assistant to pick up newly supported service types
- Confirm the service still exists on the account in the MyAussie portal and matches the config entry
- If the service was replaced, delete the config entry and re-add the integration selecting the current service
- If it's a genuinely new plan type, report it upstream to the aussiebb library with the service type string
Defensive patterns
Strategy: validation
Validate before calling
services = await client.get_services()
valid = {s["service_id"] for s in services}
if service_id not in valid:
raise ValueError(f"Service {service_id} not present on account") Try / catch
try:
await coordinator.async_refresh()
except UpdateFailed as err:
if "was unrecognised" in str(err):
# service type unsupported or cancelled: reconfigure required
await hass.config_entries.async_reload(entry.entry_id) # or prompt reconfig
raise Prevention
- Select services fresh from the account list during setup rather than typing ids
- Update aussiebb library when new plan types appear
- Remove config entries for cancelled services
When it happens
Trigger: get_usage(service_id) hitting a service whose type string from the Aussie Broadband API isn't one the library knows (new plan category, e.g. some NBN/VOIP/mobile variants); the service was cancelled on the account but the entry still references it.
Common situations: Aussie Broadband adding a new service type the aussiebb package version doesn't handle; user changed plans; service id entered during setup belongs to another account.
Related errors
- Missing price data, skipping update
- api_error
- Error communicating with API: {err}
- Error communicating with API: {err}
- Received invalid data type
AI-assisted analysis of home-assistant/core@58a3fdb3ea (2026-08-14).
Data as JSON: /api/errors/c5ea4415e14f7996.
Report an issue: GitHub.