cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Google Hub 2 : Trying to add a device with voice match but app reports "no wifi connection"q

MilesAB
Community Member

I'm trying to add my daughters voice to the Google hub 2. It recommends using Family link (where she is already setup). I go to Family link > google assistant > add XXX to new devices. Then the app reports there is no wifi connection. I have turned my android phone on and off and there is a good wifi connection.

I also tried the other route of using Google home on my daughters tablet and Family link. It also reported "no wifi connection". I then tried adding my daughter as a a home member through Google home. Using "Invite person" it then told me to open family link....which again reported "no wifi connection". Seems like an ongoing bug. 

 

Does anybody have a solution?

101 REPLIES 101

BlackRaph
Community Member

Not working for me...  I'm getting crazy with Google Home.

Kieranof
Community Member

The uninstall updates got me past that error, now it just keeps telling me "No Devices found" when it searches for my kid's device that I want to add to the Household. I cannot get past that error, I have ensured both devices are on the same Wifi network and tried different networks, rebooted both devices. nothing works, any ideas anyone? Help, please

anindis
Community Member

I don't know if it helps someone, but in my case the problem was in my smartphone language.

I'm from Kazakhstan, so my default language is Russian. And when I tried to add voice match to a device I had "No internet connection" trouble. I changed my smartphone language to English US and everything worked.

Updates removal solution didn't help

Jimac
Community Member

I too have the same issue(trying to add voice recognition for my daughter's on a new Nest Hub device in their room).  Rolling back the version of Google or Family Link hasn't helped.  Very frustrating!  

Jimac
Community Member

Changing the Language to English US didn't work either.

KevAndPolly
Community Member

I am also struggling. Tried everything above. I have managed to get to the select devices option for one of my children but once selected it then says "authentication token not ready" or something similar. 

Good fun!

 

Google, sort this out. Having nest speakers was supposed to make everything easier, not more stressful. A room full of vinyl records and a turntable would be easier at this point. 

 

GarrettDS
Community Specialist
Community Specialist

Hey there,
Sorry for the late response, but I wanted to drop in here to help. 

I understand that these issues can be confusing but I definitely wanted to stop by and see how I could help. 

Just wanted to double check to see if you were still needing help on this? If so, what troubleshooting steps have you tried? 

I look forward to hearing from you.

Best regards, 
​​​​​​​Garrett DS
 

This is still very much an issue and not only on nest devices. I can't connect my headphones to Google Assistant because of the same bug!

Jake
Community Specialist
Community Specialist

Hey all,

 

I wanted to check in and see if you are still in need of any help with your device? Please let me know, as I would be happy to assist, and answer any questions you may have.

Best regards,
Jake

Jake
Community Specialist
Community Specialist

Hey all,


I want to ensure you are good to go, and everything is working properly. Please let me know if you are still having trouble, as I will be locking the thread due to inactivity. 

Best regards,
Jake

PIR3lly
Community Member

He Jake. 

For me the problem is still there. I just can't get it to work and I've kind of given up as it seems that no-one has the solution. 

Henkvdwal
Community Member

Well problem not fixed so still need a fix. If you have a fix you may close it but otherwise please keep it open

KevAndPolly
Community Member

Apologies, I honestly thought that you were trying to be ironic or something. 

 

No. 

 

Of course the issue is not fixed. 

joymyr
Community Member

The reason for the inactivity is that everybody is waiting for a fix. Don't close the thread before the fix is available.

tsile
Community Member

Well... For me I still cant my child's voice. Any other suggestions?

 

 

 

stevehoot
Community Member

Hi Jake,

Any news or update on this please?

I have my own post (here) and have a ticket with their support (ticket number 3-4397900003317).

As all I had since 25h Jan and getting first line support engineers, scripted answers, and no interest with them bothering to read this or my own forum post, I've flagged my disappointment and frustration. Should I not see a stark improvement in their awful support and / or a resolution (or at least a workaround) I'll be sending back all four of my Google Nest devices.

Please feel free to reference both my forum post and / or my ticket number if you speak to Google support.

Thanks,

 

Steve

Kevin18
Community Member

@Jake wrote:

Hey all,

 

I wanted to check in and see if you are still in need of any help with your device? Please let me know, as I would be happy to assist, and answer any questions you may have.

Best regards,
Jake


Yes.. tried everything above. I can uE Google assistant just fine. But it's when I try to ad voice match to My phone it gets frustrating. 

Kevin18
Community Member

Yes. Tried everything they listed, This issue is on My phone. And i'm trying to ad voice match to My phone since i don't wanna waste money on a overpriced speaker with the same features when I already have the same thing in My phone. I can use Google assistant just fine but I can't use voice match cus everytime I try to ad it, it just says "No internet connection" i'm almost certain that it has nothing to do with My internet since I have 400mbps fiber and I'm the only one on that ground cable. 

Jahuu
Community Member

Same issue seems to persist still. Will have to triple check my kids tablet settings when I have properly time to debug this, the error message being about missing wifi connection doesn't help much hunting the right setting to check 🤣

Jahuu
Community Member

Checked and retried and the same issue persists. Tried also removing groups from Google Home, with no effect. And it seems to me that Google hasn't done anything about this, apparently they just don't care do their products work as intended.

JonasCF
Community Member

I have the same issue. I use iPhone.

the apps i have tried with is Google home and family link as described above.

when k6 describe uninstall and reinstall google app updates. I can’t figure out witch app he refers to? I can’t find any of those settings for the two apps I tried? 

Micha_123
Community Member

Sorry but the family link app is now realy an TRASH app, not possible to add childs to my HOME, if i put the email of my childs it says i need to do it within the Family Link app, if i open the Family link app and try to add devies to my childs account within the Family link app it says  No WIFI connection or it "Problems with the conneciton, check connection and try again" 

not possible to add child to my "home" 

 

so im done with the stupid Famili link APP. 

 

i delete childs accounts, make new (normal 18 years ) Accounts then i can them add them to the home without the stupid google  Family link app. and check for an 3rd party parrental control app.

 

PIR3lly
Community Member

Hello all, just wanted to share my experience.

I'm running into the exact same problem. Not with nest, but with a Sony XR-65A84J. This has google assistant build in and works really nice (even when in standby). 

Anyway, when I try to add two accounts of my sons in google home, I get the warning that I need to use Family Link (they are younger than 13). So I open Family link and it comes with the "no wifi connection" error. So I tried the trick with removing Google updates. This works and it now searches the active wifi connection. Only to find "no devices". And I'm absolutely positive they are both connected to the same wifi. 

So I'm completely stuck now. I just want to have voice match for my kids to work, so they don't use the assistant to call up some weird (18+) results on a 65 inch screen...

Any help would be much appreciated!

Same here. the workaround works for a normal account. but when trying for a child (Family link) no result.
I can't ad speakers for my children.
I use Sonos speakers.
There should be no need for a workarroud it should work by default.
I have tried helpdek google but no luck there.

 

yea but there should be no need for a workaround on a default baccount also. It should yust work

Umberto
Community Member

Same here: after a lot of tinkering and a pointless conversation to the support, I'm stuck at the "no devices" error.

Has anyone found how to get past it yet?

nope. biggest isseu is I cant add my kids to my smarthome afer al this time. som my kids cant turn on or of lights with their phone.

ont normal it has to take so long for google to fix this.

 

benbyrne1980
Community Member

Same problem on going for me. Uninstall and reinstall updates not made any difference. Same for family link app. Using Google Pixel phones with Google Nest Mini. You would think that would work!

 

Help, Google!!

Nopats
Community Member

Same issue. Tried multiple phones to add assistant to chromecast speaker(sony srs) without success. Tried the update workaround but still couldn't add it. 

Smoothy
Community Member

Same here. Trying to add device with Voice Match on a child's tablet. No Internet Connection message, even though I'm connected while it brought up the list of devices.

 

One issue after another.

Jimac
Community Member

I don't know if it will help any of you, but the issue went away, when I individually removed all devices in Home from groups I'd created, then deleted the groups.  It would then let me add the Voice Match for my kids accounts and I could re-create my groups and add devices to them again.  

It seems a very fickle/flawed software set. 😞

 

Jahuu
Community Member

Thanks for sharing, I tried this also, didn't help at my case.

Flagg
Community Member

I have the same issues, can't setup face match (nest doorbell battery) cause it keeps saying there is no WIFI connection, which there is obviously.

 

Unistalled Google app updates restarted everything from phone to routers, turn of 5ghz WiFi and only use 2.4, but to no avail.

jimmyh
Community Member

Same issue here. "No internet connection". I can't even try the workaround because the kids with their profile can't uninstall the Google app's updates, I can't work out how to allow that via Family Link.

Jahuu
Community Member

Actually me neither, I

so I settled trying unistallation on my own device, that didn't help though.

Asinthadeshan
Community Member

Ok 

NomenEstOmen
Community Member

I too tried to add my child's voice to a Google Nest Audio, and ran into the same message as others have: "No Wi-Fi connection" and "Make sure your phone is connected to a Wi-Fi network". I am sure it is connected to the same wi-fi as the Nest. This hasn't worked for months now.

 

I tried this again while recording the logging. The logging reveals that it can actually find the device, but that connecting to it fails with a "cast socket status code" of 2283. There are lists of CastStatusCodes online, but 2283 is not on them. What does that code mean?

The full logging is pretty verbose (~10 secondes was about ~600 KB), but I tried to extract the important parts:

 

[09-05 22:10:06.670 6717:6717 I/LibAssistantScanner]
startScan

[09-05 22:10:06.671 6717:6717 I/Quality]
Skipped: false 1 cost 16.653675 refreshRate 0 processName com.google.android.googlequicksearchbox:search

[09-05 22:10:06.681 6717:6717 I/Quality]
Skipped: false 1 cost 8.996446 refreshRate 0 processName com.google.android.googlequicksearchbox:search

[09-05 22:10:06.682 6717:6717 I/LibAssistantScanner]
(REDACTED) #onDiscoveryQuerySent, subtypes: %s, transactionId: %d

[09-05 22:10:06.686 4543:4543 W/DiscoveryManager]
BroadcastReceiver is already registered

[09-05 22:10:06.687 4543:14149 I/DiscoveryManager]
Filter criteria(CC1AD845,%urn:x-cast:com.google.cast.media) scannerFlags(2)

[09-05 22:10:06.688 4543:14149 W/GuestModeDeviceProber]
setFilterCriteria

[09-05 22:10:06.689 6717:6717 I/A]
(REDACTED) Fetch Eureka info of device [id=%s] over %s

[09-05 22:10:06.690 6717:6717 I/A]
(REDACTED) Fetch Eureka info of device [id=%s] over %s

[09-05 22:10:06.691 6717:6717 I/A]
(REDACTED) Fetch Eureka info of device [id=%s] over %s

[09-05 22:10:06.691 6717:6717 I/A]
(REDACTED) Fetch Eureka info of device [id=%s] over %s

[09-05 22:10:06.692 6717:6717 I/LibAssistantScanner]
stopScan

[09-05 22:10:06.693 6717:6717 I/A]
(REDACTED) #getNextDelegate currentState %d

[09-05 22:10:06.693 6717:6717 I/oplus.android.OplusFrameworkFactoryImpl]
get feature:IOplusDynamicVsyncFeature

[09-05 22:10:06.693 6717:6717 I/oplus.android.OplusFrameworkFactoryImpl]
get feature:IOplusDynamicVsyncFeature

[09-05 22:10:06.693 6717:6717 I/oplus.android.OplusFrameworkFactoryImpl]
get feature:IOplusDynamicVsyncFeature

[09-05 22:10:06.697 6717:6717 I/LibAssistantScanner]
stopScan

[09-05 22:10:06.700 4543:4543 W/DiscoveryManager]
BroadcastReceiver is already registered

[09-05 22:10:06.703 6717:6717 W/MediaRouter]
Ignoring invalid provider descriptor: null

[09-05 22:10:06.706 4543:14149 I/DiscoveryManager]
Filter criteria(%urn:x-cast:com.google.cast.media) scannerFlags(2)

[09-05 22:10:06.706 4543:14149 W/GuestModeDeviceProber]
setFilterCriteria

[09-05 22:10:06.706 2111:3375 D/NsdService]
Discover services

[09-05 22:10:06.712 2111:3375 D/NsdService]
mdnssd [discover, 2, _googlecast._tcp.]

[09-05 22:10:06.723 2111:3375 D/NsdService]
Discover 2 2_googlecast._tcp.

[09-05 22:10:06.736 2111:3375 D/NsdService]
Native daemon message SERVICE_FOUND: 603 2 "Nest-Audio-e43a77120869961a5b1e19877b87159f" _googlecast._tcp. local.

[09-05 22:10:06.738 2111:3375 D/NsdService]
Native daemon message SERVICE_FOUND: 603 2 "Nest-Audio-7d8a5b7e03ae7d1a418ce2ec62b3c92b" _googlecast._tcp. local.

[09-05 22:10:06.738 2111:3375 D/NsdService]
Native daemon message SERVICE_FOUND: 603 2 "Google-Cast-Group-7187eb005c2a4f21b47ec075c663ca5f" _googlecast._tcp. local.

[09-05 22:10:06.739 2111:3375 D/NsdService]
Native daemon message SERVICE_FOUND: 603 2 "Chromecast-95aba14b81de9a59090e26807685d0a1" _googlecast._tcp. local.

[09-05 22:10:06.740 2111:3375 D/NsdService]
Resolve service

[09-05 22:10:06.743 2111:3375 D/NsdService]
mdnssd [resolve, 3, Nest-Audio-e43a77120869961a5b1e19877b87159f, _googlecast._tcp., local.]

[09-05 22:10:06.744 2111:3375 D/NsdService]
Resolve service

[09-05 22:10:06.744 2111:3375 D/NsdService]
Resolve service

[09-05 22:10:06.746 2111:3375 D/NsdService]
Resolve service

[09-05 22:10:06.746 2111:3375 D/NsdService]
Native daemon message SERVICE_RESOLVED: 608 3 "Nest-Audio-e43a77120869961a5b1e19877b87159f._googlecast._tcp.local." "e43a7712-0869-961a-5b1e-19877b87159f.local." 8009 199 "I2lkPWU0M2E3NzEyMDg2OTk2MWE1YjFlMTk4NzdiODcxNTlmI2NkPTI3RTg0RTMyMzEzMjhDMjg3MkJFODY2QjU1NUZEMDlDE3JtPUJCODU3OTM5RThEQzc0NjEFdmU9MDUNbWQ9TmVzdCBBdWRpbxJpYz0vc2V0dXAvaWNvbi5wbmcbZm49V29vbmthbWVyIHNwZWFrZXIgcmVjaHRzCWNhPTE5OTQyOARzdD0yD2JzPUZBOEZDQTgyQTBFNARuZj0xA3JzPQ=="

[09-05 22:10:06.746 2111:3375 D/NsdService]
mdnssd [stop-resolve, 3]

[09-05 22:10:06.747 1106:1207 W/netd]
dnssd_clientstub DNSServiceProcessResult called with NULL DNSServiceRef

[09-05 22:10:06.749 2111:3375 D/NsdService]
mdnssd [getaddrinfo, 4, e43a7712-0869-961a-5b1e-19877b87159f.local.]

[09-05 22:10:06.750 2111:3375 D/NsdService]
Native daemon message SERVICE_GET_ADDR_SUCCESS: 612 4 "e43a7712-0869-961a-5b1e-19877b87159f.local." 120 192.168.68.112

[09-05 22:10:06.750 2111:3375 D/NsdService]
mdnssd [stop-getaddrinfo, 4]

[09-05 22:10:06.751 1106:1207 W/netd]
dnssd_clientstub DNSServiceProcessResult called with NULL DNSServiceRef

[09-05 22:10:06.800 6717:13892 I/A]
Cache not exist

[09-05 22:10:06.801 6717:13892 I/A]
Send request to fetch CRL bundle

[09-05 22:10:06.803 4543:4543 E/.gms.persisten]
Invalid ID 0x00000000.

[09-05 22:10:06.804 4543:4543 W/ChimeraUtils]
Module com.google.android.gms.cast missing resource cast_module_display_name(0)

[09-05 22:10:06.805 4543:4543 D/BoundBrokerSvc]
onBind: Intent { act=com.google.android.gms.cast.service.BIND_CAST_DEVICE_CONTROLLER_SERVICE dat=chimera-action:com.google.android.gms.cast.service.BIND_CAST_DEVICE_CONTROLLER_SERVICE cmp=com.google.android.gms/.chimera.CastPersistentBoundBrokerService }

[09-05 22:10:06.805 4543:4543 D/BoundBrokerSvc]
Loading bound service for intent: Intent { act=com.google.android.gms.cast.service.BIND_CAST_DEVICE_CONTROLLER_SERVICE dat=chimera-action:com.google.android.gms.cast.service.BIND_CAST_DEVICE_CONTROLLER_SERVICE cmp=com.google.android.gms/.chimera.CastPersistentBoundBrokerService }

[09-05 22:10:06.816 4543:4706 I/CastService]
[instance-1] [com.google.android.gms] follow session disabled, with outputSwitcher: disabled

[09-05 22:10:06.817 4543:4706 I/CastService]
[instance-1] [com.google.android.gms] acquireDeviceController: Google Play services client: 222615000 and APK: 222615000

[09-05 22:10:06.818 4543:14149 I/CastService]
[instance-1] [com.google.android.gms] Connecting to device ("Woonkamer speaker rechts" (e43a77120869961a5b1e19877b87159f))

[09-05 22:10:06.819 4543:14149 I/CDC|API|1]
[API] Creating a new CastDeviceController from com.google.android.gms for "Woonkamer speaker rechts" (e43a77120869961a5b1e19877b87159f)

[09-05 22:10:06.827 14796:14825 V/FlurryAgent]
NetworkAvailabilityChanged : NetworkAvailable = true

[09-05 22:10:06.828 14796:14825 V/FlurryAgent]
NetworkAvailabilityChanged : NetworkAvailable = true

[09-05 22:10:06.828 14796:14825 V/FlurryAgent]
NetworkAvailabilityChanged : NetworkAvailable = true

[09-05 22:10:06.831 6717:14884 I/A]
Cache not exist

[09-05 22:10:06.831 6717:14884 I/A]
Send request to fetch CRL bundle

[09-05 22:10:06.848 14796:14810 I/ba]
Successfully registered with Phenotype.

[09-05 22:10:06.849 2111:2361 I/commit_sys_config_file]
[notification-policy,351137]

[09-05 22:10:06.859 4543:14149 I/DeviceAuthChannel]
[controller-0001-com.google.android.gms API] New nonce generated: [94, -110, 109, 74, 15, 23, 18, 107, -89, -1, -21, 71, -33, 24, 101, -107]

[09-05 22:10:06.968 6717:13891 I/A]
Cache not exist

[09-05 22:10:06.968 6717:13891 I/A]
Send request to fetch CRL bundle

[09-05 22:10:06.977 6717:6717 I/A]
(REDACTED) #onDeviceAdded: Not adding device [name: %s] as it is not AssistantDeviceReady

[09-05 22:10:07.097 4543:14887 I/CastService]
[instance-1] [com.google.android.gms] onConnectionFailed: status = Cast socket status code 2283

[09-05 22:10:07.098 4543:4543 E/RCNRemoteClientAdaptor]
CastClient connection failed. Device = "Woonkamer speaker rechts" (e43a77120869961a5b1e19877b87159f)

[09-05 22:10:07.098 4543:14887 W/CDC|API|1]
[API] Ignoring message. Namespace 'urn:x-cast:com.google.cast.tp.deviceauth' has not been registered.

[09-05 22:10:07.103 4543:14887 I/CastService]
[instance-1] [com.google.android.gms] Disconnecting

[09-05 22:10:07.103 4543:14887 I/CastService]
[instance-1] [com.google.android.gms] Disposing ConnectedClient; controller = CSC|[API] .

[09-05 22:10:08.337 6717:6717 I/A]
(REDACTED) #onDeviceAdded: Not adding device [name: %s] as it supports multi-zone groups

 

 

I got the logging using the Logcat Reader app, though it's not easy to use and requires adb to enable it. It's possible to send your own logs to Google, though. Nearly all screens with a three-dots menu in the top-right corner have a Send Feedback item. That can include system logs and a screenshot.

tmo10984
Community Member

The workarounds here that involve reinstalling updates don't work for me, however I believe I've discovered a new workaround.

When presented with the error about not having WiFi connection you can press the Try Again button repeatedly very fast and after about 5-10 seconds of furiously tapping it moves through to allow voice training!

Whether it truly gets wired up is another question.

eCoLL77
Community Member

Sorry for the late reply. I couldn't resolve this issue either. What I then did: on my daughter's tablet I set her up with the voice assist. Then I removed all the updates from the Google app on my phone and then added her to the household. It took two tries and after that we were successful. It works great now as the device shows different content based on the voice of the person asking for it. However it took several hours to resolve... come on Google you can do better than that!

dimitar2204
Community Member

Same, but not with a Google Home device, but regular headphones!