Handle 403/404 errors gracefully for users without gear

- Change 403 Forbidden errors from ERROR to DEBUG level
- Change 404 Not Found errors from ERROR to DEBUG level
- Add helpful message indicating user may not have gear configured
- Prevents error spam in logs for users without Garmin gear
- Integration continues to work normally without gear sensors
This commit is contained in:
Ron Klinkien
2025-11-06 16:06:02 +01:00
parent d6e669494d
commit 2f2f38839a

View File

@@ -486,9 +486,12 @@ class GarminConnectDataUpdateCoordinator(DataUpdateCoordinator):
if err.response.status_code == 401:
_LOGGER.error(
"Authentication error while fetching Gear data: %s", err.response.text)
elif err.response.status_code == 403:
_LOGGER.debug(
"Access forbidden while fetching Gear data (user may not have gear configured): %s", err.response.text)
elif err.response.status_code == 404:
_LOGGER.error(
"URL not found error while fetching Gear data: %s", err.response.text)
_LOGGER.debug(
"Gear data not found (user may not have gear configured): %s", err.response.text)
elif err.response.status_code == 429:
_LOGGER.error(
"Too many requests error while fetching Gear data: %s", err.response.text)