Long time Sonos user. It used to be rock solid. Not any more. We have 4 Zone Players in the house (no PLAY speakers), and since the 9.0 app, it's practically unusable.
Our zones are Office, Shop, Living Room, and Pool. 95% of the time I am using it in Shop with an Amazon Fire tablet (new model). What happens is the controller app in the shop will randomly switch the room to Pool. Sometimes I can switch back to Shop, and other times Shop is completely missing, with the only room available to choose it Pool. Quitting the app doesn't work. I have to go into settings / advanced and do a reset controller. All the rooms come back and Shop is now selectable and works.
Other times, it switches to Pooll all by itself, and when I choose Shop, it says "Sonos Player not found" (or something similar). Again controller reset in the app fixes it. But most of the time, I can just go to Rooms, select Shop and start playing again.
The other issue/annoyance that has existed since V8 is that my Now Playing screen will drop down, and the tablet is left with whatever screen was up before I started playing. I can touch the arrow to raise up the Now Playing screen and it will just randomly drop down by itself. It never used to do that. It would always leave Now Playing up (even when music has been stopped) making it an easy one-touch to start playing again.
I have put in a brand new Fire HD8 tablet, loaded the latest Sonos app, but these issues remain. I have also tried connecting to different WIFI (a temp WIFI AP a few feet from the tablet in the Shop) and had even tried enabling the option to use SonosNet instead of WIFI, but no difference.
All my Zone Players are wired to ethernet. In the shop, the ZP:Connect is about 6 ft from the tablet.
I would like to submit diagnostics from this tablet. Please advise.
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Page 1 / 2
Userlevel 7
+22
Note regarding Duplicate IP addresses - you can look at your router and it will certainly show all your Sonos units and the IP addresses assigned to them. That doesn't mean that some other device on your network is not incorrectly using the IP address that Sonos is using. In most duplicate IP address issues it is not the Sonos unit at fault it is another device on your network that has been assigned a new IP address and is not using the new address but an old expired address (that Sonos is now being directed to use).
Best way to resolve is go through your router list of all Sonos devices and give them all new fixed addresses higher up in area your router never starts assigning to. On my router I have it set to assign IP addresses between 100 and 300. I have all of my Sonos units set for like 250, 251, 252, 253. This makes sure the Sonos units are on clean IP addresses that have never been used by other devices. Never an IP address issue since. You need to do this with every Sonos unit not just one to insure you have stability across your mesh.
Once you go through all your Sonos units and assign them new fixed numbers. Reboot them all and your troubles will be gone and you won't have any issues after updates with IP address conflicts.
Best way to resolve is go through your router list of all Sonos devices and give them all new fixed addresses higher up in area your router never starts assigning to. On my router I have it set to assign IP addresses between 100 and 300. I have all of my Sonos units set for like 250, 251, 252, 253. This makes sure the Sonos units are on clean IP addresses that have never been used by other devices. Never an IP address issue since. You need to do this with every Sonos unit not just one to insure you have stability across your mesh.
Once you go through all your Sonos units and assign them new fixed numbers. Reboot them all and your troubles will be gone and you won't have any issues after updates with IP address conflicts.
+1
Ok cheers. Some things to try. I'll feedback what happens for me
+1
Well.....tried fixing then .240 upwards but issue still happened shirtly after. Now done full power down reset and a factory hard reset of my router.....so far so good, but it's early days as it's been ok for a few days after other attempts. Fingers crossed though so I can just get back to enjoying my Sonos
I’m getting this happen as well. I’ve put my comments in the thread about the latest iOS app freezing if you need to see my comments. I tried the Android app on my phone and this is starting up with the wrong zone occasionally as well - I closed the app whilst it was on the Lounge zone and when I restarted it again it was on the ZP90 Office zone.
The iOS app has also unknown to me started the ZP90 Office zone playing when it was supposed to be stopping playback on the Lounge zone. My ZP90 was therefore playing continuously without me knowing for a couple of days.
I’ve had a long phone chat with Sonos support and sent a few diagnostics off but haven’t heard back for a day and a half.
The iOS app has also unknown to me started the ZP90 Office zone playing when it was supposed to be stopping playback on the Lounge zone. My ZP90 was therefore playing continuously without me knowing for a couple of days.
I’ve had a long phone chat with Sonos support and sent a few diagnostics off but haven’t heard back for a day and a half.
There is some sort of huge disconnect between the controller app and the device itself.
Agreed. I’ve had exactly that happen a couple of times as well. It’s like it’s forgotten which zone it’s controlling and what state the player is in (play/stop)
In addition to that I’ve then left it for a minute or so after that has happened and then it displays the splash screen as if it has restarted the app.
There is some sort of huge disconnect between the controller app and the device itself.
Agreed. I’ve had exactly that happen a couple of times as well. It’s like it’s forgotten which zone it’s controlling and what state the player is in (play/stop)
In addition to that I’ve then left it for a minute or so after that has happened and then it displays the splash screen as if it has restarted the app.
Yes, I've been seeing the same sorts of problems, but not on 9.x - I'm currently on 8.6 - mine mainly goes wrong on my android phone, though.
Someone on another forum I visit is reporting this same problem on the ios app. It’s gone quiet from Sonos support. I’ve replied to their support email 3 times with new information and updates and never received a reply
JohnG666,
In your case, it certainly sounds like it might be a duplicate IP address issue. Try unplugging all of your Sonos devices from power, then reboot your router. Once the router comes back up, plug in one Sonos device back into power, and give it a minute or two to boot up, before moving on to the next and plugging it in.
This issue is a problem with the router losing track of what IP address it has handed out, and is often exposed when Sonos causes the soft reboot of the speaker during a software update. Another way to keep this from happening again is to go in to your router’s DHCP reservation table, and set up reserved IP addresses for all of your WiFi connected devices.
Frankly, this may also be the OPs issue as well, but given that s/he has already submitted a diagnostic, I’m loathe to step on the Sonos rep’s toes when they arrive to work tomorrow.
In your case, it certainly sounds like it might be a duplicate IP address issue. Try unplugging all of your Sonos devices from power, then reboot your router. Once the router comes back up, plug in one Sonos device back into power, and give it a minute or two to boot up, before moving on to the next and plugging it in.
This issue is a problem with the router losing track of what IP address it has handed out, and is often exposed when Sonos causes the soft reboot of the speaker during a software update. Another way to keep this from happening again is to go in to your router’s DHCP reservation table, and set up reserved IP addresses for all of your WiFi connected devices.
Frankly, this may also be the OPs issue as well, but given that s/he has already submitted a diagnostic, I’m loathe to step on the Sonos rep’s toes when they arrive to work tomorrow.
+1
Cheers I'll try another router reboot. Tried it a few times before, fixes things only for a short time. I've also went fixed IPs too. I was away for 2 weeks put everything off except the main router too but problem was back after a few days. Unless my router is dodgy. It's a Plusnet hub, under a year old, but probably not the best.
I have a similar issue and posted a question too: https://en.community.sonos.com/troubleshooting-228999/connect-amp-disconnecting-from-the-controller-6810940
I should reiterate there that for me (the OP), that merely selecting "Reset Controller" in the Sonos app advanced settings brings back the dropped / missing Zone Players. Now, if it were some sort of network/DNS/IP/Router issue, then merely resetting the app shouldn't bring back the Zone Players. So far, I haven't been convinced it's not some screw-up in the app.
As far as the app just switching rooms randomly, nothing changes in my network that often that would cause a ZP to disappear. Since everything is on my local network, it isn't a router issue.
As far as the app just switching rooms randomly, nothing changes in my network that often that would cause a ZP to disappear. Since everything is on my local network, it isn't a router issue.
+1
Thinking about it. Sometimes when my players have disappeared randomly from Sonos they are still listed on my router IP list. Could be the list hasn't refreshed or the players are still indeed on my LAN
Yea, I'd suggest that even if the "reset controller" is indeed working, it could be just catching the next time that the duplicate IP address bounces from and to your Sonos, and it catches the new connection while it's up. The biggest issue with duplicate IP addresses is that they're incredibly hard to see on all of the servers I've ever had. The server only takes a snapshot of what is connected at a particular moment, and none of mine have ever shown "and this has been connected for X amount of time", which would be the key thing to identifying duplicate IP address issues. Of course, I've got about 70 random things connected to my wifi, so it's hard for me to remember them all at any particular moment, which is one of the reasons I went with the DHCP reservations, after a minute or two of reading to figure out how to do it.
So it's still possible in my mind that it is indeed a duplicate IP address, and you're losing contact momentarily, and then it's catching back up. And it being local means it probably is indeed your router, rather than anything outside of your local LAN. Duplicate IPs can occur with both wired and wireless signals, too.
I'd definitely try the refresh of unplugging all Sonos devices, then rebooting the router, and plugging back in each Sonos device one at a time, allowing each to boot up before moving on to the next. At the very least, it won't hurt anything.
But if none of that works, I'd definitely recommend that you submit a system diagnostic within 10 minutes of replicating this issue, and contact Sonos to discuss it. There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution. In skimming the thread, I didn't see one indicated from you, so it might be helpful. Especially if you think there's a screw up in the app, the diagnostic should reveal what's causing the speakers to fail.
I doubt it is the app, but I've been wrong before, and will be wrong again. Give them that diagnostic, then call in, and see what they say. Or try the Twitter or Facebook contact points, if that's more convenient to you.
So it's still possible in my mind that it is indeed a duplicate IP address, and you're losing contact momentarily, and then it's catching back up. And it being local means it probably is indeed your router, rather than anything outside of your local LAN. Duplicate IPs can occur with both wired and wireless signals, too.
I'd definitely try the refresh of unplugging all Sonos devices, then rebooting the router, and plugging back in each Sonos device one at a time, allowing each to boot up before moving on to the next. At the very least, it won't hurt anything.
But if none of that works, I'd definitely recommend that you submit a system diagnostic within 10 minutes of replicating this issue, and contact Sonos to discuss it. There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution. In skimming the thread, I didn't see one indicated from you, so it might be helpful. Especially if you think there's a screw up in the app, the diagnostic should reveal what's causing the speakers to fail.
I doubt it is the app, but I've been wrong before, and will be wrong again. Give them that diagnostic, then call in, and see what they say. Or try the Twitter or Facebook contact points, if that's more convenient to you.
Userlevel 7
+22
I've found nmap to be fairly good at tracking IP addresses for this sort of thing, it shows the responses from the network, not cached data from a server or router.
code:
stan@dell-3620:~> nmap 172.16.1.1-254
Starting Nmap 7.70 ( https://nmap.org ) at 2018-08-06 13:37 MST
Nmap scan report for SonosZB-4C.home (172.16.1.110)
Host is up (0.00047s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
1443/tcp open ies-lm
Nmap scan report for SonosZP1-04.home (172.16.1.120)
Host is up (0.0011s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
1443/tcp open ies-lm
Nmap scan report for SonosZP3-6A.home (172.16.1.126)
Host is up (0.00050s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
1443/tcp open ies-lm
Nmap scan report for SonosZP5-E2.home (172.16.1.132)
Host is up (0.0017s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
1443/tcp open ies-lm
Userlevel 7
+22
Things to look for is always a fun game to play when presented with networking issues, some aren't obvious.
I'd start with the nmap above to get a list of what Sonos device is currently answering at each IP address.
Next I'd check the "About My Sonos System" on each of your controllers and see what IPs they are each showing.
Last look at your DHCP server's logs and see what activity they show for your Sonos gear's MAC addresses.
I'd start with the nmap above to get a list of what Sonos device is currently answering at each IP address.
Next I'd check the "About My Sonos System" on each of your controllers and see what IPs they are each showing.
Last look at your DHCP server's logs and see what activity they show for your Sonos gear's MAC addresses.
+1
Ok just had a wee flicker of the issue. Resumed a playlist on my Connect, then after 1 song, shown track stopped updating and when i try to skip or pause etc...I get "unable to play the seleceted....". When I did the About My Sonos System, my 2 Play5s gave full info, but the Connect only had the player name and Connect....nothing else
+1
My Connect is the player hardwired too, fixed IP. I also can't submit diagnistics when this happens. It's not always the Connect either
300 - Really?
I do it slightly differently, having everything important, including NAS devices, Sonos kit and controllers and PCs/laptops either reserved or static under .100 - dynamic from 101 to 199 - 200 onwards reserved for future use, if needed.
Agreed... Which is why when, after doing all that, and there is still a problem with the Sonos system, it's unlikely to be a network issue.
Just to put "duplicate IP addresses" issue to rest (at least for me), I have gone into my DHCP server and setup reservations for all 4 of my Zone Players, and power cycled each of them, one at a time, and identified that each Zone Player has picked up their respective reserved IP address.
I have done a "reset controller" on the Fire Tablet in question, and it found (as it always does after a reset controller) all four Zone Players (which are, btw, 2 x CONNECT and 2 x ZP100).
One thing I have noticed is that when the Sonos App loses control (switches room or stops refreshing the screen with the current song info, or just can't control the ZP any longer) that it always can still see the ZP100's and just the CONNECTS are missing from the list.
In any case, time will tell (not too much time, so today I should know as my issue is VERY FREQUENT and DAILY or HOURLY).
I have done a "reset controller" on the Fire Tablet in question, and it found (as it always does after a reset controller) all four Zone Players (which are, btw, 2 x CONNECT and 2 x ZP100).
One thing I have noticed is that when the Sonos App loses control (switches room or stops refreshing the screen with the current song info, or just can't control the ZP any longer) that it always can still see the ZP100's and just the CONNECTS are missing from the list.
In any case, time will tell (not too much time, so today I should know as my issue is VERY FREQUENT and DAILY or HOURLY).
One day later (after setting static IP's to all ZP's), I checked in on the tablet controller this morning and saw it was still on SHOP where I left it (although the Now Playing screen had dropped down like it always does by itself) so I tried pressing play on the screen and it sat there and sat there and sat there...finally the app just spontaneously closed. Crashed I guess.
I did a "Submit Diagnostics". Since no Sonos staff is following this thread, I will get with their support directly to follow up on the diagnostics.
In summary, for me, duplicate or conflicting IP's is NOT what is causing all this craziness that makes using my Sonos frustrating.
I did a "Submit Diagnostics". Since no Sonos staff is following this thread, I will get with their support directly to follow up on the diagnostics.
In summary, for me, duplicate or conflicting IP's is NOT what is causing all this craziness that makes using my Sonos frustrating.
Well, please come back and let us know what they discover the issue is, so that we can learn more information about the potentials.
Encountering the same problem for weeks now, will get in the loop with diagnostics and support now, too.
Following the system update which sent my five CR100 to the recycling bin, I replaced them with Android devices (Nexus 5) and right away started seeing random switches and the app hanging. CR200 controllers seem to be not affected. Several carefully sequenced reboots did not help to resolve the issue.
Following the system update which sent my five CR100 to the recycling bin, I replaced them with Android devices (Nexus 5) and right away started seeing random switches and the app hanging. CR200 controllers seem to be not affected. Several carefully sequenced reboots did not help to resolve the issue.
I spend an hour with telephone support last week trying to work out what was going wrong. We eliminated the obvious causes and I've disabled my CR200 by taking the battery out to rule that out as a potential cause.
I'm still getting this problem on my iPad and on my Android phone. It's not just one particular zone where it's happening either. On Monday I was using the Android phone in the office to control the office zone. The wifi router is in that office less than 2 yards away. It randomly chose different zones to display when waking the phone out of sleep approximately half a dozen times during the working day.
So today I've removed my router and put the Virgin Superhub into router mode (it was previously in modem mode) and I'm now using that for wired and wireless connections - this would rule out a problem with my router.
The problem is still happening.
This afternoon the following happened:-
Using my iPad I set Radio 6 Music (Tunein) playing in the lounge.
I left it playing for at least 45 minutes.
Woke iPad out of sleep - the Sonos app was full screen and displaying the Kitchen zone and saying no music selected. The Lounge zone was still happily playing the radio station with no interruptions.
Diagnostic submitted - 131808964
I'm still getting this problem on my iPad and on my Android phone. It's not just one particular zone where it's happening either. On Monday I was using the Android phone in the office to control the office zone. The wifi router is in that office less than 2 yards away. It randomly chose different zones to display when waking the phone out of sleep approximately half a dozen times during the working day.
So today I've removed my router and put the Virgin Superhub into router mode (it was previously in modem mode) and I'm now using that for wired and wireless connections - this would rule out a problem with my router.
The problem is still happening.
This afternoon the following happened:-
Using my iPad I set Radio 6 Music (Tunein) playing in the lounge.
I left it playing for at least 45 minutes.
Woke iPad out of sleep - the Sonos app was full screen and displaying the Kitchen zone and saying no music selected. The Lounge zone was still happily playing the radio station with no interruptions.
Diagnostic submitted - 131808964
I've just had word that there appears to be a bug in the software that can cause this to happen.
JohnG666, thanks for the update. It certainly seems the problem is with the Sonos app. I've spent the last 3 days working with Sonos support also. They said my logs pointed to a connection issue. They asked me to change the ethernet cable at the ZP, so I did that. No change. I put in a new ethernet switch where the affected ZP is, but no change. Since I switched CONNECT units a couple weeks ago, and the problem stayed with the room, I knew it wasn't a defective ZP.
Day before yesterday, I was thinking what other device could I use as a controller, and remembered I had a couple-year-old LG Android tablet in the drawer. Pulled it out, charged it, and turned it on and brought it up to date. Updated SONOS app to the current version. Interestingly, it works flawlessly. So far (granted it's only been two days), it does not lose control, freeze, switch rooms, crash, or fail to update the current song on the Now Playing screen. It works normally. My issue with the Now Playing screen dropping down randomly (I leave it on Now Playing, but i'll come back and it's dropped down as though I've touched the "drop down" arrow on the upper left) is MUCH BETTER. It's only done it once.
Reading the recent reviews on the Google Play Store, it's obvious there is an issue with this app, yet Sonos Support acts like they've never heard of the issue before. Instead of saying they're aware of the issue, they make people waste time trying all sorts of unrelated things. Not cool.
In any case, for now, at least I'm working. Not sure why this tablet is working, when plenty of other people with Android are having the same problem, and my Fire Tablets run the same Android version of the Sonos App.
Still lots of questions with no answers. Could you elaborate on what "bug" is in the software and what you heard?
Day before yesterday, I was thinking what other device could I use as a controller, and remembered I had a couple-year-old LG Android tablet in the drawer. Pulled it out, charged it, and turned it on and brought it up to date. Updated SONOS app to the current version. Interestingly, it works flawlessly. So far (granted it's only been two days), it does not lose control, freeze, switch rooms, crash, or fail to update the current song on the Now Playing screen. It works normally. My issue with the Now Playing screen dropping down randomly (I leave it on Now Playing, but i'll come back and it's dropped down as though I've touched the "drop down" arrow on the upper left) is MUCH BETTER. It's only done it once.
Reading the recent reviews on the Google Play Store, it's obvious there is an issue with this app, yet Sonos Support acts like they've never heard of the issue before. Instead of saying they're aware of the issue, they make people waste time trying all sorts of unrelated things. Not cool.
In any case, for now, at least I'm working. Not sure why this tablet is working, when plenty of other people with Android are having the same problem, and my Fire Tablets run the same Android version of the Sonos App.
Still lots of questions with no answers. Could you elaborate on what "bug" is in the software and what you heard?
Page 1 / 2
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.