Sonos Bridge Not Detected When Using Sonos Controller

[battags]

I also tried connecting with controllers on both Android and iOS.

[battags]

I'm still not seeing my Sonos devices under "Active Lease" for DHCP.  If I go to static leases, I can see that the router knows about the devices (I matched the MAC address to Sonos' range) and they have an IP address.  Creating a static lease of that MAC to the same IP address doesn't make them any more discoverable.

I also can't do the usual http://<IP ADDRESS>:1400/status to get to Sonos' status page for the device.

[battags]

Some information about the network:

root@AlmondPlus:~# brctl show
bridge name   bridge id      STP enabled   interfaces
br-lan      8000.e4718530a3e1   yes      eth1
                     wlan00
                     wlan10

root@AlmondPlus:~# brctl showmacs br-lan
port no   mac addr      is local?   ageing timer
  1   00:0e:58:19:50:f8   no         0.99
  1   00:0e:58:8d:74:60   no         1.84

<snip /> <-- I removed all of the non-Sonos ones when I copied this in



root@AlmondPlus:~# brctl showstp br-lan
br-lan
 bridge id      8000.e4718530a3e1
 designated root   8000.000e581950f8
 root port         1         path cost       100
 max age         6.00         bridge max age         6.00
 hello time         1.00         bridge hello time      1.00
 forward delay         4.00         bridge forward delay      4.00
 ageing time       300.00
 hello timer         0.00         tcn timer         0.75
 topology change timer      0.00         gc timer        71.29
 flags         TOPOLOGY_CHANGE_DETECTED


eth1 (1)
 port id      8001         state           forwarding
 designated root   8000.000e581950f8   path cost       100
 designated bridge   8000.000e581950f8   message age timer      5.19
 designated port   8001         forward delay timer      0.00
 designated cost      0         hold timer         0.00
 flags         

wlan00 (2)
 port id      8002         state           forwarding
 designated root   8000.000e581950f8   path cost       100
 designated bridge   8000.e4718530a3e1   message age timer      0.00
 designated port   8002         forward delay timer      0.00
 designated cost    100         hold timer         0.77
 flags         

wlan10 (3)
 port id      8003         state           forwarding
 designated root   8000.000e581950f8   path cost       100
 designated bridge   8000.e4718530a3e1   message age timer      0.00
 designated port   8003         forward delay timer      0.00
 designated cost    100         hold timer         0.77
 flags         

[battags]

More debugging...

if I run arp -n

I see this for the Sonos devices:
? (10.10.10.105) at <incomplete>  on br-lan

(I also flushed the cache with "ip neigh flush dev br-lan")

[Monomakh]

I, too, am having Sonos problems since beginning to use the Almond+.

I currently have the A+ set up as an AP. With the Sonos bridge connected directly to the A+, I am able to connect to the Sonos components maybe 1/4 of the time. If I put the bridge back on the main router, I am able to connect but of course the remote components have a spotty connection, which was the whole point of using the AP.

So, the A+ has to be blocking something even in AP mode, right? How can I diagnose this?

[biznews]

Did anybody ever come up with a fix for this ?   My Almond works fine with Sonos but the Almond + doesn't connect at all.

[Rahaman]

any active user on this thread ?

I would like to solve this issue ................

[buddybar]

I don't have any solution.  I am in the same boat.  Using my android phone and the new almond+, I cannot "find" my sonos.  This did not happen with the first almond or with other routers.

[LGNilsson]

Please PM/work with Rahaman so we can solve this issue, he's part of our test team and will be working with you guys on this.

[battags]

I've been periodically plugging my Almond+ back in and updating to whatever the latest beta firmware is and seeing if any of the controllers can find a Sonos device.  It fails EVERY time, which is highly disappointing.

I hadn't tried in a while and just installed the latest beta and it doesn't work still so I will be unplugging the Almond+ again and enabling my previous router.  This hasn't worked since Day 1 which is highly disappointing.

[battags]

Any update?  I sent a PM with no response yet.  I've posted a good amount of information from my own debugging.  What else do you guys need?

[mrv777]

I'm not sure if my issue is related to the Almond+, but every few days the Sonos app on my phone can't find my Sonos3.  I have to unplug my Sonos3, re-plug it in, and then everything with it works fine.  The Sonos3 directly connects to the Amond+'s wifi

[battags]

I just wanted to update this thread in case anyone searches for Sonos support.

I worked over the phone with the support team (who were great and spent *a lot* of time with me) and we were unable to figure out why the Sonos Bridge did not work (their test one worked for them).  I was able to get my Sonos working with the Almond+ by *NOT* using the Sonos Bridge and using Sonos' new WiFi connection/support.  That works perfectly for me due to the fact that the WiFi signal is pretty strong in my house.  It may not be a solution for everyone.

[Monomakh]

As an update, the problem is the songs bridge. Take the bridge out of the network and connect the play speakers to WiFi directly, and magically everything works again.