Sonos problems (one for Vex hopefully)
Sonos problems (one for Vex hopefully)
Author
Discussion

thebraketester

Original Poster:

15,835 posts

169 months

Monday 24th June 2019
quotequote all
We have had a Sonos Play 1 for a while now and it has been absolutely faultless.

A week ago we added a Sonos One.

Now... for some reason the Sonos Play 1 keeps disconnecting. I have reset it twice now and it will work for a a bit, then it will not show up on either the iphone app or the macos app.

Any ideas to as why this might be happening?

Thanks
Rich

AshW

3,836 posts

272 months

Tuesday 25th June 2019
quotequote all
Have you updated the firmware?

rdjohn

7,194 posts

226 months

Tuesday 25th June 2019
quotequote all
All my firmware is up to date, but my current issue is even more bizarre.

I have a Play in the bedroom as my 7:30 radio alarm and a Connect to my Bose system in the rest of the house.

Every day between 11 - 11:30, the Connect turns off and the Play starts. I have deleted and reinstalled the iPad App and my morning alarm, but it still does it.

anonymous-user

85 months

Tuesday 25th June 2019
quotequote all
In the Sonos app check Settings/Date and time, to make sure you’re on GMT london time. If you can do the same with the Bose, do so.

OP: you can get Sonos units dropping off your network due to IP address conflicts on your network. Conventional advice is to power everything down, then power up the router, let it stabilise for a couple of minutes, then power up each Sonos device in turn (wired first) letting each one establish a connection and appear in the app before powering up the next one.

A longer term fix if you’re able is to get into your router and assign fixed IP addresses to each piece of Sonos kit on your network.

When Sonos is set up properly it’s very stable and reliable. However it isn’t quite as easy to set up properly as the Sonos instructions suggest - it takes a bit of work under the hood.

thebraketester

Original Poster:

15,835 posts

169 months

Tuesday 25th June 2019
quotequote all
Time setting are ok.

All systems are up to date.

Both Sonos have unconflicting IP addresses although I might set them up with static IP addresses to see if that helps. 10.0.1.161 and 10.0.1.190 are the DCHP addresses

As soon as I hardwire the problematic sonos into my network it works fine, and keeps the same up address.

Do the sonos devices have to be within a certain range of each other?

Road2Ruin

6,545 posts

247 months

Tuesday 25th June 2019
quotequote all
thebraketester said:
Time setting are ok.

All systems are up to date.

Both Sonos have unconflicting IP addresses although I might set them up with static IP addresses to see if that helps. 10.0.1.161 and 10.0.1.190 are the DCHP addresses

As soon as I hardwire the problematic sonos into my network it works fine, and keeps the same up address.

Do the sonos devices have to be within a certain range of each other?
Yes, if you are using the Sonos mesh connections system, which I think it does by default. In my old house more than about 7 meters was a problem, but that was through some old, thick, stone walls.

thebraketester

Original Poster:

15,835 posts

169 months

Tuesday 25th June 2019
quotequote all
OK. I might try and locate them next to each other and see if that fixes it, I can live with it wired but I would still like to get to the bottom of why it won’t behave wirelessly.

thebraketester

Original Poster:

15,835 posts

169 months

Thursday 27th June 2019
quotequote all
Its a proximity issue... When placed next to each other they work perfectly. Looks like I will have to hard wire one. Bit crap really, we are not talking a huge distance here.

Podie

46,649 posts

306 months

Thursday 27th June 2019
quotequote all
thebraketester said:
Its a proximity issue... When placed next to each other they work perfectly. Looks like I will have to hard wire one. Bit crap really, we are not talking a huge distance here.
I still run the old Sonos bridge - seems far more stable.