does the ecobeechangemode resume at the next scheduled event?
Meaning, if I leave the house, it goes to “away” and say at 4 I have a program scheduled to run, but wont be home until 5, will it begin to run at 4 or wait until I get home?
Hi Kavvy,
You may want to read the information I provided at the wiki about the holdType parameter.
See the configuration section (item 3b) under:
http://thingsthataresmart.wiki/index.php?title=My_Ecobee_Device#Configuration
In brief, it’s up to you. You can set it up both ways.
That is done via the Ecobee configs, right? Ive done the “Hold until next scheduled…” but I wanted to make sure if your app sends it to “away”, that the ecobees next programming (scheduling) wont be affected.
Im not a programmer, so parsing through the API config parameters is a bit cryptic. While Im sure I could pull the answer from there, trying to wrangle 3 kids at nap time, while determining if my Ecobee will resume a scheduled event, regardless If Im home or not, is a bit of a handful.
As specified at the wiki, you need to set the holdType preference to nextTransition. It’s a configurable
parameter under:
https://graph.api.smartthings.com/device/list when you click on MyEcobee Device.
Regards.
P.S. I hear you about the kids, I have 2 boys (9 and 12): they keep me busy as well.
While they were asleep, I configured it appropriately.
Looking forward to your permanent workaround.
Yves,
I’m at 4 days without a token loss. I am still on the last batch of beta code and will switch over tomorrow. Good work sir! You seem to have outsmarted the platform bugs. (Knocks on wood to avoid being the jinx of the group!)
Don’t worry think I’m the jinx. I upgraded and just a few hours later wouldn’t refresh and getting token expiration messages. Have pollster running every 10. 
Hi, just re-execute steps 6c to 8 in the instructions file.
During my beta testing, I’ve seen that, in some cases, just updating the code may have some ripple effects on the http connection.
Regards
Im going to stick with Ecobeeinit Service Manager even if it has been proven less reliable than the standalone device.
Both solution eventualy going to loose token.
and it is so much easier enter username for all thermostats in cellphone app, then clicking thru pages and redoing pins for each thermostat.
Hello,
It’s up to you but, I’ve done some beta testing with a ST user with 6 ecobee3 thermostat at his home, and, and also based on my testing at different locations, the standalone device is much more robust.
In fact, I haven’t experienced any connection issues for days with the new code at my home since I installed it. With the Service Manager, it’s practically every couple of days (and sometimes more often).
My 2 cents.
EDIT: Also, do not use pollster against the device if you use the Service Manager as the 2 smartapps will conflict with each other. Use a 5-min polling interval to avoid any authorization tokens lost.
ok, is this like the standard reboot it 3 times support suggestion ;)? the token was expired at the time I updated the devicetype code, so after doing so I generated a new pin and gave it to ecobee. Refreshed and confirmed that it was working but few hours later expired again. I’ll try it one more time.
Hi, which version are using? Just to make sure that you have the latest version.
3.8.6 of the My Ecobee Device, not using MyEcobeeInit.
Ok, could you send me some logs whenever you have a chance?
Please send it to my email address: services@maisonsecomatiq.com
Regards.
sent…20 characters
Hi, If you’re planning to use MyEcobeeInit (Service Manager), just make sure to
have the lastest version that I just uploaded (v2.7.7) at the temporary google drive link.
This version will allow you to reset your authorization tokens after the re-login at ecobee.
The previous version was not doing it properly. You then don’t need to reinstall the device.
Regards.
EDIT: please contact me at services@maisonsecomatiq.com for any issues/questions related to MyEcobee device.
Closed per OP request