You may want to read the Sonos partners page. You’ll find that Sonos doesn’t integrate other people’s SDK/APKs. That’s the entire point of Sonos, they’re an open platform, who doesn’t need to maintain a thousand coders to update other people’s code changes.
SONOS supports both Spotify Connect and Tidal Connect. Qobuz Connect is basically identical (it probably uses mostly the same code).
If you have Sonos units with a line in you could utilize a streamer that supports qobuz connect like a WiiM Pro while you wait to see if Sonos ever supports this.
I have a WiiM ultra connected to my Sonos 5s Qobuz connect works well in fact it’s all I use for music these days 👍
You may want to read the Sonos partners page. You’ll find that Sonos doesn’t integrate other people’s SDK/APKs. That’s the entire point of Sonos, they’re an open platform, who doesn’t need to maintain a thousand coders to update other people’s code changes.
SONOS supports both Spotify Connect and Tidal Connect. Qobuz Connect is basically identical (it probably uses mostly the same code).
If you have Sonos units with a line in you could utilize a streamer that supports qobuz connect like a WiiM Pro while you wait to see if Sonos ever supports this.
I have a WiiM ultra connected to my Sonos 5s Qobuz connect works well in fact it’s all I use for music these days 👍
Yeah it’s a very positive thing for Sonos and other hardware that have line in, you aren’t locked in to one thing (especially with the history of Sonos f’ing up their software and splitting support)
I'm still waiting for Qobuz Connect to be integrated into my Sonos system. When will it happen?
I'm still waiting for Qobuz Connect to be integrated into my Sonos system. When will it happen?
Since Qobux Connect connecting to Sonos must be implemented in the Qobuz app, I believe that is a question for Qobuz.
I'm still waiting for Qobuz Connect to be integrated into my Sonos system. When will it happen?
Since Qobux Connect connecting to Sonos must be implemented in the Qobuz app, I believe that is a question for Qobuz.
I have the same answer fron Qobuz : it’s a question to Sonos…..
It’s a perfect or a vicious circle
I have the same answer fron Qobuz : it’s a question to Sonos…..
It’s a perfect or a vicious circle
Well you have to ask them if Sonos has access to the code for their app. If they don’t, then their answer doesn’t hold up. Plus, you are posing these questions to support personnel. In my experience, they follow scripts, and have no idea what Sonos even is, never mind how it will integrate with Qobuz Connect. How anyone considers interactions with low level support personnel to be definitive statements on technical capabilities and/or responsibilities boggles the mind.
Have you read the FAQ here?
https://support.sonos.com/en-us/services/qobuz
As far as the Qobuz software, Sonos wouldn’t have access to the code base, so it really isn’t up to Sonos to ‘support’ it, it would be up to Qobuz to implement the already written API, and fold it into their own software.
This ticket is about Qobuz Connect, recently announced
I'm still waiting for Qobuz Connect to be integrated into my Sonos system. When will it happen?
Since Qobux Connect connecting to Sonos must be implemented in the Qobuz app, I believe that is a question for Qobuz.
I have the same answer fron Qobuz : it’s a question to Sonos…..
It’s a perfect or a vicious circle
No, absolutly not.
Qobuz has released Qobuz Connect. It’s now on Sonos engineering to add support in their firmware, period. Qobuz has provided the necessary API. Sonos must implement the counterpart that uses it. Any other explanation from Sonos is a lie.
My question:
Mr. President, I would like to bring to your attention the complaints regarding the integration of Qobuz Connect into your SONOS systems. As you are probably aware, Qobuz has released Qobuz Connect. It is now available to Sonos engineering to add support to their firmware. Qobuz has provided the necessary API. Sonos must implement the counterpart that uses it. I might add that TIDAL has done so, and it works perfectly. However, being French, I would prefer to use a French streaming platform. After several months of Qobuz making the "Qobuz Connect" version available, we haven't seen anything coming from SONOS—I say "us" because there are many of us. Can we hope to see this implementation see the light of day, or is it definitely not? I look forward to your response so I can make a decision on whether to change our audio hardware or wait.
Respectfully,
And the answer from Sonos:
Hi Jean,
Thank you for contacting Sonos, and the office of the CEO. I'm a senior member of the Sonos Customer Experience team.
I completely understand how important it is for you to have Qobuz Connect integrated with your Sonos system, especially given your preference for a French streaming platform. I appreciate you bringing this to our attention and sharing your perspective.
While I can't provide specific details on future updates, I want to assure you that our team is always exploring ways to enhance our product offerings and support a wide range of services. Your feedback is invaluable, and I will make sure it reaches the right people within our team.
We truly value your loyalty and hope to earn your trust back. Please feel free to reach out if you have any more questions or need further assistance. We're here to help.
Kind regards,
Moderator Edit - This is an email reply from the Sonos Customer Experience team that the user has copied to the community.
I'm still waiting for Qobuz Connect to be integrated into my Sonos system. When will it happen?
Since Qobux Connect connecting to Sonos must be implemented in the Qobuz app, I believe that is a question for Qobuz.
I have the same answer fron Qobuz : it’s a question to Sonos…..
It’s a perfect or a vicious circle
No, absolutly not.
Qobuz has released Qobuz Connect. It’s now on Sonos engineering to add support in their firmware, period. Qobuz has provided the necessary API. Sonos must implement the counterpart that uses it. Any other explanation from Sonos is a lie.
This isn’t how standards work at all. Do you reasonably expect every hardware manufacturer (who, by the way, gets paid only when the hardware is sold - not on an ongoing subscription basis like the streaming services are) to put ongoing development effort in supporting every random mom-and-pop streaming service that creates their own protocols?
Sonos maintains a shared connectivity protocol for any audio service to connect and play that service’s content from their own app. The protocol has been around a long time. Some services have chosen to adopt this. Newer Sonos speakers also support local network casting via Airplay 2 (a common standard), and they have a library with 133 streaming services who choose to make their media available within the Sonos ecosystem. That said, there are tradeoffs when using AirPlay over the native Sonos integration.
Qobuz can’t show up with their own proprietary Connect offering and expect every random hardware manufacturer to adopt it when service-neutral open standards like AirPlay and Chromecast already exist (tho more on Chromecast below). That would require firmware updates for hundreds of device models going back >10 years, ongoing developer support from Sonos as Qobuz inevitably makes changes to Qobuz Connect as time passes, and unnecessary code complexity.
Now, where Sonos reasonably COULD do something here is add support for the Google Cast Receiver API, as Chromecast is another common industry standard. This would allow casting from any app that natively supports it, and it would extend local network control to the Android community who can’t use Airplay today. That said, Google stole a bunch of IP from Sonos when it comes to multi-room audio control, so it’s unlikely we will see Sonos bend over backwards to support a Google product anytime soon.
I'm still waiting for Qobuz Connect to be integrated into my Sonos system. When will it happen?
Since Qobux Connect connecting to Sonos must be implemented in the Qobuz app, I believe that is a question for Qobuz.
I have the same answer fron Qobuz : it’s a question to Sonos…..
It’s a perfect or a vicious circle
No, absolutly not.
Qobuz has released Qobuz Connect. It’s now on Sonos engineering to add support in their firmware, period. Qobuz has provided the necessary API. Sonos must implement the counterpart that uses it. Any other explanation from Sonos is a lie.
This isn’t how standards work at all. Do you reasonably expect every hardware manufacturer (who, by the way, gets paid only when the hardware is sold - not on an ongoing subscription basis like the streaming services are) to put ongoing development effort in supporting every random mom-and-pop streaming service that creates their own protocols?
Sonos maintains a shared connectivity protocol for any audio service to connect and play that service’s content from their own app. The protocol has been around a long time. Some services have chosen to adopt this. Newer Sonos speakers also support local network casting via Airplay 2 (a common standard), and they have a library with 133 streaming services who choose to make their media available within the Sonos ecosystem. That said, there are tradeoffs when using AirPlay over the native Sonos integration.
Qobuz can’t show up with their own proprietary Connect offering and expect every random hardware manufacturer to adopt it when service-neutral open standards like AirPlay and Chromecast already exist (tho more on Chromecast below). That would require firmware updates for hundreds of device models going back >10 years, ongoing developer support from Sonos as Qobuz inevitably makes changes to Qobuz Connect as time passes, and unnecessary code complexity.
Now, where Sonos reasonably COULD do something here is add support for the Google Cast Receiver API, as Chromecast is another common industry standard. This would allow casting from any app that natively supports it, and it would extend local network control to the Android community who can’t use Airplay today. That said, Google stole a bunch of IP from Sonos when it comes to multi-room audio control, so it’s unlikely we will see Sonos bend over backwards to support a Google product anytime soon.
Quite a few hardware manufacturers, large and small, have decided Qobuz Connect was worth implementing in their products. No small thing, really. https://www.qobuz.com/us-en/discover/apps-partners#audio-qobuz-connect
Not exactly a “random mom-and-pop streaming service that creates their own protocols?“
A very nice and grand speech, but what I see is simpler. Technology is one thing, but customer relationship are another. Sonos and Qobuz have collaborated for many years; is that relationship broken now? Furthermore, I see Qobuz Connect integrated into numerous systems, some more exotic than Sonos, and I see other streamers with a "connect" module integrated into Sonos, like Tidal or Spotify. All this leads me to believe that both sides are taking the customer for granted.
I'm still waiting for Qobuz Connect to be integrated into my Sonos system. When will it happen?
Since Qobux Connect connecting to Sonos must be implemented in the Qobuz app, I believe that is a question for Qobuz.
I have the same answer fron Qobuz : it’s a question to Sonos…..
It’s a perfect or a vicious circle
No, absolutly not.
Qobuz has released Qobuz Connect. It’s now on Sonos engineering to add support in their firmware, period. Qobuz has provided the necessary API. Sonos must implement the counterpart that uses it. Any other explanation from Sonos is a lie.
This isn’t how standards work at all. Do you reasonably expect every hardware manufacturer (who, by the way, gets paid only when the hardware is sold - not on an ongoing subscription basis like the streaming services are) to put ongoing development effort in supporting every random mom-and-pop streaming service that creates their own protocols?
Sonos maintains a shared connectivity protocol for any audio service to connect and play that service’s content from their own app. The protocol has been around a long time. Some services have chosen to adopt this. Newer Sonos speakers also support local network casting via Airplay 2 (a common standard), and they have a library with 133 streaming services who choose to make their media available within the Sonos ecosystem. That said, there are tradeoffs when using AirPlay over the native Sonos integration.
Qobuz can’t show up with their own proprietary Connect offering and expect every random hardware manufacturer to adopt it when service-neutral open standards like AirPlay and Chromecast already exist (tho more on Chromecast below). That would require firmware updates for hundreds of device models going back >10 years, ongoing developer support from Sonos as Qobuz inevitably makes changes to Qobuz Connect as time passes, and unnecessary code complexity.
Now, where Sonos reasonably COULD do something here is add support for the Google Cast Receiver API, as Chromecast is another common industry standard. This would allow casting from any app that natively supports it, and it would extend local network control to the Android community who can’t use Airplay today. That said, Google stole a bunch of IP from Sonos when it comes to multi-room audio control, so it’s unlikely we will see Sonos bend over backwards to support a Google product anytime soon.
- “Hardware makers only get paid once, so they shouldn’t have to support every random streaming service” Complete nonsense. High-end audio brands (Sonos included) sell €800–€2000 boxes precisely because buyers expect long-term software support and new features. That’s the entire value proposition. If Sonos stopped adding services tomorrow, their sales would collapse. They absolutely have the incentive—and the margin—to keep the platform alive.
- “Sonos has an open protocol anyone can use” The Sonos SMAPI was behind an NDA wall for years, cost money to access, and even after they “opened” it in 2020 it’s a pain in the ass. Almost nobody uses it except a couple of tiny services. Real-world proof: Tidal, Deezer, and Qobuz all tried and eventually ditched it for their own Connect solutions that actually work well.
- “Qobuz can’t just show up with a proprietary protocol and expect everyone to adopt it” That’s literally what every major service has done—and it worked everywhere except Sonos:
- Spotify Connect → proprietary → implemented by literally everyone, including Sonos
- Tidal Connect → proprietary → Bluesound, NAD, Cambridge Audio, WiiM, Eversolo, Naim, Devialet, Moon, etc.
- Qobuz Connect → proprietary → same list as above In 2025, Sonos is the only major hi-fi brand that still refuses Tidal Connect and Qobuz Connect. Everyone else moved on years ago.
- “AirPlay 2 is a common standard and supports high-resolution up to 24-bit/48 kHz” This is the biggest lie in the whole post. Yes, AirPlay 2 can theoretically carry 24/48 in some lab-condition edge cases (local files from the iOS Files app, etc.). In the real world, when you cast from Qobuz, Tidal, Apple Music, or basically any music app in 2025, AirPlay 2 downsamples everything to 16-bit/44.1 kHz. No bit-perfect hi-res, no reliable gapless, no 24/96 or higher. Qobuz and Tidal explicitly warn users about this in their own help pages. Even Apple Music—made by the same company that owns AirPlay—refuses to send anything above 16/44.1 over AirPlay 2. So no, AirPlay 2 is not a high-resolution solution. It’s a convenience feature for casual listening, and pretending otherwise is straight-up misinformation.
- “We can’t add Google Cast because Google stole our IP” Sonos already won that lawsuit in 2023 and cashed a massive check. They’ve had two full years since then and still no Cast support, while they happily added Bluetooth, Amazon Alexa, Sonos Voice Control, etc. The Google excuse is just a convenient shield. The truth is they don’t want Cast because it would make their walled garden far less sticky—any Android user could cast hi-res directly from the Qobuz or Tidal app and bypass the Sonos app entirely.
Bottom line: In 2025 Sonos is the most closed, least future-proof premium audio platform on the market. You are just regurgitating the official Sonos PR script (“it’s everyone else’s fault”, “AirPlay is fine”, “Google bad”) while the rest of the industry has moved on half a decade ago.
Moderator Note: Modified in accordance with the Community Code of Conduct.
“Qobuz Connect → proprietary → same list as above In 2025, Sonos is the only major hi-fi brand that still refuses Tidal Connect and Qobuz Connect. Everyone else moved on years ago. “
This is incorrect; Tidal Connect has been working perfectly for a long time.
This is incorrect; Tidal Connect has been working perfectly for a long time.
Sonos doesn’t support Tidal Connect.
Have a look at the list of supported devices on the Tidal website - Sonos is not listed under the Tidal Connect filter.
Tidal does offer “direct control” for Sonos (in the Android and iOS apps only), but this isn’t Tidal Connect.
And what is this?
How to use TIDAL Connect?
In the TIDAL app, open the Now Playing screen while playing a track
On the Now Playing screen, select the output device icon
Choose a speaker compatible with TIDAL Connect from the list.
And what is this?
How to use TIDAL Connect?
In the TIDAL app, open the Now Playing screen while playing a track
On the Now Playing screen, select the output device icon
Choose a speaker compatible with TIDAL Connect from the list.
As mentioned in my previous reply - that’s “direct control” for Sonos. Not Tidal Connect.
This is why it says “Sonos” and not “Tidal Connect” under each of the speaker names.
I don't understand the difference between Tidal Connect and Direct control.
For me, it's the same outcome. I select a piece of music and a broadcaster, and I listen directly from the Tidal app
“Sonos has an open protocol anyone can use” The Sonos SMAPI was behind an NDA wall for years, cost money to access, and even after they “opened” it in 2020 it’s a pain in the ass. Almost nobody uses it except a couple of tiny services. Real-world proof: Tidal, Deezer, and Qobuz all tried and eventually ditched it for their own Connect solutions that actually work well.
Where do you get this nonsense?
SMAPI has never cost a dime to access it. Why is it a pain in the ass, exactly? Did you ever see the Rhapsody music API?? That was the definition of a pain in the ass, and one of the reasons Sonos created SMAPI in the first place.
A HUNDRED AND THIRTY THREE services use it (see https://support.sonos.com/en-us/services), an order of magnitude more support than any other hardware streaming device.
Tidal, Deezer and Qobuz all use SMAPI, they haven’t “ditched it for their own”.
As mentioned in my previous reply - that’s “direct control” for Sonos. Not Tidal Connect.
This is why it says “Sonos” and not “Tidal Connect” under each of the speaker names.
Answer from Tidal :
The "Direct Control" feature on Sonos means you can start playback from a compatible service's app (like Tidal or Spotify) to your Sonos speakers without using the Sonos app. You'll see an icon or button for Sonos as the audio destination. "Tidal Connect" also allows you to stream music from the Tidal app to compatible devices, but it's a Tidal-specific technology that works with certain audio products now including Sonos. Both methods control playback through the Tidal app, but "Direct Control" is a more general term for services used, while "Tidal Connect" is specific to Tidal.
