We can stream SiriusXM on Google Home again
If you had SiriusXM stop working on your Google Home speaker, this is the good news: Google has pushed a fix. The company posted an update to its Nest Community confirming the issue is resolved, and users who were blocked from playing SiriusXM on Home speakers are reporting the service works again. We tried to reproduce the problem in a handful of typical setups and, in line with community reports, asking a speaker to play SiriusXM now often yields normal playback.
How the problem showed up
The failure did not affect the SiriusXM app itself. People could use SiriusXM on phones and other devices, but when they asked a Google Home speaker to play SiriusXM the reply was an unhelpful message that the content either wasn’t available or couldn’t be played. That pattern came up repeatedly in user reports across a Google Home subreddit thread started by one account that first called attention to the problem.
Affected users tried the usual troubleshooting steps: verifying subscriptions, unlinking and re-linking their SiriusXM account, and rebooting speakers. None of those steps restored playback while the bug persisted. Google acknowledged the issue privately to at least one user and said resolving it could take weeks while engineers investigated. The tone in community threads swung between frustration — people losing alarms and daily stations — and cautious optimism as incremental reports of restored playback started to appear.
What likely happened – and what we don’t know
We still do not have a technical root cause from Google. A theory raised by users proposed the problem only hit numbered satellite channels, while internet-only or app-only SiriusXM content continued to play. That theory fits some reports, but it is not confirmed by the company. The Nest Community post announcing the fix did not list a cause or the exact change that corrected playback.
That lack of detail is annoying but not unusual for service-side fixes. When the problem lives in backend integrations between two services there is often nothing for users to update locally. We want to see a fuller post-mortem, but for now the practical result is clear: Google rolled out a fix that restores SiriusXM playback on Home speakers. Based on how these integrations usually work, the change was probably a server-side configuration or an API routing correction rather than a client patch, but we would want Google to confirm that before treating it as settled.
What to try if you were affected
- Ask your Google Home speaker to play a SiriusXM station. Try a known-number channel and an internet-only channel if you use those.
- If playback still fails, unlink and re-link the SiriusXM account in the Google Home app and reboot the speaker.
- Check the SiriusXM app on your phone. If the app plays fine there, the issue is specific to the speaker path and a future server-side change may be required.
Those steps match what users already tried while the bug was active. Now that a fix is live, asking the speaker again is the first and simplest check. If your routines or alarms use SiriusXM, test them directly so we know they fire correctly rather than waiting for the next morning.
How widespread was this?
The volume of complaints in the subreddit thread and related discussion suggests the problem touched a large number of users. We do not have an internal metric or a formal outage report to quantify the scale. The pattern we saw was a sudden, service-specific failure that persisted for more than a few days for many households. Community sentiment moved from irritated to relieved as confirmations of restored playback accumulated, though a minority of users still report lingering failures.
Quick comparison – behavior during the bug versus now
| Item | Behavior during the bug | Status after Google’s fix |
|---|---|---|
| Playback on Google Home speakers | Failed to play SiriusXM channels; speaker returned an availability error | Restored for users who report success in the Nest Community |
| SiriusXM mobile app | Functioned normally | Continues to function normally |
| Numbered satellite channels – user theory | Possibly affected while some internet-only channels worked | Unconfirmed, but overall playback appears restored |
Why this matters
We rely on voice speakers for routine listening. When a service we use every day stops working without a clear reason it becomes a real disruption. This episode shows two things. First, integrations between voice assistants and third-party streaming services are fragile. Second, fixes can arrive quietly from the server side without a visible client update.
We want transparency from the companies involved. A short post explaining the cause and the fix would help us trust the integration longer term. Until we get that, the practical outcome is more important: SiriusXM playback works again on Home speakers for many users, and there are simple steps to retry the service if you were impacted.
What to watch next
- Check Google’s Nest Community for any follow-up notes from the team that announced this fix.
- Monitor community threads for reports about particular channels or content types still failing. If a pattern crops up, collect example channels and timestamps to share in troubleshooting threads.
- If you rely on SiriusXM for alarms, routines, or daily radio, test those automations now so you know they work before you count on them again.
Our verdict
We are relieved that this was fixed and that the SiriusXM app kept working while the speaker path was broken. We would like more technical transparency from Google about what failed and why. For now, we recommend trying SiriusXM on your Google Home speaker and re-linking your account if you still see trouble. Tell us what you find so we – and other readers – can spot any lingering edge cases together.