What's the best way to handle a long-running script?

[Timmiej93]

I want to create my own wakeuplight script, which should be interruptible.

I started off writing a script that just queues up a lot of tasks by using light.dimTo(x).afterSec(y), with incrementing values for x and y, but this doesn't seem to work that great. As far as I know, this is also not interruptible, and will continue until all queued commands have been executed.

So my questions:
Is it possible to interrupt / cancel items queued by .afterSec(y)?
Is there a better way to have the script running for the entire duration, with the possibility to interrupt it?

[dannybloe]

yes, either you wait for 2.4 which has a cancelQueuedCommands() on the device. Until then reissuing a command should clear the queue (device.setState(device.state)). But I'm not sure that always works as expected.

Other than that you can create a timer trigger like every minute and check against a time stamp (perhaps you set it in a uservariable in the gui) and read that value in your script. Perhaps in combination with persistent variables (see dzVents doc).

I know that allangam has scripts for exactly this situation. He's on the forum as well.

[emme]

yes, either you wait for 2.4 which has a cancelQueuedCommands() on the device.

[Timmiej93]

^^ Couldn't express it any better than that.

On the topic of allangam, I can't find him for the life of me, unfortunately. I think I'm gonna have to go back to bash for now (the horror...)

[dannybloe]

Oops, his forum name is BakSeeDaa

[Timmiej93]

That probably explains why that name came up a lot, lol. Thanks for the tip, I'll look into it.