Was scouring the internet for the particular error that I'm getting, but haven't found a single case that is recent or relevant.
The problem is that I can't cast SiriusXM via mobile app or desktop browser to any of my Chromecast devices. This includes speaker groups and Chromecast Audio devices.
Any time that I try from Chrome (have tried Edge as well), I select the cast button, then I select a device, I hear the device "connect" (it plays that little tune) and then I receive this error:
Chrome Version 100.0.4896.75 (Official Build) (64-bit
If I try to cast from my phone, I get the same "Oops, something went wrong" message, but I don't see the error 1001 on it. It appears to be the same error though.
Oddly enough, I can stream just fine from other sources, like music.youtube.com or whatever. I have disabled ad-blockers, pihole and anything else that might be causing this to no avail. Mind you, I've been casting SiriusXM for years, but it just simply stopped working a couple weeks ago.
Anyone else have this problem?
I do seem to be able to cast my entire screen from a desktop computer to a Chromecast device and SiriusXM will play through the TV, but that isn't where I want to listen to music.
On a side note, I have called SiriusXM support and they were unable to resolve. We removed the app on my phone, removed the streaming source from Google Home and re-added it, logged out of my account, logged back in, etc. I knew these troubleshooting steps wouldn't help, since it wasn't working via desktop browser either, but we tried.
I have posted on Reddit as well just a little while ago, but figured I should post it here instead.
Answered! Go to the Recommended Answer.
Thanks for bringing this up and for being a step ahead of us. Please reboot your Chromecast Audio and casting devices. Also, make sure the OS version of your mobile phone and computer is updated. If the same issue persists, please perform a factory reset on your device and try again.
Keep me posted.
I'm sorry, but I'm not sure how those troubleshooting steps will assist me. It's occurring with all of my available cast devices as well as the speaker groups, including a smart speaker made by Insignia. Casting from my desktop browser (edge and chrome) are affected as well as my Pixel 5, however ONLY from the SiriusXM app or website. As stated previously, other sources are able to cast just fine, such as music.youtube.com.
I will try to factory reset on one of them, but I don't think it's going to help.
Hey there scythe944,
I apologize about the late response on this thread, are you still running into this error? After checking out the YouTube video you posted with the issue, it does look like it is a SiriusXM error. You may need to get a hold of SiriusXM support to see if they are aware of any issues going on with their service.
I'm sorry we couldn't be more helpful here, but if you had any other questions or concerns, please let us know!
Hi Jeran, yes, the issue is still occurring. I opened up a case with Google support and they had me do additional troubleshooting but ultimately haven't found the exact cause yet (Case ID [2-4966000032521]).
I did reach out to SirusXM support and they weren't aware of any issues and were blaming the problem on Google Cast, since streaming on all of my devices (car radio, web browser, Yamaha Receiver, Google Nest devices, etc all work fine.) but casting doesn't work.
Google support asked me to submit feedback within the Google Home app about a week ago and I haven't heard anything back since.
At this point, I'm clueless as to what the issue is and so is Google support, and SiriusXM doesn't want to own up to it being their problem.
Hey there scythe944,
That's good to hear that Google opened a case and is working with you. Google Support would have access to more tools than we would here on the Chromecast Community Forum. I would encourage you to keep working with them.
I'm sorry I couldn't have been more help, but if you had any other questions or concerns, please let me know.
Appreciate you trying, Jeran. Hopefully we can figure out the actual cause at some point. Not the end of the world, but it is a wonderful convenience to be able to cast SiriusXM to my speaker groups and play music to multiple parts of my home and outside when I want to. I can still cast other sources, but it's nice having a DJ so I can focus on other things 🙂
By any chance, do you use any Ubiquiti hardware for your network? Have any Unifi Access points? I was under the assumption that I was the only one having this problem, but now that there may be another, I'm trying to figure out a pattern.
Okay, thanks! You may want to contact google support directly and open a ticket with them (click on the Chromecast Help Center link on the bottom of this page, the click on "Contact Us" or just go to: https://support.google.com/chromecast/gethelp) and see if you can get a ticket created. I guess you could reference my ticket# Case ID [2-4966000032521] and see if we can get them to look into why there's more than one person having this issue now.
I have the exact issue on Ubiquiti hardware. So glad I found your post. I have been battling this for a while. Not the biggest of deals, but I love listening to sirius and the casting inability really stinks when you buy better hardware.
I just posted to UI on the early access forum. Maybe you could go post your findings as well?
Hey there scythe944,
I looked at the case notes, and it looks like you are able to ask your Assistant to play from SiriusXM to your speakers. You've confirmed that the Google Home app is connected to SiriusXM, but the error code still occurs when you try to cast from Google Chrome. I also see you've already submitted feedback on this, so the engineering team should be looking into this, but I'll leave this thread open for a while longer and see if I can find out anything about this issue.
I appreciate your patience on this, if you had any more questions, feel free to let me know.
I have experienced the same problem with trying to cast the Sirius XM app to the Chromecast device plugged into my Samsung smart tv. The solution turned out to be simple -- use the Google Home app to initialize the connection with Chromecast.
I am casting from a Google Pixel 5 running Android 12 (May 5, 2022 update). Like other casting apps, Sirius XM recognizes the Chromecast and offers it for casting, but attempting connect typically results in a long wait that never ends when trying to connect.
The solution that worked for me? Open the Google Home app and cast your screen. Once that is done, go back to the Sirius XM app and choose the Chromecast for casting. Google Home will gracefully disconnect and let Sirius XM take control. You can now just close the Google Home app.
BTW - forget about trying just to cast the audio from Google Home. It "works", but the quality is unacceptably low. Directly casting from Sirius XM is actually optimized for audio quality, and the quality is waaaay better.
I'm pretty sure this is not a Google problem. The developers at Sirius XM clearly missed a step that other Android app developers did not in establishing the Chromecast connection in the first place.
Hope this helps! Back to rockin' out to Sirius XM...
Thanks @TXChromecastV1 , however I already figured that out and am able to cast when sharing my screen. The problem is that I have a high quality stereo with a Chromecast audio that I'd like to cast to, and have been able to cast SiriusXM for many years, only stopped working a couple months ago. Additionally, I have speaker groups and 3 stereos around my house that I'd like to stream to at the same time, you can't cast your screen to a speaker group. Thanks anyway though!
I recently started getting the same issue trying to cast Sirius to a Nest speaker. Finally tried to a Nest Hub, and got the same error as above. CC-101, transfer-failed.
The workaround (casting Google Home to the speaker (audio mirroring) and then sirius did not work. Same error.
Called Sirius, and spent 15 minutes being told I need to contact Chromecast support, before they finally allowed they would endorse a case (their words) on their end for this. Was promised a callback tomorrow. We'll see what happens.
Just reporting that I have received the exact same error for years neither Sirrus nor Google will help/acknowledge. I actually think nobody can cast Sirrus to a Google cast device and most just give up. Clearly a implementation issue on Sirrus side since all other apps work fine but they won't address it.
I have this same issue - can't cast with Sirius, but could with others like Youtube, etc. I signed out of my sirius account on the web, then opened an incognito window and was able to cast! So, I went back to a normal browsing tab(on Chrome), cleared the cache, and can now cast. It seems as though whatever SiriusXM is putting into cache is screwing things up, but at least clearing it will fix it.
As for how to fix it on mobile, I am not sure, and don't have time to test right now, but perhaps signing out, clearing cache and trying again would work as well?
glad it worked for you, incognito mode didn't help me either. Even if I try to cast with Edge which I don't use hardly ever, it didn't work in that browser either. I was able to setup a separate router (Access point) and connect my chromecast and phone to that same SSID and that worked, so it seems to be something with certain networking gear, particularly Unifi (Ubiquiti stuff).
Due to the flurry of activity lately, I decided to take a fresh look at things... and I will say, I just made a bit of progress. Can you post what your topology is with your Unifi equipment?
I am currently using a UDM SE, then USW-Aggregation, and then on to other switches. All of my access points are connected to the next switch downstream, a USW 48 port POE Pro.
Today, I decided to move 1 access point to the POE port on the UDM Pro, and eliminate all other equipment on the network. I created a new AP Group with just the 1 access point, and setup a separate WiFi network there. I moved a Home Mini onto that network, along with my phone. I assigned my default LAN to that network. Guess what? Sirius casting worked for the very first time ever!
Unfortunately, moving back to the other AP groups returns to non-functioning, and more importantly, moving to a VLAN, even on the UDM, does NOT allow it to cast. I opened up all firewall rules for that network, and even setup a brand new VLAN, but still does not work.
So for the moment, the trail ends there for me today. Hopefully you can validate my findings on your network, and let me know. I have not received any replies on the UI forum, and no reply to my ticket, either. I will update that post later tonight, as well.
My Unifi topology appears to be much simpler than yours:
Modem > USG 3P gateway > USW-16-PoE switch > then there's 3 AP's, a U6-Lite, UAP-AC-M and a UAP-AC-LR.
I have 4 wireless SSID's, each with their own VLAN ID.
There used to be an article on how to setup the Multicast DNS settings and such to make an IoT network for Chromecasts and that's what I followed originally, but I can't seem to find it anymore.
Ok, I also have a Unifi network. But similar to scythe944, I have a home VLAN and the cast devices are on an IoT VLAN that cannot route to the home VLAN (except mDNS and a few other specific ports/IPs)
I don't have time to test right now, but will see if I can do some testing later. I already have 4 SSIDs, so can't create a new one, but I can see if I can simplify something. I did try connecting my phone to the IoT and casting "locally" there, but that did not work.
(And since we're looking at local network items, everything is also behind a pihole)
I have tried those workarounds so far on my UDM, but none have worked yet. If you have a moment where you can spare a few minutes of downtime, maybe try one Access Point with a new network on your default lan, with just phone/pc and a cast device. I did it eliminating switches, but perhaps trying it with your switch will be another good test (but that never worked for me, previously).
This is good news, for sure... I will keep poking around! Thanks for letting me know.
I'll jump in here too - I've had this problem for almost 2 years. All started when I upgraded to an all Unifi network. UDMP -> US24poe and several Unifi WAPs. Like the rest of you the problem casting is ONLY with Sirius - everything else works fine. I've tried so many combinations over this timeframe that I can not remember them anymore. I am fairly certain that the problem is Unifi's in some way that they are handling rules on the UDMP or in the switching, but have not been able to nail it down with Wireshark - yet. I do know for sure that when I was using other gateway/switch (non-unifi) with Unifi WAPs, it worked perfectly.
I also did an all wired test - where I used the ethernet adapter for my chromecast Audio, and an ethernet attached laptop. That too failed - ruling out an issue with the WAPs.
I'm sorry for the late response, but we appreciate the information that you've shared in this thread. I already passed this along to our team and they are currently working on it. If you haven't tried sending feedback about this, they'd suggest you send feedback using the Google Home app so they can get some logs about this issue. When sending feedback, please use this tagging "CCT3 SiriusXM Chromecast error".
jamurphy, thanks for keeping us in the loop and glad to hear that this has been sorted out on your end. Feel free to reach back should you need help in the future.