Reply to thread

Edward,


You seem to expect PowerScheduler to completely manage the system power. Actually, Windows is responsible for automatically suspending (standby, hibernate, shutdown) the system. PowerScheduler's main purpose is only to prevent automatic suspension in certain scenarios (eg. network activity). It's very important that you understand that clearly.



Windows is responsible for recognising all regular system user activity - including terminal service log in - and delaying/preventing automatic suspension. PowerScheduler doesn't have to do anything, so that's why that activity isn't tracked.



The correct understanding is: PS prevents Windows from suspending the server when there is network traffic.



The correct understanding is: PS prevents Windows from suspending the machine for X minutes after the last MediaPortal user activity.



You are mistaken. MediaPortal user activity (eg. going to a different section within MediaPortal, playing media within MediaPortal) is the only valid condition related to the timeout setting. Network traffic, file shares, processes etc. are not MediaPortal user activity, so they are not valid conditions.


As explained above: system activity such as terminal service log in/out is not valid MediaPortal user activity. PowerScheduler doesn't have to detect or handle that activity because Windows already detects and handles it.



I think you may have created this problem for yourself when you enabled the force-standby-when-idle setting:

[2016-08-23 07:59:23,094] [Log ] [TVService] [DEBUG] - PS: PowerScheduler forces system to go to standby when idle: True


http://wiki.team-mediaportal.com/1_MEDIAPORTAL_1/141_Configuration/TV-Server_Configuration/13_Plugins/Power_Scheduler/2_Server_Configuration#PowerScheduler_forces_system_to_go_to_standby_when_idle


As far as I can see, that setting is the reason why you only get the 2 minute grace period.


Why did you enable that setting?


Regards,

mm


Top Bottom