Hue light: No traceback for timeouts or refused connections to the bridge #8524
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.
Description:
When the Hue bridge is stressed**, some times a timeout or a
ConnectionRefusedError
happens. The exception doesn't need to be logged.The errors are like this:
A simple error message like
"The bridge refused the connection"
helps much more to analyse the logs.** When doing a lot of light changes (in my case, with Hyperion working as an Ambilight TV with 6 hue bulbs), the bridge goes to some overload, and sometimes doesn't answer to HA.
Related issue (if applicable): fixes #8003
Example entry for
configuration.yaml
(if applicable):