Behind error 4004-0 is the message "There was a problem checking for the update. (4004 / 0)." That wording is the clue: it's an update-check failure, not a pairing failure. The Bose app finds your speaker on the local network fine, but the speaker can't complete a handshake with Bose's servers over the internet — usually a router/DNS hiccup or a filtered network, sometimes just a transient outage on Bose's end. (Bose doesn't publish a numbered definition for 4004-0, so this is read from the on-screen message and a very consistent pattern of owner fixes.) It shows up across Bose's connected speakers and Smart Soundbars (300/600/700/900), in both the older SoundTouch app and the current Bose Music app.
The likely cause
The speaker has Wi-Fi and a local IP — that's why the app can see it — but the route out to Bose's update server is blocked. Almost always that's the router or DNS, not the soundbar. So you reboot the network path before you touch the speaker.
Fix it
- Reboot the whole path, in order. This is the single most-reported fix. Unplug the modem and router, unplug the Bose speaker, wait at least 60 seconds, then power the modem first (let it fully sync), then the router, then the Bose. Owners report this clearing a 4004-0 that had blocked updates for days.
- Confirm phone and speaker are on the same network with real internet. Same Wi-Fi, same band, and load a website on the phone over that Wi-Fi (not cellular) to prove the network actually reaches the internet.
- Force-close the Bose app, then reinstall it if needed, and retry the update.
- Simplify the network for the update. On a dual-band router, temporarily switch off the 5 GHz and guest networks so the speaker joins 2.4 GHz cleanly — Bose's own setup advice. Band-steering and mesh setups are common culprits.
- Rule out DNS or a captive portal. If reboots don't help, point the router's DNS at a public resolver (
8.8.8.8/1.1.1.1), or test the speaker on a phone hotspot. If it updates on the hotspot, your home network's DNS or content filter (Pi-hole, ISP filtering, hotel/captive-portal Wi-Fi) was blocking Bose's server. - Retry in an hour. Because it's an update-check error, a Bose-side outage can cause it — the same steps that failed can succeed later with no change on your end.
Don't confuse it with a device-side fault
4004-0 is an app message about reaching Bose's servers. It's not the same as the speaker's own light-bar states: a light bar scrolling white left-to-right for 20+ minutes means a firmware flash is stuck on the device, and a solid red bar is a device error. Those are fixed by power-cycling the soundbar itself (unplug ~60 seconds) or a factory reset — not by reinstalling the app.
FAQ
What does 4004-0 actually mean? The Bose app couldn't check for or download an update because the speaker can't reach Bose's servers — a network/DNS path problem, not a broken speaker.
Why does the app find my speaker but still fail? Because the app talks to the speaker over your local network, while the update needs the internet path to Bose. The first works, the second is blocked — classic DNS or captive-portal signature.
Is it my soundbar or Bose's servers? Often Bose's side. If a full reboot and a DNS change don't help, wait an hour and retry before assuming hardware.