Here is my post about it in the following thread:
Hi @slagle, @jotto, @jarettp, @dvanzuiden,@stvdano,@benmctee
FYI, after some testing on my end, I have observed the following facts:
(1) Before the peak of connection issues that we’re all experiencing with my custom Ecobee Device now, I had been able to correct any connection issues by re-authenticating with ecobee, and this action would “reset” the connection and any connection issues would disappear after.
(2) Now, even if I try to “reset” the connection by re-authenticating with ecobee, the connection issues stick. The only way is to uninstall the Service Manager and delete the device to create another one.
Also, since yesterday, somebody has pointed out to me that the ecobee’s access token expiration time is now expressed in seconds (not in minutes like before)…
This is a recent change that was implemented just yesterday:
The change does not explain all the connection issues in the last week, but it explains the fact that I can no longer ‘reset’ the connection with ecobee since yesterday.
There may be also more rate limiting done either on the ST or the ecobee side that I’m not aware of.
I implemented more defensive coding into My Ecobee Device, MyEcobeeInit and ecobee3RemoteSensorInit to avoid connection issues in the future.
MyEcobee device at home has been now stable for a while, and hopefully it will work also for anybody
who uses it.
Please let me know of any issues, especially with ecobee3RemoteSensorInit as I cannot test
it at home (I do not have any ecobee3’s remote sensors).
So, in order to correct their current connection issues, ST users need to
(1) Remove My Ecobee device and any ecobee3’s remote sensors from all smartapps
(2) Uninstall MyEcobeeInit, ecobee3RemoteSensorInit
(3) Get the latest MyEcobeeDevice, MyEcobeeInit and ecobee3RemoteSensorInit code at my beta branch
(4) Re-execute MyEcobeeInit and ecobee3RemoteSensorInit