8000 Discovery - same Chromecast added multiple times · Issue #7959 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Discovery - same Chromecast added multiple times #7959

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
dthulke opened this issue Jun 8, 2017 · 6 comments · Fixed by #12474
Closed

Discovery - same Chromecast added multiple times #7959

dthulke opened this issue Jun 8, 2017 · 6 comments · Fixed by #12474

Comments

@dthulke
Copy link
Contributor
dthulke commented Jun 8, 2017

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.46.0

Python release (python3 --version):
Python 3.4.2

Component/platform:
media_player.cast
discovery

Description of problem:
If the IP address of a Chromecast changes it is added as duplicate to Home Assistant.

Expected:
Home Assistant recognises that it is the same Chromecast and does not add it a second time.

Problem-relevant configuration.yaml entries and steps to reproduce:

discovery:
  1. Start home assistant in a network with a single Chromecast
  2. Change the IP address of the Chromecast
  3. Chromecast appears twice in Home Assistant

Traceback (if applicable):
Not applicable

Additional info:
Related to #5588

The problem is that the IP address is part of the discovery_hash in discovery.py.
Additionally it is probably necessary to update the existing Chromecast instance to use the new IP address.
@balloobbot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@pschmitt
Copy link
Contributor
pschmitt commented Aug 23, 2017 •
edited
Loading

Same issue here with a Sony SRS-ZR7 Cast-enabled speaker with version 0.51.2. I do get a media_player.sony_srszr7 and media_player.sony_srszr7_2

@dthulke
Copy link
Contributor Author
dthulke commented Sep 8, 2017

I also updated to version 0.52.1 and still have the same issue.

@Mike1082
Copy link

I am on version 0.56.2 and this exact issue happens with my Roku devices. @dthulke seems to be correct about the IP addresses. I just updated my switch and WAP yesterday, so both of my Rokus just got new IPs. New entities were created, and my automations based on the Rokus stopped working (the newly created devices get the state updates).

@dgomes
Copy link
Contributor
dgomes commented Feb 19, 2018

Have everyone tested using the last version 0.63.3

The entity registry should have solved this issue

@ 9A8E OttoWinter
Copy link
Member

@dgomes This is not fixed (yet) by the entity registry, because the entity registry only works if a unique_id property is added to the entity. #12474 would fix that though.

@OttoWinter OttoWinter mentioned this issue Feb 21, 2018
Merged
3 tasks
@home-assistant home-assistant locked and limited conversation to collaborators May 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Cast unique_id and async discovery OttoWinter/home-assistant
6 participants
@pschmitt @dgomes @Mike1082 @OttoWinter @dthulke @balloobbot
0