home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.9k stars 30.97k forks source link

Google Home speakers, chromecasts and display no longer working #128220

Open mptpro opened 1 month ago

mptpro commented 1 month ago

The problem

As of a week ago all of my Google Speakers (regular and mini), Chromecast devices and Display no longer work with HA.

The Google Home entry in Ingratiations shows no errors, but in Entities it shows the red circle with the message "Not Provided".

Within a Google Entry I see the message, "This entity is no longer being provided by the cast integration. If the entity is no longer in use, delete it in settings."

What version of Home Assistant Core has the issue?

2024.10.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Google Home

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 month ago

Hey there @emontnemery, mind taking a look at this issue as it has been labeled with an integration (cast) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `cast` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign cast` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


cast documentation cast source (message by IssueLinks)

seanmccabe commented 3 weeks ago

Getting the same issue

seanmccabe commented 3 weeks ago

Additionl data from the debug log:

2024-10-29 17:57:48.002 DEBUG (SyncWorker_10) [homeassistant.components.cast.discovery] Starting internal pychromecast discovery
2024-10-29 17:57:48.002 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.80
2024-10-29 17:57:48.002 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.81
2024-10-29 17:57:48.002 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.82
2024-10-29 17:57:48.002 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.83
2024-10-29 17:57:48.002 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.84
2024-10-29 17:57:48.002 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.85
2024-10-29 17:57:48.002 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.86
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.87
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.88
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.89
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.90
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.65
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.66
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.67
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.52
2024-10-29 17:57:48.003 DEBUG (SyncWorker_10) [pychromecast.discovery] Addded host 192.168.10.53
2024-10-29 17:57:48.005 DEBUG (Thread-3) [pychromecast.discovery] HostBrowser thread started
2024-10-29 17:57:48.006 DEBUG (Thread-3) [pychromecast.dial] Resolved service HostServiceInfo(host='192.168.10.80', port=8009) to 192.168.10.80
2024-10-29 17:57:48.060 WARNING (MainThread) [zeroconf] Error with socket 52 (('10.192.1.254', 5353))): [Errno 126] Required key not available
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 1265, in sendto
    self._sock.sendto(data, addr)
OSError: [Errno 126] Required key not available
2024-10-29 17:57:48.078 DEBUG (Thread-3) [pychromecast.dial] Resolved service HostServiceInfo(host='192.168.10.80', port=8009) to 192.168.10.80
2024-10-29 17:57:48.090 DEBUG (Thread-3) [pychromecast.dial] Resolved service HostServiceInfo(host='192.168.10.81', port=8009) to 192.168.10.81
firebowl commented 1 week ago

Same here

firebowl commented 1 week ago

Solved problem by adding IP to known Hosts.

biva commented 3 days ago

Hi @firebowl , thanks, could you please share how you added the IP to known hosts?

firebowl commented 3 days ago

@biva Go to Google Cast Integration and then to Configure. There you can add the IPs of your cast devices.

image

image

biva commented 3 days ago

Thanks, I have seen that and already added it, but I still can't see the device :(

biva commented 2 days ago

I removed the integration, then added again. Nothing. Then the entity came back. And then it became unavailable again :(

seanmccabe commented 2 days ago

I get the exact same issue. I've previously posted the logs and there is an error in the logs. I've got the Google devices on a seperate subnet, as they've always been and now despite having the IPs listed, everything is still unavailable.