Timers and Pesters

I just upgraded to version 6 -some GREAT new stuff.

I'm trying to get timers working.

I created a timer device - used the timers plugin to load a time. and received this error:
-=-=-=-=-=-=-=-=-=-=-
Sep 17, 2013 2:31:20 AM
Timers and Pesters Error Error in plugin execution CallPluginFunc:

Traceback (most recent call last):
<type 'exceptions.TypeError'>: getActionConfigUiXml() takes exactly 3 arguments (2 given)
-=-=-=-=-=-=-=-
Is there a step by step example of what and how to use timers

Bob Ross

[jay (support)]

Can you give me the exact steps you go through to create the error? I can't seem to replicate the error here.

So....

When I did it again - Well, it worked ok

Sorry

Bob

Well - I may have screwed up

I had a timer running - I deleted the device. It deleted.

Now I get these in the Log.

Bob
=-=-=-=-=-=-=-=-

Sep 17, 2013 8:16:49 PM
error Timer loop error occured: -1700

Sep 17, 2013 8:17:04 PM
error Timer loop error occured: -1700

Sep 17, 2013 8:17:19 PM
error Timer loop error occured: -1700

Sep 17, 2013 8:17:34 PM
error Timer loop error occured: -1700

Sep 17, 2013 8:17:49 PM
error Timer loop error occured: -1700

Sep 17, 2013 8:18:04 PM
error Timer loop error occured: -1700

Sep 17, 2013 8:18:19 PM
error Timer loop error occured: -1700

Sep 17, 2013 8:18:34 PM
error Timer loop error occured: -1700

[jay (support)]

Hmmm - have you reloaded the plugin?

unloaded - reloaded

rebooted -

I did not unload, reboot and reload.

whats a 1700 error

Bob

So...

Another bit of data - I had installed and moved to the 6.01 folder "Indigo Timer Script" maybe that's the cause.

I removed "Indigo Timer Script", I unloaded "Timers and Pesters", killed the server. Restarted the computer.

Made a copy of my database, downloaded a fresh copy of Indigo. installed it.

Copied back my database.

Yep still get the -1700 error

Tonight, unless another idea, I will reload my 5.X database and start there

Thanks
Bob

[jay (support)]

Sorry, you're right, that 1700 error is from your timer script not from the Timers plugin. The script is being executed from some schedule that's executing every 15 seconds (see the log timestamps) so you'll need to find which one and disable it. That script isn't one of our scripts so I don't know what could be causing the error.

I put that in the thank you column - I now know what to look for!!

Bob