The short answer
Most of this comes down to three things: device names that sound alike, wrong room assignments, and several speakers hearing you equally well. Rename devices to short distinct words, assign every device to the correct room, and reduce microphone sensitivity on the speaker that keeps winning when it should not.
Voice assistants decide which speaker responds by comparing how loudly each heard the wake word. In an open-plan space, or through a doorway, that comparison is close enough to go wrong regularly. Separately, a command such as turn on the lights depends entirely on which room the assistant thinks you are in.
Fix 1: rooms
Every device needs to be assigned to a room, and the assignment needs to be accurate. Two things commonly go wrong:
- Devices added quickly during setup default to no room or to the wrong one.
- Devices moved physically are rarely reassigned in the app.
Open the app, go through every device, and check the room. This is tedious once and it resolves most cases of the wrong lights responding to a room-relative command.
Also check that speakers themselves are assigned correctly, because that is what makes turn on the lights mean the lights in the room the speaker is in.
Fix 2: names
Use short, distinct names
One or two syllables that do not sound like each other. Kitchen and Chicken is a real and common problem.
Avoid names that echo common words
A device called Light inside a room called Lights confuses the parser. So does anything containing the assistant’s wake word.
Do not describe, name
Left Bedside Lamp is harder to say and harder to recognise than Nightstand.
Rename anything you stumble over
If you find yourself repeating a command, the name is wrong. Renaming takes ten seconds.
Check for duplicates across integrations
A device connected through two different integrations appears twice, and the assistant may act on whichever it finds first. Remove the duplicate.
Fix 3: which speaker answers
- Reduce microphone sensitivity on the speaker that keeps answering from the next room, where that setting exists.
- Move speakers apart and away from the doorway between two rooms, which is the worst position because both rooms hear it.
- Turn off the microphone on a speaker you only use for music in a room where another speaker handles voice.
- Check for a preferred speaker setting in the app, which some platforms offer per room or per user.
- Move a speaker away from a hard wall or corner, which amplifies and reflects your voice and makes it seem closer than it is.
Speakers near a television are a special case, because they both hear television dialogue and compete with it. Moving a speaker a metre away from the television, or to the other side of the room, reduces both false triggers and wrong-speaker responses noticeably.
Fix 4: groups and routines
Groups let a single command control several devices, and a badly configured group is a common cause of unexpected behaviour. Check that:
- Each group contains what you think it contains, since devices get added to groups and forgotten.
- A group name does not clash with a device name or a room name.
- Routines do not use trigger phrases that shadow ordinary commands. A routine triggered by good night will intercept every use of that phrase.
- Nested groups are not creating loops or ambiguity.
Fix 5: voice recognition
Both major platforms can recognise different people and give personalised results. When that recognition degrades, you get generic answers, refused personal requests, or the wrong person’s calendar. Retrain voice recognition for each household member, and add anyone who has joined the household since setup.
This also affects which speaker responds on some platforms, because the assistant uses voice profiles as part of the decision.
Fix 6: the awkward one, accents and phrasing
Assistants are trained on particular language variants, and setting the wrong region or language causes persistent recognition problems. Check the language setting matches how you actually speak, including the regional variant. Where a household mixes languages, both platforms support multiple languages simultaneously, which works better than switching back and forth.
Phrasing helps too. Assistants parse a device or room name followed by an action more reliably than a long descriptive sentence. Turn the kitchen light on works better than could you please switch on that light in the kitchen for me.
Before rebuilding your configuration, check whether the platform is having an outage. Commands that suddenly stop working across every device, or that produce error responses rather than wrong actions, are usually a service problem rather than something you configured.
Why does a speaker in another room answer me?
Because it heard the wake word more loudly than the nearer one, which happens through doorways and in open-plan spaces. Reducing its microphone sensitivity or moving it away from the doorway usually fixes it.
How do I stop the TV triggering my speaker?
Move the speaker away from the television, reduce microphone sensitivity, and consider changing the wake word if one particular programme keeps setting it off.
Why does turn on the lights affect the wrong room?
The speaker you spoke to is assigned to the wrong room, or the lights are. Room assignment is what makes room-relative commands work, and it is the first thing to check.
Can I have different wake words on different speakers?
On some platforms, yes, and it is a practical solution in a house where two rooms are acoustically connected. Check what your platform supports.
Should I rename my devices?
If you ever have to repeat yourself, yes. Short, distinct, one or two syllable names are recognised far more reliably than descriptive phrases.
The short version
Audit every device’s room assignment, then rename anything you stumble over to something short and distinct. Reduce microphone sensitivity on the speaker that keeps answering across a doorway, and move speakers away from walls, corners and televisions. Check groups and routine trigger phrases for clashes, and retrain voice recognition for everyone in the house.
