Give up on Sonos ?

So the only thing that’s changed is the internet provider -- and presumably the router as well -- and it’s somehow Sonos’ fault that things aren’t right? That doesn’t sound terribly logical does it.

First off, after a router change everything on the network will need to re-request fresh IP info. This should happen on its own eventually but can be hurried along by powering kit off and on again. In the meantime local communications could well be flaky. 

Next, the new router -- assuming it’s wireless -- could well have changed WiFi channels from those used by the old one. This could be interfering with SonosNet.

By the way, do you have split S1 & S2 systems? Your profile lists Play:5/gen1, which can only run S1, and Sub/gen3, which requires S2. 

Tell us more about your network. Have you changed routers? Are any of your SONOS units wired to the network?

On the S1/S2 issue, I removed the gen3 sub and the One-SL’s.  Those are a different (S2) system at another location.  The home system is all S1. 

Yes, the Elon Musk Starlink has its own router with wifi.  They then charge extra for an ethernet adapter which feeds a few hard-wired devices, including a gen1 Play:5.  It was required when I set up my system to have at least one Sonos device hard-wired.  Not sure if that’s still the case.  Certainly the means for adding devices has changed with my other S2 system, which is at my apt, not at home. 

Logging into the Starlink router shows considerably less info than, say, what I recall from a previous old Netgear router.  May have to touch base with the Starlink folk to get better info.  I’ve tried cycling power on everything (by tripping the main for 5 minutes), which made no operational difference. 

Don’t I recall something way back when about the Sonos network being independent of the wifi network, which seemed to be a criticism.  Then later Sonos became more wifi integrated?  Certainly when I log into the router and look at all attached devices, my Sonos units are in the list with MAC and IP  addresses. 

It was a call to Sonos CS that essentially wrote me off as satellite internet not being adequate for Sonos.  Figured the Forum would get me a better assessment, as usual.

 With respect to wired or wireless, the early competition attempted to crush SONOS by claiming “liar”, “liar”, SONOS is not a wireless system because at least one unit must be wired. This was a very strong claim in the marketplace. It was a cheap trick for SONOS to also allow WiFi and all of the “liar” claims were instantly crushed. Overall, WiFi is not well suited for supporting real time audio (that’s why the SonosNet was developed) and I recommend wiring at least one unit to the network. SONOS then builds a private wireless mesh network and ignores WiFi.

Depending on the sophistication of the STARLINK router you might be better off wiring only one SONOS unit or wire multiple SONOS units only to a network switch that is wired to the router. Most consumer grade switches will work fine. The buzzword is “unmanaged switch”.

Make sure that STARLINK is set to use channel 1, 6, or 11 on the 2.4GHz segment, not “Auto”. Use 20MHz channels. It’s usually best to set SONOS to use a different channel.

You should be able to play music from your NAS even if all of the satellites crash. You will need WiFi to support wireless controllers, but a wired computer will work fine on SonosNet. Some wireless routers are reluctant to share data between network segments, particularly if the WiFi connection is on the 5GHz segment.

[Note that, while a wired computer can play music, it cannot setup the system]

If nothing else works can you add a second router? I don’t know Starlink and it might have internal configuration issues.

Best would be setting the Starlink to bridge mode, the other option would be to set the second router as a client of the Starlink.

You’d need your Sonos, Controllers and NAS all connected to the second router.

Thanks for the reply.  When I was on Hughesnet, Sonos CS looked up their router specs and said it was so bad that they were surprised it worked with Sonos at all.  I got a Netgear Nighthawk R6700v3, turned off Hughes wifi and fed the Hughes into the Netgear.  Worked fine.  Tried the same with Starlink with poor results.  Maybe victim of inexperience, but will try again.  I’m guessing that “bridge mode” is what Starlink calls bypass mode which turns off its wifi.  Will try that today.

Don

Thanx, tried that but found Netgear not connecting to internet, which gave me no access.  So turned Starlink wifi back on, so now I have two routes.  Making Netgear the preferred one.   Haven’t really gotten to the Sonos part yet.  Thinking of starting over usint a ONE as the hardwired unit instead of the old Play:5 G1.

I assume that the WAN port of the NETGEAR was connected to the STARLINK.

There is something odd with respect to the NETGEAR configuration if you cannot operate the SONOS system. Not having access to the Internet will not prevent operating the SONOS system to play local sources

It’s not the end of the world if you have both STARLINK and NETGEAR WiFi active, but it is not optimum. If you do this, make sure that both use different SSID’s, none of your devices use the STARLINK SSID, and your wired devices use only the NETGEAR.

Thanx, Buzz.  Yes, the WAN port of the Netgear is connected to the Starlink.  As I said, haven’t had a chance to deal with the Sonos yet.  Today’s tasks are dealing with last night’s storm and a failed Generac, and the IRS ;=)