Sonos · microphone

Sonos Ray soundbar microphone sounds bad or is not detected

Sonos Ray soundbar microphone sounds bad or is not detected: selected input, app permission, boom position, Bluetooth call profile and hardware should be separated. Scoped to Ray, with the model boundary and safe stop points made explicit.

Direct answer

For the Sonos Ray soundbar, selected input, app permission, boom position, Bluetooth call profile and hardware should be separated. First, record locally and compare a call app.

What this covers

  • Sonos Ray soundbar (Ray)
  • Sonos product; Wi-Fi/Ethernet, Bluetooth, voice, home-theater and line-in capabilities vary.
  • The specific fault this record addresses: microphone sounds bad or is not detected

What it does not cover

  • ×The same symptom on a different Sonos product line, which has its own record and its own cited source
  • ×An on-screen error code whose meaning has not been checked against this exact model's manual
  • ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step

Differential

What actually causes this, and how to tell them apart

These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.

  1. 1

    The application is using a different microphone

    What separates it Callers report poor quality, with the phone's own microphone being used instead of the headset's.

    How to confirm Applications keep their own input selection independently of the system default.

  2. 2

    The microphone opening is blocked

    What separates it Muffled or quiet voice pickup, with visible debris in the small openings.

    How to confirm Clean carefully with a dry soft brush.

  3. 3

    Wind or background noise is overwhelming it

    What separates it Poor pickup outdoors or in a noisy environment.

    How to confirm Headset microphones are small and close to the body. Noise-reduction processing helps but has limits.

  4. 4

    The application does not have microphone permission

    What separates it No input at all in one application while others work.

    How to confirm Both phones and computers gate microphone access per application, and the prompt is easy to dismiss.

  5. 5

    The soundbar's far-field microphones are muted

    What separates it Voice control not responding, with a mute indicator lit.

    How to confirm Most voice-enabled speakers and soundbars have a physical microphone mute, which is easy to press by accident.

Before you touch a setting

Record this first — changing settings destroys the evidence

Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.

  • Which input device the application itself has selected, as opposed to the system default.
  • Whether the problem affects one application or all of them.
  • Whether the microphone openings are clear.
  • Whether a physical microphone mute is engaged.
Try in this order0 of 5 completed
  1. Select the headset explicitly as the input in the application

    Reversible

    Applications keep their own input selection separately from the system default.

  2. Check microphone permission for that specific application

    Reversible

    Access is gated per application and the prompt is easy to dismiss by accident.

  3. Clean the microphone openings with a dry soft brush

    Reversible

    They are small and collect debris, which muffles pickup.

  4. Check for a physical microphone mute on a speaker or soundbar

    Reversible

    Most voice-enabled devices have one and it is easy to press without noticing.

  5. Record a short test and listen back before troubleshooting further

    Reversible

    This turns second-hand reports of poor quality into something you can actually assess.

Model-specific

What is true of this model and not of its siblings

Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.

Model scope
Ray. Sonos product; Wi-Fi/Ethernet, Bluetooth, voice, home-theater and line-in capabilities vary.
Type — entry soundbar, OPTICAL only
The entry Sonos soundbar — crucially it connects to the TV by OPTICAL audio only, with NO HDMI/eARC and NO Dolby Atmos. So HDMI-ARC troubleshooting does not apply; you must use the TV's optical output and set the TV to output audio over optical.
WiFi-first for streaming
Controlled via the Sonos app over WiFi for streaming and grouping; a missing speaker is usually a network issue. TV sound comes via the optical cable.
TV remote setup
Because it uses optical (not HDMI-CEC), you set it to learn the TV remote's volume via IR during setup — if the TV remote does not change its volume, redo that remote-learning step.
Symptom boundary
This record covers Sonos Ray soundbar when it microphone sounds bad or is not detected. A different symptom on the same hardware, or this symptom on a different Sonos product line, has its own record with its own causes and its own cited source.

Evidence ledger

Sources behind this answer

Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.

Where the manufacturer's article stops. Sonos publishes this as "Sonos Voice Control requests not working". the Sonos article for a microphone that is muted, not detected, or not hearing requests. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and Ray is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.

Exact questions

Common follow-ups

How do I connect my Sonos Ray to my TV — it has no HDMI?+

The Ray uses OPTICAL audio, not HDMI — that is by design. Run an optical (TOSLINK) cable from the TV's optical-out to the Ray, and set the TV's audio output to the external/optical system (often disabling the TV speakers). Since it does not use HDMI-CEC, complete the remote-control setup in the Sonos app so the TV remote's volume buttons control the Ray over IR. There is no ARC to configure because the Ray has no HDMI.

People say I sound distant on calls.+

Check which microphone the application is actually using — applications keep their own input selection independently of the system default, and it is common for a call app to use the laptop or phone's built-in microphone while your headset handles playback. Selecting the headset explicitly as the input usually fixes it immediately.

Does this answer apply to every Sonos model?+

No. It is scoped to Ray. Sonos product; Wi-Fi/Ethernet, Bluetooth, voice, home-theater and line-in capabilities vary.

What should I record before troubleshooting microphone or calls?+

Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.

Why is a factory reset not the first step?+

A reset can erase accounts, networks, maps, schedules or preferences without distinguishing microphone, calls. The ordered checks preserve that evidence.

When should I stop and use qualified service?+

Protect private recordings and stop for liquid/physical damage.

Change recordSept. 1, 2026 — Built out with researched, cross-checked per-model specifications and model-specific guidance. Aug. 17, 2026 — Published with explicit Ray applicability, a microphone diagnostic boundary and first-party support provenance.
Report a correction
Wrong device or version?

Match the path before repeating the steps.

Match another device