new error

[10der 832]

Hi!

 

after update, I can see a new error

 

[DEBUG] 13:05:42: Scene started... [DEBUG] 13:11:19: [1;31m2018-03-25 13:11:19.023551 [ error] timer handler failed with error

 

Hey, Fibaro, what is it? the similar error I was seen some weeks ago on Polish forum... 

 

thnak you!

 

 

[DEBUG] 13:05:42: Scene started...
[DEBUG] 13:11:19: [1;31m2018-03-25 13:11:19.023551 [ error] timer handler failed with error

[10der 832]

is anybody home?

[henri-allauch 4]

Hello  @10der

Yesterday 27/04/2018 for the first time since 2 years I have this error.

[DEBUG] 19:26:00: [1;31m2018-04-27 19:26:00.248397 [ error] timer handler failed with error

Last update FirmWare 4.170    Le 25/03/2018

Edited April 28, 2018 by henri-allauch

[Jamie mccrostie 82]

Hey @10der

@henri-allauch

Did you guys ever find out  anymore about this error? Appeared on a main event scene today which has worked perfectly since xmas.

thanks

 

Edited June 18, 2018 by Jamie mccrostie

[10der 832]

I can reproduce it.

 

Please login or register to see this code.

this script dead after 39- 60 sec after start with this error. My IMHO root issue in implementing and combination setTimeout function + net.HTTPClient.

 

 

 

Edited June 18, 2018 by 10der

[Jamie mccrostie 82]

Hmmm the same scene i have running on 2x HC2s

one has error one not

Scene has run since xmas no problem 

[10der 832]

¯\_(ツ)_/¯

[Jamie mccrostie 82]

27 minutes ago, 10der said:

¯\_(ツ)_/¯

 

Is that Klingon?

Ahrrr Shrug 

Edited June 18, 2018 by Jamie mccrostie

[10der 832]

2 hours ago, Jamie mccrostie said:

 

Is that Klingon?

Ahrrr Shrug 

 

 

Yes, cap. Worf.

[henri-allauch 4]

Please login or register to see this code.

Mysteries

[10der 832]

11 minutes ago, henri-allauch said:

No I did not change anything, and the error is no longer apparent !!!!

 

heisenbug. it is difficult to recall and localize this error because it is not permanent and occurs from time to time.

[cag014 731]

On 3/25/2018 at 3:40 PM, 10der said:

Hi!

 

after update, I can see a new error

 

[DEBUG] 13:05:42: Scene started... [DEBUG] 13:11:19: [1;31m2018-03-25 13:11:19.023551 [ error] timer handler failed with error

 

Hey, Fibaro, what is it? the similar error I was seen some weeks ago on Polish forum... 

 

thnak you!

 

 

[DEBUG] 13:05:42: Scene started...
[DEBUG] 13:11:19: [1;31m2018-03-25 13:11:19.023551 [ error] timer handler failed with error

Saw this error several times during last few weeks and have asked about it fibaro's support

Here is support reply

Hi,
This error can be related to one of “services” in the system (this depth in the system) or RAM usage (your HC2 get temporary out of available RAM memory)

If issue appears again we will investigate.

Have a nice day.

 

Edited June 18, 2018 by cag014

[cag014 731]

After several tries I came to conclusion that this error indicates that there is a real error in the code. The problem that the system somehow unable to identify and provide correct description of the error and shows generic error

  [1;31m2018-04-27 19:26:00.248397 [ error] timer handler failed with error.

In all cases the problem was that some variable value turned to  "nil" during code execution and  this generates this generic error. That's why this error appears time to time.

 

So please add more debug information at your code to catch the problem.

Going forward I hope Fibaro team will fix this issue and will provide correct error description...

Edited June 26, 2018 by cag014

[tinman 1,070]

On ‎6‎/‎18‎/‎2018 at 9:04 AM, 10der said:

 My IMHO root issue in implementing and combination setTimeout function + net.HTTPClient.

 

no, it does have something to do with nil values, you have to check results before formating/using them, that line of code mak no sense:

 

Please login or register to see this code.

it should be 

 

Please login or register to see this code.

 

Yes, error message is bit strange, but it's just because it gets killed middle of time

[cag014 731]

1 hour ago, tinman said:

 

no, it does have something to do with nil values, you have to check results before formatting/using them, that line of code make no sense:

You're absolutely correct, but I expect to receive correct error information and not some generic note that doesn't help to identify the problem.