Anyone else having problems with 0.92 and Hue?

Configuration
1

Since upgrading to 0.92, every time HAss restarts I get this in the log

2019-04-26 18:14:41 ERROR (MainThread) [homeassistant.components.hue.light] Unable to reach bridge 192.168.1.51 ()
2019-04-26 18:15:10 INFO (MainThread) [homeassistant.components.hue.sensor_base] Reconnected to bridge 192.168.1.51

This isn’t a behaviour I’ve seen before and the upshot of it is that although HAss does eventually register the hub, HAss can’t see my lights so they disappear from the web interface and none of my automations work.

I’m posting here first rather than posting this as a bug just in case there’s something I’ve missed. I can’t see any breaking changes or similar mentioned in the announcement.

There’s no apparent problem with my network:

steve@nuc:/srv/docker/hass-config$ ping  -c 10  -i  0.2  -w 3  192.168.1.51
PING 192.168.1.51 (192.168.1.51) 56(84) bytes of data.
64 bytes from 192.168.1.51: icmp_seq=1 ttl=64 time=0.355 ms 
64 bytes from 192.168.1.51: icmp_seq=2 ttl=64 time=0.361 ms
64 bytes from 192.168.1.51: icmp_seq=3 ttl=64 time=0.304 ms
64 bytes from 192.168.1.51: icmp_seq=4 ttl=64 time=0.303 ms
64 bytes from 192.168.1.51: icmp_seq=5 ttl=64 time=0.282 ms
64 bytes from 192.168.1.51: icmp_seq=6 ttl=64 time=0.303 ms
64 bytes from 192.168.1.51: icmp_seq=7 ttl=64 time=0.295 ms
64 bytes from 192.168.1.51: icmp_seq=8 ttl=64 time=0.307 ms
64 bytes from 192.168.1.51: icmp_seq=9 ttl=64 time=0.283 ms
64 bytes from 192.168.1.51: icmp_seq=10 ttl=64 time=0.298 ms

--- 192.168.1.51 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 1840ms
rtt min/avg/max/mdev = 0.282/0.309/0.361/0.026 ms

And it’s definitely the Hue hub:

steve@nuc:/srv/docker/hass-config$ curl -s http://192.168.1.51 | grep -i hue\ per
    <title>hue personal wireless lighting</title>
      <img class="header-logo" src="hue-logo.png" alt="hue personal wireless lighting" />
      <h1>hue personal wireless lighting</h1>

As I said, I just want to check I haven’t missed something before I report a bug. Anyone else seen this?

Thanks

Steve

2

I am, and always have (since starting with HA in Jan’19).
Constantly getting entries in the log, like:

2019-05-08 08:59:53 ERROR (MainThread) [homeassistant.components.hue.sensor_base] Unable to reach bridge 192.168.0.9 (Error requesting data from 192.168.0.9: None)

My Pi, Hue and AP are sitting next to each other.
Never have issues trying to control Hue devices.

arch    armv7l     python_version  3.5.3  
dev     false      version         0.92.2 
docker  false      virtualenv      true   
hassio  false      mode            storage
os_name Linux
3

Me too. I’ve looked into it several times, but I have very little to add beyond the following:

  • I see it consistently during restarts - sometimes it doesn’t even load the lights, so I restart again and it complains again but loads the light (without any changes to config)
  • I thought it was an issue with the v1 hue, so I bought the v2, but I received the same result - on the other hand v2 added last know state of the light and is much more responsive
  • it also seems to be tied to hue moving to async
4

Same issue here.

5

I also have this issue.

2019-05-30 16:47:24 ERROR (MainThread) [homeassistant.components.hue.light] Unable to reach bridge 10.0.0.X (Error requesting data from 10.0.0.X: [WinError 64] The specified network name is no longer available)
2019-05-30 16:47:24 INFO (MainThread) [homeassistant.components.hue.light] Reconnected to bridge 10.0.0.X
6

Same here, sometimes I have to restart several times to get them to show up.

7

Just an idea. Is the bridge up and running before HA.

8

Yes, mine works fine with the app & HomeKit

9

Same issues with Hue on 93.2, with both of my bridges.

2019-05-30 17:43:07 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 192.168.1.87
2019-05-30 17:44:03 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 192.168.1.143

10

So the only recent change that I made was that I was prepping my config to use !secrets all over the place. I was super paranoid, so I also did the IPs of my devices, including my hue hubs.
After removing the !secrets entry for the IP addresses, I’m no longer seeing the error. Perhaps you have an extra space or something?

11

long, long story this is: see Philips Hue changed to unavailable among many others…

check, my experience indeed… that’s when things started to go awol. has to do with the Hue api not pushing, so HA has to poll the hub. Many requests are made to convince Philips to change to Push Api. check the dev forum on the Hue community for that.

12

I just upgraded to 0.94.0 updated python to 3.7.3 and this appears to have resolved. Yes both… after updating to .94 you get a warning that python 3.5 will be deprecated in August, so it bit the bullet.

I really hope that putting this out here doesn’t damn me, but this has been my experience.

13

I have the same problem in the latest version 0.96.5
If I remove the hue integration and set it up anew (without restarting hass), then I have the lamps available. The other icons (motion, etc… ) are though not available.

14

I have a lot of problems with Hue too. Everytime (and I say EVERYtime) I restart my home assistant (on a Raspberry Pi 4) i see all the hue lights as unavailable. I must always unlink hue integration and link again (tapping on the bridge button). It’s really frustrating. No one can help with these problems?

15

I also have the same issue and I have to delete the integration and re-include it every time. I sure hope that it’s a clean unistall and re-install, part of me is wondering if we have remnants in config files every time that we uninstall. I sure hope that there is a fix for it as well, it used to work flawlessly in the past. Now this causes issues when we recover for power failures and I am not home. I would prefer not moving to any other Zigbee solutions as I also like to use the Hue app from time to time.

16

I assure you that it happens on a fresh install too. In my case I tried to install on a linux computer, then a fresh install in a Raspberry Pi 4 via docker… every time the same problem: when I reboot (or as you said for a power failure) all lights are unavailable.

17

Same issue here, after fresh install on latest raspbian version, home assistant is unable to reach the hue bridge, all light unavailable, have to set it up again with the link.

Hopefully a workaround or solution comes up soon…

18

Did you try to add this in configuration.yaml?
With the new versione of HA (102) it seems to work.
If I delete this the lights don’t work, if i write this they work even when i reboot…

hue:
  bridges:
    - host: 192.168.xx.xx
      allow_unreachable: true
19

Yes I tried, but now the lights randomly become unavailable even when I don’t reboot.
They also randomly become available again after a while, can be couple of days though.

20

I too have issues with the Hue, but only with the outdoor motion sensor (my lights continue to work fine), and it only happens after a reboot of the RPi (HASSIO) v0.101.2.

The motion sensor, temperature and lux level sensors appear, then 5 secs later disappear, then reappear again 5 secs later…and repeat.

I have to remove the integration, and re-add it each time. I’ve not done anything special in my setup…everything is picked up by the discovery component. I have 2 Hue bridges on the network and I’ve tried associating the motion sensor with the other bridge in case that resolved it, but it still has the same issue.

EDIT: I’ve been re-adding and rebooting over the past 2hrs and the problem is persisting now :cry: