scheduler as a service ?

[pauldb38]

Hi i currently use windows Home Server and have Teldus installed on the server, i can control my items no problems but sometimes the server restarts for updates or for varios tasks it runs, i have put the scheduler in the startup folder but as i dont have auto logon set it only runs when i log in which isnt ideal. Can the scheduler be set as a service or if not is there any plans to make it a service ? Also sometimes when it starts up i loose all my events ?

[stefan.persson]

Hi,
Telldus Scheduler in windows is using Windows Task Scheduler for the actual scheduling. Telldus Scheduler acts as a front end, and adds tasks to Windows Task Scheduler. The tasks are set to run even if you're not logged on, no matter if Telldus Scheduler is in Autostart/Startup or not.

This works fine in for example WIndows XP, but we haven't tried it in Windows Home Server. It would be good if you could examine the created tasks directly in Windows Task Scheduler, or create a task manually and see if that runs when you're not logged in. The same thing about the missing tasks, have they disappeared from Windows Task Scheduler? If so, I have no idea why this could be at the moment.

[pauldb38]

Hi Stefan

Thanks so much for coming back to me since i upgraded to the latest version that was released i think yesterday ? i havent had the problem of missing schedules or at least so far so good. So am i presuming right here i could go into windows schedular and alter each event to run hourly or what ever time scale from the advanced tab ? I can see the events in the windows schedular so will give it a go ie not been logged in at all been well this will work and solves my problem lol. I will report back asap. Again thank you for coming back to me.

Paul.

[pauldb38]

After looking into this i think i have a issue with the windows scheduler i can see all the jobs and if i click on them and run them they work but if i leave them to run by themselves they look as though they are running well it says there running but there not sending the on / off commands to the sockets any ideas ?

[pauldb38]

Right i looked at some technet articles one of them suggested stopping the service and then deleting the log file , i have done this and bingo its appears to be working even without me logging in. I have taken this a stage further and Edited one of the schedules so at 22:00 it sends a off to one of the sockets in my daughters room but clicked on advanced tab and made it so it runs every 30 mins until 6am in the morning. If this works i'm going to be a really happy bunny because it means i have 1 task instead of allot of off tasks to do the same job. Will report back.

Then what would be great if this new Net version of the tellstick can actually tell me the status of each socket ie off or on ?

[pauldb38]

As promised i said i would post results of the Schedule tasks , I made as task in tedus Scheduler called Ebbs Off , this turned the main socket off in my daughters room. But knowing what my daughter is like she will switch it back on with the remote control , so i went into windows Scheduler found the job Ebbs Off opened it up , then went to advanced and told it to run every 30 mins from 22:00 to 06:00 and it ran like a charm. What would be really good is the have this in teldus scheduler so you can do it all in one plase. The thing i love about this is i have one Job instead loads of separate one for each command , just makes it so easy to set up and administer here the log file from window Scheduler on my windows home server .... As you can see it returns 0 at the end of every job to say its completed the task.

ebbs off.job" (DeviceSchedulerAgent.exe)
Started 24/09/2011 22:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 24/09/2011 22:00:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 24/09/2011 22:30:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 24/09/2011 22:30:05
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 24/09/2011 23:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 24/09/2011 23:00:05
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 24/09/2011 23:30:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 24/09/2011 23:30:05
Result: The task completed with an exit code of (0).
"Back Of TV Off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 00:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 00:00:00
"Back Of TV Off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 00:00:10
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 00:00:10
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 00:30:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 00:30:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 01:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 01:00:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 01:30:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 01:30:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 02:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 02:00:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 02:30:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 02:30:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 03:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 03:00:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 03:30:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 03:30:15
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 04:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 04:00:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 04:30:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 04:30:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 05:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 05:00:04
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 05:30:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 05:30:05
Result: The task completed with an exit code of (0).
"ebbs off.job" (DeviceSchedulerAgent.exe)
Started 25/09/2011 06:00:00
"ebbs off.job" (DeviceSchedulerAgent.exe)
Finished 25/09/2011 06:00:05

[stefan.persson]

Hello again,
Great that editing of the windows scheduler task itself makes things easier for you and that it seems to be running even when you're not logged on.

I'm not sure that we will implement repeatable events (like your every 30 minute-event) in the Telldus Scheduler. We're aiming for a new cross platform scheduler instead, and will probably not put very much more work into Telldus Scheduler. But when you describe your scenario, I realize that repeatable event can be of much use. We will consider it as a new feature.

TellStick Net will not know the on/off state of devices for sure, since there is no communication back from the devices. It will however receive remote control signals, so if someone turns on a light using a remote, its status in TelldusCenter will be updated too.