PowerScheduler++ 1.4.0.x - Stable versions for MediaPortal 1.4 (6 Viewers)

[Jay_UK]

Hi there,

I thought the "overrunning" script might have been an issue.

I will give you new version a try...

I've heard you can not delay/alter the suspend process?

I was wondering if the following "idea" might work?

I believe you can configure it such that suspend does not happen if a certain process is running? How about PS++ creating a dummy process that prevents suspend from running, then once the external command is completed (or a pre-set timeout has been met), then the dummy process is terminated and you issue a suspend (which can continue to run)?

J.

 

[michael_t]

I've heard you can not delay/alter the suspend process?
I was wondering if the following "idea" might work?
I believe you can configure it such that suspend does not happen if a certain process is running? How about PS++ creating a dummy process that prevents suspend from running, then once the external command is completed (or a pre-set timeout has been met), then the dummy process is terminated and you issue a suspend (which can continue to run)?

Since Windows Vista it is not possible to postpone or cancel a suspend once initiated. But you can prevent a system from automatically going to suspend due to idle timeout. So PS++ watches processes and tells Windows not to suspend while they are running. Your proposal cannot work since the external command is triggered with the power event that windows sends when a suspend has been initiated and thus it would be too late to prevent or cancel it...

Michael

 

[megahorst]

I do have a problem with scheduled reboot.
I have configured a daily reboot at 8:15. What I see from my logs is, that this time is not respected. I made myself a litte batch that logs the wakeup, suspend and reboot times:

wakeup;09.07.2013; 2:09:05,90
suspend;09.07.2013; 2:11:09,92
wakeup;09.07.2013; 8:14:06,82
reboot;09.07.2013;23:00:20,41
suspend;09.07.2013;23:26:28,24
wakeup;10.07.2013; 8:14:09,54
reboot;10.07.2013;23:55:29,49
suspend;11.07.2013; 0:21:37,19
wakeup;11.07.2013; 0:56:43,07
suspend;11.07.2013; 0:58:45,74
wakeup;11.07.2013; 8:14:06,84
reboot;11.07.2013; 8:46:10,70
suspend;11.07.2013;23:02:03,27
wakeup;11.07.2013;23:26:06,81
suspend;12.07.2013; 0:22:02,25
wakeup;12.07.2013; 3:00:16,82
suspend;12.07.2013; 3:33:33,27
wakeup;12.07.2013; 4:48:59,81
suspend;12.07.2013; 4:51:01,97
wakeup;12.07.2013;18:48:06,82
suspend;12.07.2013;23:02:14,38
wakeup;13.07.2013; 8:14:07,01
suspend;14.07.2013; 1:37:03,57
wakeup;14.07.2013; 8:14:06,81
reboot;14.07.2013;23:00:29,57
suspend;14.07.2013;23:18:37,35
wakeup;15.07.2013; 0:11:07,01
suspend;15.07.2013; 2:52:12,16
wakeup;15.07.2013; 8:14:06,84

I have configured PS++ to allow standby only between 23:00 and 08:00. Could this be the reason for this?

I have added the logs from the last days.

 

[Jay_UK]

Hi Michael,

If we can not stop a suspend power event, how about we change it from being a suspend into a awaymode while the script is running, then to suspend after?

This works fine on my system, when I press my power button, if a defined process is running then the systems goes into away mode, once the process has completed it enters suspend.

I was wondering if I could crudely just enter the name of my script into the list of processes within PS++?? I will give it a try.

J.

 

[michael_t]

I have configured PS++ to allow standby only between 23:00 and 08:00. Could this be the reason for this?

Zhis is definitively the reason. PS++ does not reboot a system that is not allowed to go to standby. Otherwise it would possibly reboot during a recording or whilst streaming or ... The "allowed standby times" are the same - standby is not allowed and therefore the system keeps running. PS++ waits for standby to be allowewd again the whole day that reboot is scheduled for. So at 23 o'clock when standby is allowed again, the reboot takes place if there is no other reason why standby should be prevented.

Michael

 

[michael_t]

I have configured PS++ to allow standby only between 23:00 and 08:00. Could this be the reason for this?

Zhis is definitively the reason. PS++ does not reboot a system that is not allowed to go to standby. Otherwise it would possibly reboot during a recording or whilst streaming or ... The "allowed standby times" are the same - standby is not allowed and therefore the system keeps running. PS++ waits for standby to be allowewd again the whole day that reboot is scheduled for. So at 23 o'clock when standby is allowed again, the reboot takes place if there is no other reason why standby should be prevented.

Michael

 

[CGT]

Hi, I don't know when this happened but for some reason PowerScheduler++ has disappeared from my TV Server Config! Re-installing won't bring it back. What can I do?

Maybe it is worth mentioning that when I reinstall it, the Temp files are extracted to my RAM drive which surprises me a little bit...

-----------------
Edit:
OK, I just unistalled PowerScheduler++, rebooted and reinstalled. This time it worked!

 

[CGT]

...Unfortunately, now I have found a new problem:
Although I have checked "Unmute master volume.." in the Client preferences my audio is muted when I record and hit the standby key twice (see attached log)

 

[Jay_UK]

Hi Michael,

I tried adding the script to the process list, but it didnt work.

Can you confirm which happens first, is it the external script is launched, or is it PS++ checks to see if a defined process is running (which should prevent standby or go to awaymode)?

Many thanks,

J.

 

[kiwijunglist]

Hi Michael

I use PS++ with forced sleep for my tv-server. I also use this PC to sometimes browse the web etc, due to the limitations in a service detecting idle events it means I have to:
1. Enable 'do not sleep when mp client is not running'
2. I have to have MP client always running in the background
3. If MP client happens to be not running my HTPC will not shutdown

Have you thought of a PS++ helper application that just runs in the taskbar to detect inactivity. This would be a completely optional install, but if the user had 'do not shutdown when mp client is not running' enabled it would also look to this app if running for inactivity prior to forced shutdowns. This would mean that users wouldn't have to always have MP client running, and if MP client was not running the HTPC would still sleep.

Regards
Kiwi