HD200 will not wake up server

[BlueH2O]

Originally Posted by fac13

Usually an extender is resumed from standby, not started from cold, at least in my house, but this does not generate a 31100 broadcast, even if repeated attempts to reach the last-used server fail. I've traced it and it just sends packets to port 31099 at the last-used server IP address, over and over, forever.

If your server is also set for wake-on-lan with directed packet, in combination with the before mentioned method, you cover all your bases.

[ellweber]

fac13,

In my case the HD200 seems to broadcast to port 31100 each time it wakes up, but only once. I can make it work by waking the HD200 then sleeping it again followed by a reawakening. I remain hopeful that Sage will clean this up for us.

Perhaps the HD100 is behaving differently. The HD200 broadcast on 31100 does not seem to be IP address specific.

Lynn

[Fuzzy]

They've GOT to just set it up to send magic packets to the last known server MAC. That's really the only good solution.

[fac13]

Originally Posted by ellweber

fac13,

In my case the HD200 seems to broadcast to port 31100 each time it wakes up, but only once. I can make it work by waking the HD200 then sleeping it again followed by a reawakening. I remain hopeful that Sage will clean this up for us.

Perhaps the HD100 is behaving differently. The HD200 broadcast on 31100 does not seem to be IP address specific.

Lynn

That's useful to know, thank you. I have re-checked and tried the "latest" (July) beta HD100 firmware and can confirm what I said in my previous post - the HD100 does not broadcast to port 31100 when waking up.

That explains why the workaround is of rather less use to me than it is to HD200 owners, thanks.

[ellweber]

fac13,

I think BlueH2O is running HD100s and, based on his posts further back in this thread (#s 28, 30 and 32), has gotten closer to making this work smoothly than I have.

The 100 and 200 do seem to behave differently. It seems like what we have done, or something similar, could be put directly into the extender without much risk. WOL is not hard to set up, is very well established and should work on any Sage Server platform.

Lynn

[wheelrandolph]

I have tried all sorts of methods to wake server so I could use HD-200. (I am currently trying from my Nexus One phone). Pinging, magic packet(Droid Wake), Gmote, etc. Nothing will wake it. I read in this Sage forum last year that the Ipod would work so I keep my spouses Ipod handy near other remotes just to wake up server. It uses the Remote app which is supposed to be for controlling Itunes on your pc. I DON'T ever have Itunes open on the server and it still works!
If this works so easily it can't be so hard I would'nt think to implement in SageTV.

Randy

[techhome]

I previously submitted a request to Sage.

Since, I've migrated my server to a new WHS build. Although I used relatively low power components, it still pulls 115-118w. It's configured for Wake on LAN and the Lightsout addin is installed. WOL and Lightsout work perfectly with my Squeezebox, as it sends a magic packet to the server when turned on. I believe implementing magic packet in the HD200 should be possible and a fairly trivial effort. Thus, I'm happy to see activity on this thread. I considered the lack of a complete power management solution to be a bug and have submitted a support request. My email and Sage's response is as follows:

Re: SageTV Support Request
...
Mon, January 25, 2010 10:45:37 PM
From: Doug
To: SageTV Support <support@sagetv.com>
________________________________________
Excellent,
Much Thanks

________________________________________
From: SageTV Support <support@sagetv.com>
To: Doug
Sent: Mon, January 25, 2010 8:31:26 PM
Subject: RE: SageTV Support Request

Doug,

I don't know, but I will also pass along your suggestion to the developers.

George

-----Original Message-----
From:
Sent: Friday, January 22, 2010 7:49 PM
To: SageTV Support
Subject: Re: SageTV Support Request

Thanks for your response George. In regards to the HD200 (bug #1), my old
Squeezebox2 sends a magic packet to wake the server when it is powered on. This was not an original feature of the Squeezebox2. Instead it was an
enhancement, rolled out with a firmware revision. Couldn't the same be
done to the HD200?

Doug


________________________________

From: SageTV Support <support@sagetv.com>
To: Doug
Sent: Fri, January 22, 2010 6:45:15 PM
Subject: RE: SageTV Support Request

Doug,

1. Unfortunately the HD200 can't wake the server.

2/3. I will pass both of these to developers to look into changing for a
future release.

Thanks,

George Oms
SageTV, LLC
http://www.sagetv.com

-----Original Message-----
From: Doug
Sent: Thursday, January 21, 2010 9:11 AM
To: support@sagetv.com
Subject: SageTV Support Request


>SUPPORT REQUEST
++++++++++++++++++++++++
NAME: Doug
EMAIL:

SOFTWARE: SageTV
VERSION: Version 6.6
TYPE OF USER: Licensed User

OS: WinXP Home Media Center
OS( OTHER? ):
CAPTURE DEVICE: Silicon Dust HDHomeRun
CAPTURE DEVICE ( OTHER? ):
PROCESSOR: P4 2.8C
MEMORY: 2G
GRAPHICS CARD: Radeon 9600
DVD MPEG2 ENCODER: PureVideo
AC3 Codec
ADDITIONAL HARDWARE: MCE Remote

SERVICE PROVIDER: Comcast
BROADCAST CITY (LOCATION): Baltimore - Anne Arundel County Digital
COUNTRY: USA
SERVICE: SageTV Service
SERVICE TYPE: Cable

>+++++++++++ REQUEST ++++++++++

REQUEST DESCRIPTION: I have SageMC, (2) HDHRs and (2) soon to be (3) HD200s.
As a former user of XPMCE, GBPVR, MythTV etc; congrads on bringing to market
the best PC based DVR and Media Canter solution, by far!

My server presently also functions as a front-end for a HDTV, but display of
1080i broadcast stutters a bit and I will soon resign the machine to be a
backend server, only and add a 3rd HD200 to the setup. Problems/bugs:

1. HD200s do not wake the Sage server from S3, WOL works fine from my
squeezebox to the same server.

2. When open, the SageTV UI generated by my HTPC/server overrides the
WinXPMCE power management and prevents video sleep and S3. I consider this
a bug, Sage should allow the HTPC to sleep if there is no content being
consumed either directly on the server or via extenders.

3. As a greener, and more complex, solution to minimizing energy
consumption, Sage extenders should go into standby after a long period of
time with no user input, perhaps 3-hours as a starting point. Similarly
many users will power off their TV without stopping liveTV in Sage. There
should be a similar timeout to stop LiveTV in the HTPC & extenders alike
upon no user input, again 3-hours is suggested. I see no sense in
indefinitely spinning a HDD to buffer a TV channel that is in all
likelihood, not being watched.

Doug

[fac13]

I agree with all of that, and thanks for taking the trouble to raise a ticket.

SageTV users could of course do it for themselves. Most of the firmware code is open source and published by Sage, we can telnet into the box, the way in which code is found and executed during startup is pretty transparent. Setting up a tool-chain to compile an etherwake binary is the hardest bit. Most other embedded-linux devices have active hacking communities, I'm not sure why the Sage extenders haven't yet. It's all perfectly legal, we just need to get somebody with the right skills interested!

What would be really nice would be if Sage would just indicate whether they intend to implement your suggestions or not.

[jerryt]

Here is another option for people who have a windows OS running on their network while their server is sleeping;
http://wrcs.codeplex.com/
http://pingwol.codeplex.com/

It installs an application which will listen for a static IP address on your network, and when the device (Client, HD100, or HD200) comes online, the application will send the WOL magic packet to your server.

[David G]

I've had an HD100 for a couple years and it was perfectly able to wake the server. A friend of mine just gave me his HD200 (switched to a cable PVR) - you're telling me the HD200 can't do what the HD100 did without breaking a sweat???

[Djc208]

Originally Posted by David G

I've had an HD100 for a couple years and it was perfectly able to wake the server. A friend of mine just gave me his HD200 (switched to a cable PVR) - you're telling me the HD200 can't do what the HD100 did without breaking a sweat???

If you managed to get your HD100 to wake the server the HD200 should. But neither will send any sort of specific wake command (magic packet, etc.) to the server. So if you can get your PC to wake on directed traffic or you're not going into the deeper sleep states you should be fine with either device.

[gabe1475]

Originally Posted by jerryt

Here is another option for people who have a windows OS running on their network while their server is sleeping;
http://wrcs.codeplex.com/
http://pingwol.codeplex.com/

It installs an application which will listen for a static IP address on your network, and when the device (Client, HD100, or HD200) comes online, the application will send the WOL magic packet to your server.

Does this install on the server or another computer on the same network? If on the server, this works great, if not I still have to leave a computer on.

[jerryt]

Originally Posted by gabe1475

Does this install on the server or another computer on the same network? If on the server, this works great, if not I still have to leave a computer on.

It can be installed on any windows computer on your network which never sleeps. If I had a windows based NAS, this would be a good option.

Currently I am using batch files to automatically check the server status and send magic packets if needed, but this is on a windows SageTV Client. Would not help HD100 and 200 owners.