core: 0.95.0 Google Cast Ignore Discovery Not Working

Home Assistant release with the issue:

arch	x86_64
dev	false
docker	true
hassio	true
os_name	Linux
python_version	3.7.3
timezone	America/Los_Angeles
version	0.95.0
virtualenv	false

Last working Home Assistant release (if known): 0.94.4

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

Nothing special really, docker in a virtualbox with direct network access.

Component/platform:

Description of problem: I have - google_cast in my ignore section of discovery and it always worked until the last update.

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

discovery:
    ignore:
    - plex_mediaserver
    - apple_tv
    - google_cast
    - igd

Traceback (if applicable):

Additional information:

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 10
Comments: 40 (8 by maintainers)

Commits related to this issue

fixing Chromecast Discovery Credits: https://github.com/home-assistant/home-assistant/issues/24786#issuecomment-524804435 — committed to J3n50m4t/HomeAssistantConfiguration by J3n50m4t 5 years ago

Most upvoted comments

0.100.1 still not fixed 😦

jarzebskim on Oct 11, 2019

0.99 - still not working.

jarzebskim on Sep 19, 2019

Well they are making changes to the way discovery works in HA, but the new way of doing it seems to have removed the ability to ignore certain devices from being discovered. Hopefully they will add back in this functionality.

Nice idea on using an automation for a workaround, the ‘persistent_notification.dismiss’ service may do what you need. I’m currently using the ‘Adding the google_cast devices then not using them’ workaround for now.

I think I may have found the code causing the notifications, take a look at homeassistant/generated/zeroconf.py

If you remove/comment out the following lines:

    "_googlecast._tcp.local.": [
        "cast"
    ],

then it should stop these notifications. Note unofficial fix, try at own risk, etc. and will probably be overrwritten by the next update, but worth trying 😃

DeviousPenguin on Jul 21, 2019

0.96.2 - still not fixed

my idea to workaround is create automation to delete this one specific alert

I don’t think this will be fixed soon

jarzebskim on Jul 20, 2019

I got an email from them saying that they were going to close this at the end of the month since no traction has been made.

Can I ask you keep this issue open a little longer? I may have a working fix this, it involves patching the existing discovery component and adding it as a custom component, and if I get it working I can share a way to disable discovery for certain devices.

I’m working on a way to make it so when a new version of HA is released it will continue to work.

To anyone still having this issue, can you tell me if you are using a VENV in install of HA or HASSIO?

DeviousPenguin on Nov 1, 2019

My temporary solution:

automation:
- alias: 'Remove new devices notification'
  trigger:
    - platform: state
      entity_id: persistent_notification.config_entry_discovery
      to: notifying
    - platform: homeassistant
      event: start
  action:
    - service: persistent_notification.dismiss
      data:
        notification_id: config_entry_discovery

rasmusbe on Aug 26, 2019

Still no changes in 0.96.0

phischmi on Jul 12, 2019