What is about the life time sibscription. I propose to cancel it but i see only problems with Roon
I just sent you an email about that
Log files uploaded as you’ve asked, please advise
Thank you! We got all the uploads.
Would you please be so kind as to let us know the local date and time when the Sonos devices disappeared?
It will help our technicians a lot in pinpointing the issue
a have a daily restart of the system around 5:00 am and the system has worked until 12:00-12:30
I wanted to let you know that we’re still looking into this. I’ll follow up as soon as I have an update
I wanted to check in
Our team took a deep dive in your logs and we couldn’t find any network errors or any errors at all pointing to the disappearing of your Sonos zones. This also means that, unfortunately, we don’t have any actionable steps
We want to take this further. Are there any updates on your end? Any change in behavior?
it has been taken a little more time to respond, sorry.
But until today, there is no changes.
I’m wondering about your reaction, as i know, a lot of users has this problem with Sonos.
Somtheings i haven’t tested is to run the Sonos purelly over WIFI (or only one player connected via LAN), this action needs a lot of work and improvements in my house.
Do you have any ecperience if this is can helps?
Be aware if you wire one speaker to ethernet you will switch you system over to Sonosnet.
The details are on the link below.
Hi Beka I don’t want to pile in on this, but since build 903 I’m having exactly the same problem, at least once or twice a day.
Everything is wireless, all devices are on reserved DHCP addresses, and Sonos is 100% reliable if used separately. I have supplied multiple logs in the past, but this worked for month’s until build 903.
I have rebooted everything on the network and all device’s multiple times but I cannot find anything to make this reliable.
All my Roon Ready devices are completely stable, but Sonos devices inside Roon just disappear randomly.
I am happy to create a new ticket if you can get anyone from QA involved, or I can go back to my old ticket.
any chance to investigate what happens in build 903? have a look to Michael comments.
I wonder if sonos is doing something weird in the background like going to sleep and only listening on certain ports for traffic.
I have a similar issue, sonos vanishes from roon. If I wake the sonos up with the native app, it comes back on roon. So clearly the app is capable of doing something that roon can’t.
I’ll see if I can run some network captures off my router to see if I can see what port the sonos app is using when it hits the speaker
David a good check, though I have played all Sonos device’s and they never come back until I restart the Rock.
It’s strange that it started happening the night I installed build 903.
The same thing happened a couple of releases ago, which I logged during the beta test. It wasn’t a fun month where I rebuilt my network twice.
Eventually I removed all plugged in Ethernet ports and went pure WiFi which has worked perfectly since.
To me there is something flakey with the Roon discovery process and it also seems to affect Meridian devices.
Any news from Roon to this topic. What has been changed in Roon that Sonos has now this problems
I can’t remember which version introduced it, but I raised a ticket in that beta at that time. Went away for me, but back with a vengeance as of the last three releases.
Rebooting 3 to 4 times a day depending on how long I am awake. I would say that it lasts on average about 4 hours before it loses them all.
@support it would be really good if developers would actually take a look at this and work with a couple of customers to improve debugging around Sonos discovery and why it falls off.
Hello beka, hello Roon support
I’m wondering that no reaction appearing to this topic. It seems that I’ve invested my money into a not working software. Sorry but the problem with Sonos isn’t only in my setup, a lot of people has the same issue. Are you interested to solve this topic???
I can definitely see how everything from where you stand would point to us not paying attention to this issue. You are right, it is affecting you, as well as a few others.
Our investigation is ongoing, but, it is taking us so much longer than we had expected, due to the complexity of the issue and numerous differences in setups and devices.
This week there’s a new round of work to get closer to a resolution.
Please, don’t give up on us just yet
However, make sure you check at all your Sonos components have moved over, and are showing as ‘wired’ - WM: 0
If your components are not showing wired, then turning off / turning on of your wired component can sometimes make the components join.
Or by changing the Channel which Sonos is using can also get the components to join the ‘Wired’.
I’ve previously had a lot of dropouts, see here Roon Dropouts - Why? - #6 by jamie
However, I haven’t had any for a over a month now.
Beka thanks for this update.
I for one am always hopeful that this will be fixed.
Sometimes things are too quiet with these issues but thanks for offering some hope at last, it is most appreciated.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.