Can't connect Google Mini to T-Mobile Home Internet

randomusername007 wrote:

I tried all the above with T-Mobile support (and Google support) and still couldn't get the two to work together. I just got off the phone with T-Mobile support and they shipped the Home Internet Gateway router knowing that it doesn't work with Google Home devices. They may offer a firmware or other update in the future that fixes the issue, but for now, I was told that they don't work together.

My Google Home Mini works normally with the gateway, from the first day I set the gateway up four months ago.  However, I didn't try to  configure it. I kept the wifi password the same as it was for my old DSL modem. At first, when I set up the gateway, I went by the number of characters they suggested for the wifi password, or whatever, and once I had one device set up, I used the "change the wifi password (SSID)" function in the app, changed it to my old wifi password and all my smart devices connected normally.

There are about a dozen known quirks of T mobile home internet, and not working with google home devices (including the Google Home Mini) is not one of them.

There are at least 300,000 users of T mobile home internet and probably more than a couple thousand who use Google Home devices. It's so important to me, I don't know what I'd do without it, if it didn't work. So, my suggestion is if you have your old connection service provider still, see if you can get the Google Home Mini working with that, and then do a factory reset (paper clip in hole at top of black inset on gateway), go through the entire setup again, but this time at some point, after one device is connected, change your wifi password to the one the mini uses in your old wifi setup, and see if that works. I wish I could be more help, and offer something simpler to do. Maybe someone else will.

I tried all the above with T-Mobile support (and Google support) and still couldn't get the two to work together. I just got off the phone with T-Mobile support and they shipped the Home Internet Gateway router knowing that it doesn't work with Google Home devices. They may offer a firmware or other update in the future that fixes the issue, but for now, I was told that they don't work together. 

The fact that T-Mobile shipped a router/modem knowing it wouldn't work with smart home devices (or at least Googles) is the kind of thing you'd expect from one of those new brands that you see on Instagram lol. Definite hit to the T-Mobile rep. Got a credit on my bill since it basically doesn't work. Going to give it a couple more weeks and if there's no update cancel the service and go back to Verizon or something. Bummer.

So what has worked for me is to factory reset the gateway device. Once you set it up log into the settings online (192.168.12.1) and divide the 2.4hz and 5gz. But after you separate them go to configure ssid 5, under set ssid to configure make sure to go through all of them and turn off any "enable ssid" other than the ssid 5. For me the ssid 9 was named the same as my 2.4 and Google devices don't like 5gz. Sorry if this is confusing wording but I hope it helps. 

The firmware update to 1.2003.03.0178 fixed the Google Home Mini issue for me too.

Jbt1982 wrote:

I was having the same issues until late last week when my firmware updated to 178 and *so far* everything has been working perfectly. My Google home/home minis/home hubs now all connect and have been working flawlessly and my Chromecast with Google TV is the same. Previously none of the Homes/hubs would connect and the Chromecast would connect, but some of the apps such as Hulu (regular Hulu, not Hulu Live) would not load. Additionally, when pressing the Google Assistant button on the Chromecast remote nothing would happen. Everything nowworks correctly. Fingers crossed that the firmware is pushed out to everyone soon and the fixes are complete and permanent!

I'm having the same experience now. I posted about two weeks ago at my wits end about the Home devices not connecting or staying connected. It seems that the new update and/or something that's been tweaked on T-Mobile's end has fixed some issues and all my devices have been connected for over a week now and all work fine. Before I was able to get them connected but they would glitch out or by the time I got home from work, they were disconnected. Fingers crossed. Now if we could just get some more settings and if my service wouldn't drop out so much during the day, then I'll be happy, lol!

quietmint wrote:

+1 here. Please help, someone from T-Mobile! Definitely an issue. We need some firmware update from T-Mobile on this.

Several other threads here mention that Google devices work fine if you use your own WiFi router (turn off the WiFi signal from T-Mobile, plug your other WiFi into the Ethernet cord). It's ridiculous that this is the only solution.

(There's also some incorrect thread here mentioning T-Mobile blocks third party DNS providers, and points to this as a possible cause of Google devices failing. I tested this and found it to be false; using a third-party DNS provider like Cloudflare or Google works fine so that thread is a red herring)

 

In my case, my Mini speaker eventually did connect (I just left it in the broken state "there's a glitch" overnight). Now I can ask it questions and get a reply but can't stream any audio by voice ("play the news" or "play some music" both respond with "ok" and play nothing) or cast audio from an app like Spotify on my phone/computer.

Also having this issue

I am on the phone with them about this right now. I am using the Cycliner Router thingy.  The woman I am speaking with claims she is Level 3 Support (I have that number from a previous call).  However, she first wants to try and connect me to the 5Ghz band b/c she says by default the router is connected by default to the 2.4 Ghz band. But I am telling her I am set up with both by default - as I see in the GUI -- (i.e. this is how it came; I did no tweaking).  But this is odd b/c everything I have read on the internet says the reason we are having this issue with Wyze camera, Google Nest Mini speakers and Echo devices is b/c those devices need 2.4 Ghz (and not 5 Ghz).  I am getting the feeling that I am talking to someone who thinks she's is Level 3 Support.  Btw she just got back on line. She says that those devices are not supported. But a new firmware upgrade is needed.  I am not on the list to get that upgrade she says. My software/firmware ends in 0168.  That means according to her, that I am on the older one (relatively speaking).  From a conversation a week or so ago with a legit Level 3 Support, that gentleman said these newer routers (the cylinder ones) don't support much tweaking.  He suggested I use my replaced Time Capsule (apple world, speak) which I am currently using behind the T-Mobile Router for mac mini Time Machine backup and as a Gigabyte Switch, to control the 2.4 GHz band and set up those incorrigible devices to the Time Capsule. I am going to need my tech friend to come over for that. I am a knob.  I just sound kinda tech knowledgable, at least to me.  The purported Level 3 Support woman says she is going to call me back later. I will come back and report which she informs me.  

I was having the same issues until late last week when my firmware updated to 178 and *so far* everything has been working perfectly. My Google home/home minis/home hubs now all connect and have been working flawlessly and my Chromecast with Google TV is the same. Previously none of the Homes/hubs would connect and the Chromecast would connect, but some of the apps such as Hulu (regular Hulu, not Hulu Live) would not load. Additionally, when pressing the Google Assistant button on the Chromecast remote nothing would happen. Everything nowworks correctly. Fingers crossed that the firmware is pushed out to everyone soon and the fixes are complete and permanent!

Does anyone from T-Mobile read these messages? Or is this all customers? 

Charles in Glendale AZ

I just wanted to add my voice to the chorus here. My Google Home Mini does the same thing, in that it goes through the setup, but then fails at the completion of the setup.