settimeout - cleartimeout

[Neo Andersson 62]

Guys anyone can assist me, cause i am probably missing something evident..

 

I am using a simple formula , where this timer start when my Rain sensor detects rain, so it waits 3 sec and then prints the message

Please login or register to see this code.

later in the code i am testing the timer, and if exists i want to clear it

Please login or register to see this code.

However this always throws me this error

[19.01.2023] [03:23:22] [ERROR] [QUICKAPP51]: in Event({"type":"device","id":57,"property":"value"}) => ..: ./include/eventDefinitions.lua:113: Wrong parameter type, number required. Provided param '[Timer:31866 02:31:47 01/19/23]' is type of table

 

So this indicates that rainref is a table when i assign it to seTimeout, on the other hand Cleartimeout functions awaits number...

 

Then i open a completely new QA, just for testint this functionality..i am following the same procedure...and in the other QA the rainref is a number, so the Cleartimeout can work...

 

What the hell is going on???

 

Anyone any clue???

 

This is my simple testing QA, and in this the timer references are always numbers and not tables..

 

Please login or register to see this code.

 

 

 

 

[jgab 1,562]

Sorry, you seems to be using fibaroExtra in your code and there was a some code that fell out the last rewrite.

Either download the latest fibaroExtra (0.955) or add this line to your code

Please login or register to see this code.

I never use the fibaro.clearTimeout version, only clearTimeout (why type 7 extra characters?), so I didn't notice that the function was dropped.

 

Edited January 20 by jgab

[jgab 1,562]

The reason fibaroExtra is rewriting the setTimeout function is that it is more helpful then the standard version:

1. It will give a decent error message if the function provided to setTimeout crashes.

2. It can (optionally) warn if the timer runs late

3. It can specify times longer than 24.8 days....  <

Please login or register to see this link.

>

4. ....and the ref's printed representation contains the timer ID and the time it will expire. That was what you were seeing because the fibaroExtra's ref contains that extra information, but it requires that we use the fibaroExtra's clearTimeout to handle the ref. I had forgot to patch fibaroExtra.clearTimeout so it used the standard version that expects the standard ref.

Edited January 20 by jgab

[Neo Andersson 62]

4 hours ago, jgab said:

The reason fibaroExtra is rewriting the setTimeout function is that it is more helpful then the standard version:

1. It will give a decent error message if the function provided to setTimeout crashes.

2. It can (optionally) warn if the timer runs late

3. It can specify times longer than 24.8 days....  <

Please login or register to see this link.

>

4. ....and the ref's printed representation contains the timer ID and the time it will expire. That was what you were seeing because the fibaroExtra's ref contains that extra information, but it requires that we use the fibaroExtra's clearTimeout to handle the ref. I had forgot to patch fibaroExtra.clearTimeout so it used the standard version that expects the standard ref.

Thanks Jan, so when I use fibaroextra, it is better to use simpy clearTimeout(ref) formula instead of fibaro.clerTimeout(ref) right?...and the same goes to setTimeout()...?

[jgab 1,562]

57 minutes ago, Neo Andersson said:

Thanks Jan, so when I use fibaroextra, it is better to use simpy clearTimeout(ref) formula instead of fibaro.clerTimeout(ref) right?...and the same goes to setTimeout()...?

With the patch or the latest fibaroExtra it doesn't matter. Use what you remember  

[Neo Andersson 62]

On 1/20/2023 at 11:31 AM, jgab said:

With the patch or the latest fibaroExtra it doesn't matter. Use what you remember  

Jan, did you mean (0.945) for the lates update? Becuase you wrote 0.955 as for the lates version, and i cant find that file..

[Neo Andersson 62]

8 minutes ago, Neo Andersson said:

Jan, did you mean (0.945) for the lates update? Becuase you wrote 0.955 as for the lates version, and i cant find that file..

Jan, I have found the latest 0.955 version, and i changed every fibaro.clearTimeout and fibaro.setTimetout to simple clearTimeout and setTimeout, however now i am getting this error

 fibaroExtra.lua:139: attempt to perform arithmetic on a function value (local 'ms')

[Neo Andersson 62]

4 minutes ago, Neo Andersson said:

Jan, I have found the latest 0.955 version, and i changed every fibaro.clearTimeout and fibaro.setTimetout to simple clearTimeout and setTimeout, however now i am getting this error

 fibaroExtra.lua:139: attempt to perform arithmetic on a function value (local 'ms')

Okay, now i see, it is not compatible with Fibaro regular settimeout function i think...the argument order is different...

[jgab 1,562]

33 minutes ago, Neo Andersson said:

Okay, now i see, it is not compatible with Fibaro regular settimeout function i think...the argument order is different...

Well, for 10 years fibaro had only setTimeout(fun, ms) and then they added fibaro.setTimeout(ms, fun) and changed the order and the reason is unknown....

Both are there in QA's and fibaroExtra supports both.  Choose one. I prefer just setTimeout...

[Neo Andersson 62]

3 minutes ago, jgab said:

Well, for 10 years fibaro had only setTimeout(fun, ms) and then they added fibaro.setTimeout(ms, fun) and changed the order and the reason is unknown....

Both are there in QA's and fibaroExtra supports both.  Choose one. I prefer just setTimeout...

Actually the old order is not supported, as I wrote you above

Just now, Neo Andersson said:

Actually the old order is not supported, as I wrote you above

I mean setTimeout(ms,fun) doesnt work as you can see

[jgab 1,562]

15 hours ago, Neo Andersson said:

Actually the old order is not supported, as I wrote you above

I mean setTimeout(ms,fun) doesnt work as you can see

I tried to explain it in my post...

Fibaro have both

Please login or register to see this code.

defined. They chose to switch the order of the arguments in the later fibaro.setTimeout introduced - we don't know why.

fibaroExtra modifies setTimeout(fun, ms) but the modification of the original fibaro.setTimeout(ms, fun) had dropped.

Now they are both in fibaroExtra and you can chose whichever version you want. but of course you need to provide the arguments in the correct orders...