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.