Some ST exceptions are thrown by the ST backend (not my code). However, they don’t affect the DTH’s normal processing. I’ve contacted ST support about it, but they haven’t indicated when they will be corrected (it’s part of a long list of issues I guess).
The TimeoutExceptions are due to the ST rate limiting and affect all cloud-to-cloud integration devices (not only MyEcobee device).
Hi Yves,
I’m having issues to talk to the Ecobee thermostat and I have enabled the Trace and get that error:
refresh_tokens>warning: local tokens still expired after refreshParentTokens() call
Is that related to the cloud to cloud issues you mentioned above?
Thanks
Please upgrade to the latest version (V5.7.7) and re-authenticate using MyEcobeeInit if there is a connection issue.
No other contributors are experiencing connection issues (myself included), but there maybe a localized issue with your ST account.
Refer to the troubleshooting section of My ecobee Device (item 6) at the ST community wiki on how to set up a watchdog in MyEcobeeInit smartapp. There are some ST scheduling issue from time to time that could interfere with the tokens renewal logic:
Right now my Theremostat and Sensors are working and showing temps, but they are not correct, it looks like they are not updating. Here is some logs, is this related to the database slowdown going on right now. Also, my vents using your keenvent manager is not working at all and was working fine 3 days ago.
As the ST platform is fairly technical and can be sensitive to changes (especially for cloud -to-cloud integration devices), I always offer my technical support as packages at my store. They sell as low as few bucks per month.
If you want peace of mind, you can either choose my support packages or (if you are tech-savvy) take some time to read my detailed instructions at the ST community wiki under the configuration and troubleshooting sections. Those sections are also indicated in the rft installation file provided with the download zip file.
I did a quick check of the many user sites all over the US and Canada that I monitor as part of my support packages, and none of them are experiencing any authentication issues which leads me to believe that you have either some localized ST account or configuration issues. Please take note that some of my contributors have multiple ecobee thermostats and remote sensors at their locations.
I got them and answered to all your questions. Your logs have ST exceptions, but nothing that can prevent MyEcobee device to run properly. Everything is working fine.
The smartapp does not create another device if an existing one is running (unless you’ve removed the MyEcobeeInit smartapp before which you should not do in this case.).
It will reset its authentication tokens, that’s all. Be sure to run it under the right shard.
Now, that you have another device, you need to review your smartapps to use the new one. There is no shortcut.
Regards.