Google Cast devices get unavailable after reboot

[smarthomefamilyverrips]

The problem

Duplicate of #110725

Still same issue! Several of my Google Cast devices show up unavailable

@emontnemery can you have a look please

What version of Home Assistant Core has the issue?

2022.2.5

What was the last working version of Home Assistant Core?

2023.12.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Google Cast

Link to integration documentation on our website

https://www.home-assistant.io/integrations/cast/

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: root Source: components/cast/helpers.py:64 First occurred: 15:50:33 (1 occurrences) Last logged: 15:50:33

Uncaught thread exception Traceback (most recent call last): File "/usr/local/lib/python3.11/threading.py", line 1045, in _bootstrap_inner self.run() File "src/zeroconf/_services/browser.py", line 783, in zeroconf._services.browser.ServiceBrowser.run File "src/zeroconf/_services/browser.py", line 702, in zeroconf._services.browser._ServiceBrowserBase._fire_service_state_changed_event File "src/zeroconf/_services/browser.py", line 712, in zeroconf._services.browser._ServiceBrowserBase._fire_service_state_changed_event File "src/zeroconf/_services/init.py", line 56, in zeroconf._services.Signal.fire File "src/zeroconf/_services/browser.py", line 290, in zeroconf._services.browser._on_change_dispatcher File "/usr/local/lib/python3.11/site-packages/pychromecast/discovery.py", line 142, in add_service self._add_update_service(zconf, typ, name, self._cast_listener.add_cast) File "/usr/local/lib/python3.11/site-packages/pychromecast/discovery.py", line 244, in _add_update_service callback(uuid, name) File "/usr/src/homeassistant/homeassistant/components/cast/discovery.py", line 64, in add_cast discover_chromecast(hass, browser.devices[uuid]) File "/usr/src/homeassistant/homeassistant/components/cast/discovery.py", line 37, in discover_chromecast info = info.fill_out_missing_chromecast_info(hass) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/cast/helpers.py", line 64, in fill_out_missing_chromecast_info unknown_models = hass.data[DOMAIN]["unknown_models"]

KeyError: 'cast'
```

### Additional information

See issue #110725

[home-assistant[bot]]

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)}}

[joostlek]

Please move relevant pieces of information from that issue to here. An issue should contain information and not act as redirect to other issues.

[smarthomefamilyverrips]

Please move relevant pieces of information from that issue to here. An issue should contain information and not act as redirect to other issues.

@joostlek done!

[joostlek]

Also, why are you creating a new issue if the old one isn't closed?

[smarthomefamilyverrips]

Because there is no movement on old one so looks like just get lost in the mass, but i can close it also ;)

[joostlek]

That's not how it works. Making more issues doesn't help solve it faster. If everyone started doing that we'd have at least 15k issues.

[smarthomefamilyverrips]

@joostlek riekt naar machtsmisbruik ;)

[smarthomefamilyverrips]

@joostlek tuurlijk duimpje na beneden, je zou ook gewoon kunnen uitleggen waarom er geen enkele reactie komt op de orginele issue bijvoorbeeld en me vragen of ik deze issue kan sluiten. het is erg irritant dat helft van me cast apparaten niet beschikbaar is want dit geeft ook log errors voor automatiseringen aangezien de gevraagde actie niet gedaan kan worden, met bij effect dat de automatisering ook voortijdig stopt. Maar anyway bedankt voor de "hulp" 👍

[joostlek]

If you want an explanation on why there was no response yet, you could also ask around on discord or the forums. You also did not ask for this explanation.

The only thing i did was point out that the issue was filled incorrectly, and after checking the issue you were pointing out, find out that it's an unclosed issue by the same person. Me and a few other members like to check out new issues so we can help solve them earlier (maybe it's a config mistake, maybe it's an easy fix) and make sure the right people are notified. Another aspect of that task is closing duplicates. Issues with the same root cause are bad because they splinter the discussions and cause noise for the people who want to fix them. As part of this, I closed your issue and then I got accused of misusing my power?

That's not how it works.

Now for the issue: I don't know why this is caused. Please don't forget we are human as well, we also have our own things to take care of.

I was thinking about looking into it with my cast devices, but after showing such audacity I'm rethinking my decision.

[smarthomefamilyverrips]

@joostlek I understand all you say no problem. Only I did explain to you why i did open the new issue, so why you not simply added to your "this is not how it work" remark same as what you typed in your last message "Please don't forget we are human as well, we also have our own things to take care of." and ask me to please stick with the original posted issue and say you will close this now.

Would that not be more friendly as we where already in discussion? ;)

I assume you also can understand that I am kind of annoyed having this issue for weeks already.

"I was thinking about looking into it with my cast devices, but after showing such audacity I'm rethinking my decision."

Would be nice someone would have a look BUT If you put it like this, please don't I can wait for the code owner also in that case. ;)

Fijne avond!

[smarthomefamilyverrips]

@joostlek just want to add in case you did feel offended by my words, then I am sorry this was not my intention.

[joostlek]

Thanks. I think it was also me who was a bit irritated by the fact that you opened a separate issue to raise awareness. Just try to act helpful (not talking about other cases), and creating noise by opening new issues isn't the way to go. And that irritation is not personal, but just general. There are people who regularly create issues that should not have been issues in the first place. So recently I just tend to be a bit more harsh and close the issues. Otherwise that 2.5k issues will never go down.

Fijne avond :)

[smarthomefamilyverrips]

@joostlek no problem, let's just say we both where a bit "on a edge" and forget about it ;), as said before I totally understand and I appreciate all the work you guys do. I also try to help out people with issues as much as possible by responding if I have/had similar issues and found a solution to solve it.

I just will keep track of my original posted issue, post new findings there, and hope soon comes a solution before I throw my HA Blue unit out of the window :))))