Enable verbose on ecobee2 (nothing else) and send me the log when you get a 500.

Enable verbose on ecobee2 (nothing else) and send me the log when you get a 500.

OK.

Maybe it will repeat tomorrow morning.

No such luck. With verbose on ecobee2 only, it functioned just fine.

 

I'll leave the verbose logging on, and check it from time to time.

 

Update: All is fine at 5:30 PM

Edited January 13, 20187 yr by larryllix

OK got it @ 7:18 x2,  7:20 & 7:23 AM. All created by selecting [ecobee2] nodepage.

 

Note: NodeLink is responding very slowly as log fills

    "message": ""
  }
} [ecobee2]
2018-01-14 07:20:11 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)
2018-01-14 07:22:46 - Ecobee Data: {
  "thermostatCount": 2,

logfile_2018-01-14.txt

Edited January 14, 20187 yr by larryllix

This error 500 from ecobee2 node webpage only occurs in the morning, when ecobee1 is on climate type = "Custom3".

 

Ecobee2 changes to climate type = "Home" at 5:00 AM every morning and stays on that climate type, until 5:00 PM.

After ecobee1 changes to climate type = "Home", then ecobee2 webpage behaves properly.

 

 

2018-01-18 06:44:57 - Error Processing Request: /ecobee2.htm (Index was outside the bounds of the array.)
 

Looks like NodeLink v0.9.1 fixed up the webpage error 500 for the ecobee2 during certain climate type slots! I checked during four consecutive mornings now, and it never fails.

 

 

Thanks a lot!  Looks like that  was a tough one to sleuth!