-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Issues With Unresponsive Lights that are added through home assistant #22
Comments
+1 have the same issue with some of my lights |
+1 same issue for me |
@mariusmotea do you have an idea what could be the issue? would be nice if this could get fixed soon :) |
i don't use this integration to debug it by myself so i need to see what is returned from homeassistant. For me it looks like we always expect an array and for some reasons (maybe api changes) it is not there 'NoneType' object is not subscriptable |
@mariusmotea : thanks for your very fast answer. I am using the DIYHue docker container and (on another system) the hassio-addon - both have the same issue. Can I generate a debug log for you ? How do to this? |
Sounds like an issue with diyHue itself then, rather than the add-on. I've stopped using diyHue because of these issues, but I seem to remember that the lights I mainly had issues with were those with missing settings (i.e. brightness-only lights without color control, or switch-only lights with no brightness or color) |
@mariusmotea : I now activated the debug log and I can see the following:
seems that there is a handshake error with HomeAssistant... |
Same issue here - a recent HA update broke this and diyhue needs to be updated to correct this. Right now DIYHUE - HA is totally broken |
yes, i agree! Would be nice if the author of the HomeAssistant -DIYHue communication could have a look at it and try to solve the issues. Not sure who did it? Maybe @mariusmotea or @maxbec know more here? |
unfortunately my lights are added to homeassistant using hue integration and i don't have any lights in homeassistant to use the websocket integration.
|
@mariusmotea: understand. I have added all my zigbee lights via the zigbee2mqtt integration in DIYHue and some other lights via the homeassistant web socket communication. The mqtt ones look to be fine. I now started the container again in debug mode and here is the log. Maybe this helps you to figure out the issue. 1.) the very first mqtt server error seems to be related to the startup of the DIYHue container - I guess this is no real issue due to the fact that the mqtt lights seem to work.
". This seems to be the problem for me - HA seems to send None as Brightness if the light is off.
What do you think? |
OSError: [Errno 113] No route to host this means that mqtt broker is not reachable, it is a networking issue or the mqtt broker is stopped. |
@mariusmotea : i now fixed the mqtt issue on my side, but still some of the lights (e.g. Schlafzimmer Deckenlicht) which are connected via the homeassistant_ws stay unavailable... I only see the following in the debug log:
Furthermore I figured out that I can not connect with the Hue Essentials App at the moment. I think it is related to @#26 Here is the log when I try to connect:
|
do you still get this error with the latest version? |
Here is some of the output from the Addon inside of home assistant:
2023-11-07 12:21:10,358 - services.stateFetch - INFO - start lights sync
2023-11-07 12:21:10,359 - services.stateFetch - WARNING - Light Bars is unreachable: 'NoneType' object is not subscriptable
2023-11-07 12:21:10,360 - services.stateFetch - WARNING - Floor Light is unreachable: 'NoneType' object is not subscriptable
2023-11-07 12:21:10,360 - services.stateFetch - WARNING - Bathroom Light 3 is unreachable: 'NoneType' object is not subscriptable
2023-11-07 12:21:10,361 - services.stateFetch - WARNING - Bathroom Light 2 is unreachable: 'NoneType' object is not subscriptable
2023-11-07 12:21:10,362 - services.stateFetch - WARNING - Bathroom Light 1 is unreachable: 'NoneType' object is not subscriptable
2023-11-07 12:21:10,363 - services.stateFetch - WARNING - Kitchen Light 1 is unreachable: 'NoneType' object is not subscriptable
2023-11-07 12:21:10,363 - services.stateFetch - WARNING - Kitchen Light 2 is unreachable: 'NoneType' object is not subscriptable
2023-11-07 12:21:10,364 - services.stateFetch - WARNING - Can Light 1 is unreachable: 'NoneType' object is not subscriptable
2023-11-07 12:21:10,364 - services.stateFetch - WARNING - Fan Light is unreachable: 'NoneType' object is not subscriptable
It seems that diyhue finds the lights through the home assistant API and they are all controllable through the hue app but the hue app as well as the diyhue webpage marks the lights as offline/unresponsive
The text was updated successfully, but these errors were encountered: