Skip to main content
Question

Sonos Voice Control never registers follow up commands for me.

  • January 20, 2026
  • 2 replies
  • 39 views
TastyChimera
Forum|alt.badge.img

Since Sonos Voice Control was released, it has responded to 100% of my first command after saying “Hey Sonos”. (Unless of course I asked it something it couldn't do, that's on me, not it)  However, while it’s sitting there in “Follow up/Continued Conversation” mode? It never EVER registers my second command.

For example. Having music playing then saying “Hey Sonos, Switch to TV Input” CHIME and it does it. Then while the light is still on, I say something like “Volume Thirty Percent” or “Set Volume To Thirty Percent” and after I’m done the light goes out and nothing happens. EVER.

But if I say “Hey Sonos” for both commands? It has the audacity to tell me that I don’t need to say Hey Sonos each time……. 😒

This has been like this since it launched. Over 3 years now. I believe sonos voice assistant hasn't been updated since 1.1 (Will be three whole years in Feb)

 

Anyone Else?

2 replies

Corry P
Forum|alt.badge.img+19
  • Corry P
  • Sonos Staff
  • January 21, 2026

Hi ​@TastyChimera 

Welcome to the Sonos Community!

I am sorry to hear of this issue you are having with getting Sonos Voice Control to obey the follow-up commands you give it.

Please see our Control Sonos with Sonos Voice Control help page. On it, there is the following information:

Follow-up requests

With some voice requests, you can make additional requests for a few seconds afterwards without saying “Hey Sonos” again. For example, when asking Sonos to play the next track, you can continue skipping tracks by repeating “Next.” You can also keep increasing or decreasing the volume.

Example requests

  • Play some music. Louder.
  • Skip this track. Again. Volume up.
  • Fast forward. More.

From this - and especially the word “some” - it would seem that only certain commands will work in follow-up mode.

Does this explain your current experience, or are these the kind of commands you are already trying to give it?

Please remember that Sonos Voice Control runs locally on your speaker and not in the cloud with vast data centres at its disposal.

Incidentally, I removed the previous reply to your post as it was a spam post. I also removed your subsequent reply for the thread's legibility.

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
    TastyChimera
    Forum|alt.badge.img
    • TastyChimera
    • Author
    • Contributor I
    • January 23, 2026

    Sorry but the response was a little frustrating as I gave an exact example of the command I’m trying to send :-P

    And I feel it really shouldn’t be an issue of cloud vs local processing. As the commands I’m trying to send are one at a time, and they are all commands Sonos Voice Control is confirmed to be capable of. 

    More likely, it seems to be an arbitrary limitation of what commands can follow others.

    For example. If I can through Sonos voice Control do each of these Actions on their own

    • Switch Inputs
    • Change Volume
    • Start Music
    • Skip Tracks
    • Change Night Mode and Speech Enhancement Settings
    • etc

    There isn’t really a reason why those commands can’t be used one after the other. Other than a choice by the development team to create a list of acceptable follow-up commands instead of allowing all known commands to be executed whenever the device is listening. 

    My other gripe, is, if Sonos Voice Control locks itself into a control type for that “session”? Volume/Track Skipping/etc? <(The commands you can say “more” or “Next” to). Then why would it tell me not to say “Hey Sonos” twice? By your description I’d have to do this to get it to register a new command chain as only specific follow-up commands are allowed...

     

    It’s kind of an annoying limitation and one that doesn’t seem to need to exist.

    Terms & ConditionsCookie settingsAccessibility statement