core: Philips Hue changed to unavailable

Home Assistant release with the issue:

Last working Home Assistant release (if known): unsure… but upgraded to 0.78 and issue still persists.

Operating environment (Hass.io/Docker/Windows/etc.):

Docker running on Mint. Component/platform:

Description of problem: Philips Hue hub becomes unavailable when it is actually online and responsive. Therefore all lights switch to “changed to unavailable”. Then switch back to the previous state.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

hue:
  bridges:
    - host: 192.168.0.11
      allow_unreachable: true
      allow_hue_groups: true


tried both to false.. same problem

Traceback (if applicable):

Additional information: thread on the forum https://community.home-assistant.io/t/philips-hue-changed-to-unavailable/

errors from the logs 2018-09-18 12:46:01 ERROR (MainThread) [homeassistant.components.light.hue] Unable to reach bridge 192.168.0.11 2018-09-18 12:46:06 INFO (MainThread) [homeassistant.components.light.hue] Reconnected to bridge 192.168.0.11

All custom components were removed, all additions components were removed and it still happened. Sometimes every 5-10 minutes.

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 4
Comments: 95 (43 by maintainers)

Most upvoted comments

I’ve opened a PR to add the logging to the Hue component. You will be able to configure the logger component to show these logs in the next release:

logger:
  logs:
    homeassistant.components.light.hue: debug

balloob on Oct 2, 2018

This logic is now live in the beta and will be part of 0.80.

balloob on Oct 8, 2018

I put this in that forum thread, but maybe it will help diagnose…

Upon boot the entire hue system was unavailable. The logs would say, ‘hue system taking longer than 10 seconds’. I run everything on copper , no wifi used (I have WiFi, but the only things that connect to it are some phones and ESP32(s). Also no zigbee (other than Hue).

I rebooted many times over multiple days, tried many, many different possible fixes, none of which worked. What finally fixed it for me was:

discovery:
  ignore:
    - philips_hue

erichiller on Nov 27, 2019