Sonos Move and Starlink 2nd gen

I’m a little confused. Are you having issues connecting your Move to the Netgear router, or to the StarLink router? Or are you having trouble connecting the Netgear router to the StarLink router?

Apologies if I didn’t explain this well. Our only internet source is the Starlink satellite system. Sonos does not work with it so with our first Starlink I purchased a Netgear router, hooked that to the Starlink, connected Sonos Move to that and it worked. However, unlike the 1st gen Starlink, the 2nd gen satellite/router (which we now have in our new house) has no ethernet connection to plug into. So I purchased Starlinks ‘ethernet adapter’. Hooked up the Netgear router to that - internet works fine on it. But I tried to connect the Sonos Move to it and it will not connect. 

OK, thanks or the explanation, makes more sense now. I’m not sure what their “ethernet adapter” is supposed to do. Hmmm, let me go look it up. 

You’re talking about this device? https://www.amazon.com/Starlink-Ethernet-Adapter-External-Network/dp/B0B4KSBR7L

Based on what I see, it has an ethernet connector on it, that you’ve wired your Netgear to? 

Have you changed anything on the Netgear from the last time it was in use? Like, for instance, the SSID/Password, or maybe the type of signal it uses (AC, rather than b/g/n)?

Ideally, your Moves should connect to the exact same SSID and password that you previously had them set up to. Normally speaking, I’d suggest connecting one to the router with an ethernet cable in order to pick up any new SSID/password you may have set up, but the Move doesn’t have an ethernet port. 

If you’ve changed your wifi / network name (SSID) and password, you’d likely need to follow the instructions in the FAQ, I’ve not ever dealt with a Move in that fashion before. 

But there shouldn’t be anything unique about connecting to the Netgear device. The Sonos has no idea about your source of internet (the StarLink), it’s only concerned about the network being generated by the Netgear. I’d want, just in case, to be sure that those two devices are separated by at least three feet, so that they’re not causing any interference with each other, but I’m imagining that you’ve not got one sitting on the top of the other. 

At first I kept the same configuration and SSID/pw the on the Netgear  - this had worked on the gen 1 Starlink in our previous home. Tried both 2.4 and 5 ghz channels and Sonos Move could not connect. It finds it, it chimes but I get to the same spot every time: ‘There was a problem connecting your Sonos Move to “”. ‘ So I tried a factory reset on the Netgear, set everything up the same, still no luck. I reset the Sonos Move, still not connecting. I even tried a different wireless router (TPLink). Still no luck.

If the Sonos has no idea about the source of internet, why will it not work directly with the Starlink router? Something is not working and I am suspecting there is an issue connecting to the 2nd gen Starlink since this all worked fine with the 1st gen? The difference being Gen 1 had a built in ethernet connection while the 2nd gen does not and you have to purchase that ehternet adapter. 

To the best of my knowledge, it should ‘just work’ with the StarLink, assuming the StarLink is putting out a accessible signal for the Sonos to connect to (see here) .

I don’t, however, fully understand this comment on that page: 

• Wireless internet connections such as satellite, mobile hotspots, or LTE routers

I do wonder if that’s a reflection of the potential number of devices supported by those ‘routers’. At least ‘unsupported’ merely means ‘may not’ and not ‘will not’. I’d certainly test it.

To my knowledge, my friend has his Sonos connected to his StarLink network in his vacation home. 

I have a positive outcome. I also have a Sonos Beam but i had not yet tried connecting to it because it is hard wired to our tv and thats all we use it for. However I attempted to wifi it on the Sonos app. I was able to successfully connect it to the Starlink router and it then updated the network settings in the app. It then updated the Move. I have both now working with the Starlink router, no Netgear router required! I can only conclude that the Move had an issue connecting to the satellite network on it’s own or the Starlink ethernet adapter causes an issue. 

Two different kinds of ‘wired’ for that Beam, but I’m delighted that you’re where you want to be ;)

That’s great news, did you use the Starlink ethernet adapter to connect to to the Starlink network?

Beam connected to Starlink via Starlink Ethernet adapter?

 Thanks 

Hi there, 

Actually no, I did not need the Starlink ethernet adapter at all. Initially, I could not get the Sonos Move to connect to Starlink any which way, it kept erroring out both wirelessly and through a router hooked up to the Starlink ethernet adapter. However, I was able to set up the Beam wirelessly to Starlink through the Sonos app. It must have fixed something because I was then able to add the Sonos Move wirelessly. 

Hello, how can i connect a sonos one gen2 with starlink network??

As explained above via wifi on the Starlink router?

I tried similar fixes.

I tried similar fixes.

I have seven Sonos speakers (One x2, Beam x1, Roam x2 and Move x2) and was only ever able to add four of them to the Starlink network.

The only suggestion from Sonos Support, having told me that Starlink is not supported, was to remove that network and reconnect them all to the coexisting other network.

The only suggestion from Sonos Support, having told me that Starlink is not supported, was to remove that network and reconnect them all to the coexisting other network.

However, this also failed, and you have to laboriously go through the 3 to 4 minute set up Per speaker to connect to a new network to actually find this out. 
Then, you have to remove all networks individually from each speaker, remove all networks from the Sonos app, and start again from scratch with the non-Starlink network.

then, you have to remove all networks individually from each speaker, remove all networks from the Sonos app, and start again from scratch with the non-Starlink network.

Days of fault, finding, time-consuming, setup, and frustration with their app and support.

I find this software, extremely unsophisticated and slow. For a product line of this cost and premium positioning, this is unforgivable.

I find this software, extremely unsophisticated and slow. For a product line of this cost in premium positioning, this is unforgivable.

I have had friends throw out entire Sonos systems, for this very reason, and their support team, and the CEO, who you are supposed to be able to email with such large concerns, seem unresponsive

Not sure why you felt the need to repeat sentences throughout. I’ve just hooked up a PLAY:5 gen 2 to a StarLink system, although I’m unaware if it’s a gen 2 StarLink system. I did have to do three separate factory resets to get it to connect, but I’ve been playing a Bluetooth signal through a Roam to the PLAY:5 for at least three hours now, no issues. There are also several other PLAY:3s and Sonos Ones all connected, running S2 (15.7) and my friend has Spotify hooked up, again, no issues beyond when the damn StarLink itself loses connectivity, about once an hour for about 30 seconds…slightly longer when it rains. But that’s a StarLink signal fault, has nothing to do with Sonos per se, as Safari, Zoom, etc, all drop.