The Acoustimass Bass Module 700 of my Bose Lifestyle 650 stopped working following a system update. The status light blinks in the sequence of Amber - White -- Red repeatedly. The Bass Module was connected wirelessly.
The acoustimass randomly connects once in a fortnight or so, but its rare.
I tried to see if there is any solution available online, and I was surprised to find this issue was faced by many owners in different times.
For me, it started when I went ahead with the installation of an Auto Update. After the update was over, it kept asking me to update again and again while turning the system off. This happened some 4-5 times, and after that the Bass Module stopped connecting with its status blinking from Amber to White and then Red in repeated sequence.
Following are the things I already tried seeing the suggestions from all other related posts.
1. Reset and Factory reset: I tried the 30 second reset numerous times. Then did the factory reset from the console using 'Setup' and 'Source' buttons - Had to do all the setup and pairing again, but no positive outcome from Bass Module.
2. Connected the Acoustimass via 3.5mm cable: The bass was still non-functional. The sound in fact started breaking from all other speakers in this setting. So I disconnected and setup the acoustimass back wirelessly.
3. Tried the USB update: No success. However, I noticed the update skips from around 50% to around 95% and completes. May be it is not able to update the Bass module and that is the part being skipped? (Just a guess). The module in this case was connected in wireless mode. I also switched off my WiFi Router to rule out any chance of interference.
4. Kept the Bass module in different places, but no change in its behavior.
I am located in Bangalore, India. Could you please help me with this issue?
This status sequence is not even documented in the user manuals.
If the firmware/software did not update properly, is there another way to force the update in the Bass Module 700?
Following are some of the links I found related to similar issues, but no resolution was found:
Exactly the same status: