eHome receiver prevents computer from sleeping

Hi, I have read tons of forum posts but I still can't figure out the issue I have.
I have a win7 media center PC with an (external) eHome receiver.
If "allow this device to wake the computer from sleep" is disabled on the eHome device my sleep (S3) works perfectly - however I can't use the remote to wake up the computer obviously.
If I enable "allow this device... " for the eHome receiver then put the computer to sleep, it wakes up instantly (gets back to logon screen since it's how it is configured).
I have looked for Bios and eHome driver updates, couldn't anything... any idea would be very welcome!

I have had a lot of sleep-wake up problems using the Microsoft Infrared receiver and remote with Windows Vista and lost my sleep :). I was totally fed up.

I haven't really put it into much use or tried it With Windows 7 since it is time-consuming and also I had various other options/solutions. That included the EZ Commander with its own IR receiver EZ Commander - An innovative I/O solution to replace PC remote/mouse/keyboard/presenter ,the Logitech Harmony Remote which uses the same MS infrared receiver and then the Lenovo Multimedia keyboard and remote with USB nano dongle. I now have all these and do not want to add any more.

At present I am exclusively using only the Lenovo Multimedia Keyboard and remote with my HTPC and am happy with it. Lenovo - Laptop and desktop - Keyboards & Mice 57Y6336 (US) . Can put my HTPC to sleep and wake up easily without any problems whatsoever.

Now you have to do your own research on what you would go with.:)

Thanks!

I already have a Harmony, and it was still waking up the computer - the remote actually doesn't matter, the receiver is the pb.

I finally figured out what was going after lots of reading: I needed to move the USB jumpers on my motherboard to +5VSB. I had seen that mentioned from people who couldn't wake up their computers, but apparently it can also cause it to wake up immediately when trying to sleep.

Glad you figured it out. In fact this is one of the basics and we always tend to forget the basics after-a-while. In order to wakeup, the USB device should always be powered with 5V. When installing the motherboard, if one cares to go through the manual religiously, the setting up the jumpers for the USB ports is invariably mentioned. In the Device Manager also one has to set the the Power Management functions properly (not allowing the computer to turn off the device to save power and allowing the device to wake up the computer)

Ponmayilal said:

Glad you figured it out. In fact this is one of the basics and we always tend to forget the basics after-a-while. In order to wakeup, the USB device should always be powered with 5V. When installing the motherboard, if one cares to go through the manual religiously, the setting up the jumpers for the USB ports is invariably mentioned. In the Device Manager also one has to set the the Power Management functions properly (not allowing the computer to turn off the device to save power and allowing the device to wake up the computer)

Yes, I knew that part, the news for me is that in Win7 on my machine at least, if you set the jumper to 5V (non SB) then configure a device behind it to wake up the computer, Windows (I assume) will do that "sleep - wake 5s later" dance - that's what threw me off.

hmmmm...........the problem I had with Windows Vista and the MS Infrared receiver was equally strange. I could put the HTPC to sleep using the MS remote.I could wake it up too using the remote but immediately after the wake-up, the IR receiver will get derecognised and the remote can no longer be used. The IR receiver had to be plugged out from the USB port and plugged in again for it to be recognised and the remote usable.

There was also a time-element involved in it. If the PC is woken-up within four minutes of it being put to sleep, everything was fine. The IR receiver will continue to be recognised and the remote usable.Anything above four minutes, it was a disaster.

Many had this problem and it was brought out in the Green Button Forum of MS MediaCenter Team. The MS team gave no solution. After trying out various hotfixes and registry modifications suggested by other users - each time religiously executing them on a clean install of Vista - for almost three full months, I gave up frustrated.

Some users did find a work-around by plugging in the MS Infrared receiver to an externally powered USB hub to resolve the issue but it didn't work out for many users including me.

Basically none including the MS team could give out a technical reason for this behaviour and nip it in the bud. If one does not know the cause of the problem, then no tangible solution could come out. ( One may remember that Vista disarmed the USB KB and mouse for many users making them powerless and twiddling their fingers.)

I was so fed up that I did not want to try it on Windows 7 and that is why the EZ Commander and Lenovo Multimedia remote and KB. I am happy eversince.:)