NodeLink v0.9.10 remaining bugs

[larryllix]

Running NodeLink v0.9.10 and the ecobees stats and Venstar are running fabulous now! Your hard work and persistence really paid off here!

I found a few times that NodeLink doesn't like to reboot but after repeated errors a reboot makes it runs for days and weeks without any errors.

This is one error that has happened every few days to a week and it seems to happen as the last poll of the day. It's no a big deal and doesn't seem to affect any performance but since I can capture it easily,  I thought it may give you clues for ny further digging you do on this.

Here is the webpage copy and a small snippet that co-incides with it from the log. The log doesn't seem to  reveal any other details but I included the last few polls up to it.

Thanks io_guy!!!

logfile_2018-03-22-trimmed.txt

[io_guy]

Can you send me a bigger piece of log so that I can compare the data from a successful grab to the failed index grab?

[larryllix]

Here is a half MByte. Those fies are over 11 MByte.I fell asleep several times with my finger on the shift PgUp buttons to delete the other 10 MByte! LOL It's a weird feeling to wake up and woder why you are glued to a keyboard.

 

 

logfile_2018-03-22.txt

[larryllix]

@io_guy

Another clue to these midnight errors for ecobees.

I get these for both ecobees, whenever I get them.
       2018-03-22 23:59:33 - Ecobee Timer Error - Index was outside the bounds of the array. [ecobee2]

This only happens when my logging level is Notice or lower and there is no logfile written that day, yet. It seems to be NodeLink trying to close a non-existent file, possibly.

The errors seem to be reported each night if  there is no other lines to report.

Thanks!

[io_guy]

Found the bug, will be fixed in next version.

[larryllix]

Found the bug, will be fixed in next version.

You da man!

Sent from my SM-G930W8 using Tapatalk