Google Home Wont Play Music but Can Answer Questions: Fixes to Try
Quick Answer
The most common reason Google Home, Nest speakers/displays, or Google Assistant can answer questions but won’t play music is a broken authorization between your Google account and the music service (Spotify, YouTube Music, Pandora, etc.). Basic Assistant answers can still work because they don’t always require the same service login tokens that music playback does.
Start with these three checks:
1) Ask the device: What is my default music service. If it answers with a service you don’t use, or says none, the link is likely broken or changed.
2) In the Google Home app, open the device and check which account is currently controlling it. If the wrong Google account is active, music requests may fail while general questions still work.
3) Try a very specific request: Play some music on YouTube Music. If one service works but another fails, the problem is the authorization for the failing service, not the speaker.
This issue most often affects Google Home Mini, Nest Mini, Nest Audio, Nest Hub, Nest Hub Max, and Chromecast/Google TV playback when started by voice.
Why This Happens
The dominant root cause is authorization failure: the device can hear you, reach Google’s servers, and respond, but the music provider connection (the permission and login tokens that allow Google Assistant to control the service) is expired, revoked, out of date, or tied to a different account than the one currently speaking.
Closely related causes that fit the same pattern include:
1) The default music service changed, or was unset, after an app update or account change. Assistant answers still work, but music requests have nowhere valid to go.
2) The music service account was logged out on your phone, had its password changed, or requires a new consent prompt. The speaker cannot complete that prompt on its own.
3) Voice Match is identifying you as a different household member (or as a guest). Assistant can still answer general questions, but music tries to use the wrong person’s linked service.
4) Home structure or device assignment changed (moved to a new Home, removed and re-added, or duplicated homes). The device may be controlled by an account that can answer questions but does not have the music service linked.
5) An overlooked technical cause: the request reaches Google, but the handoff to the music provider is blocked by DNS filtering, a privacy feature, or a router security setting. This can selectively break music streams while leaving basic Assistant responses intact.
A real-world scenario: you changed your Spotify password or reinstalled Spotify on your phone. Google Home still answers What time is it, but Play my playlist fails because the Spotify permission token stored in Google Assistant is no longer valid.
A common user mistake: linking the music service while signed into a different Google account on the phone than the one used by the speaker’s Home. Everything looks linked on the phone, but the speaker is controlled by another account in the household.
Most Likely Causes in Real Homes
1) Music service link expired or revoked (most common after password changes, subscription changes, or app reinstalls).
2) Wrong default music service selected, or default service not set.
3) Voice Match mismatch: the device is not recognizing the correct person, so it uses the wrong service link.
4) Device is in the wrong Home or controlled by the wrong Google account (often after moving, changing phones, or adding family members).
5) Network filtering or DNS/security features blocking the music provider endpoints while leaving Google Assistant endpoints reachable.
Step-by-Step Fix
Confirm the symptom is authorization-related, not audio-related.
What to do: Ask: Set volume to 50 percent. Then ask: Play music. If it says it can’t play that right now, or asks you to link a service, that points to service authorization. If it plays a short chime and then stops, that can still be authorization or a stream handoff problem.
What the result means: Volume changes prove the speaker is responsive. A specific music failure message usually indicates a broken service link or default service issue.
If it fails: If volume commands do not work, fix basic device control first in the Google Home app (device offline, wrong Wi‑Fi, or mic muted). Then return to Step 2.
Check the default music service in the Google Home app.
What to do: Open Google Home app > Settings > Services > Music. Confirm your preferred service is selected as default for your account.
What the result means: If default is None, or a service you don’t use, Assistant may answer questions but won’t know where to play music from, or it will try a service that is not linked.
If it fails: If you cannot change the default, or the service shows as unlinked, continue to Step 3 to re-link.
Re-link the music service to refresh authorization.
What to do: In Google Home app > Settings > Services > Music, tap the service > Unlink account (if available), then Link account again. Complete the sign-in and permission prompts fully.
What the result means: A successful relink replaces expired tokens and reauthorizes Google Assistant to control playback.
If it fails: If linking loops, errors, or returns to the same screen, move to Step 4 to confirm you are using the correct Google account on the phone.
Verify you are editing the same Google account that controls the speaker.
What to do: In the Google Home app, tap your profile icon and note the active Google account. Then open the device in the Home app and confirm it appears under the correct Home. If you have multiple accounts, switch accounts and check Settings > Services > Music again.
What the result means: If the service is linked under one account but the speaker belongs to a Home controlled by another account, music requests can fail while general questions still work.
If it fails: If you find the speaker is in the wrong Home, fix Home membership in Step 5.
Check Home structure and membership for conflicts.
What to do: Google Home app > Settings > Household. Confirm the people listed are correct, and that the device appears in the intended Home and room. Remove duplicate homes you no longer use, or move the device to the correct Home.
What the result means: Music service links are tied to accounts and can behave differently across Homes. A device in an old Home can answer questions but fail on personalized media.
If it fails: If you cannot move the device cleanly, remove the device from the Home app and add it back after Step 8 (reboot order) to avoid stale configuration.
Run a Voice Match test to confirm the device is using the right person’s service link.
What to do: Ask: Who am I. If it answers with the wrong person, open Google Home app > Settings > Google Assistant > Voice Match. Retrain voice model for the correct account and ensure Voice Match is enabled for that device.
What the result means: If Voice Match is wrong, the device may attempt to use another household member’s music service authorization or a guest mode path that cannot access your linked service.
If it fails: If Who am I keeps returning the wrong person, temporarily disable Voice Match for other accounts on that device and retest music. If music starts working, re-enable accounts one at a time.
Try a targeted command that bypasses the default service.
What to do: Say: Play jazz on YouTube Music (or another specific provider). Then try: Play jazz on Spotify.
What the result means: If one provider works and the other fails, your device and network are generally fine; the failing provider’s authorization is the issue.
If it fails: If all providers fail, continue to Step 8 to clear local state and refresh network paths.
Check language and region settings that can break service handoff.
What to do: Google Home app > Settings > Google Assistant > Languages. Ensure the same primary language is set across household members who use the device. Also confirm your music service account region matches where you are using it.
What the result means: Some services and subscription features are region-limited. Assistant answers are global, but music playback may fail if the service account is set to a different region or the Assistant language combination is unsupported by the provider integration.
If it fails: If changing language causes confusion for other users, revert and focus on Step 9 (hotspot test) to separate authorization from network filtering.
Use a proper reboot order to clear stale sessions without guessing.
What to do: Unplug the speaker/display for 30 seconds. If you use a modem and router, power off modem first, then router, wait 60 seconds, power on modem, wait until it is fully online, then power on router, then plug in the Google device last.
What the result means: This forces fresh IP/DNS sessions and can clear a stuck connection to the music provider while leaving your account settings intact.
If it fails: If music still fails but questions work, the issue is likely still authorization or service-side. Continue to Step 9.
Run a hotspot test to separate account authorization from home network filtering.
What to do: Create a temporary hotspot on your phone. Connect the Google device to the hotspot Wi‑Fi (you may need to set it up again in the Home app to change Wi‑Fi). Then ask it to play music.
What the result means: If music works on the hotspot, your home network is blocking or interfering with the music provider handoff (DNS filter, router security, or IPv6/DNS issues). If it still fails on hotspot, authorization/account configuration is the likely cause.
If it fails: If hotspot works, proceed to Step 10. If hotspot does not work, skip to Step 11.
If hotspot works: inspect router settings that selectively block streaming services.
What to do: Check your router app for features like parental controls, content filtering, DNS filtering, or security scanning. Also check if the device is being placed into a restricted profile. If your router has band steering, temporarily split 2.4 GHz and 5 GHz into separate names and connect the speaker to the more stable band in your home (often 2.4 GHz for distance).
What the result means: Music services rely on multiple domains and CDNs. Filters can block those while still allowing Google’s basic Assistant endpoints. Band steering can also cause brief disconnects that interrupt the stream handoff.
If it fails: If you cannot find the setting, a quick check is to change DNS on the router back to your ISP defaults temporarily and retest. Then re-enable features one at a time to identify the blocker.
If hotspot does not work: refresh Google Assistant’s cloud-side permissions.
What to do: On the phone using the same Google account as the Home, open the music service app and confirm you are logged in and can play audio there. Then return to Google Home app and re-link the service again. If the service supports it, sign out of the service app, sign back in, then re-link in Google Home.
What the result means: If the service app itself is not playing, the issue is with the service account/subscription. If the service app plays but Google Home still cannot, the Google-to-service authorization is still not completing correctly.
If it fails: Continue to Step 12 to check device authorization conflicts and stale devices.
Remove stale device authorizations and duplicates.
What to do: In the music service account settings (inside Spotify/YouTube Music/Pandora, etc.), look for a list of connected devices or authorized apps. Remove old Google speakers, old Chromecasts, and any unknown entries. Then try again from the Google device.
What the result means: Some services limit device authorizations or get confused by duplicates with similar names, causing playback to fail or start on the wrong target.
If it fails: Rename your Google device in the Home app to a unique name (for example, Kitchen Speaker 2) and retry the command.
Advanced Troubleshooting
Only use this section if the basic fixes above did not restore music playback.
Account or cloud issue: If multiple devices fail the same way across different networks, your Google account may have a stuck permission state. In Google Home app, remove the music service link, wait a few minutes, then link again. Also confirm the Google account has a valid payment method if the service requires it, and that the subscription is active. If the service recently changed plan tiers, re-accept any updated terms in the service app.
Network issue (when hotspot test points to home Wi‑Fi): Check the router client list and confirm the speaker has a stable connection (not rapidly disconnecting). If your router shows the device bouncing between nodes in a mesh system, pin it to the nearest node if your mesh allows it, or relocate the speaker slightly to improve signal stability. If you use custom DNS, disable it temporarily. If IPv6 can be toggled, test with IPv6 off and then on; some networks handle streaming endpoints better with one mode than the other.
Firmware/software cause: A pending firmware update on the speaker or a stuck Google Home app state can block service handoff. Leave the speaker powered on and connected for at least 30 minutes to allow updates. Update the Google Home app on your phone. If you use multiple phones/tablets, make changes from one device at a time to avoid conflicting saves.
Configuration conflict: If you have multiple Google Homes with the same name, or speaker groups with overlapping devices, try playing to a single device first (not a group). Group playback requires additional coordination and can fail even when single-device playback works, especially when authorization is borderline or the network is filtering multicast traffic.
When to Reset or Replace
Soft restart is appropriate when: the device is responsive, appears online in the Google Home app, and only music playback fails. Use the power unplug method and the modem-to-router-to-device reboot order described earlier to clear sessions.
Factory reset is appropriate when: the device is assigned to the wrong Home and cannot be moved cleanly, it repeatedly shows as linked but will not complete authorization, or it behaves differently than other speakers on the same account after you have re-linked services and confirmed Voice Match.
What a factory reset removes: Wi‑Fi settings, Home assignment, room name, speaker groups, and device-specific preferences. It does not delete your Google account, but you will need to add the device again and reapply settings.
Hardware safety warning: Do not open the device, pry the screen, or attempt internal repairs. Use only the official reset method (button sequence or reset option for your model) and normal power cycling.
Replace only after: you confirm the same account and service can play music on another Google/Nest device on the same network, but this specific unit consistently fails even after a factory reset and re-setup. That pattern suggests a device-specific fault, though it is less common than authorization problems.
How to Prevent This
Keep account links stable: When you change a music service password or switch plans, expect to re-link the service in the Google Home app. Do it once from the primary household account to avoid duplicates.
Use clear household ownership: Decide which Google account is the Home owner and link music services there first. Add family members afterward. This reduces cases where a speaker answers questions but cannot access the right media permissions.
Maintain Voice Match hygiene: If multiple people use the same speaker, keep Voice Match trained and avoid having the same person signed into multiple Google accounts on the same phone when making Home changes.
Network habits that help authorization handoff: Avoid aggressive DNS filtering or security features unless you know how to allow the music provider domains. If you use a mesh system, place nodes so the speaker has a stable connection and does not roam constantly. Stability matters more for continuous streaming than for short Assistant replies.
Routine service management: If you rename devices, rename them uniquely. If you remove a speaker from your home, also remove it from the music service’s connected devices list to prevent stale targets.
FAQ
Why can Google Home answer questions but not play music?
Questions and smart home commands can work with basic Google connectivity, while music playback requires a separate authorization link to a specific provider. If that link is expired, revoked, or tied to a different Google account than the one controlling the speaker, music fails even though Assistant responses still work.
Is this always a Wi‑Fi problem?
No. A common misconception is that any playback issue must be Wi‑Fi. If the device reliably answers questions, Wi‑Fi is often good enough for basic Assistant traffic. The more likely issue is the music service authorization or default service selection. Use the hotspot test to prove whether your home network is involved.
Why does it say to link a music service even though I already did?
This usually means the service was linked under a different Google account than the one currently active in the Google Home app, or the permission token expired after a password/subscription change. Unlinking and re-linking from the correct account typically resolves it.
Why does music work for one person but not another in the same house?
That points to Voice Match or account-specific linking. The device may recognize one person correctly and use their linked service, but treat another person as a guest or misidentify them, causing it to use the wrong (or unlinked) service path.
Why does it work on a phone but not on the speaker?
Your phone can play directly from the music app using its own login. The speaker relies on Google Assistant being authorized to control the provider on your behalf. If the Google-to-provider authorization is broken, the phone still plays fine while the speaker fails until you re-link the service in the Google Home app.
There’s a kind of calm that comes after the noise clears—like exhaling and realizing you don’t actually have to keep bracing. The fix isn’t hidden anymore, and the story doesn’t need to keep re-litigating the same ground.
What’s left feels smaller, almost ordinary, which is probably the point. The world keeps moving, and you get to move with it, minus the extra drag.
