Google Cast
cast
Support for mDNS discovery in your local network is mandatory for automatic discovery. Make sure that your router has this feature enabled. If mDNS does not work in your network, the IP addresses of the Cast devices can be manually entered in the configuration as mentioned below.
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
media_player | Media player (as switches) | Only TVs and receivers get a TV tile; other players show as power and play switches; Needs its own HomeKit Bridge in accessory mode |
1 report below say how a device from this integration behaves in the Home app.
What people report
Chromecast, Nest Hub and Cast speakers work locally for media. Local media needs correct URLs, and dashboard casting to Nest Hub broke in 2026.
- Works5
- Partly works5
- Not working2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Chromecast Audio | Works | Popular for music with amp and speakers; HA is better cast controllerSaved copyFor music: Chromecast Audio + Amp + Speakers For announcements: Nest (née Google Home) Minis. Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2024-10 | |
| Chromecast devices | Works Local | Local media casting works once internal URL is plain HTTPSaved copyHi @emontnemery, I've attached a full log file with the most recent logs of casting a file to a chromecast device. I am not seeing anything wrong directly. anything I should look for? I hope you find some time to help me with this issue. home-assistant.log thanks in advance! Cheers. Excerpt saved from GitHub on 2026-10-23. | Issue #65835 · 2022-02 | |
| Google Cast groups | Works Local | Added to device registrySaved copyProposed change Add Google Cast groups to device registry ## Type of change <!-- What type of change does your PR introduce to Home Assistant? NOTE: Please, check only 1! box! If your PR requires multiple boxes to be checked, you'll most likely need to split it into multip Excerpt saved from GitHub on 2026-10-23. | PR #66805 · 2022-02 | |
| Google Chromecast Audio | Works | Several can sync to the same song with no subscriptionSaved copyI have several chromecast audios, google home devices, and chromecast, I can sync them all to the same song, no subscription needed. Not sure where you read that. Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2020-06 | |
| Google Home Hub | Works Local | Image casting failed on firmware 1.52.x then fixed itselfSaved copy… various ways to announce messages in my house. A nice example is the "washing is done" automation, which first plays a TTS message "Washing is done!" on my Google Home Hub, and then shows an image of a Washing machine for the next 15mins to make sure you can see what was said if you miss the voice announcement. Few days ago, casting the image broke: it simply wouldn't show anymore and logs indicated something like `2021-04-27 13:29:37 ERROR (Thread-16) [homeassistant.components.cast.media_player] Failed to cast media https://*redacted*/local/icons/wasmachine-green.png from internal_url … Excerpt saved from GitHub on 2026-10-23. | Issue #49758 · 2021-04 | |
| Google Home / Nest Mini speakers | Partly works Cloud | Multi-room audio via Cast has issues like dropouts and syncSaved copyI'm gonna be brutally honest with you. If you want decent multiroom audio, like Sonos, get rid of your Google mini speakers. Sure, you can use the Cast integration, pre-define groups in Home app and use Spotcast (custom integration that allows to play Spotify over Chromecast). But it has issues (like dropped Chromecast speakers, Spotify API changing and no option for on the fly speaker changing). I have 6 of them and only use them for voice commands and notifications (after having used it like mentioned above and going crazy at a point). So get a couple of Raspberry Pi's and install … Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2021-07 | |
| Google Nest Audio speakers | Partly works | Work 'when they want to'; grouping trade-offs between Google Home and HASaved copy… different option to Sonos, which I've never used, I'd suggest Wiim. I've got 4 setup throughout the house. They work well and you can use whatever dumb speakers you have with them. I've also got GoogleHome Nest Audios mixed in which work when they want to. These speakers are mainly used for voice control of HA, for the rare occasion an automation isn't handling everything. Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2025-08 | |
| Google Nest speaker | Partly works Cloud | Casting notifications plays chime first and lags badlySaved copyWith Google devices, when you cast any kind of notification, it plays that annoying casting sound BEFORE your notification plays. And it lags like crazy. I have exactly one Alexa device in my office and casting notifications to it is so much better. Quick, no lag and no additional s\*it that it plays. It also doesnt show a "Playing screen" and stays on the time, which is what I like. ​ P.S. Integrating both in HA is a piece of cake. Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2023-12 | |
| Nest Audio / Google Nest Mini speakers | Partly works | Pairs unpair, ignore commands, freeze; cheap but headaches; MA playback cannot skip tracksSaved copyOh boy. I really don't feel like typing it out again, but... - I have 3 Nest Audios, 4 Nest Minis, and 4 Home Minis - Speaker pairs constantly unpair and need to be factory reset - They constantly refuse to acknowledge commands - They just... stop. No lights, no touch response, nothing - They intermittently claim to have lost WiFi, despite all other IoT devices around them working. This has persisted through half a dozen routers, three ISPs, WiFi 4, 5, and 6, Multicast snooping enabled, disabled, subnet routing enabled, disabled, DNS on default, Google DNS, DNSSEC enabled/disabled, etc. etc. … Excerpt saved from the Arctic Shift Reddit archive on 2026-10-23. | Reddit comment · 2024-02 | |
| Nest speakers and Chromecast devices | Partly works Local | Cast integration blocks SiriusXM casting from phone; disabling worksSaved copyThe problem Starting a few weeks ago or so regular casting of SiriusXM to any nest speaker or google device fails with error code 1001 when trying to cast from phone or computer. This can be fixed by disabling the Google Cast integration on Home assistant. If i start the casting and then re-enable the cast integration everything seems to work fine and I can still control the devices. After stoping casting, while the integration is still running, I am unable to start a cast again from phone or computer. This is fixed by disabling the integration again. This is only occuring with SiriusXM. … Excerpt saved from GitHub on 2026-10-23. | Issue #93360 · 2023-05 | |
| Google Home speaker media_player | Not working | Broken in Home Speaker appears as device with 4 switches | Works in HA; speaker device class unsupported by bridgeSaved copyThe problem Speakers are not shown as speakers in HomeKit, but (in my case) as 4 switches. If I add the speaker direct to HomeKit (without HomeAssistant over the AirPlay2 functionality), then the speaker could be added as speaker as it should. ### What version of Home Assistant Core has the issue? core-2024.2.0 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue HomeKit Bridge ### Link to integration documentation on our website … Excerpt saved from GitHub on 2026-10-23. | Issue #110075 · 2024-02 |
| Google Nest Hub | Not working Local | show_lovelace_view fails with UnsupportedNamespace on current appSaved copyThe problem When I attempt to cast a dashboard to my Google Nest Hub the device tries to connect, but doesn't accomplish at displaying the dashboard. When reviewing the logging I noticed the following entry: line 973, in send_app_message raise UnsupportedNamespace( ... ... ) pychromecast.error.UnsupportedNamespace: Namespace urn:x-cast:com.nabucasa.hast is not supported by current app. Supported are urn:x-cast:com.google.cast.sse, urn:x-cast:com.google.cast.cac I'm on the latest version of the core, so this is not the old issue that was resolved some versions ago. ### What version of Home … Excerpt saved from GitHub on 2026-10-23. | Issue #177170 · 2026-07 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 286,574 (40.44%) |
|---|---|
| Added in | Home Assistant pre 0.7 |
| Set up in the UI | Yes |
| Maintainers | @emontnemery |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.