Bugzilla – Bug 9474
no WOL after PowerOn
Last modified: 2008-10-17 04:15:40 UTC
Powering on the SB3 with the main supply does not result in issuing a WOL packet to the squeezecenter. Instead, an error message is scrolling at the display continously. See http://forums.slimdevices.com/showthread.php?p=339586#post339586 for details. Either a WOL packet should be sent out or the display should get blank after some time, like it was with earlier firmwares. Connecting the SB3 to an unswitched mains supply, where it consumes >5 Watts of power is NOT an option.
Seems that more people do find this behaviour really annoying: http://forums.slimdevices.com/showthread.php?t=52451 I do NOT agree that this is an enhancement! The permantly scrolling error message is a BUG that makes it unusable with a switched mains supply!
Just adding the current behavior as it is implemented right now: The change in behavior was intentional as support needed a way to debug connection issues. So every time you reset or power-cycle SB3 it will show the error message over and over again. Only after the first successful connection it won't show the message repeatedly. (But again only until you power-cycle SB3.) As for the WOL, you should see a 'Waking SqueezeCenter' and a WOL packet should be sent out if you press power.
I agree that the error message showing over and over again is annoying but you won't see it if you _only_ power SB3 up if you actually are going to use it. (I.e. it either connects to your running SC or you connect it to SN.) Anyway, turning the error message off after some time is probably the way to go. This should help in your situation and would still help support debugging connection issues. Sending a WOL packet automatically in that situation _without_ manual interaction (like pressing a button on the remote), seems more problematic as I can see people powering up their SB3 and then wondering why their PC also turned on magically. I tend to _not_ change that behavior.
(In reply to comment #3) > I agree that the error message showing over and over again is annoying but you > won't see it if you _only_ power SB3 up if you actually are going to use it. You're right, but my Squeezebox is connected to a Home-Stereo-Receiver with a switched mains output. I think this is a fairly common and useful setup. Powering on the Stereo-Receiver (and listen to FM-Radio, but not the squeezebox) results in this annoying display. No chance of powering down the squeezebox - searching for the remote and pressing power will fire a WOL packet and wake up the server... Up to firmware 88, the behaviour was perfect.
(In reply to comment #3) > Sending a WOL packet automatically in that situation _without_ manual > interaction (like pressing a button on the remote), seems more problematic as I > can see people powering up their SB3 and then wondering why their PC also > turned on magically. I tend to _not_ change that behavior. Although I personally would like a dark display like in firmware 88 even more than a WOL packet, I do not understand your arguments here. Do you think that people powering up their squeezebox do like continously scrolling displays more than a server automatically starting? Besides that: They have no alternative anyway: Either they press the power-button of their already power-up squeezebox (I would have believed that this would turn off the squeezebox) and the WOL is send out, or they pull the plug...
I really have a hard time understanding what would be the problem of sending out the WOL packet. It seems to me that is what the user would expect, else why did he power on the SB? If the Squeezecenter machine is programmed to automatically go to a power down mode, I don't see an inconvenience factor. The worst case is if the sever is _not_ programmed to automatically suspend to a low power state and cycling the power on the SB would activate the server indefinitely. But even in that case, there is sufficient visual indication to the user that his server is up and he can take appropriate action. In short, I think that users would find it understandable and logical if powering up a squeezebox has similar consequences to pressing the "logical" power button on the remote. In both cases, users usually want everything to be ready to play music.
It is just as simple as that: use-case 1.) SB is powered up together with other A/V-Equipment, but is not to be used immediately. Dark display like in Firmware 88 is perfect. If one wants to use the squeezebox, pressing power at the remote wakes up the SC. use case 2.) SB is powered up together with other A/V-Equipment, and is to be used immediately. Automatic WOL packet would be perfect here. If one wants not to use the squeezebox, server will fall asleep again after the configured idle-timeout. Both use-cases are perfectly valid and ok. But there is simply no use-case at all for the current firmware-implementation with a constantly scrolling error-message without WOL-packet. That's why I call this a bug.
I _do_ want the Squeezebox to send a WOL signal when I press the power button on the remote. I do _not_ want it to send a WOL signal after booting from pwer off state. As with others, my SB gets power when I switch on my AV receiver - which does not necessarily mean that I want to use the Squeezebox. I just want the SB to be dark, see bug 9477: https://bugs-archive.lyrion.org/show_bug.cgi?id=9477 Referring to feelfree's comment: From my point of view, use case 2 is not "perfectly valid and ok". I requires that your server falls asleep after a while and that you do not care about it waking up. I my case, neither is the case.
Removing the 'display scrolling continuously' part of the bug description, since that's covered in bug 9477. This bug is now only about the WOL packet behavior.
I would be inclined to stick with our traditional WOL behavior, which is that a WOL packet is not sent at power-up, since users may not want their PC to be awakened every time they connect power to the SB3. If you are planning to listen to the SB3, all you have to do is hit the 'power' button to send the packet.
Ok, I agree, pressing power for firing a WOL packet is ok. I hit another minor problem today: If you press power too early (during Logitech logo or when display says "press right arrow for setup"), you'll get into setup, although you really didn't want to. And most annoying: There's no easy way out of this setup-menu. A hard power-cycle once again is the fastest way I found.
Power only sends a WOL packet if the player is trying to connect to SC. Either wait until then or if you accidentally pressed a button before, chose SC from the menu and connect to it. Then press power. I am going to close this bug as I understand we agreed that we don't want automatically send out a WOL packet upon powering the device on.
*** Bug 4426 has been marked as a duplicate of this bug. ***