Disclosure: this is a troubleshooting reference. It contains no product recommendations and no affiliate links — it exists to save you from troubleshooting a problem Sonos already knows about.
Here’s a scene every Sonos owner knows. An update lands. Something stops working. You spend an hour factory-resetting speakers, rebooting routers, and re-reading settings menus — before finally discovering, on page six of a Sonos Community thread, that everyone has this problem and Sonos is already working on a fix. The hour wasn’t troubleshooting. It was a tax on not knowing.
This page exists to kill that tax. It’s a living, honestly-dated tracker of the known Sonos firmware and app issues — what broke, when it was first reported, whether it’s fixed, and what to do in the meantime. Not forum threads with 47 contradictory replies. Not Sonos’s release notes, which tell you what was fixed but not what stayed broken. One maintained table, kept current, with every issue linked to the full fix guide on this site.
Last verified: October 2026. The tracker is updated when this site’s troubleshooting coverage changes — new guide published, workaround confirmed, issue resolved. What it is not: an exhaustive Sonos bug database. It covers what this site’s guides document, dated and attributed. That limitation is stated plainly below, because a tracker that pretends to know everything is worse than one that tells you exactly what it knows.
The known-issues tracker
| Issue | Affected | First reported | Status | Workaround / next step |
|---|---|---|---|---|
| Speakers disappearing from the app after the v80 redesign Speakers vanish from the app, rooms go missing, or the app insists no system exists — sometimes reappearing after a reboot, then disappearing again. App problems guide |
All S2 systems on app v80.x | With the v80.x app redesign | Improving — Sonos has shipped fixes since launch, but owners still report recurrences after updates | Phone reboot first; then app reset (Account → App Preferences → Reset App); check VPN/guest-network/band-steering |
| Features removed in the v80 redesign Queue management gutted, the line-in “Uncompressed” option gone, playlists misbehaving, alarms unreliable. App problems guide |
All S2 systems on app v80.x | With the v80.x app redesign | Partially restored — Sonos has been restoring functionality update by update; check the current release notes before assuming a feature is gone forever | Update both app and speaker firmware; check release notes; don’t update on day one of a major redesign |
| Surround/sub setup wizard crashes Adding surrounds or a sub through the app crashes mid-setup on specific phone/OS combinations; previously paired stereo pairs don’t appear as surround options. App problems guide |
Systems adding surrounds/subs via app v80.x | With the v80.x app redesign | Ongoing — Sonos has acknowledged setup-flow bugs; owners still report failures on specific devices | Reboot the phone, start the wizard fresh, add surrounds via Settings → System → soundbar → Add Surrounds; unpair stereo pairs first; try a different phone |
| Trueplay producing worse sound / missing after app updates Post-update tuning reports cluster around bass loss (“non-existent” bass), muddy mids — including on the Arc Ultra — or Trueplay missing entirely from the Arc’s settings. Trueplay troubleshooting guide |
iOS Trueplay users; Arc Ultra owners report the bass-dampening variant most | Reported alongside app updates; the Arc Ultra cluster is ongoing | Ongoing — current workaround is Trueplay off plus manual EQ | Check the phone’s microphone permission for the Sonos app (the new app dropped the warning prompt); turn Trueplay off and compare; re-run in a quiet room after a phone reboot |
| App and speaker firmware out of sync: features break after updating one side The app and speaker firmware are separate updates. Updating one without the other produces the classic “everything was fine until the app updated” symptom set — features missing, settings unreachable, Trueplay gone. Update problems guide |
Any system where the app and firmware versions diverge | Recurring with every staged rollout | Ongoing by design — Sonos rolls updates out gradually, so version skew keeps happening | After every app update, open the Sonos app → Settings → System → System Updates and check the speakers match; update the app first, then the speakers |
| S1-only products can’t take S2 firmware Playbar, Play:5 (Gen 1), and Play:1-era hardware cannot run S2 firmware. A mixed S1/S2 household hits a hard wall: the old products can’t join an S2 system. Compatibility matrix |
Playbar, Play:5 Gen 1, Play:1-era hardware | Since the S1/S2 split (documented in our update guide) | Permanent — this is by design, not a bug; no fix is coming | Check the compatibility matrix before buying anything for a mixed system; decide deliberately whether to run separate S1 and S2 systems or replace the legacy hardware |
| TV firmware updates disabling HDMI-CEC → soundbar goes silent A TV software update or settings reset can switch HDMI-CEC off without telling you. The soundbar was fine yesterday; today there’s no sound from the TV at all. Beam no-sound / HDMI-ARC guide |
Any soundbar on HDMI-ARC after a TV update | Recurring — documented in our no-sound guide | Recurring — TV makers keep shipping updates that reset CEC | Re-enable CEC in the TV settings (it has a different brand name on every TV — the no-sound guide has the table); re-run the TV’s audio output setup; check the TV for its own software update |
How to use this tracker
When something in your system breaks, check this page before you start troubleshooting. If your symptom is in the table and the status says ongoing or recurring, the honest move is often to apply the workaround and wait for Sonos — an hour of settings archaeology won’t fix a Sonos-side bug. If your symptom isn’t in the table, it may be specific to your setup: run it through the Sonos Doctor, which walks you through the five diagnostic paths (no sound, app problems, dropouts, update failures, Trueplay) and points you at the right fix guide.
The v80 redesign is the canonical example of why this page exists. Owners who checked the community first learned within minutes that speakers vanishing from the app was a widespread regression with a known workaround (phone reboot, then app reset) — and that no amount of factory-resetting would fix what was, fundamentally, a software bug on Sonos’s side. Owners who didn’t check spent their evenings rebuilding systems that were never broken. The difference between those two evenings was one piece of information: is this just me, or is it everyone? That is the only question this tracker exists to answer.
And if the problem started the day of an update and the community is reporting the same thing — r/sonos and the Sonos Community forums surface problems days before Sonos acknowledges them — that’s the signature of a Sonos-side issue. Wait for the patch. The tracker’s job is to make that call easy instead of expensive.
How the tracker stays current
This is a curated digest, not a scraper. The table updates when this site’s troubleshooting coverage changes: a new fix guide published, a workaround confirmed by community reports, or an issue marked resolved after owners confirm it. Every row links to the full guide where the evidence lives — the tracker is the index, the guides are the source of truth.
Two maintenance rules, stated so you can hold us to them. First: no row gets a “resolved” status without a confirming source — a Sonos release note, an acknowledged fix, or sustained community confirmation. “Seems fixed” doesn’t count. Second: the “first reported” column uses this site’s own guides as its source. Where our guides document an issue without a specific date, the table says so (“with the v80.x redesign”) rather than inventing a month. Precision about what we know and what we don’t is the whole point of a tracker worth bookmarking.
The honest limits of this tracker
Four limits, stated upfront — because a tracker that pretends to be comprehensive is a liability, not a reference.
One: it’s not exhaustive. This table covers what this site’s guides document. Sonos has hundreds of thousands of owners and dozens of product combinations; there are bugs we’ve never covered. If your symptom isn’t here, that doesn’t mean it isn’t real — it means it isn’t in our guides yet. The Sonos Doctor and the dropouts guide cover the problem-shaped demand the tracker doesn’t.
Two: it’s not first-hand testing. The issues here are compiled from Sonos’s public statements, release notes, and community reporting (r/sonos, Sonos Community forum) as documented in our guides. We say “owners report” where the evidence is community-sourced, and we don’t claim to have reproduced bugs in a lab we don’t have.
Three: Sonos changes things server-side. Some fixes arrive without an app update, without a firmware version, and without a changelog — behavior just quietly improves. Statuses can go stale between verifications, which is why the page carries a verification date and the update rules above.
Four: firmware moves fast and this page is a snapshot. A tracker is only as good as its last update. If you’re reading this months after the verification date, treat the table as a starting point and check the linked guides — which carry their own verification dates — before acting on anything dated.
The tracker answers “is this a known problem, and what’s the current state.” The Doctor answers “what’s wrong with my system specifically.” The system planning guide is where you go once everything works again and you’re thinking about what to add next. Together they’re the clinic this site is becoming: diagnose, track, plan — and never waste an hour troubleshooting a bug Sonos already knows about.
