The Sonos Sub and it’s HT device bond together over an ad-hoc 5Ghz wireless connection - some routers may not report seeing the Sub once it’s set as a slave device as the connection is handled by the main player - I would ignore your router in this instance and look at why there are connection issues between the Sub and the Beam instead.
The first thing to check in the Sonos App is that the Beam’s WiFi has not been switched off in its room settings as this is needed for the ad-hoc wireless connection.
As you are also using a Google Nest WiFi mesh network setup, I also suggest perhaps reading this helpful Staff thread relating to Sonos and mesh WiFi systems and to consider the advice mentioned in the main post:
https://en.community.sonos.com/troubleshooting-228999/troubleshooting-sonos-on-wifi-6856334?postid=16520976#post16520976
Hi folks,
ah the intricacies of networking..! Many thanks for the help. I checked and the mesh is using ‘bridge’ mode. I then updated the network via the Sonos app, basically resetting the network connections between each device and the network. That seemed to work nicely - it rediscovered the sub and connected it to the Beam perfectly. Now to wait to see if it sticks.
The periodic falling off the network is a bit interesting. I wonder if there is something happening on the mesh network periodically that interrupts the connection…. anyway. fixed for now, so I’ll keep an eye on it.
Appreciate the prompt and practical help.
thanks!
Hi @mattc1971
Welcome to the Sonos Community!
Google Home mesh network to extend coverage with a Home device sat right next to the speakers.
All WiFi devices like to have 1m separation from each other, and especially from Access Points. The Beam and Home device are likely interfering with each other due to proximity, and separating them should clear up the issue.
I hope this helps.