<snip snip>
As a side rant, I'm really getting tired of this kind of thing from Apple... there are few good engineering reasons for the kind of user experience they are intentionally inflicting on their customers more and more (hello? how many different charging cables and base stations are you going to force us to buy???). I mean, Bonjour and traditional WOL coexisted on the Mac before... There is no reason they should not be able to now. But, nope, a magic packet cannot reliably wake a mac... They seem intent to force you to do EVERYTHING the apple way (like MS is always derided for). The devious motive just seems more likely here... people have been screaming about this issue since at least Lion and I think maybe it came in during Snow Leopard (not sure there). So, since it isn't fixed by now, it is "by design" which is BS...
I understand your frustration, and don't consider myself an Apple "fan boy," though I do have several of their products, I also have PCs (my first two computers were a Mac Classic and a 286 12mhz clone w/ monochrome monitor, so I go way back w/ both). So I won't try to defend "for them" or whatever, your gripes are legitimate, however I don't think there are "devious" motives in play. Making things work easily for customers sells stuff and brings them back, shackling them to crappy design and/or hardware will not keep them around long. But, WOL is really sort of a black art on any OS, just google around and you'll see a bunch of really weird almost esoteric and not totally stable implementations on the consumer side where OSes, NICs, routers, switches, etc, vary wildly compared to a more controlled corporate environment. Why do some of my PC NICs ask if I want to turn on WOL, and also if they should only respond to a "magic packet?" An imprecise barometer, but not too many wikipedia articles have the phrase ". . .can be a frustrating technology to implement," however,
WOL's wikipedia entry does. hah.
Even the best case scenario in PCs is a little difficult to understand, and also
this is just the OS side, you then want to make sure your
BIOS supports it, you adjust your NIC card properly, then hopefully if your
switch/router has the right firmware to pass it along.
So, a couple things in no good order.
- I think the energy savings in any computer or standalone device that's used in a "server" type role should take a backseat to that device's stability and performance. Having a regular consumer OS computer go to sleep only to be woken up so that it can stream and transcode video is a tradeoff I would not want to make just because Macs and PCs both will tend to wake up and automatically go into generally more and more CPU significant background task processes the longer they have been in a sleep or powered off state. Macs run a pretty big slew of cleanup &
housekeeping scripts, along with system updates, and
spotlight indexing usually in the very early AM hours. If your Mac hasn't been on for a day or two or more, and you bring it to life remotely and instantly ask it do transcode video and stream it, that can be a big performance killer. I'm slightly rusty on the inner workings of Windows, but also know that it does a variety of similar things like file indexing, OS updates, malware & virus definition updates and scans in off hours and/or upon wake up of the OS.
So, of all the places in your home computing/networking/entertainment, etc. devices, potentially the most tangible trade off for power savings would be felt on a computer that you want to go into as full of a sleep mode as possible except when using it to stream.
I have 3 desktops in my home and none of them ever go to full sleep (i.e. the drives spin down, display goes to powersave, but they'll still do CPU operations and network activity, and kick on the drives if they need to) because I am probably only going to use them for 5-10 minutes here or there once or twice a day, and I don't want my exact time of usage to coincide with full overlap onto when it wants to do its maintenance and housekeeping, just making me work slower when all I wanted to do was one simple task.
I also have a NAS that is a faster file server than any of my PCs are to each other, and can also house, organize, transcode, and stream to the outside world any video I have stored on it, and it draws 30w/h while its disks are active, and significantly less when its idle and spins them and its fans down (here's a pic of me testing its draw w/ a "killawatt meter, it's the pic on the
bottom).
- All that said, I played around more with devices on my LAN, and ways of sending WOL commands or otherwise waking stuff up and have a couple of observations.
1. I don't believe Macs themselves use the "Bonjour sleep proxy," I used a few network activity monitors and believe it's just for A/V devices like AirPlay speakers and Apple TVs.
2. With varying degrees of success I could send my Macs WOL commands, but it seemed to be about the least reliable method to consistently bring them out of sleep. Doing a screen share or direct file share was 100% consistent (as was using the iOS remote app to stream music through their speakers or from their iTunes libraries to other computers/speakers).
3. I installed the AiCloud Smart Access app and turned that feature on my router, despite it sort of scaring me for how many holes it punches through w/ UPNP and unknown
security risks (
correction, known risks
). Oddly, it didn't recognize the actual Mac I was typing from as being on my network, but it did recognize a few other PCs & Macs (including a sleeping one) I did not stay around long enough to try its WOL command.
4. I tried maybe 4 different iOS apps to try to hit my Macs with WOL commands and they were very flaky, at best. I tried doing it just by IP, none of them asked for MAC address, some were occasionally kind of effective.
5. You mentioned using "gotomypc" on the Mac and logging into it remotely, OSX has a built in VNC server (sharing > screen sharing) and you can log into it from any VNC viewer (some work better just setting a VNC p/w, some you can use your login credentials), I wasn't clear if you planned on watching your streamed video via remote connection to the Mac or were just using the connection to wake your Mac up. Hopefully it would be just to wake up, I would speculate the overhead on both CPU and bandwidth might make simultaneously streaming video difficult or impractical.
- I also just
found the difference between a regular WOL packet and a "magic packet"
Wake on Directed Packet - accepts only patterns containing the adapter's Ethernet address in the Ethernet header or containing the IP address, assigned to the adapter, in the IP header.
Wake on Magic Packet - accept only patterns containing 16 consecutive repetitions of the adapter's MAC address.
Oh I'll sleep well tonight knowing that!
So ya, long story short, maybe swap a few bulbs out to LED and use those as personal green credits to just keep your Mac on medium alert instead of asleep, or get a NAS, the wattage is low, the speeds are fast, and my Synology can transcode many kinds of video probably faster than my upstream could manage smoothly.