-
-
Notifications
You must be signed in to change notification settings - Fork 33.8k
Excessive traceback of errors updating hue lights: timeout and refused connections #8003
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can confirm i am getting the same problem. Happens with random lights and logs errors multiple times per day. I can still control the lights via the UI and automations work.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
):0.46.0
Python release (
python3 --version
):3.5.2
Component/platform:
light.hue
Description of problem:
Logs are filled with traceback of errors about timeout or rejected connections when trying to update the state of some hue lights. In my case, this happen multiple times each day (but not always)
Expected:
Better error handling so logs are cleaner.
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
I'm using a 2º gen Hue Bridge (the one compatible with Siri) with 9 hue bulbs. The ones that fail are 1 bulb located far away from the bridge, and a group of three bulbs that I use with hyperion to simulate a phillips ambilight around my tv running kodi. The lights in the group only fail when hyperion is running (and changing the lights very fast), so for these I think it is a problem of bridge overload. For the distant lamp, I think the bridge is not seeing it sometimes. Anyway, I thing the traceback should not appear in the log.
The text was updated successfully, but these errors were encountered: