Philips Hue problem with discovery\restart 0.104

[sagitt]

Home Assistant release with the issue:
0.104

Last working Home Assistant release (if known):
0.103

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

Integration:
https://www.home-assistant.io/integrations/hue/

Description of problem:
After upgrade i see an hue to pair with ignore option (hue already configured), so i ignored it with new feature (I have hue in discovery\ignore!!!). After a restart, my hue won't work and show invalid config. So i deleted integration and show 2 hue... as image. If i try to re-pair the hue without ignore, restart ecc.. the same.

with the second one, all works fine. i think there is a problem with hue\discovery. I configured it in yaml.

Philips HUE

Platforms

hue:
bridges:
- host: !secret philips_hue_host
allow_unreachable: true
allow_hue_groups: false

[probot-home-assistant]

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!

[nzepp]

I am having a similar issue, after upgrade from 0.103 to 0.104.1 and 104.2 my bridge is discovered each time I restart. The bridge is already in the config but cannot communicate with the devices. I removed it completely and restarted, it found the bridge and i paired it but it did not bring the devices back. I rebooted hassio and the discovery found another bridge. Regardless of how many times I re-add it, I cannot get it to load the hue devices

[plasticrake]

I'm having similar isssues to @nzepp and @sagitt. With the existing paired bridge all the devices were unavailable and showed a new bridge to discover. I paired with the "new" bridge and it added a duplicate bridge and the devices seemed to be working. I removed the "old" bridge and now all the devices are unavailable still.

I do see this in the logs. The IP is correct and is reachable from the device.

Unable to reach bridge 10.0.0.222 ()
January 17, 2020, 12:45 PM components/hue/light.py (ERROR)

[plasticrake]

Upgrading to 0.104.2 seems to have fixed my hue issues.

[plasticrake]

I spoke too soon. After another restart on 0.104.2 all hue devices went back to unavailable. They were only working on the first start on 0.104.2.

[nzepp]

I also upgraded to 0.104.2 and had limited success.

I then deleted everything related to hue from my configuration (including the bridge definition in configuration.yaml) restarted and allowed discovery to find the bridge. It added the hue, works, and has continued to work across multiple reboots. Not sure if this will work for everyone but worth a try.

It might be worth a try for @plasticrake and @springstan to see if results are consistent.

[balloob]

Please define limited success. Errors in your logs ?

[nzepp]

Please define limited success. Errors in your logs ?

Worked intermittently when I had the IP of the bridge coded into configuration.yaml. Works as expected when using discovery and removing all hue config from configuration.yaml

[bcmitri]

I've seen this issue twice since upgrading. In each case, my Hue hub is re-discovered, leaving me with an old set of devices that are no longer configured and a new set of devices that are not yet configured. When I go through the configuration process for the newly-discovered devices, I'm left with duplicate integrations / entities that I later need to clean up.

[nzepp]

Since Upgrading to 0.104.2 and removing the hue section completely from my configuration.yaml file I have not had issues (knock on wood).

[inverse]

Even after removing the configuration and setting up the integration again I am still running into issues :/

Logs seem indicative that it's failing to reach the bridge even though it's clearly accessible.