My Core runs on a MacBook pro OS Catalina 10.15.7, Roon version 2(build 1244)
Networking Gear & Setup Details
Fritz! Router
Connected Audio Devices
Naim ND5 XS2, Naim MuSo2 (Chromecast) and various Sonos devices
Number of Tracks in Library
1785 Albums
Description of Issue
After the latest update, my Core will not connect to Sonos, although they are listed on the Audio section. They are in a different category to the Naim devices. In addition, I run Roon on my iPad and thisdoes not connect to the Core, nor can it see any audio devices, music library etc.
Sonos speakers updated and Roon for many of us will “lose control of the audio device” which in my case means it doesn’t even start playing just delays a few seconds and then says it has lost control. Roon pushed out an update but that has yet to resolve. i am sure they are working on this.
I am having same issue since Sonos updated. Roon did push out an update also but it has not resolved yet. I can work around via airplay but for some reason the path stream goes lossless purpose down to green - not knowledgeable enough on why Sonos stream from Roon is lossless but the Roon via Airplay to Sonos changes things a bit. (I can’t say I can hear the difference but I did enjoy seeing the lovely purple instead of the sad green ) Anyway I think Roon will need to fix this.
Same issues as my co-posters. Roon and Sonos don‘t lile each other any more
Roon Core Machine
ROCK - NUC8BEB, 256GB SSD, 8 GB RAM, i-5-8259U
Networking Gear & Setup Details
Fritzbox 7590
Fritz Repeater 3000 (Sonos Playbase connected via Ethernet, all other sonos devices are connected wireless via sonosnet)
Sonos Boost
Connected Audio Devices
Sonos Playbase (+2x Sonos One + Sub)
Sonos One SL
Sonos Roam
Iphone
Rodecaster Pro USB
Number of Tracks in Library
“26,000 tracks”.
Description of Issue
Trying to play „via Sonos streaming“ devices throws the „Roon lost connection to Audio device“ error
Both playbase and One SL have the issue
I did not test roam
Airplay works
Sonos version 15.2
Roon OSVersion 1.0 (build 256) production
Roon Server Software
Version 2.0 (build 1244) production
UPDATE: The Sonos ROAM is working fine. Speculation: This could be because it operates directly from the Wifi-Accesspoint and is not part of the proprietary Sonosnet configuration.
2023-04-02 08:46:21.303 Roon[1539:46542] The type Broo.Engine.BrooOpenGLView does not have a constructor that takes an ObjCRuntime.NativeHandle parameter but a constructor that takes an System.IntPtr parameter was found (and will be used instead). It’s highly recommended to change the signature of the System.IntPtr constructor to be ObjCRuntime.NativeHandle.
2023-04-02 08:46:21.363 Roon[1539:46542] The type Broo.Engine.OpenGlWindow does not have a constructor that takes an ObjCRuntime.NativeHandle parameter but a constructor that takes an System.IntPtr parameter was found (and will be used instead). It’s highly recommended to change the signature of the System.IntPtr constructor to be ObjCRuntime.NativeHandle.
2023-04-02 08:46:21.367 Roon[1539:46542] The type Broo.Engine.CocoaComponents does not have a constructor that takes an ObjCRuntime.NativeHandle parameter but a constructor that takes an System.IntPtr parameter was found (and will be used instead). It’s highly recommended to change the signature of the System.IntPtr constructor to be ObjCRuntime.NativeHandle.
2023-04-02 08:46:21.404 Roon[1539:46542] The type Broo.Engine.SooloosSecureTextFieldCell does not have a constructor that takes an ObjCRuntime.NativeHandle parameter but a constructor that takes an System.IntPtr parameter was found (and will be used instead). It’s highly recommended to change the signature of the System.IntPtr constructor to be ObjCRuntime.NativeHandle.
Hi, Same issues here, rebooting and restarting everything in the house the past weekend with no luck.
But I’m happy to see its a known issue and the Roon-team is looking into it.
I’m not going to do the workaround as I use my Roon system with other endpoints that still work, and I just use the Sonos app for streaming from Qobuz while waiting for a fix.
My Roon system developed this problem sometime in the middle of last week. I cannot say whether it was immediately after the Roon Core update or the Sonos update.
Today, I did a full power down and sequential restart of my entire home network, to include the cable modem, network switch, Eero, and Sonos devices. I also closed all Roon controller and Sonos apps on my computers and iOS devices, and powered down my computers. My Roon Core is installed on a headless Mac mini M1 that has operated flawlessly.
After all that, I still got the “Roon lost control of the Audio device” when trying to play music on a Sonos device. All of my 5 Sonos speakers show up as enabled in the Roon Audio settings.
Roon functions flawlessly on my 3 Roon streaming endpoints (Lumin, Cambridge, Bluesound). Roon Arc continues to work fine in my car using Apple CarPlay.
I really hope that the Roon and Sonos engineers can solve this problem soon.
At 1:58 EDT, I tried to play the first song in a Daily Mix. The track I attempted to play was Bill Evans/Sunday at the Village Vanguard/Gloria’s Step [Take 3]. I tried to play the track on a Sonos Play 5.
I am unsure if I am yet on your list of having diagnostics enabled. However, I will gladly test again if you confirm that I am on your list of impacted subscribers.
Same. I had an updated play 1 and and a play 1 not updated to the most recent sonos update. Tge updated one failed and the non updated one worked. Updated sonos on all devices and now both play 1s are not playing through Roon. They play via sonos app. 2 connect devices not effected.
Since my Roon rock nuc is headless I won’t be pulling out a monitor to command line temp fix this.
This issue seems intermittent to me. Sometimes I get the “Roon lost control of the audio device” message but when I regroup the same couple of zones it seems to work again it seems to work again. Weird.
Im still waiting for a fix. My airplay recievers still work and my bluesound node2 still works. so frustrating since my kids room all have sonos speakers in them and I have to tell them its currently broken.
) Anyway I think Roon will need to fix this.