Why do I get Philips hue errors? Not using it

Configuration
1

I got errors of Philips Hue in my logs, however I don’t use it…
Why do I still get those errors?

Error in the log:

17-03-06 03:17:02 WARNING (Thread-12) [netdisco.philips_hue_nupnp] Could not query server https://www.meethue.com/api/nupnp: HTTPSConnectionPool(host='www.meethue.com', port=443): Read timed out. (read timeout=5)

2

Do you have a Phillips Hue Hub? The error makes it appear as though discovery is finding one.

3

Nope, nothing of philips hue installed…

4

Anything like a zigbee hat or stick?

5

I only using an aeotec z wave stick and a few fibaro dimmer modules, no philips hue…

6

Well then I don’t have any more ideas.

7

I have the same problem. not using hue

8

Same here. No hue but the error in the logs.

9

I have the same warnings and I don’t use hue.

10

I’m using Hue and I see the same errors.
When I retrieve the URL manually, I get my Hue bridge IP as response:

# curl https://www.meethue.com/api/nupnp
[{"id":"00xxxxxxxxxxxx46","internalipaddress":"192.168.xx.yy"}]

So my guess is, that this is used by the discovery component to determine if there’s a Hue bridge and what IP it has.
I’m not sure what caused the error. Probably some congestion on the Philips side (meethue.com) that prevented a timely response from the API.

From what I read in the documentation, a simple:

discovery:
  ignore:
    - hue

should get rid of the errors (preventing any future auto-discovery of a Hue bridge).
Maybe it’s philips_hue - the docs are not clear on that.

Sebastian

EDIT: it seems to be philips_hue - using only hue fails the config check.

11

I recently installed pihole. To my surprise my pi (running only pihole and Homeassistant) is querying www.meethue.com every 5 minutes even though I am fully sure I don’t use hue and don’t use the emulated hue…

I think this is a bug.