System unreliable after disabling SonosNet so I went back

The One SL supports 5Ghz, but I think Sonosnet only does 2,4Ghz. You might have a bad spot in your 5Ghz network.

If it’s possible try WPA2 to see if the WiFi connection sticks.

Hmm definitely not. The access point is within line of sight of the speaker. No other devices have trouble maintaining a connection to the network there.

My Ruckus AP logs show that the speaker has a strong connection but at some point, it falls off the network (I’m guessing because it needs to refresh WPA3 security keys) and consistently fails to reauthenticate. I suspect a problem with WPA3 but according to Sonos’s documentation, WPA3 is supported by the One SL as is 5GHz networks.

I would rather not do this since it would mean downgrading my network security but I do suspect some problem with WPA3 since the speaker has no problems connecting but then falls off the network at some point. Could be hours, could be days later.

I am wondering whether the Era 100s have the same problem, I am tempted to upgrade my One/One SL to them but am extremely hesitant if they have the same issue.

Probably easiest to disable Sonosnet and wait for the failure and submit a diagnostic, follow up with a support call when convenient.

You could look at the signal info in the settings to see if that is an issue.

My Ones are happy on my wifi with no Sonosnet. However neither is wired, you might try that too.

Yeah I’m thinking I may do that since I am off work in a couple of weeks and will have time to mess around with this then.

FYI my system has been rock solid for a couple of years since I got myself a Boost/moved to SonosNet and then ended up hardwiring (most) everything except for this one problematic speaker (on Wi-Fi) which does not have a network jack nearby. The only reason I’m now trying to move everything back to Wi-Fi is because I understand SonosNet is eventually completely going away so I want to get ahead of it. But trying to move everything back to Wi-Fi is reminding me of all the frustration I had trying to get this working on Wi-Fi in the first place.

I would also try the One/OneSL pair both on WiFi. I’ve had problems in the past with a stereo pair with one wired and the other WiFi. The WiFi one would drop at some point. It looked like an S2 problem, because it doesn’t happen on S1 or with Sonosnet.

Another test would be to relocate one or both speakers.

I would simply leave SonosNet enabled if your system works flawlessly with it enabled. You say that you do not have the 2.4 Ghz radio enabled so its not interfering with anything.

Use it while its still available.

The ERA 100 is compatible with WPA 3.

I know, but my point is that the One SL is also listed as compatible with WPA3 but starts failing to (re)authenticate at some point.

Currently testing to see whether having both speakers in my stereo pair on Wi-Fi makes a difference.

Have you ever tried all the Sonos devices on WiFi?  Some routers don’t like a mix of Ethernet & WiFi.

Link to a Ruckus Unleashed Sonos setup.

https://gameandtechfocus.com/network-ruckus-unleashed-intermediate-guide-sonos-setup/

Not all your Sonos devices are compatible with WPA3 encryption. You also don’t want to downgrade your entire network to WPA2 encryption for security reasons. The best compromise and still have strong encryption security is to use WPA2/WPA3 Personal encryption protocol.

If you are using your own Router some have (or rather all today) have some type of security software built-in either free or via subscription. I advise using it as an extra layer of security in addition to WiFi Protected Access (WPA) Encryption.

All my Sonos devices are using WPA3, no issues. I’m not using Ruckus.

Ruckus recommend you continue to use SonosNet, but you may want to check recommended settings:

https://support.ruckuswireless.com/articles/000006140

I guess for me I don’t understand why people want an Enterprise Network setup for home use which is always more complicated…Sonos or not. IMHO Enterprise Network setups in a home environment are more about “bragging” rights as opposed to practicality. The only exception I can think of is if some is running a business from home requiring servers and VPN access from the outside and of course high and/or military grade security.

Or maybe there is tech teen who needs to be isolated from regular home users.

On the other hand, I can see why some choose to go the prosumer/enterprise route.

I wish Apple had continued the Airport line…

After moving away from Apple network devices, I tried a few consumer brands that didn’t quite cut it. I was then introduced to Ubiquiti, and never looked back.

Prosumer/enterprise equipment is fine to use in my book, but users need to have some basic knowledge of how to configure them. Jumping on the bandwagon because it the latest trend, is no reason to ditch systems that are more user friendly.
 

This is not just isolated to networking…. 😉

Who said anything about bragging rights? I do not seek those. It’s OK if you do not need advanced features but I am knowledgeable enough to understand how to set up and maintain my network, and as an IT guy by trade, I don’t need to be lectured about downgrading my network so I can use my prosumer speaker equipment.

However, it is confusing because later versions of Unleashed now specifically have a Sonos compatibility toggle (mentioned in the technote) which defaults to On, and it appears to specifically address the issues previous versions of Unleashed had with Sonos on Wi-Fi. Time will tell, but so far after unwiring both of the speakers in my stereo pair, neither has dropped off the network so that is promising.