World-Class Superstar

Problem: why does a library update kill the queue?

Forum|Forum|4 years ago
December 9, 2021
38 replies
489 views

After having installed the 13.4.1 update this problem occurs: a daily update of my music library at 11.50am removes the active queue in one of my rooms. Radio play in other rooms is not affected. The problem occurs repeatedly and can be reproduced.

Diagnostic: 78616423.

Please advice what to do. TIA.

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.

Show previous replies

Ken_Griffiths

@beynym
Just to add I’ve also tried the above whilst the music is still playing from the NAS… the queue stays in my case, but I’m happy to try whatever steps to try to reproduce this and to try to help you get to the root cause of the issue.

B

beynymAuthor

World-Class Superstar

What I did was this:

Put a Sonos Playlist in the queue of the room (the Port).
Changed the time of the automatic library update to 5 minutes in the future.
Waited 5 minutes.
At exactly the time of the scheduled update the music stopped, the room with the Port disappeared for a second from the left pane of the desktop controller, then re-appeared without the queue.

That's it. I have repeated this procedure and every time the outcome is the same.

Ken_Griffiths

What I did was this:

Put a Sonos Playlist in the queue of the room (the Port).
Changed the time of the automatic library update to 5 minutes in the future.
Waited 5 minutes.
At exactly the time of the scheduled update the music stopped, the room with the Port disappeared for a second from the left pane of the desktop controller, then re-appeared without the queue.

That's it. I have repeated this procedure and every time the outcome is the same.

Ok I will try the same thing…

What does the Port’s Status LED show when this happens and is it always the same Sonos playlist, which I assume is a playlist of tracks held on your NAS?

B

beynymAuthor

World-Class Superstar

That's it. I have repeated this procedure and every time the outcome is the same.

Ok I will try the same thing…

What does the Port’s Status LED show when this happens and is it always the same Sonos playlist, which I assume is a playlist of tracks held on your NAS?

I did not check the Port's Status LED. The Sonos Playlist is indeed a collection of tracks from my NAS (a WD MyCloud Home).

Ken_Griffiths

I created a Sonos playlist which I called “Port Test Playlist’’ using the same ED Sheeran tracks for ease and then loaded that saved playlist into Ports queue again and began playing.
I set a library index schedule 5 minutes ahead of local time 19.05hrs. (I’m in U.K.) and the tracks continued playing ..queue stayed in place post indexing.

Ken_Griffiths

I’m wondering if something is causing the Sonos Port to reboot - I dont seem to be able to reproduce the issue here. I was hoping I could.

It might be the way the WD MyCloud NAS share is working (perhaps?) - What SMB version is in use? Have you got the files shared as read/write access? If so, maybe try them with read-only permissions, although I’m fairly sure Sonos does not write anything to the local library.

B

beynymAuthor

World-Class Superstar

Thanks for trying to find a solution. I think it's now up to Sonos to examine the 2 diagnostics I've sent them.

B

beynymAuthor

World-Class Superstar

I’m wondering if something is causing the Sonos Port to reboot

You might be on to something here.

It might be the way the WD MyCloud NAS share is working (perhaps?) - What SMB version is in use? Have you got the files shared as read/write access? If so, maybe try them with read-only permissions, although I’m fairly sure Sonos does not write anything to the local library.

It's a WD MyCloud Home NAS. It has no configuration panel, therefore I can't know what SMB it's using. My music files are normal all the way, haven't changed the attributes since I got them, so that can not be part of the problem. And yes, Sonos never writes anything to the local files.

Ken_Griffiths

@beynym
Well I’m sorry I couldn’t help reproduce the issue, maybe someone with the same NAS can perhaps check things out for you aswell. As you say the diagnostic report might perhaps reveal something too with the Port itself.

Hope you get it sorted. If you do discover what the issue is, then perhaps post the outcome back here.