V0.9.13 - new ecobee security?

[larryllix]

This error just started last night. Although I get a stream of these errors  reported now, the data still gets through to ISY mostly.
Complaints about new tokens received from ecobee have continued today despite a NodeLink reboot.

It appears as if  ecobee is changing their access security maybe.

2018-05-09 23:05:01 - Ecobee Web StatusError - InternalServerError [ecobee1]

 

logfile_2018-05-09.txt

[larryllix]

This appears to happen once every hour now. Still functions OK in ISY though.

2018-05-10 06:37:20 - ISY Node Server config detected (profile 1)
2018-05-10 06:37:29 - Ecobee: New tokens received from ecobee.com [ecobee1]
2018-05-10 07:37:39 - Ecobee Web StatusError - InternalServerError [ecobee1]
2018-05-10 07:40:39 - Ecobee: New tokens received from ecobee.com [ecobee1]
2018-05-10 08:40:48 - Ecobee Web StatusError - InternalServerError [ecobee1]
2018-05-10 08:43:48 - Ecobee: New tokens received from ecobee.com [ecobee1]

[io_guy]

Turn down your log level.

[larryllix]

6 hours ago, io_guy said:

Turn down your log level.

OK Thanks. Which way is down?   IIRC, I had both screen and file logs at Notice.  Currently I have webpage at Notice and file at Debug.

Did I expose something that  really doesn't affect performance/function?

I assume different levels record more or less severity of normal data to errors.

[io_guy]

https://en.wikipedia.org/wiki/Syslog#Severity_level

Those errors show up at >= 6.  They're information only - the ecobee tokens expire every hour.

[larryllix]

12 minutes ago, io_guy said:

https://en.wikipedia.org/wiki/Syslog#Severity_level

Those errors show up at >= 6.  They're information only - the ecobee tokens expire every hour.

OK cool!

I wondered about that as the token has a 3599 parameter with it triggering a seconds per hour idea. Strange security.
The error report line just before every token issue made me think something was wrong there.

 

Thanks