-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
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
Hue dependency buggy #7749
Comments
Phue just released version 1.0 that carries this fix. Dependency should be updated to that version. |
This was referenced Jul 11, 2017
fabaff
added a commit
that referenced
this issue
Jul 11, 2017
pvizeli
pushed a commit
that referenced
this issue
Jul 11, 2017
Merged
dethpickle
pushed a commit
to dethpickle/home-assistant
that referenced
this issue
Aug 18, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
):Running home assistant through docker. This issue appears at least in versions 0.32, 0.39, 0.45 so I would guess that it appears in all in between versions.
Python release (
python3 --version
):Component/platform:
Philips hue dependency phue.py
Description of problem:
On version 0.9 of phue there is a bug with a connection being closed before the response is managed which leads to it returning None when it should return values. This leads to a crash on the Home Assistant component that manages the lights since it is expecting json and getting None instead.
Expected:
Lights being detected and working properly.
Problem-relevant
configuration.yaml
entries and steps to reproduce:The standard configuration is enough for the malfunction.
Traceback (if applicable):
Additional info:
This issue is fixed in the phue library with PR #109 studioimaginaire/phue#106 .
It is fixed in current master and I have requested a tag of 0.9.1 so it can be updated on Home Assistant. This needs some monitoring on Home Assistant part so it updates when the dependency bumps its version.
The text was updated successfully, but these errors were encountered: