Sonos · disconnecting

Sonos Beam (Gen 2) keeps disconnecting

Sonos Beam (Gen 2) keeps disconnecting: trigger, range, interference, competing hosts, battery and firmware should be recorded. Scoped to Beam Gen 2, with the model boundary and safe stop points made explicit.

Direct answer

For the Sonos Beam (Gen 2), trigger, range, interference, competing hosts, battery and firmware should be recorded. First, test charged devices nearby with other hosts' Bluetooth off.

What this covers

  • Sonos Beam (Gen 2) (Beam Gen 2)
  • Sonos product; Wi-Fi/Ethernet, Bluetooth, voice, home-theater and line-in capabilities vary.
  • The specific fault this record addresses: keeps disconnecting

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 body is between the source and the accessory

    What separates it Dropouts when the phone is in a back pocket, or when turning a particular way.

    How to confirm Bluetooth is heavily absorbed by water, and a body is mostly water. Moving the phone to a front pocket or the other side commonly resolves it entirely.

  2. 2

    2.4 GHz interference

    What separates it Dropouts in specific locations — near a router, a microwave in use, or a crowded office.

    How to confirm Bluetooth shares the band with Wi-Fi and microwave ovens. Interference is location-specific and moving a few metres often confirms it.

  3. 3

    The battery is low

    What separates it Dropouts increasing as the charge falls.

    How to confirm Low battery reduces transmit power and causes instability well before the device shuts down.

  4. 4

    The accessory is trying to switch between two paired devices

    What separates it Brief dropouts with a phone and a laptop both nearby and both paired.

    How to confirm Multipoint devices switch automatically and can oscillate. Disconnect one of the two while testing.

  5. 5

    Firmware needs updating

    What separates it Dropouts that began after an update, or a known issue in a specific release.

    How to confirm See app-update — connection stability is one of the most common subjects of audio firmware fixes.

  6. 6

    A Wi-Fi speaker is dropping off the network rather than off Bluetooth

    What separates it A mains speaker or soundbar disappearing from the app.

    How to confirm These are network devices, so this is a Wi-Fi problem: check signal strength at the speaker's position and whether its address has changed.

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.

  • Where the source device is carried when dropouts happen — a back pocket puts a body directly in the path.
  • Whether dropouts are location-specific, which points at interference.
  • The battery level when it happens.
  • Whether two devices are paired simultaneously.
Try in this order0 of 5 completed
  1. Move the phone to a front pocket or hold it in your hand

    Reversible

    Bluetooth is strongly absorbed by the body, and a phone in a back pocket puts a body directly in the radio path.

  2. Test in a different location

    Reversible

    Interference from Wi-Fi equipment and microwave ovens is location-specific and moving a few metres usually confirms it.

  3. Charge the accessory fully and retest

    Reversible

    Low battery reduces transmit power and destabilises the link well before the device stops working.

  4. Disconnect the second paired device while testing

    Reversible

    Multipoint devices can oscillate between two sources, producing brief repeated dropouts.

  5. Install any pending firmware update

    Reversible

    Connection stability is among the most commonly fixed issues in audio firmware.

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
Beam Gen 2. Sonos product; Wi-Fi/Ethernet, Bluetooth, voice, home-theater and line-in capabilities vary.
Type — compact soundbar (WiFi + HDMI eARC)
A compact soundbar with virtual Dolby Atmos (no up-firing drivers — it simulates height), connecting by HDMI eARC and WiFi. 'No TV sound' is the eARC/HDMI-CEC link; streaming/grouping is WiFi/app.
WiFi-first
Controlled via the Sonos app over WiFi; a missing speaker is usually a network issue.
Virtual Atmos
Its Atmos is virtualised through its drivers, so the height effect is subtler than the Arc's dedicated up-firing speakers — that is the design, not a fault.
Symptom boundary
This record covers Sonos Beam (Gen 2) when it keeps disconnecting. 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 "Products missing from the Sonos app". a Sonos product that keeps dropping off shows up as missing from the app; this is that path. Probed 2026-08-21: title-verified. What that article does not carry is the model boundary — it is written for a product line, and Beam Gen 2 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

My Sonos Beam Atmos doesn't sound as 'tall' as expected.+

The Beam creates Dolby Atmos virtually — it has no dedicated up-firing height drivers like the Arc, so it simulates the height effect through processing. The overhead sense is therefore subtler by design, not a fault. Make sure the TV is passing Atmos (Dolby Atmos should show in the Sonos app during Atmos content) and the room is set up in the app. For stronger height effects, the Arc has real up-firing drivers.

My earbuds cut out when I put my phone in my back pocket.+

That is expected physics rather than a fault. Bluetooth is strongly absorbed by water, your body is mostly water, and a phone in a back pocket puts your body directly between the transmitter and your ears. Moving the phone to a front pocket or carrying it in your hand resolves it almost every time.

Does this answer apply to every Sonos model?+

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

What should I record before troubleshooting disconnecting or drops?+

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 disconnecting, drops. The ordered checks preserve that evidence.

When should I stop and use qualified service?+

Stop for swelling, heat, liquid or damaged ports.

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

Match the path before repeating the steps.

Match another device