Core: "New device discovered" message since 0.69

[oncleben31]

Home Assistant release with the issue: 0.69.0 and 0.69.1

Last working Home Assistant release (if known):
0.68.1

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

Hass.io on RPI3

Component/platform:

code or discovery

Description of problem:
After each reboot, I have a tile with the message: “New Device Discovered. We have discover a new devices on your network. Please Check it out” with a link to Configuration/integration section.
When I click on “Check it Out” I get two dialog boxes:

“Configured” showing:
Philips hue new
Integration: Philips Hue Bridge
Added by: import
State: loaded

“Available” showing:
a) deCONZ -
b) Philips Hue Bridge -
c) Zone - (Not sure why this is here as I don’t have zones configured.)

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

#zone:

Traceback (if applicable):
N/A

Additional information:
deConZ and Zone feature not used.
Issues shared with other users: see https://community.home-assistant.io/t/new-device-discovered-message-with-0-69/53178/5

[awarecan]

Got exactly same message.

I am using Philips hue, but not deCONZ nor Zone.

[dshokouhi]

duplicate of #1174 from polymer

https://github.com/home-assistant/home-assistant-polymer/issues/1174

[kellerza]

Do you all have discovery: and manual emulated_hue:?

[dshokouhi]

I do

[lvlie]

Discovery and normal hue here. Have zones configured as well, but is seems that adding of zones to the configuration thingy triggers this

[kellerza]

Please try:

discovery:
  ignore: philips_hue

[arsaboo]

@kellerza I thought ignore was removed for Hue.

[arsaboo]

BTW....I am seeing the same

[kellerza]

@arsaboo Only for a while in dev, it's back

It was removed / misplaced from the validation string for a while :-)

[dshokouhi]

I am going to close the bug I opened in polymer so we only have 1 unless the bug really belongs there?

[awarecan]

discovery:
  ignore: philips_hue

done the trick

Can we make it as default behavior? If there is already a configured hue, than ignore the hue discovery.

[kellerza]

@awarecan although this is possible (add phillips_hue to ignore if a manual hue / emulated_hue is found) I don't think this is the right approach.

In the original config_entries vision @balloob had to option to permanently disable discovery of certain components, so once that is implemented, this issue's problem will disappear.

For now I suggest we close this issue, with the manual ignore as a short term fix and config_entries solving this specific case (and more) in the long run.

[oncleben31]

Okay the workaround do the job.
I don't know what is standard here. Do we keep it open to have a reminder. Or do we close at it seems to work as design even if not so obvious for the users ?

[Mariusthvdb]

if one is ignoring the philips_hue under discovery, do you delete it first in the discovered settings, and then let it read the setting s from the config hue: ?

or let it discover first automatically, and then ignore.

btw, ignoring the ikea_tradfri (though not yet automatically added in the new settings) does improve its reliability a lot

btw2 why not comment out the full discovery ? If you've manually configured Hue and/or Tradfri, and dont need the other 2, there's no need for it?

leave this open please, since it really is an open issue, not resolved by this 'workaround'.