Reply to thread

Message

<blockquote data-quote="yhoogi" data-source="post: 514894" data-attributes="member: 69599">Nothing is shown in the calender as the calender is not used at all. The task is regularly checking (I think in a 5min interval) the next programmed event and is setting the timer accordingly. This should be respected with the timeout period before the computer goes to hibernate/stby. (e.g. I have set the LO timeout to 15min which gives the plugin 3 cycles just in case)&quot;MP_Aufnahmen&quot; is the event to control the wake-up task. So you have to enable of course that the task is allowed to bring back the computer from hibernate/stby. Therefore the task is not required to be started at system startupTo my understanding &quot;WHS_LO_erw&quot; on the other hand is checking regularly the DB and handing over the the next event to &quot;MP_Aufnahmen&quot;. This task is also starting &quot;MP_Aufnahmen&quot; in case it is not running. So, you have only to ensure to start &quot;WHS_LO_Erw&quot; at system startup.Btw Larry: Just out of curiosity: Why two seperate tasks? I guess there is a reasoning behind it?If I understood you right, one should avoid to manipulate the LO settings during record. This could have nasty side effects <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />One should also not try to force manually the computer into stby during record as no next event is scheduled and the computer will not come back to life anymore until a LO client initiates a wake-up.I see here a potential weakness as you have also other conditions which may keep the WHS alive (specific tasks, IP addresses, etc..). But I have no idea currently to suggest some better solutionCheers,</blockquote>

[QUOTE="yhoogi, post: 514894, member: 69599"] Nothing is shown in the calender as the calender is not used at all. The task is regularly checking (I think in a 5min interval) the next programmed event and is setting the timer accordingly. This should be respected with the timeout period before the computer goes to hibernate/stby. (e.g. I have set the LO timeout to 15min which gives the plugin 3 cycles just in case) "MP_Aufnahmen" is the event to control the wake-up task. So you have to enable of course that the task is allowed to bring back the computer from hibernate/stby. Therefore the task is not required to be started at system startup To my understanding "WHS_LO_erw" on the other hand is checking regularly the DB and handing over the the next event to "MP_Aufnahmen". This task is also starting "MP_Aufnahmen" in case it is not running. So, you have only to ensure to start "WHS_LO_Erw" at system startup. Btw Larry: Just out of curiosity: Why two seperate tasks? I guess there is a reasoning behind it? If I understood you right, one should avoid to manipulate the LO settings during record. This could have nasty side effects :) One should also not try to force manually the computer into stby during record as no next event is scheduled and the computer will not come back to life anymore until a LO client initiates a wake-up. I see here a potential weakness as you have also other conditions which may keep the WHS alive (specific tasks, IP addresses, etc..). But I have no idea currently to suggest some better solution Cheers, [/QUOTE]

Verification