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. 

Qobuz has encouraged Sonos users to contact Sonos to advocate for Qobuz Connect integration. They explicitly suggested that Sonos users reach out to Sonos to push for collaboration on developing Qobuz Connect for Sonos devices.

Great. Unfortunately, this is a Sonos public community, and not a connection to directly pass on your comments to Sonos directly. You need to call Sonos Support directly.

And frankly, Sonos has already written the API, and provides that to anyone who wants to use it. What Sonos doesn’t have is access to Qobuz’s code base to do the integration. I suspect your contact at Qobuz doesn’t quite understand how this works. 

Connect is a built in solution. Other manufacturers have published firmware update. Sonos did it for Spotify Connect.

The qobuz app is only a remote controller. You can switch off your phone and keep listening Qobuz.

Qobuz created an SDK. It is up to Sonos to add it to the firmware of its products. Taking in account that we can’t Chromecast to Sonos, and that DLNA is not working that well, I would say that this would be a no-brainer, if technically possible on the devices.

Much smaller manufactures could do it. Sonos for sure also has the resources to do it and for sure there is a lot of overlapping between Qobuz and Sonos userbase.

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. 

I will not discuss political policies of each platform. Both have SDKs and maybe incompatible policies. What I know is Sonos provides “Spotify Connect” and we are talking about something equivalent (from a smaller player). I also know there is already a huge list of providers with this integration with Qobuz working from day one.

https://help.qobuz.com/en/articles/314578-list-of-brands-integrated-into-qobuz-connect

As a costumer (3 sonos devices at home), and particularly because of the lack of Chromecast support, to me this would be a valuable feature, as Sonos support in Android has a lot to desire, particularly since the app changes we all know about.

The last device I bought, wasn’t Sonos because of this lack of integration with Android (and open source, as DLNA also is not working properly from my experience). So, up to them to decide if Qobuz costumers are valuable enough or not for the investment. But to me, it seems Sonos is falling behind in many aspects. An app is not good enough for me. Neither is integration with Apple ecosystem (which works alright, but my home is not only Apple ecosystem).

Technically, Spotify Connect integrated with Sonos, Sonos didn’t integrate with Spotify Connect. It’s ultimately a question of who does the effort, and where it is done. Sonos has written the code already, there are a few folks who have integrated it into their own systems (Spotify and Apple being great examples), but Sonos engineers don’t have any access to other people’s code bases to do the integration. 

It’s up to Qobuz as to whether they want to integrate the already existing Sonos efforts into the Qobuz code base. 

And I certainly agree, there are features in ‘native apps’ which are nice, and would be lovely to have access to when controlling Sonos. Which ends up being the reason I sometimes use AirPlay 2 or Bluetooth to communicate with appropriately enabled speakers in my Sonos system. 

Are you positive about this? The ‘foo Connect’ linkage seems to be a good deal more intimate than the regular A.N.Other service integration offered by the Sonos partners API.

Hmm. To judge by the breadth and timeliness of the brand integration linked above I’d guess that a ‘Qobuz Connect’ module was issued to the vendors in question.

AirPlay2 and Bluetooth are woeful alternatives. They’re both limited to AAC on Sonos, and require the participation of the mobile device in the stream path.

I confess I gave up waiting for Qobuz Connect and went with Roon, which IMHO is superior to all of the above. 

No, I don’t work for Sonos, so I’m not sure about any of it. It’s all based on my knowledge about how Sonos has operated in the past, and the way the Sonos system works currently. 

Not sure I agree with ‘woeful’, but I’ll agree that there are some challenges at times. But it works, if I want to use another application’s features with sound coming from my Sonos.

Qobuz need to read https://docs.sonos.com/docs/cloud-queue-play-audio and link their new Connect service to their existing SMAPI implementation. Sonos have nothing to do here.

Sonos Supporting QoBuz Connect would be great. WiiM support of Qobuz Connect works perfectly . As an owner of a pair of ERA300, that i love, please Sonos, give us Qobuz Connect support. Thanks.

Sonos can barely support their own software. Qobuz connect might be a bit much for Sonos.
 

Perhaps when the new CEO confessed the company didn’t understand how their products were being used by their customers they were more focused on hardware than software?

Given the broad support for Qobuz connect and Sonos’ omission, it might be an indication that Sonos is choosing a closed route like Apple rather than an open route like Android.

Send an e-mail to the Sonos CEO at ceo@sonos.com and request “Qobuz Connect”.

I too was really surprised that the number one home speaker system would not be available to use with Qobuz connect at launch. All the back and forth on this thread about who should contact who - we’re just making the point that it SHOULD be implemented or they are missing 70% of the home audio market. C’mon Qobuz and Sonos let’s get it implemented! 

Airgetlam’s argument is false.  Sonos could integrate with Quboz Connect if they wanted to, they have chosen not to. Just as they have chosen not to integrate with Chromecast, Tidal Connect, or Spotify Connect. 

On the other hand, Sonos HAS chosen to integrate with Airplay. This is a decision that Sonos has made, not Apple.  So there is precedent for Sonos breaking from their so-called principle of only allowing integrations through their own API.

Similarly, Qobuz has chosen not to integrate with Sonos.  Tidal has. If you look at the casting options in the Tidal app, you will notice there is a difference between the Sonos casting option and all other Tidal Connect options.  In this case Tidal chose to use the Sonos API and not wait for Sonos to integrate with Tidal’s own interface.

Saying that it is always the other guy’s fault is usually misleading. It always takes two to tango.  Qobuz has now provided an interface for Sonos, and Sonos has previoulsly had an itnerface for Qobuz.  To date, neither company has chosen to use the respective options.

​@bdander 

„Just as they have chosen not to integrate with Chromecast, Tidal Connect, or Spotify Connect.“

Sonos does support Spotify Connect. 
 

But aside from the technical integration I think such a direct control option can’t be a one man show. Also if Quobuz will have to manage the main part on technical side, imo Sonos would have to agree or at least support such an integration, because as far as I know it works a bit differently than the standard API integration. In case of Spotify sometimes you see that the  „Spotify cloud“ direct control option is down but standard API way still works. 
So I think though direct control might be based on API functionality in the end there are some other aspects that might need some help from Sonos to be done. 
Just my personal thoughts on how it works…

And just to underline what ​@ratty said…

Airplay and bluetooth work completely different and can’t be compared or called alternatives to a direct control feature, because there is not just control but also stream transfer. 
 

The only services I know that support direct control for Sonos are Spotify, Tidal and Amazon (but Amazon working somewhat differently via their Alexa cloud). 

Maybe Sonos is just prioritising - Qobuz is about 1,000 times smaller than Spotify, and about 4-500 times smaller than Apple Music, in subscriber numbers. Could that be it?

Imho that could be a reason, if there will be any effort or even costs for Sonos, but I can’t imagine that’s the case. 

My guess is that Sonos and Qobuz both want us to use their own apps. Qobuz has made itself available as a service in the Sonos app, probably because connect was far awaty and this increased the pool of potential users. With connect out, their reality has changed, but for Sonos, it’s still a smaller player.

For me, Sonos natively supporting Qobuz Connect would be a massive increase in value for both Sonos and Qobuz. ANd I feel Sonos, with their software woes of late, have more to lose than even a small player as Qobuz.

More and more ‘one stop shop’ streaming options get released every year, that can be used with external speakers, without having to place a full sized receiver somewhere. WiiM and the likes are a massive threat in my opinion.

As much as it’s great to point fingers at both/either Sonos and Qobuz for not making the first move here, the reality is that it’s embarrassing that as of 2025 there isn’t yet a modern open standard for _both/all_ parties to adopt/implement to connect streaming services & their control apps to hardware player endpoints (including hardware that isn’t Sonos, and streaming services that aren’t Qobuz), and that companies like Sonos and Qobuz (or Spotify) aren’t working to iterate and improve one. The announcement of Qobuz Connect shouldn’t be a big deal, but it unfortunately is because the whole playing field is a proprietary non-interoperable-by-default mess.

Sonos’s first party app is an embarrassment, and they’re not doing themselves any favors trying to keep people in it. IMO they should be focusing on hardware (which they mostly excel at, in their segment), updating their network stack from the early 2000s, and leaving software UX to people that clearly understand it much better.

The Sonos first-party desktop apps can’t detect their own hardware across a VLAN, although the mobile apps (and Spotify Connect) can. The whole thing is a bit of a janky mess on the Sonos side, which leads me to assume that their “Connect” API also leaves something to be desired and it is not open for third party pull requests to improve (I have not attempted to implement against it, so just basing this assumption on the rest of the network weirdness).

The tech world is a very different place from what it was in 2002 when Sonos started. However, they haven’t evolved and paid down technical debt left over from that era, and it’s showing.

Quelles sont les nouvelles sur le sujet ?

Spotify connect  et Tidal connect fonctionnent parfaitement !!!!

Qui de Qobuz ou Sonos  fait barrage à l’integration 

What's the latest news on this topic? Spotify Connect and Tidal Connect work perfectly!!!! Which of Qobuz or Sonos is blocking the integration?

SONOS supports both Spotify Connect and Tidal Connect. Qobuz Connect is basically identical (it probably uses mostly the same code).

Agreed, but the code needs to be changed on the Qobuz side.
 

Not sure I agree about it being the same code, I’ve worked with too many engineers who think they can do better (and often can). Most companies I’ve worked for were certainly unexcited in ‘sharing’ the code effort their staff had made.

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.