# Issue with Google Chromecast

**URL:** <https://community.homey.app/t/issue-with-google-chromecast/110773>\
**Category:** Questions & Help\
**Tags:** homey-pro\
**Created:** [May 31, 2024, 10:58am UTC](https://community.homey.app/t/issue-with-google-chromecast/110773 "2024-05-31T10:58:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jo\_De\_Vulder](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jo_de_vulder/32/79290_2.png) [@Jo\_De\_Vulder](https://community.homey.app/u/Jo_De_Vulder)\
**Post date:** [May 31, 2024, 10:58am UTC](https://community.homey.app/t/issue-with-google-chromecast/110773/1 "2024-05-31T10:58:10Z")

</div>

This is more of a **solution** than a problem I’m presenting. For quite some time, I’ve had issues with Google Chromecast devices suddenly becoming unreachable and not responding to cast commands, such as playing internet radio. This is particularly annoying when casting to a Google speaker group. The only solution used to be restarting my Homey PRO.

I’ve finally identified the cause of the problem, which is the overload of the internal mDNS network on my LAN. mDNS is responsible for discovering most cast devices, including Chromecast speakers, Sonos, and other devices. To resolve this issue, I installed an mDNS repeater on my network. I am currently running it on a Synology NAS, but it can also be run on a regular PC.

I hope this helps others who are experiencing similar issues, often due to having too many devices on their network (mea culpa 😊).

Jo

---

<div class="post-metadata">

**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\
**Post date:** [May 31, 2024, 7:44pm UTC](https://community.homey.app/t/issue-with-google-chromecast/110773/2 "2024-05-31T19:44:16Z")

</div>

> [@Jo\_De\_Vulder](#):
>
> I installed an mDNS repeater on my network. I am currently running it on a Synology NAS

You mean mDNS as Docker container ?

---

<div class="post-metadata">

**Author:** ![Jo\_De\_Vulder](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jo_de_vulder/32/79290_2.png) [@Jo\_De\_Vulder](https://community.homey.app/u/Jo_De_Vulder)\
**Post date:** [May 31, 2024, 10:13pm UTC](https://community.homey.app/t/issue-with-google-chromecast/110773/3 "2024-05-31T22:13:42Z")

</div>

You can install it in a Docker container but I installed it via Entware. You can find lots of tutorials to install an mDNS repeater

Jo

---

<div class="post-metadata">

**Author:** ![tonybau](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/tonybau/32/117843_2.png) [@tonybau](https://community.homey.app/u/tonybau)\
**Post date:** [October 14, 2024, 3:52am UTC](https://community.homey.app/t/issue-with-google-chromecast/110773/4 "2024-10-14T03:52:48Z")

</div>

How did you determine that it was excessive mDNS traffic? what tools did you use ?

---

<div class="post-metadata">

**Author:** ![JohnK](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/johnk/32/30919_2.png) [@JohnK](https://community.homey.app/u/JohnK)\
**Post date:** [March 11, 2025, 6:29pm UTC](https://community.homey.app/t/issue-with-google-chromecast/110773/5 "2025-03-11T18:29:38Z")

</div>

Dag Jo

Since I use a lot of chromecast speakers, and I seem to have the exact same problem… Homey needs a restart to recognize speaker groups… After some hours I can’t start internet streams anymore.

As my Homey and speakers are on the same vlan, i just ask myself how a mdns repeater (that casts mdns from one ethernet adapter to another) is fixing this problem. Will you please help me understand by give a little more elaboration? I am sure there are many others beside myself who will learn from it!

Thanks!