I'm using Squeezebox Server 7.7.2. I have two squeezebox booms. The first I purchased in 2008-ish and the other in 2010-ish. Both boom's have worked flawlessly since then. However...
Within roughly the last year, the 2008-ish era boom has become quite flaky. It is slow to connect to the server, and frequently loses contact with the server. I have tried resetting the box with these techniques:
* hold down the 'plus' on the remote when I plug in the boom
* hold down the 'brightness' on the remote when I plug in the boom
* hold down the '2' key on the boom when I plug in the boom
When the boom is working, I've confirmed that the remote is working just fine. Neverthless, none of the above actions causes any kind of reset with the boom.
I've seen instructions about pressing the '1', '2', or '3' key on the remote...but my remote does not have a '1','2' or '3' key on it.
The only kind of reset that has had any affect whatever, is to hold down the power button on the boom for 10 seconds. However, that merely allows me to redo the 5-step networking setup. And when I redo that setup, I notice that the boom has still memorized my wireless network name and password.
Ultimately I don't know if fully resetting the boom, which I'm failing to achieve, will solve the problem anyway. The only other thing I can think about is my wireless router, which I have changed about a year ago. But if there was a problem with the new wireless router, I would rather expect the boom never to work - rather than be flaky.
So I'm looking for advice of what to try next. I'd also like to know if there is such a thing as a squeeze-boom hospital, where sick booms can be sent to get better.
And while I'm at it, is there any news of a new boom replacement? I love these devices, and am greatly saddened that they have been discontinued.
Results 1 to 4 of 4
Thread: Flaky Boom Wireless Connectivity
2012-06-02, 13:58 #1
- Join Date
- May 2009
Flaky Boom Wireless Connectivity
2012-06-06, 15:38 #2
Don't use the remote.
I have never been able to use the remote for this purpose either. I have four booms, and my experience has been to use the "+" button on the Boom itself for a factory reset. Unplug, hold the "+" button while pluging the power cord back in. For Xilinx reset, use the "1" key intead of "+".
FWIW, this is the proceedure shown on page #29 of my 2008 Logitech Feature Guide.
SqueezeCenter 7.3.4 running on a DIY PC, Windows 7 64 bit o.s., with Inguz Audio EQ/DRC. (1) Transporter, & (4) Booms connected through a Linksys WRT54gs router and Linksys WAP54g access point. Using an iPad with both SqueezePad & iPeng for controllers. Transporter => Rotel RC1070 preamp => Rotel RB1080 2 channel amp => Bowers & Wilkins 805 Speakers.
Headphone setup: Transporter => Woo Audio WA22 balanced headphone amp => Sennheiser HD800 headphones.
2012-06-07, 20:03 #3
Wifi problems may be changes in environment ( think neighbours ,radio etc , baby monitors other networks ).
Have you swapped places with the boom's to see if the problems follow the boom or if the other one will have problems in the same spot ? Another test can be to swap power supply ( a long shot but easy to try )--------------------------------------------------------------------
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3 sub.
Kitchen: Touch + powered Fostex PM0.4
Misc use: Radio (with battery)
iPad1 with iPengHD & SqueezePad
(in storage SB3, reciever ,controller )
server HP proliant micro server N36L with ClearOS Linux
2012-06-11, 15:32 #4
- Join Date
- Nov 2006
I have occasionally had a boom lose the WiFi connection and not reconnect. Usually going through the network setup again accepting the remembered SSID and WPA2 password fixes this. When it doesn't resetting the wireless router usually does the trick.
I did have one really odd case with a boom that would connect, the clock would start to update and then within a few seconds it would get stuck. That turned out to be a duplicate IP address with a classic in another room. Obviously a firmware bug somewhere as the addresses are allocated with DHCP and there should be no duplicates but it is not at all certain the bug is in the boom firmware - more likely perhaps to be in the wireless router firmware.