Unable to play to Sonos device

Support
1

Roon Core Machine

Roon version version 2 (build 1277)

Mac Mini
Model name: Intel(R) Core™2 Duo CPU P8600 @ 2.40GHz
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 36 bits physical, 48 bits virtual
CPU(s): 2
Debian

Networking Gear & Setup Details

eero pro 6 mesh

Connected Audio Devices

Sonos beam via wifi

Number of Tracks in Library

20 000 tracks

Description of Issue

I can’t play to the Sonos beam. It appears as an audio device but before any music comes out it reports “roon lost control of the device”
I followed instructions as per Sonos - "Roon lost control of the audio device" after Sonos Update [Resolved: Update Sonos Firmware] - #55
but it did not make any difference.
The sonos device does not need a firmware update.

2

Hey @Peter_Bonifacio,

Ben with the support team here, thanks for writing in! I was able to review a recent core diagnostic and see that the Beam was active and had playback. Are you still running into issues here?

If so, please reproduce the issue and share the specific date and time. Thanks!

4

Hi Ben, I reproduced the problem today at about 30/06 11:10 Australia/Melbourne time (UTC 01:10).
Thanks for looking at this.

5

Hey @Peter_Bonifacio,

Thanks for the update! If possible, as a next step I would test out hardwiring your sonos device to your router/ core and see if the issue persists.

I would also refresh your RAAT Server. You can generate a new RAATServer instance on your device by following these instructions, but please be aware that this will reset your Roon Settings → Audio Tab to factory settings and I would advise making a backup of any custom DSP settings you have:

  • Create a Backup of your current Roon database
  • Exit out of Roon
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RAATServer”
  • Rename the “RAATServer” folder to “RAATServer_old”
  • Restart the Roon App to generate a new RAATServer folder

I’ll be on standby for your reply. Thanks!

6
  1. Connected sonos through ethernet
  2. Followed instructions as above re RAATServer.
    No difference.
    Tested again on 01/07 at about 11:01 Australia/Melbourne time .
8

Hey @Peter_Bonifacio,

Thanks for the time stamp! We’re seeing some reoccurring expired airplay device errors around that time, and so it has me thinking - your Beam may be attempting to use Airplay 2 protocol, which is not yet supported in Roon.

If possible, can you confirm which generation Beam you’re using? We’ll need to determine if it’s backward compatible and can still function on the Airplay 1 protocol.

Let me know, thanks! :+1:

9

Here are details …

IMG_2605
IMG_2605960×2079 112 KB

11

Hey @Peter_Bonifacio,

Thanks for the info! If possible, can you reset the Beams settings to default from the sonos app? You can see the Beam from your Sonos app/network correct?

To confirm, you have also tried streaming via the Sonos Streaming protocol and not Airplay, correct?

Let’s reset your database as a next step:

  • Create a Backup of your current database
  • Exit out of Roon
  • Navigate to your Roon Database Location
  • Find the folder that says “Roon”
  • Rename the “Roon” folder to “Roon_old”
  • Reinstall the Roon App from our Downloads Page to generate a new Roon folder
  • Verify if the issue persists on a fresh database before restoring the backup
12

Hi Benjamin
I tried all this in response to an earlier request.
That is

  1. I have done a factory reset
  2. The problem occurs with the Sonos protocol and not Airplay (airplay works ok when it appears - which is not always)
  1. I have already done a reset of the RAATServer folder.
  2. I can’t locate the “Roon” folder based on the information provided …
root@deb:~/.RoonServer# find . -name Roon -ls
root@deb:~/.RoonServer# find . -name RoonServer -ls
root@deb:~/.RoonServer

Do you mean the ./RoonServer directory itself?

Blockquote

13

Hey @Peter_Bonifacio,

My apologies, I had thought your core was running on an macOS device.

Yes, that should do it. We’re essentially refreshing your database to continue troubleshooting on a clean slate.

14

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.