# Keeps losing connection to Chromecast and Google/Nest devices

**URL:** <https://community.homey.app/t/keeps-losing-connection-to-chromecast-and-google-nest-devices/156482>\
**Category:** Devices\
**Created:** [June 23, 2026, 10:07pm UTC](https://community.homey.app/t/keeps-losing-connection-to-chromecast-and-google-nest-devices/156482 "2026-06-23T22:07:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Layne\_Staley](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/layne_staley/32/154300_2.png) [@Layne\_Staley](https://community.homey.app/u/Layne_Staley)\
**Post date:** [June 23, 2026, 10:07pm UTC](https://community.homey.app/t/keeps-losing-connection-to-chromecast-and-google-nest-devices/156482/1 "2026-06-23T22:07:33Z")

</div>

For the past few weeks, my Homey Pro 2023 has constantly been losing connection to my Chromecast devices and Google/Nest speakers. They are connected and accessible in the Google Home app.

The Google Chromecast app in Homey hasn’t been updated for two years. Could there possibly have been some changes when Google switched to Gemini? That switch happened for me a few weeks ago.

Is anyone else experiencing this problem?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 23, 2026, 10:51pm UTC](https://community.homey.app/t/keeps-losing-connection-to-chromecast-and-google-nest-devices/156482/2 "2026-06-23T22:51:44Z")

</div>

Make sure to reserve IP addresses @ your DHCP server for both Homey and Google devices.

I did not switch to Gemini, and Chromecast app devices are functioning OK-ish, as usual:

- Often it works pretty well
- Often there’s huge delays (read: up to several minutes) in response times
- Sometimes it stays quiet (for days) in my home; and without touching anything, it starts talking again \> It really simulates a person 🤣

---

<div class="post-metadata">

**Author:** ![Layne\_Staley](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/layne_staley/32/154300_2.png) [@Layne\_Staley](https://community.homey.app/u/Layne_Staley)\
**Post date:** [June 23, 2026, 11:22pm UTC](https://community.homey.app/t/keeps-losing-connection-to-chromecast-and-google-nest-devices/156482/3 "2026-06-23T23:22:58Z")

</div>

Hehe, I recognize that situation.  
The Homey already has a reserved IP address, I’m going to try doing the same for my Google speakers and Chromecast devices. But it has worked for over half a year—it’s only started acting up in the past few weeks (pretty much exactly when I switched over to Gemini in Google Assistant).

Btw… thanks for quick reply.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [June 25, 2026, 12:47pm UTC](https://community.homey.app/t/keeps-losing-connection-to-chromecast-and-google-nest-devices/156482/4 "2026-06-25T12:47:13Z")

</div>

Switching to Gemini doesn’t matter, I’ve also switched to it and it works fine still. Chromecast/casting works separate from the voice assistant. Have you tried rebooting your router? This often helps with discovery issues

---

<div class="post-metadata">

**Author:** ![Layne\_Staley](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/layne_staley/32/154300_2.png) [@Layne\_Staley](https://community.homey.app/u/Layne_Staley)\
**Post date:** [July 9, 2026, 2:13pm UTC](https://community.homey.app/t/keeps-losing-connection-to-chromecast-and-google-nest-devices/156482/5 "2026-07-09T14:13:30Z")

</div>

I separated the Wi-Fi bands, so 2.4 GHz and 5 GHz now have separate SSIDs instead of using Smart Connect (ASUS). Since then, both my Chromecast and Homey have been much more stable. The difference is significant.

It’s still strange, though, because everything worked perfectly with Smart Connect until recently.
