Google Cast integration not connecting to manually defined hosts

[ristoavila]

The problem

Old version of HA core was able to find my two nvidia shield with IP address. I have two defined as known hosts 192.168.0.8;192.168.0.10 this used to work with the old HA core.

New version seems to ignore these and no media player statuses are created.

I have multiple interfaces and iptables to block traffic from external network on the host but this has not been changed in the between HA versions.

What version of Home Assistant Core has the issue?

2024.1.6

What was the last working version of Home Assistant Core?

2023.5.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

cast

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]]

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

[emontnemery]

@ristoavila just to be clear, you've not tried any Home Assistant Core versions between 2023.5 and 2024.1?

[ristoavila]

yes, I've only updated from 2023.5 to 2024.1. Not sure why this is happening now and it seems that after a long time it sometimes finds the devices. With out the iptables rules and multiple NICS it finds these directly. Is there possibility to hardcode specific device or IP address that is only used? Currently I also see some broadcasts to 0.0.0.0 and these cause failures due to fact I dont want HA to broad cast all IP's I have.

[MrFinchMkV]

Hey, I have the same issue after updateing home-assistant OS to version 12.1. Maybe that helps someone to identify the problem.

[MrFinchMkV]

I changed from FQDN to IP in the setup of the configuration (known hosts) and it worked again :)

[ristoavila]

I've been using the IP all the time in the cast setup, and its still a problem. I recall that the broad cast address definition was some point dropped out so now I have no clue what IP address is advertized as there are multiple. Previously I had it set in the settings that use 192.168.0.1 for the broadcast advertizement.