8000 Google Home group shows up twice after home assistant has been running for a day · Issue #11905 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Google Home group shows up twice after home assistant has been running for a day #11905

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
dshokouhi opened this issue Jan 25, 2018 · 10 comments · Fixed by #12474
Closed

Google Home group shows up twice after home assistant has been running for a day #11905

dshokouhi opened this issue Jan 25, 2018 · 10 comments · Fixed by #12474

Comments

@dshokouhi
Copy link
Member
dshokouhi commented Jan 25, 2018 •
edited
Loading

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.61.1

Python release (python3 --version):
3.6.3

Component/platform:
media_player/cast

Description of problem:

After home assistant has been running for almost a day I will notice that one of my google home groups shows up under 2 entity ID's and automations stop working on the original one. So if I have media_player.home_notification after some time I will also see media_player.home_notification_2 show up.

Expected:

The media_player cast group should only be identified under 1 entity ID instead of multiple later on

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

discovery:
  ignore:
  - netgear_router

media_player:
  - platform: cast
  1. Turn on home assistant and have google home groups configured to show up (I have 2 but only has the issue)
  2. Keep home assistant running for 1 day
  3. Check entity listing to see the group show up twice

Traceback (if applicable):

My log shows the following errors for the cast platform consistently throughout

2018-01-23 18:02:28 ERROR (Thread-9) [pychromecast.socket_client] Error reading from socket.
2018-01-23 18:02:28 WARNING (Thread-9) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-01-23 18:02:28 ERROR (Thread-9) [pychromecast.socket_client] Failed to connect, retrying in 5.0s

2018-01-23 19:20:36 WARNING (Thread-5) [pychromecast.socket_client] Heartbeat timeout, resetting connection

Additional info:

image
@point-4ward
Copy link
Contributor

I'm not seeing this behaviour on my system.

In fact, not wishing to tempt fate, my chromecast implementation has been working great the last few updates.

I still get the occasional error messages in the log for failed to connect or heartbeat timeout but it hasn't affected the actual operation of the devices or the groups.

@Mudsie
Copy link
Mudsie commented Jan 25, 2018

I have also seen this behaviour. Ended up with 3 versions of one group and 2 of another. A restart of HA results in a single group being present as expected. Will monitor and report back if this was a one off.

@freol35241
Copy link
Contributor
freol35241 commented Jan 25, 2018 •
edited
Loading

home-assistant-libs/pychromecast#165

@point-4ward
Copy link
Contributor

That's interesting, I don't use discovery at all and just have

platform: cast

in my config, so it's 'discovering' the devices that way rather than being defined one-by-one.

How is everybody else's configured?

@dshokouhi
Copy link
Member Author

@mf-social are you disabling discovery for cast as well? or you just have it configured like I do? I did not explicitly disable discovery for the cast component and I do have it enabled.

@point-4ward
Copy link
Contributor

I have no discovery: in my config, everything is configured manually.

@dshokouhi
Copy link
Member Author

good catch, updating the description to include that as well.

@dshokouhi
Copy link
Member Author

I have not restarted home assistant since creating this bug, today I noticed my second group now shows up twice.

@JIOB
Copy link
JIOB commented Feb 3, 2018

I'm seeing this on my system. Similar config discovery: activated and cast platform under media player. I did find that by setting static IP addresses to all my Chromecast/Home devices would delay it happening but not cure it.

I wasn't aware the adding just cast was enough to discover devices i will trying telling discovery to ignore and see if that helps.

@OttoWinter
Copy link
Member

Maybe we could leverage the new unique_id feature to fix this bug. Every cast device + cast group reports a UUID, so that could be used for unique_id. I don't have any audio groups myself right now, but looking at this comment it seems like the UUID is unique for every group as well - the only thing that would be good to know is whether the UUID changes when the "elected leader" changes... Could someone with knowledge of pychromecast test that?

This was referenced Feb 13, 2018
Closed
Merged
@balloob balloob mentioned this issue Feb 21, 2018
Merged
1 task
@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
@dshokouhi @OttoWinter @point-4ward @JIOB @freol35241 @Mudsie
0