SiriusXM channels not listing in latest Sonos App... sonos and sirius pointing fingers at each other...

That’s because SiriusXM’s app has almost nothing to do with the SiriusXM SMAPI implementation which interfaces with Sonos.  In my experience, SiriusXM support has no clue when it comes to these facts and just treats everything as if it were the SiriusXM app.

Since the problem manifests itself in the Sonos app, it is a Sonos problem to fix.   

I was going to suggest that was the case, but I decided not to since I really am not an ‘expert’ on this stuff. But it’s true -- when I set up SiriusXM as a service on Sonos, I’m asked to authorize my SiriusXM account. And to do that I have to log in to SiriusXM -- directly, not via the app. The app does not participate in the process. It’s after that login that whatever information interchange is required must be occurring. And failing, because apparently SiriusXM is passing information that doesn’t conform to SMAPI.

Ahhh, no it isn’t.  The agreement between Sonos and the service providers is that they and they alone have control over what is displayed.  Sonos by design doesn’t change anything the service gives to them, so they couldn’t change it if they wanted to without violating the terms of the agreement.  

Now let me ask . . . Given these facts (which are spelled out in the Sonos SMAPI development rules), why would one be insistent on blaming Sonos if Sonos actually isn’t to blame?  It makes no sense. 

Personally, if I had a problem viewing SiriusXM content on my Sonos, and I went to the Sonos site to complain and was told several times, along with indisputable proof, that SiriusXM is the only one who can fix it, would I accept that and go to SiriusXM to complain?  Or would I double-down on blaming Sonos in some foolish face-saving gesture?  I think most would choose the former, which is why choosing the latter is a fascinating exercise in sociological behavior.  

It’s quite obvious what has happened, because it has happened before.  SiriusXM made some changes in order to release their completely new version of the app.  These changes broke some stuff in the SiriusXM implementation of their SMAPI server, and SMAPI being a secondary concern to the main SiriusXM app, SiriusXM hasn’t gotten around to fixing it yet.

This used to happen every time SiriusXM made a change to their encryption, which was often done in the early days.  The app would work fine, and Sonos would be busted for days until enough people complained at SiriusXM to get it fixed.  I was on the phone with them each time back then, explaining what Sonos was, why it was broken, and what they had to do to get it fixed.  Support had no clue, Sonos wasn’t even on their radar.

If you are looking for foolishness, look in the mirror.

The Sonos app is failing to deliver content.  Specifically, it is greying out most channels, likely because it is failing some authorization step - channels that are not part of the subscription do the same.  

Now, at that point you could make the case that SXM is not providing the correct authorization info, BUT, the Alexa app when linked to Sonos has no problem not only authorizing the correct channels, but returning the correct error message when non-authorized content is attempted.  Therefore, the API works.

You couldn’t be more wrong if you were trying to be.  Sonos doesn’t use the SiriusXM API that Alexa uses, not even close.  Instead, Sonos has the music service code their own SMAPI interface that the service and the service alone is responsible for.  This allows Sonos to support over 120 music platforms, without having to code to 120 different APIs.  I highly suggest you read here, before you double down again on foolishness:

https://docs.sonos.com/docs/content-service-get-started

Also, we have a SMAPI developer in this very thread who will concur with my post, as he/she did on page one.  You aren’t going to win this one, friend. 

LOL that’s me! Yeah this is totally on Sirius to fix. I’d show you the faulty XML they are delivering if I still had my working Sirius sub.

I wasn’t aware of the early history of their SMAPI service, but it makes total sense.

That’s for all the info. So basically if I’m bored, I should call SXM, tell them my issue and explain what Sonos is with a threat to cancel. Then nothing will happen but better than going to Sonos it appears. 

I texted SXM support and they escalated/promised me a callback.  That did happen and much to my surprise they all knew what Sonos was.  Second tier support stated as many have mentioned here--known issue, stay tuned.   So no news, but at least consistency.  We’ll see if they can get it fixed before everyone leaves SXM which is happening per their earnings call this week.