[RELEASE] Initial Setup for Ecobee3 & 4, Smart-SI, EMS, Smart-02 thermostats - My Ecobee Device

Devices & Integrations Community Created Device Types
, ,
45

Hi @drshaw,

You usually do not need to delete your device type and device(s) to solve this kind of issues, I would try first to re-authenticate.

Also, if you have a lot of SocketTimeoutExceptions, I’d try to reduce the polling interval in MyEcobeeInit and ecobeeRemoteSensorInit smartapps.

And, nothing prevents you to use the official ST integration. Of course, my smartapps only work with My Custom Ecobee device.

However, you may encounter the same issue: I’ve already opened a ticket about the ST-ecobee cloud-to-cloud connection issues, and ST support responded by this reply:

Chris Porter (SmartThings)
Jun 30, 6:02 PM

Hi Yves,

Thanks for letting us know what you are seeing. My developers have been aware of this happening for a little while now also, and have worked on it. I will let them know your thoughts about it being the security timestamp being outdated.

I don’t have an ETA around implementing a revision to the code, but developers do currently know it is not working consistently for users, and are addressing it.

Thanks for the heads up, and the suggestions.

-Chris P.
SmartThings Support

If you have a lot of those cloud-to-cloud connections issues, please also open a ST support ticket, and at one point, with a high number of ST open tickets, this issue will surely be escalated to the Engineering team.

@tslagle13 may also help in that matter.

P.S. As I wrote earlier this thread, these exceptions are related to poor cloud-to-cloud connectivity between ST and ecobee. The fact that Ecobee requires a regular refreshTokens() (every 59 minutes) also contributes to it, as the refreshToken can be lost after a while.

I also think that the cloud-to-cloud integration issues are not only specific to ecobee, as per this thread: