afterSec(x)

bdormael · Post by **bdormael** » Saturday 05 August 2017 11:21

Maybe a stupid question:

for devices we have:
device.switchOn().afterSec(10)

Can't we have this also for variables like:
variable.set('my_value').afterSec(10)

In normal LUA you can do this for variables

dannybloe · Post by **dannybloe** » Saturday 05 August 2017 22:38

Oh I didn't know that. I'll add it.

bdormael · Post by **bdormael** » Sunday 06 August 2017 7:31

dannybloe wrote:Oh I didn't know that. I'll add it.

Thx

Verzonden vanaf mijn iPad met Tapatalk

mikkel75 · Post by **mikkel75** » Monday 14 August 2017 12:50

I'm also looking for this feature - is it added now?

Thanks!

dannybloe · Post by **dannybloe** » Monday 14 August 2017 19:11

Not yet.. just got back from vacation. Catching up here...

mikkel75 · Post by **mikkel75** » Wednesday 23 August 2017 9:46

OK...but pleaaaaaseeee implement this soon - I really need it for my alarm system

Thanks...

dannybloe · Post by **dannybloe** » Wednesday 23 August 2017 9:51

I'm testing it right now on my production machine. I want to have it running for a little before we start creating Pull Requests.

mikkel75 · Post by **mikkel75** » Wednesday 23 August 2017 14:34

Sounds really good...thanks so much for doing this...

DewGew · Post by **DewGew** » Friday 25 August 2017 11:51

Is it possible to use time option to a function also? eg. " myfunction().afterSec(delay)"

dannybloe · Post by **dannybloe** » Friday 25 August 2017 12:07

No, that's handled by the Lua interpreter. Calling a function has nothing to do with Domotic's scheduling support.

mikkel75 · Post by **mikkel75** » Tuesday 29 August 2017 10:13

dannybloe wrote: ↑Wednesday 23 August 2017 9:51 I'm testing it right now on my production machine. I want to have it running for a little before we start creating Pull Requests.

How's the testing going?

dannybloe · Post by **dannybloe** » Wednesday 30 August 2017 8:21

Taking longer than expected as quite some changes have to made in the Domoticz event systems. Still working on that.

mikkel75 · Post by **mikkel75** » Wednesday 30 August 2017 9:37

OK - thanks again for your effort!

mikkel75 · Post by **mikkel75** » Thursday 07 September 2017 8:41

Any progress?

mikkel75 · Post by **mikkel75** » Monday 09 October 2017 11:42

Are we getting closer to a solution?

dannybloe · Post by **dannybloe** » Monday 09 October 2017 19:37

Eh.. it is released in 3.8551 so give it a try.

bdormael · Post by **bdormael** » Wednesday 11 October 2017 14:22

dannybloe wrote: ↑Monday 09 October 2017 19:37 Eh.. it is released in 3.8551 so give it a try.

Working perfect, thx

mikkel75 · Post by **mikkel75** » Tuesday 16 January 2018 13:10

Question:

Is it possible to cancel an .afterSec() before it is activated (the time has passed)?

The use-case is for an alarm system, where I use afterSec to time from when the PIR is trigged to when the siren should start. I want to be able to cancel the siren if the alarm is disarmed.

Thanks,
Mikkel

dannybloe · Post by **dannybloe** » Tuesday 16 January 2018 13:13

In the upcoming dzVents 2.4 you can do device.cancelQueuedCommands(). Until then you can try device.setState(device.state)).

mikkel75 · Post by **mikkel75** » Tuesday 16 January 2018 14:35

Hi,

Thanks for the quick reply.

I do it like this:

domoticz.variables('SoundSiren').set('0')

But that doesn't cancel the afterSec() - it's still called after the time-out.

Any other suggestions that might work?

Thanks.

afterSec(x)

afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Re: afterSec(x)

Who is online