Stadia Controller with bluetooth connection to ChromeCast Google Tv

[ThomasHo]

Hello guys,

i activated bluetooth on Google Stadia Controller. I connected it to my Chromecast with Google TV. Everything works fine. When i restart the controller or chromecast the bluetooth connection is established. Only the input of controller has no effect. Controller is listed as connected and apps will find my controller. if i press any button on the controller it is ignored.

workaround is to delete the device and pair again. for the first time after pairing it is working.

any suggestions?

Thanks,

Thomas

[sayhello]

I have exactly the same issue (

[ThomasHo]

Hello sayhallo,

thanks for your feedback. 

Are there any other controllers with rumble? I connected a PS DualShock 4 controller, witch works great except the rumble function.

[JenniferV]

Hi folks,

I'm sorry to hear that you're having a connectivity issue with your Google Stadia Controller and Chromecast with Google TV. 

You may also try to reboot your devices and try to re-pair it. If the issue persists and this is only happening when using the Google Stadia controller, please perform a factory reset on your Stadia controller. You can also visit the Google Stadia Help Center for additional help.

Thanks,

Jennifer

[ThomasHo]

Thanks, Jennifer for replying. I did a factoryreset on both devices, Chromecast and controller. I need a repairing everytime, that's my problem. 

Is there anyone who got it working?

[sayhello]

Yeah, I did reset as well and still the same problem. Controller pairs and works fine on the first pair. After turning it off and then back on it connects but doesn't react on any button. I need to reset it and pair again to make it work. Unfortunately I don't have any other controller to test it with Chromecast with Google tv.

[Sniker]

Same for me, the Stadia controller works flawlessly with my phone but does not work when reconnecting with chromecast. I actually have two stadia controllers and the both behave in the exact same way. 

[ThomasHo]

Are you using the 4K oder HD Version of Chromecast with Google TV?

[sayhello]

4k version.

[ThomasHo]

me, too. 

[MaxiManus]

Same problem here.

First connect works fine. Turn off controller and back on, it connects but does not perform any input. Need to repair everytime or even factory reset and pair again. The same problem if i connect it to my LG TV. On a Chromebook it works fine. PS4 Controllers work fine on Google TV and LG TV. Just stadia controllers fail.

[MaxiManus]

Btw testes with 3 stadia controllers and 2 PS4 Controllers. So it's not by coincidence.

[JenniferV]

Hello folks,

I'm sorry for the late response. If this is working with other Bluetooth devices, the issue might be with the Stadia controllers. Since we no longer support Stadia, I'd suggest you send feedback about this. Here's how. Every bit of feedback helps a ton!

Also, I'll lock this thread after 24 hours. If you still need help with your Stadia controllers, please visit the Stadia Help Center for further help.

Thanks,

Jennifer

[MaxiManus]

Well Stadia help center is read-only now. So there will be no support. It was nice that Google gave us the Bluetooth update for the controller. But when now the controller is not compatible with Google TV Stick it got shipped with... That's really a bad thing that should be fixed...

[sayhello]

Well, I don't see any issues with Stadia Controller working with my Macbook for instance.

The problem looks like to be with Chromecast with Google tv 4k and BLE devices (stadia controller in this case).

[karimtoubajie]

Hi @JenniferV ,

From the posts on this thread, it looks like it's an issue with Google TV Bluetooth.

I have 2 Stadia Controllers connected to Google TV HD and I have to unlink and add both of them every single time I want to use them (both are updated with latest firmware).

Any chance this can be bumped as a bug into the Google TV Product Teams please? From a sustainability perspective (circular economy) it would be great to get this sorted so that users don't end up discarding perfectly good controllers into landfill.

Many thanks

Karim

[ThomasHo]

I think the problem  belongs to "Google Chromecast with TV 4k" i think this device has problems with Bluetooth Low Energy (BLE) Controllers. The Stadia Controller it self works fine with other devices that support BLE.

[sayhello]

I think exactly the same.

[MaxiManus]

Yes true. While my Google TV also can't connect to my Logitech Bluetooth keyboard, there really might be a problem with Google TV's Bluetooth.

[Willoth]

Sam problem exactly. Will put in a support ticket on the Google TV as well. Suggest all of you do the same. Eather need a update to the bt firmware for the controller or for the chromecast.

[PattyBoy]

Same here. It Is annoying

[Anonymous]

Same issue here. It seems after every reset the stadia controller changes the BLE address. Because when pairing after reset i see a different address when pairing it.

Possibly the BLE address also rotates when only turning off and on again the controller. 

Seems like Chromecast with Google TV can't handle these rotating addresses. Other devices might store a different fixed address as well so they recognize the already connected controller. 

In any case, this is very annoying and could do with some fixing on the Chromecast side. 

[Carlom74]

Same issue here. With Google TV hd. Anyone here could gently point me to other forums where maybe I can find some help?  It's really weird that a Google controller doesn't work on a Google dongle... 

[karimtoubajie]

I have this problem too with the HD Google TV edition. Need to re-pair every new session which isn't a great user experience.

[artspb]

Same here with both HD and 4K. Works fine with MacBook. I hope Chromecast will get fixed at some point. 

[Ferdi1968]

Same problem with my Chromecast google tv 4k, controller is not recognized after turning off Chromecast google tv. I have to remove and reconnect. 

[robbeofficial]

Same issue here. Hoping for better BLE support in a future chromecast update

[covicanton]

Connecting to Huawei smartphone and LG TV. Same issue. On first pairing works, repaired controller is ignored. 

[covicanton]

Workaround :  on Android if you go into the device's bluetooth settings and toggle it's Input permission off and on, it will suddenly start working again. 

[WakeUp]

Same problem with my Sagem DIW 7022 with built in Chromecast…..controller doesn’t work 

[Xael]

Same here, with Google TV. Works great on first pairing. But have to forget amd re-pair each time.

Don't have that issue on all my other devices (PC, Smartphone, Steam Link)

[sco]

Same issue here, really annoying bug. Quite tiresome to pair multiple times in a day.

[Isozenic]

Just commenting to say I have the same issue with the latest updates to my chromecast google tv 4K and Bluetooth stadia controller as of today

[Mrfavila520]

Wow, having same problem here.  Too bad that this wasn't resolved.  Controller fails to work with a device made by the same company.  

[Rvanlaak]

Same here, on a Google TV that came out last July, so hopefully the Google TV team will be able to resolve this.

[BartoszB]

Unfortunately stadia controllers are no longer supported so ..... No one cares anymore. Not a great customer approach from Google if they want to sell new products. Who knows when support will end on pixel or other devices.

[Rvanlaak]

Worth knowing is that connecting the controller to the TV through a usb-cable does work as well. That prevents having to forget and reconnect the controller its bluetooth profile every time.

[Nachtmensch]

I have the same issue... 

I'm sorry to say, but Google doesn't give a ... about their customers.

As a manufacturer introducing the Chromecast and the Stadia-Controller it's just inacceptable that the basic basic functunality is not given.

I'm pretty sure it'll never be fixed! Why should they... there is no money to make...

[Postbios]

The problem is with any device that rotates the mac address. I hope the retard is due to bureaucracy and not for any other reason.

[Nachtmensch]

Well, if it's that easy. There only has to be an firmware update to fix it?!