Tracking asynchronous plugin jobs

Plugins & Plugin Development General Plugin Discussion
1

Seriously technical question, mostly pointed at MCV developers…

I’m happily running asynchronous jobs in my plugin (using and in the I_* file, and returning 5 until the job is done, then returning 4). I can see from the 04 logs in LuaUPnP.log that this is working.

But!

According to the wiki (http://wiki.micasaverde.com/index.php/Luup_Control#Luup_jobs), I should be able to track these jobs from the lu_status HTTP request, in the Jobs field for my device. I can’t. That array is always empty for plugin jobs:

Jobs: [ ]

(Though it does contain Z-Wave jobs, I notice.)

I can track the job using this undocumented URL: http://vera:3480/data_request?id=jobstatus&job=[i]jobid[/i]*, which returns something like:

{ "status": 4, "comments": "" }

So, two-part question:
(a) Is the wiki correct and the Jobs field in lu_status(2) supposed to contain my job, even though it doesn’t?
(b) Is the undocumented jobstatus call Internal And Subject To Change, or can I safely rely on it?

1.1.1245, if that matters.

  • It’s amazing what you learn by running strings on the LuaUPnP binary combined with bashing variations into a browser and sheer dumb luck.
2

I am curious to know if the jobstatus link is something we can use. Hopefully MCV can respond and give us our insite.

  • Garrett
3

futzle,

I got the answer to your second question: the jobstatus call is permanent. I’m going to document it this week (I hope).
I didn’t ask about your first question, because Aaron was busy and that requires some investigation, but I will try to find an answer to this too.

4

Thanks. That’s all I need for now. It’s in the production Caddx alarm plugin. :slight_smile: