Bugzilla – Bug 7902
Remote control won't work on start-up
Last modified: 2009-01-29 09:47:58 UTC
On my computer, a cold start of my Squeezebox v3 renders the remote control inoperable (cold start == after a hard power cycle, unplugging the power cord). I've observed the following when SqueezeCenter is in this state: - Key presses of any sort on the remote produce no visible response in the player. - According to the status page, SqueezeCenter can see the player, its MAC address, etc. - Sniffing the network with Wireshark shows traffic between SqueezeCenter and the player The workaround for this problem is to create a playlist via the web interface and start a play. The play will succeed, and after this the remote works fine until the next cold start of the player. Details of my server: SqueezeCenter Version: 7.0.1 - 18932 @ Sat Apr 19 00:30:14 PDT 2008 - Red Hat - EN - utf8 Perl Version: 5.8.8 i386-linux-thread-multi MySQL Version: 5.0.27 Platform Architecture: i686-linux Linux release: Fedora Core 6
Hi Sean, A log including player.ir messages might be useful. In your wireshark capture, do you see the IR packets even when the device is not responding? The device really doesn't DO anything with IR packets other than immediately pass them to the server.
Sean - any news?
Please re-open if you can provide any additional info, thanks!
I have a customer who is seeing this same behavior. I have asked the customer to comment on this bug when he gets a chance describing what he is experiencing.
I was having a similar problem with my squeezebox, except that mine would only respond to the remote control when there was unplayed content in tbe playlist. When the last song had played, the player would not respond to the remote control. It also asked me to configure the network again if the power was disconnected, but because I'd only had it a few days, I wasn't sure if that was normal behaviour or not. This happened on my first squeezebox within a few days of purchase. Slim Devices support didn't know what was wrong (and I had no idea what caused the fault) and suggested I return it for replacement. I've had the replacement for less than two months, and it stopped responding to the remote control a few days ago. This time though, I know what caused it. I'd noticed a spectrum anaylser being shown along with the name of the currently playing song, but couldn't disable it from the player itself. I was poking around the web interface on the weekend, looking for something else, when I saw a setting which I thought would disable the spectrum analyser, so I changed it. This caused the player to turn on, and I turned it off using the web interface. The next time I tried to use the player with the remote control, it was unresponsive. I contacted support again but they couldn't suggest anything new. I searched bugzilla and found this bug, but nothing else that suggested a solution to my problem. Then I found bug 7391, which suggested defining a player name as the solution to a different remote control problem. I had no idea that the player needed a name. I used the web interface to give it a name and now my player responds to the remote control as normal :-) It hasn't fixed my problem entirely though. It still asks for network configuration when the power is disconnected & reconnected, which I don't think it should do -- I've lost power to the player before and it connected to the server without me having to do anything.
The normal behavior should be that on power up you see the three screens: 1) "Logitech" 2) "squeezebox" 3) "Welcome to Squeezebox (To begin setup press the right arrow)" After that, if you press the right arrow, you will be guided through the network setup. However if you just leave it and don't press any buttons, it should automatically reconnect to the last network and server to which it had successfully connected. On mine, it briefly displays the message 'obtaining an IP address' then goes to the 'Squeezebox home' screen indicating it has connected to the server. Do I understand correctly that your unit is not behaving like that?
Thanks for that. It does automatically connect after a short timeout. I was too impatient to wait :-) I'm sure though that it didn't timeout that quickly when it wasn't responding to the remote control, i.e. before I gave it a name. My first squeezebox.also waited for network configuration each time, and I didn't ever see it timeout and automatically reconnect, even after leaving it for a few minutes while I searched for any clues to try to fix its problems. I've tried to clear the name to reproduce the fault, but squeezecentre won't let me do that. Is there any way around that?
You'd have to delete the appropriate player section in your .prefs file AND do a factory reset on the player by holding '+' as you connect the power.