Google Home Mini App Download

1 view

Skip to first unread message

Percival Blanco

unread,

Aug 3, 2024, 5:22:48 PM8/3/24

to chensgetsimpdeans

I found examples on how to use them in both cases but for some reason I cannot find out how to configure them so that HA sees them as media_player.office and media_player.salon.

They are on the same L2 network as the server (Wi-Fi and wired are bridged), within the name network, but I doubt the discovery will be successful as HA runs in a docker container not in host mode (so it does not see the broadcasts).

If you have in mind the example in my question - that was just an example, the one I found in the docs. I was wondering whether this is the right way to manually add google home devices and how that related to the name later used in configurations.

I guess you are running it in network: host mode - in which case you have access to the L2 of the host. I use traefik to dispatch traffic to containers. I will have to try to run a file based dynamic configuration with network: host but this not exactly obvious to set up.

wel they for sure are detected when the internal intel network card of the laptop running hassio in hyperv is the network card for hassio,; i Didnt get to detect them when i used a realtek usb nic. tried al settings azbout mdns multicast etcetera. appears some of the network cards are not compatible cause of bugs

First gen Google home mini shows up and you can connect to it on Wi-Fi, but while trying to set up the device after a long time and message pops up that says the device couldn't be authenticated and to go to support.

I just set up a second gen home mini, and a home hub, and a home max on this same network in the same room. I already read the related support articles from Google, but I don't know how to check what account this speaker is associated with when it will not not show up in the home app. I held the button to factory reset, but the issue persists.

Sorry to hear about your experience. To start with checking the account linked to your Google Nest devices, all you need to do is to open the updated Home app, and tap on the icon located on the upper right corner. From there, you can see the account that is logged in using your Google Nest devices.

Regarding your other devices, could you list down all the speakers that are set up on your network as well as its distance to each other and from the router? Let's make sure that the speakers are within a good range from the router for better connections.

The account in the corner is the one I expect, but the new device does not show up with all the other connected devices.

I have a Home Max, a Nest Hub, and a Home Mini. All in the same room, all about 30 +/- 5 feet from a new Netgear Nighthawk router on the 2.4 Ghz network. All of the other devices setup fine and my laptop and phone have max signal from this room.

Arlo has been boasting Google Assistant compatibility but I can't seem to make my google home mini act as a chime when someone rings my doorbell. How will anyone without a phone know if someone is ringing the doorbell? I don't have a chime otherwise. Is it possible to make the Google Home play a chime when someone rings the video doorbell?

Further, when I test the camera per the setup info instructions you linked, ("Hey Google, play Arlo camera on living room TV"), the TV will display the Arlo logo, then switches to a black screen that shows "Live" in the corner, and a loading icon, but nothing plays and eventually it says "the camera stream cannot be played right now."

I can view a live feed of the camera via the Arlo app AND through the Google Home app, but for some reason it will not play on my chromecast or my Smartcast TV (I tried two different TVs and got the same result for both).

We have connected the Arlo wireless doorbell to the google assistant app as per the instructions but still cannot get the google assistant to announce when someone rings the doorbell. It worked the one time when the google assistant announced that someone was on the doorbell but not after that. Can you please assist.

I also would have the Arlo Essential Wireless doorbell and would also like it to show up on my Hub when someone rings my doorbell. I had Ring that worked with Alexa and was hoping that Arlo could match that feature.

For personalized support specific to the Arlo products you own, access Support from within the Arlo iOS or Android App. Simply login to your Arlo App, go to Settings, Support, then select the Arlo product you would like support for.

I've tried every recommendation in the book restarting the "T-Mobile" device, the mini. It will go through the entire process of adding the device and at the very end, after it's verified the connection, it suddenly says it can't connect to the network and fails the addition.

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.

Having the same issues and I've tried everything! The old LTE Gateway worked fine in this regard. Why is the new Gateway crippled, why are certain settings not available, and why won't my Google Home devices connect or stay connected?

I am having the same issue, but I have one Google Home device working, but the other will not work at all. I am most likely going to cancel this service as the downloads suck and my ping test is over 200+. I did all of the restarts, reset, reboot, and reached out to customer service with no luck. They never return calls or follow-up. Therefore, I will take my business elsewhere.

After reading this thread I see I am not alone, This is very frustrating. I have two Google mini neither will work but I have 3 Amazon echo dots all working fine, sure would be nice to get a fix from T-Mobile for this issue.

I called T-Mobile and at first they did not admit that there was an issue but I told the guy to google this and you would see there is a problem. T-Mobile needs to address this if they want to be successful in their internet rollout.

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!

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.

So if the answer for everyone else is as simple as it was for me, it's almost blindingly obvious. Make sure you factory reset the Google Home Mini with the tiny round button on the bottom. Hold it for like 30 second, then set it up again. Voila.