Handle TimeoutError gracefully to prevent blocking HA startup#387
Merged
Conversation
Catch TimeoutError from aiohttp requests and convert to RequestError at the API client level, with defense-in-depth handling at the coordinator and integration setup layers. Transient API timeouts now result in ConfigEntryNotReady (auto-retry) during setup and UpdateFailed (cached data preserved) during polling.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #370
TimeoutErrorfrom aiohttp requests inRequestErrorat the API client level (client.py), converting it into theBHyveErrorhierarchy so all existing error handlers catch it automaticallyTimeoutErrorhandling at the integration setup (__init__.py), coordinator (coordinator.py), and options flow (config_flow.py) layersConfigEntryNotReady, which tells HA to retry with exponential backoff instead of blocking startupUpdateFailed, which preserves the last known cached data and retries at the next coordinator interval — entities stay available with slightly stale dataTest plan