Update News

Android Devices no longer able to join SonosNet



Show first post

161 replies

  • really annoying that it's gone; like so many people, I relied on the sonosnet for control with my android as wifi is so poor in some parts of the house. I'm going to have to go down the access points route as suggested above by ratty (or would investing in a mesh wifi system be better?)

A separate mesh WiFi would perhaps be overkill, and is not without complexity. One or two access points, wired to nearby Sonos units, may suffice.

  • it would have been nice if Sonos had alerted us to this change. Mine only stopped functioning 10 July 19.

The change came in 10.2 a couple of months back. The SonosNet announcement was made the same day.

  • should I be able to see Sonosnet on my wifi analysis app? I can't.

No. It could have been intermittently visible before, when Android attachment was an option, but you shouldn't see it now.
This change is crap!!! The option to connect to sonosnet was really handy!
Userlevel 1
Badge +2
One small caveat. After installing an access point as described, check your network matrix to make sure the root bridge is where you expect it to be. Sometimes another Sonos node which is 'wired' (albeit to a third party device) will become root. This is fixable.Important caveat, that. I found exactly this and had to fix it with help from ratty.
I did not need the access points for Sonos control; my phones were on Wifi, but reading about them here prompted me to change my wireless Airport Express in my bedroom from WiFi extender mode to access point mode after wiring it to the Connect Amp LAN port. Pleasantly surprised to see a noticeably better/consistent browsing experience thereafter, with no adverse impact on Sonos performance. I don't do video streaming; for those that do, there may be a chance of overloading Sonos net this way. But Sonos turned up a hidden benefit for me after many years of use at home, that is quite neat.


I've put an access point in the worst affected area in our house now. Not convinced that this is going to be reliable without sonosnet - I'm partially back to the bad old days of being often unable to browse music, or unable to connect.
I attach my current matrix. The boost is showing as a tertiary node. Is this right?
Can anyone advise, please?

With so many units are you not able to connect any one to the router and set up Sonos net - which is necessary for the access point solution as a replacement for the android, which, if you note, was a connection to Sonos net.
Userlevel 1
Badge +2
With so many units are you not able to connect any one to the router and set up Sonos net - which is necessary for the access point solution as a replacement for the android, which, if you note, was a connection to Sonos net.

Hi, thanks for the reply.
The Boost is connected to the router. Are you saying I need to disconnect everything else except the boost, then restart the Boost (power cycle), then add everything else in? The Access point is connected to the Dining Room connect:amp via ethernet cable.

thanks
D
@revdv Something may have been messed up. Click on the Boost in your /support/review, then '/usr/sbin/brctl showstp br0'. What does it show against 'designated root'?
Are you saying I need to
Since ratty is here, I suggest you take his advice - he knows this subject a lot better.
Userlevel 1
Badge +2
@revdv Something may have been messed up. Click on the Boost in your /support/review, then '/usr/sbin/brctl showstp br0'. What does it show against 'designated root'?

Thanks ratty
Here it is

Boost (RINCON_7828CA7268A401400)

Zone Player Info
Ethernet Ports
/VERSION
/proc/ath_rincon/status
/sbin/ifconfig
/usr/sbin/brctl showstp br0
code:
running /usr/sbin/brctl showstp br0
br0
bridge id 8f00.7828ca7268a4
designated root 8000.10da438566f8
root port 4 path cost 336
max age 20.00 bridge max age 6.00
hello time 2.00 bridge hello time 1.00
forward delay 15.00 bridge forward delay 4.00
ageing time 60.00 gc interval 0.00
hello timer 0.00 tcn timer 0.00
topology change timer 0.00 gc timer 1.70
flags


eth0 (1)
port id 8001 state forwarding
designated root 8000.10da438566f8 path cost 10
designated bridge 8f00.7828ca7268a4 message age timer 0.00
designated port 8001 forward delay timer 0.00
designated cost 336 hold timer 0.35
flags

ath0 (2) - tunnel to B8:E9:37:82:88:AD (remote STP state = forwarding, direct = 3)
port id 8002 state blocking
designated root 8000.10da438566f8 path cost 250
designated bridge 9800.b8e9378288ac message age timer 19.42
designated port 8002 forward delay timer 0.00
designated cost 317 hold timer 0.00
flags

ath0 (3) - tunnel to 00:0E:58:80:32:33 (remote STP state = forwarding, direct = 3)
port id 8003 state blocking
designated root 8000.10da438566f8 path cost 288
designated bridge 9800.000e58803232 message age timer 19.42
designated port 8005 forward delay timer 0.00
designated cost 260 hold timer 0.00
flags

ath0 (4) - tunnel to 00:0E:58:DE:62:99 (remote STP state = forwarding, direct = 1)
port id 8004 state forwarding
designated root 8000.10da438566f8 path cost 326
designated bridge 9000.000e58de6298 message age timer 19.42
designated port 8003 forward delay timer 0.00
designated cost 10 hold timer 0.00
flags

ath0 (5) - tunnel to 00:0E:58:26:CE:E9 (remote STP state = forwarding, direct = 3)
port id 8005 state forwarding
designated root 8000.10da438566f8 path cost 269
designated bridge 8f00.7828ca7268a4 message age timer 0.00
designated port 8005 forward delay timer 0.00
designated cost 336 hold timer 0.35
flags
The Netgear box you connected to the Dining Room player is STP-enabled and has become root bridge, messing up the topology. I'll send a PM.
Userlevel 1
Badge +2
The Netgear box you connected to the Dining Room player is STP-enabled and has become root bridge, messing up the topology. I'm send a PM.
thanks
Badge +1
FWIW, my Sonos "stuff" is in my home office, a separate building. After losing Sonos Net, I bought a very cheap Netgear wifi range Extender. The original signal from my wifi (tp-link) had to pass though a cinderblock wall (though it does have skylights) across an open space, through a stucco and sheet-rocks wall, through another sheet-rock wall to reach the Extender in the main house. Then, the Extender had to push its signal through another sheet-rock wall. But the signal is perfect. Not so bad.

Reply