Bugzilla – Bug 8526
When waking SqueezeCentre using remote power button (via WoL), the player isn't turned on
Last modified: 2009-07-31 10:23:11 UTC
Given following setup: - SqueezeCentre server set to go to sleep (aka standby) after an idle period - Server already asleep - Player previously powered off before the server when to sleep - Player screensaver set to Blank and/or off brightness set to lowest (i.e off) This is configured like this to allow the user to power off the player not be aware that the server is still running. Having a date/time screensaver set (for example) would be confusing as the screensaver would be displayed sometimes (when the player was off but server on) and not others (when the player is off and the the server had idled to sleep). When a user presses the remote power button, the waking up SqueezeCentre message is displayed followed by the connecting to SqueezeCentre one (OK). The display goes blank (not OK). The user then has to press the remote power button for a second time to turn the player on (the player power is off after waking up SqueezeCentre - because SqueezeCentre returns the player to the same power status as before the server went to sleep). This behaviour is not user friendly as it doesn't allow a simple on/off experience. The desired enhancement is for the player to be powered on after the player (via the remote power button) wakes the server up via WoL. I can imagine that this may require a player firmware change in order for the SqueezeCentre to know that the server was woken up by WoL from that player (i.e. the player sends a message after connecting to indicate that it woke the server up). Or it might be a SqueezeCentre-only thing! Thanks.
I'm going to mark this for 7.3 for now. We can revisit it sooner if it accumulates more votes. I agree it is confusing, especially if the display is set to blank in the player 'off' state. This seems likely to be a duplicate but I'm not sure of what. Perhaps bug 7594.
*** This bug has been marked as a duplicate of bug 4682 ***
I don't think that this bug is an duplicate of bug 4682. Bug 4682 is about the discrete IR codes not functioning the same as the toggle code (that the Logitech remote uses). If the specific problem in bug 4682 was was fixed, this bug would still remain (that a player, when powered on by WoL from IR code, returns to the same player power state as before [which may be off] rather than always returning to on). I can see how they are both related (to the power on/off experience) and that a fix to bug 4682 may be grouped together when ironing out the experience.
Reduce number of active targets for SC