Skip to main content
Trending Lyricist I
February 11, 2024

Some Sonos speakers won't join Google Nest Pro network

Like many others, I’m having difficulties connecting my Sonos speakers to a Google Nest Wifi Pro mesh network.

My Arc, Move, Five, and Amps are connected fine.  My Sub and two Ones aren’t.

Tech support had me factory reset speakers, reconnect them, restart my Nest routers, round and round for about 5 hours, and eventually everything connected.  That was two weeks ago.  Today the Sub and Ones are off the network again.  I factory reset them and tried to re-add them but that failed.

I’ve read the threads on this topic but they are all closed so I thought I would start this new one.

Here are a couple details I think make my situation particularly difficult:

  1. Not all of my Sonos are close enough to each other to see the Sonos network, so I can’t rely purely on SonosNet.  Instead, I have wired two Nest routers to each other over a long distance.  All Sonos can therefore see my wifi network.  I also have Nest routers that are not wired together.
  2. None of my Sonos are close enough to the primary router to be wired to it in normal use.  (But I’m not sure this would help anyway given point 1.)

My Arc/Sub/Ones are close enough to a Nest router that one of them could be wired to it, but it is not the primary router.

Thanks for any advice.

My advice to others is:  Do not buy the Nest Wifi Pro.  Even if you don’t use Sonos, is it is a very buggy router, not at all like the previous Google Wifi, which was rock solid.  The Nest Wifi Pro often picks a device it hates and won’t let that device connect for days or weeks at a time.  Eventually it will let that device connect and will pick some other device to hate.  I’m in a rural area with very low interference.  It is very clearly a software bug because often the hated device can still connect to the guest network.

I’m putting this under “Advanced setups” because anything involving Nest Wifi Pro is somewhere between “advanced” and “hopeless”.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

24 replies

ratty
February 11, 2024

The Nest Wifi Pro often picks a device it hates and won’t let that device connect for days or weeks at a time.  Eventually it will let that device connect and will pick some other device to hate.

 

Could you be running out of IP addresses in the DHCP pool?

quasarAuthor
Trending Lyricist I
February 11, 2024

How would I check that?

ratty
February 11, 2024

You’d need to look in the DHCP server settings for the Nest primary. Do you have a lot of devices on your network? 

ratty
February 11, 2024

This might get you to the right place: https://support.google.com/googlenest/answer/6274660

quasarAuthor
Trending Lyricist I
February 11, 2024

The Home app shows 26 connected devices, less than the 100 that a Nest Wifi Pro is supposed to handle (according to a quick google search).  So yeah, that’s quite a few devices.

ratty
February 11, 2024

26 devices is not a lot. If the pool size is not the problem you could try experimenting with IP reservation for all your Sonos devices. The above link describes how.

quasarAuthor
Trending Lyricist I
February 11, 2024

Sonos support recommended that I call back tomorrow.  They have tools that they can only use on weekdays.  But that would require me to take a day off work, and I’ve already put 9 hours total into trying to get this to work, so I think it’s time to call it quits.

Can anyone recommend alternative brands of speakers or routers that are known to work?  I could perhaps replace just my Arc, Sub, and Ones with a different home theater setup.  Or I could replace my Nest wifi mesh and reconnect all devices to that new network.

ratty
February 11, 2024

I run my system on an ASUS ZenWiFi mesh.

quasarAuthor
Trending Lyricist I
February 11, 2024

Sometimes when trying to add a Sonos product it will complain that my phone is on the Foobar network, while the Sonos product is on a different network, also called Foobar.  So I think the root of the issue is that Sonos thinks there are two networks, both coincidentally having the same name, while all my other wifi devices think of there as just being one network.

I might give the ASUS network a try.  I really don’t look forward to setting up all my Nest thermostats, laptops, chromecasts, etc, all over again.  But the only alternative I see is to toss my Sonos speakers and try a different brand of smart speakers, which would also be a massive hassle.

AjTrek1
February 11, 2024

I also you Asus ZenWifi Pro ET12 x 3 with a wired Backhaul. I had Bestbuy Geek Squad run the Ethernet wire and install wall mounted Ethernet connection plates. Some of the Ethernet (weather rated) was run on the outside of my home. That was 3 years ago.

FYI, I have 32 Sonos products, 10 cameras , 4-5 appliances, 4 TV’s, 4 AppleTV 4K boxes, 3 computers, cell phones, tablets, security system and other things on my network. Knock on wood it’s rock solid 😉

Note: I can see at least 20 other networks near by. 😂

Together Everyone Achieves More = T.E.A.M.