Hue discovery not working

Hello

I have just setup a brand new instance of home assistant. This is my second Home assistant server so I am already pretty familiar with the system.

I am running version 0.67.1 in a virtualenv
Python 3.6.5
Ubuntu 18.04 LTS

discover is switched on and has picked up my plex server automatically - however its not picking up my hue bridge to add my lights!

I have tried adding manually using :

hue:
  bridges:
    - host: DEVICE_IP_ADDRESS

But that does nothing either…

I can ping the bridge from the homeassistant server so it is reachable!

Can anyone help?

Ross

1 Like

No one else had this issue?

1 Like

A couple of things have changed with hue recently - From your main page, click configuration in the sidebar, then click integrations and see what’s there.

Thank you - found it!

Odd that it no longer shows on the main page any more to configure it! It used to.

Would be good if the manual reflected this.

Thanks again

It’s incremental development. In 0.68 you will get notifications as usual

1 Like

there’s an error in my setup, but I couldn’t imagine what that might be

34

it says discovery, but ive also setup this:

bridges:
  - host: !secret hue_ip
    allow_unreachable: true
    allow_hue_groups: true

Maybe your confusing it by using discovery and manual!

Remove the manual configuration and restart HA

Go back to Configuration side bar and go to integrations again and Hue Bridge should show up.

It worked okay for me via discovery once I knew where it was.

no, this was my setting for long now, working just fine…
ill comment it out and see what happens.

btw @robmarkcole custom component is working beautifully as ever, while that was my biggest fear… :wink:

1 Like

You are missing the line “hue” in your configuration example below.

It should be

hue:
  bridges:
    - host: DEVICE_IP_ADDRESS

If its not working there should be something in the error logs - please check and post it here

no, this is the content of my hue.yaml, which is referenced in my configuration.yaml through the line

hue: !include hue.yaml

sorry should have made that clear

Ok gotcha

So can you find any errors in the log that refer to hue? If its not working then there should be something…

rebooted with the hue settings commented out, so relying on the discovery shows this in the log:

2018-04-27 19:46:29 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Philips hue for hue
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/config_entries.py", line 186, in async_setup
    result = await component.async_setup_entry(hass, self)
AttributeError: module 'custom_components.hue' has no attribute 'async_setup_entry'
2018-04-27 19:46:29 ERROR (MainThread) [homeassistant.components.light] Error while setting up platform hue
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 82, in async_setup
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/lib/python3.6/site-packages/homeassistant/components/light/hue.py", line 56, in async_setup_platform
    bridge = hass.data[hue.DOMAIN][discovery_info['host']]
KeyError: 'host'

i still have the hue.py in /custom_components, maybe that should be taken out now?

Might be worth as you say removing everything referencing hue and letting discovery try and add it again

Im far from an expert in HA but not a novice either but I’m not sure what to make of that error…might need someone who knows a little more to chip in here…

I did take the custom_components/hue.py out and indeed the now native Hassio Hue component seems to operate as desired, showing and switching the lights.

Unfortunately @robmarkcole 's CC/sensor/hue.py stopped working. All sensors are there in the frontend, but show Unknown…

If this is really independent of the Hue in Hassio, how could this be? Only took out the hue: in configuration.yaml, should that g back after all @robmarkcole? Hope the (hassio) hue.py shouldn’t be restored…

this is the only error in the log now:

8-04-27 21:10:35 ERROR (MainThread) [homeassistant.components.light.hue] Unable to reach bridge [ip_address]

ip_address is correct and reachable… I can see and switch the lights, both through Hassio now, and my app.

no sensor is being created anymore by the CC, cant find them in the dev-tools

Please check you have the latest version of the component from GitHub. It’s just a REST sensor so shouldn’t be affected by any changes to the Hue hub component

Thanks. Yes I believed so, this is really unexpected, just after I was so fortunate to have it working before the Hassio component itself.

To be sure, it is completely independent from another setting or file is it? Only your CC in the config/custom_components/sensor.

even the sensor: - component: hue isn’t necessary anymore?

am also having the same issue. I added the hue: in configuration.yaml. HA shows the card to configure the bridge. I press the button on the Hue bridge but nothing happens, what can i do?

1 Like

The same issue here. I can see the HUE in menu - settings - Integrations - discovery - hue. Then when I press config, it wants to press the button on HUE bridge. I press the button but nothing happens. It says " Failed to register, please try again"

I’m running HASS in docker

Perfect, thanks legend.