Same problem but on Ghost Recon Breakpoint, controller doesn't respond to the game but I am able to press Stadia button and play in the menu.
Edit: problem fixed when I switch to 2.4ghz instead of 5ghz
@FOlavo The controller is a wireless device unto itself, so whether or not the Chromecast is wired will not make a difference. For the record, both CCUs I have are wired. The phenomenon occurs whether or not my CCUs are wired or wireless. In my situation, as I've stated above, I'm on Google Wifi (pre-Nest) so wireless devices (such as the controller) will attempt to connect via 2.4 or 5 GHz (or possibly between multiple wifi access points), depending on what *it* thinks is a stronger signal. It is my belief that the controller is switching between the two bands and that's what causes the temporary disconnect. The phenomenon is not consistent enough to predict and occurs even if I'm 5 feet from the router/access point. My hope is Google will push a controller update which will prevent it from switching bands/points once it locks on for the first time.
@LovecraftTapes I understand the chromecast is a wireless device by itself. I was thinking maybe somehow they interfered?! I had exact same symptons and I fixed them by going wired on the chromecast. Doenst make much sense to me, but this is what I observed and am able to reproduce it everytime.
For the record, I have a 5Ghz wifi network only (no 2.4Ghz).
I am sorry if this doesnt work for you - I was just trying to share what worked for me.
@FOlavo Thanks for the feedback. Do you have a separate SSID for 2.4 and 5 GHz channels? This is the Achilles heel for me, I think, because Google Wifi's mesh system has the *same* SSID for both channels, so wireless devices can't differentiate and, as far as I can tell, switch between the two signals as it thinks it needs to. There's no way to force the Stadia controller onto a certain band. It may be of interest to note, too, that I've only seen this happen while playing a FPS. Wondering if maybe the controller automatically switches between channels if it detects some sort of input lag while managing that monstrous throughput?