Sorry. I'm going to give you an exhaustive reply. But you might want to actually read this mini-tome since your question points up a common misconception about SrvrPowerCtrl.
SrvrPowerCtrl is "about" sending your server to sleep. Waking it up again isn't part of it's job description. Waking up from sleep relies on the WOL features built into your server and built into your Squeezebox players. When your server is sleeping, so is SrvrPowerCtrl. The only thing that isn't sleeping on your server is your NIC...your network interface card. Given the right hardware, BIOS and operating system settings, the NIC in your server will listen for a "magic packet" and, upon hearing one, wake the server back up. Squeezebox players, the Squeezebox controller and iPeng are all capable of sending such a magic packet and waking up a server. With my current setup (server running SC 7.3.4, a Transporter, several SBCs scattered around the house and iPeng on my iPhone, I have no trouble at all waking the server from sleep. I can use the IR remote with the Transporter, the SBCs, iPeng or a script on my laptop...all will reliably wake up the server. Maybe twice a year I find that my server has locked up for some reason and requires a hardware reset. But other than that, it works pretty flawlessly. Coupling SrvrPowerCtrl with Jason H's PowerSave plugin, PeterW's PowerCenter plugin and some cheap X10 gear has meant that I've ended up with a pretty "green" system: the server sleeps automatically when not in use, my big power amps turn off automatically when not in use, and all of it comes back to life in less than 30 seconds with a simple key press from a variety of remotes. I'm getting significant power savings with a minimal hit to convenience. Now, some caveats: Your Squeezebox player's ability to WOL your server isn't completely flexible. Any given player only knows how to wake one server. If you have multiple servers in your house (a minority of users, certainly) only one of them can be woken up by any given player. To tie a given player to the ability to wake a particular server, perform a factory reset of the player, set up the networking options and make sure that the server you want to be able to wake is the FIRST music source you connect the player to. Also, the SBC's WOL abilities seemingly have waxed and waned with different firmware revisions over time. In the past, to make WOL from the SBC work reliably, I've resorted to hacking the SBC and installing a WOL script that gets run when the SBC boots up. But my experience with the current SBC firmware compatible with SC 7.3.4 (7.3 r6038) is that WOL is working just fine with no special tweaks required. With each remote (IR, SBC, iPeng) it seems like one must learn its quirks in terms of just what sort of a keypress / menu selection will trigger the WOL. In the simplest case, a SB3 or Transporter "lying fallow"...i.e. not connected to mysb.com, a simple press of the power button on the remote will cause the player to fire off the WOL packet and wake the server. If the player is connect to mysb.com, then, if I'm remembering correctly, a couple of extra steps are required. Certainly, the player firmware could be enhanced to make this easier and there have been enhancement requests in the bug tracking system for just such improvements for several years now. With iPeng, it seems like there are occasions where one has to quit and then restart the app to trigger a WOL packet. Finally, with the SBC, one has to navigate the menu system to the music library and select some element (e.g. browse genres) that make the SBC realize the server hasn't responded to a query request. The SBC then fires off a magic packet and the server wakes up. Now, the biggest caveat of all: With Squeezebox Server 7.4+ and the switch from SqueezeNetwork to Mysqueezebox.com and with the new firmwares for the SBC, reliable WOL and waking of the local server has become unreliable again. This is really unfortunate. Loyal Squeezebox users seemly had to badger the developers to get WOL working reliably with SlimServer and SqueezeCenter and the 'ip3k' level players (SB2, SB3, Transporter). The switch to SBS 7.4 has seemed like a big step backwards in terms of WOL reliability. Last time I tried, there really didn't seem to be a way to wake the local server using the SBC when a player was "on" MySqueezebox.com. It's been more than a month since I last tried this, so this flaw could very well have already been fixed in subsequent SBC firmware updates. YMMV, as they say. My own approach here is that I run 7.4.x only for "development" purposes...i.e testing SrvrPowerCtrl's compatibility. I'll be skipping running all the 7.4.x releases for the purposes my own actual music listening. I anticipate that I won't be back to regularly running a current release of SBS until 7.5.2. -- gharris999 ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=72504 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
