Core: HUE Lights and sensors not available in Home Assistant 0.104.1

[gambith]

Home Assistant release with the issue:

0.104.1

Last working Home Assistant release (if known):
0.104.0

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

Ubuntu 18.4 LTS with Home Assistant 0.104.0 in Docker
Integration:

HUE

Description of problem:
After upgrade to 0.104.1 none of the HUE devices are available, Bulbs, LED Strips. Sensors and Remote Controls.

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

Configuration.yaml

hue:
    bridges:
      - host: <IP_ADDRESS HUE Bridge>

Traceback (if applicable):

2020-01-17 08:12:35 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Philips hue for hue
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 215, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/hue/__init__.py", line 114, in async_setup_entry
    allow_unreachable = config[CONF_ALLOW_UNREACHABLE]
KeyError: 'allow_unreachable'
2020-01-17 08:12:35 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Philips hue for hue
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 215, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/hue/__init__.py", line 114, in async_setup_entry
    allow_unreachable = config[CONF_ALLOW_UNREACHABLE]
KeyError: 'allow_unreachable'

Additional information:

[probot-home-assistant[bot]]

Hey there @balloob, mind taking a look at this issue as its been labeled with a integration (hue) you are listed as a codeowner for? Thanks!

[celeroncool]

Fixed by adding the following code to config

hue:
  bridges:
    - host: DEVICE_IP_ADDRESS
      allow_unreachable: true <- this
      allow_hue_groups: true <- this

According to https://www.home-assistant.io/integrations/hue/ these are optional, but after upgrade to 104.1, they are not.

[nelbs]

This didn't solve my problem. after a restart in 104.1 i get the following error
Unable to reach bridge 192.168.1.102 ()

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

[sfnetwork]

Fixed by adding the following code to config

hue:
  bridges:
    - host: DEVICE_IP_ADDRESS
      allow_unreachable: true <- this
      allow_hue_groups: true <- this

According to https://www.home-assistant.io/integrations/hue/ these are optional, but after upgrade to 104.1, they are not.

I can confirm this worked for me as well :)

[gambith]

Works for me also.

[JPReding]

Fixed by adding the following code to config

hue:
  bridges:
    - host: DEVICE_IP_ADDRESS
      allow_unreachable: true <- this
      allow_hue_groups: true <- this

According to https://www.home-assistant.io/integrations/hue/ these are optional, but after upgrade to 104.1, they are not.

Yup. Worked for me. Thankfully still permits:

allow_hue_groups: false

[dedors]

After the 0.104 update I had to remove my entry (it was just the "host:" entry) for my hue from my configuration.yaml in order to discover any lights again! (Had to remove the old setup and readd it via integrations).
Can someone test if adding new lights AND a config entry exists, it still gets discovered? So we won't all run intro trouble later on...

[michaelarnauts]

I assume this is due to https://github.com/home-assistant/home-assistant/pull/30846

[tfoote000]

Hey guys I'm still having this issue on 0.104.3. I have tried setting up Hue as an integration, and as a config, and every time I restart HA my Hue Bulbs ALL show Unavailable. This is what my homeassistant log file has:

ERROR (MainThread) [homeassistant.components.hue.light] Unable to reach bridge 192.168.142.24 ()
INFO (MainThread) [homeassistant.components.hue.sensor_base] Starting sensor polling loop with 5.0 second interval
INFO (MainThread) [homeassistant.components.hue.sensor_base] Reconnected to bridge 192.168.142.24

The result of whatever happens is that my devices still show unavailable, and to fix it I have to delete the integration and re-add it again. Any thoughts on a fix for this that I might be missing?

I have added the huesensor custom component.

I have tried adding HUE only as an integration, I have cleaned my Hue Bridge, I have turned off automatic discovery of Hue, however HA still discovers hue automatically. Here is my configuration.yaml entry:

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

[dedors]

@tfoote000: I'm not sure but I think huesensor is not needed anymore since last year. At least I removed it at some point.

My suggestion would be, remove any hue entry in configuration.yaml, delete also the hue integration on the UI, then reboot(!), then add it via integration auto discovery again. Check on integration page if it lists any lights.
At least that worked for me. Because I renamed my lights on the hue bridge a year ago, it was still working with the old names until now. So I had to update my configurations but everything is working.

[balloob]

If you use the huesensors custom component we cannot help you if things do not work. Also do not use closed issues to discuss if an issue still exist, open a new one. 105 will include a bugfix, so you can try the beta today or wait till Wednesday.