MP and PowerScheduler do not go into standby (1 Viewer)

[KvB]

TV-Server Version: 1.0.2
MediaPortal Version: 1.0.2
MediaPortal Skin: StreamedMP
Windows Version: XP sp3
CPU Type: Core2Duo
HDD:
Memory: 4Gb
Motherboard: Asus p5e-v hdmi
Video Card: onboard g35
Video Card Driver: latest
Sound Card: onboard
Sound Card AC3: onboard
Sound Card Driver: latest
1. TV Card: FloppyDTV
1. TV Card Type: dvb-c
1. TV Card Driver:
2. TV Card: FloppyDTV
2. TV Card Type: dvb-c
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case: mCubed
Cooling:
Power Supply:
Remote:
TV: Philips lcd
TV - HTPC Connection: HDMI

Hi there,

I can't seem to get my MP into standby. I enabled both the TV-server and Client plugins of Powerscheduler and set everything to go into standby after 2 minutes.

The strange thing is that in the MediaPortal log, the powerscheduler plugin complains about not being able to connect to a server. Might have something to do with it.

Any ideas? I'm stuck.

Regards,

Kees.

PS please find attached the logs.

 

[DreamMaster]

i know this isn't going to help you but i get the exact same error
i can manually go into standby and manually come out of standby but will not do it automatically :-(
i have read somewhere that ForTheRecord works very well with standby and they have just recently released a verion that will work on MP 1.0.2! So i will be trying that tonight!

 

[KvB]

Well in fact, some other thread DID help me. I'm not sure why it works now, but disabling the windows firewall works like a charm! Just disable it and restart and powerscheduler should work!

If you ever find out what port should be added to the exception list so that I don't have to disable the firewall entirely, let me know

 

[DreamMaster]

i am pretty sure my firewall is disabled already but will check tonight.
the port that it uses is 31457 (this is what you error.log says - this is the same port that it was complaining about on my machine).