Sirius Radio: "Stream stopped, you are no longer authorized to listen."

[Ron Olsen]

I am running SBS 7.5.4 on a VortexBox Appliance (Fedora 14 OS), playing SiriusXM Internet Radio through a Duet Receiver (firmware version 68).

With earlier versions of SBS, I would get the "Stream stopped, you are no longer authorized to listen" error a few times a day. Now, with SBS 7.5.4, it seems to happen quite a bit more often (every hour or so).

Hitting the Play button on the Duet Controller or in the SBS web interface resumes playback.

I filed bug #17157 to report this problem:
http://bugs.slimdevices.com/show_bug.cgi?id=17157

Please vote for this bug if you are having the same issue.

[cjfreitag]

I changed to the "Not so Sirius" plugin some weeks ago because I was having this problem, and it hasn't happened since.

[Ron Olsen]

I changed to the "Not so Sirius" plugin some weeks ago because I was having this problem, and it hasn't happened since.

I'm using that plugin now and it seems to fix the problem.

But Logitech still should fix the official plugin if that's possible.

[bwaldron]

I'm using that plugin now and it seems to fix the problem.

But Logitech still should fix the official plugin if that's possible.

Yes. Those of us who are using XM accounts no longer have our third-party plugin (which didn't have this problem), but cannot use the 3rd-party Sirius plugin.

[tebrown]

Since Logitech closed this bug as WONTFIX, I am hoping to get some more satisfaction out of this forum. I think it is irresponsible for Logitech to not even investigate this problem. If it was one user that had this issue, or was very infrequent, I wouldn't be so upset, but the primary reason I have 4 squeezeboxes in my house is to listen to a) Sirius and b) my personal music collection. If I can't do the former, then I am less inclined to buy another Squeezebox.

[Tony T]

Isn't this a SiriusXM issue? Shouldn't the complaints be made to SiriusXM:

http://www.siriusxm.com/faqs
20. "Why does the Player stop playing after 90 minutes?
Every 90 minutes we send a notice to your player to see if you're still listening. If you see this message, just click the button to continue listening. If you're not at the player and don't respond, the player will shut down within 5 minutes of the alert. We do this so we're not streaming to computers that have no listeners — and so that folks who are listening can enjoy optimum performance."

If SiriusXM sends a "return value" to the player telling it to stop playing, Logitech has to honor that request.

It's Sirius that is being irresponsible for requiring their users to "click a button" every 90 minutes.

[tebrown]

Except it doesn't happen every 90 minutes. I'd actually settle for that (for now ). I started playing Sirius this morning at 9:40 and got the "You are no longer authorized to listen." message at 9:44.

In addition, since the "not so sirius" plugin actually worked for longer than 90 when it was working, I think the problem is that Logitech is sending multiple requests using the same credentials to Sirius, forcing Sirius to generate the "you are no longer authorized to listen" message.

What bugs me the most is Logitech's unwillingness to even help investigate the issue.

[Tony T]

I agree with you that if it stops sooner that 90 minutes that Logitech should resolve this problem, but SiriusXM stopping the player every 90 minutes is not acceptable either (mine shuts-off every 90 minutes). What if our Cable Provider sent a message to the TV every 90 minutes saying "Please press any button or your Cable Box will shut off"?

Also Sirius' implementation is poor. This is an audio device, Sirius should send a 5 minute warning audibly.

[bwaldron]

Except it doesn't happen every 90 minutes.

It certainly doesn't. It can happen at any time when listening to the stream...and it is annoying.

[tebrown]

Ok.. so I had been listening to Sirius for about an hour and I got the "Stream Stopped" message. I hit play to restart, and 1 minute later it stopped again. I didn't do ANYTHING else to any of my other players during this time, so I am not sure how Logitech could think *I* am causing this failure by my actions.

How do we get this elevated at Logitech to someone who can do something about it?