Ecobee 3 Remote Sensors into ST

Devices & Integrations Connected Things
184

@gwithers105, @swamplynx and others,

The loss of ecobee authorization (and the need to re-authenticate) that you’ve been experiencing in the past weeks seems to be linked to 2 probable causes:

(1) ecobee servers seem to be less reliable by intermittence

I submitted a question to ecobee support about this issue. For the moment, they are saying that
there is no issue on their end. But, there is another ecobee developer who is
experiencing something similar to us (premature loss of authorization).

http://developer.ecobee.com/api/topics/ecobee-servers-outage

(2) There seems to be some scheduling issues on the ST side

Before last week, my Ecobee Device was pretty stable, but since some time last week, it looks
like there are some scheduling issues related to the refresh_tokens() method.

I’ve opened a SmartThing support ticket about it. In my logs, I see the same events sometimes
firing once, and other times, firing twice. As it’s related to the refresh_tokens() calls, ecobee
is seeing two close calls to refresh_tokens with few milliseconds apart, which causes some exceptions.

Here is a trace for Today in my IDE:

015-05-19 4:00:02.956 PM UTC
4 hours ago DEVICE verboseTrace refresh_tokens>expire in 59 m…
My ecobee Kitchen verbose
trace is refresh_tokens>expire in 59 minutes true
2015-05-19 4:00:02.898 PM UTC
4 hours ago COMMAND refreshChildTokens 2015-05-19 4:00:02.448 PM UTC
4 hours ago APP_COMMAND refreshChildTokens My ecobee Init sent refreshChildTokens command to My ecobee Kitchen true
2015-05-19 4:00:02.052 PM UTC

4 hours ago DEVICE verboseTrace doRequest>about to get with u… My ecobee Kitchen verbose trace is doRequest>about to get with uri https://api.ecobee.com/1/thermostat?format=json&body={"… true
2015-05-19 4:00:02.025 PM UTC
4 hours ago DEVICE verboseTrace api> about to call doRequest … My ecobee Kitchen verbose trace is api> about to call doRequest with (unencoded) args = {“selection”:{“selectionType”:"thermos… true

2015-05-19 4:00:01.973 PM UTC 4 hours ago DEVICE verboseTrace refresh_tokens>expire in 59 m... My ecobee Kitchen verbose trace is refresh_tokens>expire in 59 minutes true

2015-05-19 4:00:01.912 PM UTC
4 hours ago COMMAND refreshChildTokens

2015-05-19 4:00:01.760 PM UTC
4 hours ago APP_COMMAND refreshChildTokens My ecobee Init sent refreshChildTokens command to My ecobee Kitchen
true

And, sometimes, just once such as today at 3:00 pm UTC:

2015-05-19 3:00:05.451 PM UTC
5 hours ago DEVICE verboseTrace refresh_tokens>expire in 59 m… My ecobee Kitchen verbose trace is refresh_tokens>expire in 59 minutes true
2015-05-19 3:00:05.438 PM UTC

5 hours ago COMMAND refreshChildTokens 2015-05-19 3:00:05.225 PM UTC
5 hours ago APP_COMMAND refreshChildTokens My ecobee Init sent refreshChildTokens command to My ecobee Kitchen

There is a related ST thread about it:

I'll you let you know of any development on both fronts.

P.S. If you’re still experiencing connection loss with events firing twice in your events list (under the ST IDE), please contact SmartThings about it to increase this issue visibility. You’d need to set
the trace input parameter for My Ecobee Device to true temporarily to see the related events in your events list.

 Regards.