Thanks for including Ask Alexa Message Queue capabilities to your app as well!
Great! Glad you got the HOLD options implemented. Seems to be working well so far.
UPDATE: Ecobee Thermostat v1.2.1
1.) Ensure that Mode buttons are re-enabled after Vacation Hold ends
2.) Optimize button enable/disable - remove
isStateChange: true for all button updates
Get the latest
ecobee-thermostat.groovy from the repo…
Thank you for this device handler. I installed an Ecobee3 last week and it works great!
Hello, I just installed your device handler and smartapps. When I launch Ecobee Connect and select “ecobee Authorization” I get the following error. Clicking on Retry yields the same result.
Any guidance would be greatly appreciated.
Could you please share what Ecobee (Connect) logs to Live Logging in the IDE when this happens?
I just double checked on both iOS and Android mobile devices and it works fine for me…are you still having problems?
I got that screen earlier (on a different device) and refreshed and it worked. I think it was from yesterday’s hub firmware update.
UPDATE: Ecobee Thermostat v1.2.3 and Ecobee (Connect) v1.2.3a
Displays when thermostat is overcooling to reduce humidity
Displays when dehumidifying while cooling
Handles “Auto Away” and “Auto Home” (sensor-driven modes) - these behave same as Hold: Away/Home
Significant optimizations of the event update handler
Misc bug fixes & typo corrections
Get the latest
ecobee-connect.groovy from the repo…
Looks great… Will try it once i’m back home next week
Quick q - any issues for the folks using Keen vents using Kneect with this SmartApp ?
Nope, there shouldn’t be any problems. This DTH will work essentially the same as the Ecobee webApp - it can control/change things, but it basically reports/displays whatever the Ecobee API presents.
It doesn’t seem that you need this, but the Suite also includes a SmartApp that will open/close vents (Econet and Keen) based on the room temperature and the thermostat’s target temperature - much like the Keen app will do. I would, however, advise against using both to control your vents, if only to prevent the vents from cycling due to different algorithms, etc.
thanks for the quick reply… Have a great weekend
51a8d103-774c-419e-81ff-ddc84d6d196c 6:00:32 PM: error java.lang.RuntimeException: Unexpected status code 400 from global /clients/null with status text @ line 218 51a8d103-774c-419e-81ff-ddc84d6d196c 6:00:31 PM: error java.lang.RuntimeException: Unexpected status code 400 from global /clients/null with status text @ line 218 51a8d103-774c-419e-81ff-ddc84d6d196c 6:00:30 PM: error java.lang.RuntimeException: Unexpected status code 400 from global /clients/null with status text @ line 218 51a8d103-774c-419e-81ff-ddc84d6d196c 6:00:28 PM: error java.lang.RuntimeException: Unexpected status code 400 from global /clients/null with status text @ line 218 51a8d103-774c-419e-81ff-ddc84d6d196c 6:00:24 PM: error java.lang.RuntimeException: Unexpected status code 400 from global /clients/null with status text @ line 218
Updated to 1.2.3a first, getting a repeat error on every refresh.
Thanks for looking into this.
Did you enable OAuth for Ecobee (Connect)?
Seems like I missed that part in the documentation. Enabled OAuth and everything worked. Is it possible to add a check for OAuth enablement in the mobile UI for bone heads like me?
Thanks for your help.
The problem is so prevalent that I’m adding an error check that will note the probable cause to Live Logging on the failure.
UPDATE: Ecobee (Connect) v1.2.4
- Catch OAuth initilization errors and suggest probable cause (OAuth not enabled) in Live Logging and in Mobile UI
NOTE: Tested & Verified, August 13, 2017 @ 9:00am
As a recent nest convert, I find myself missing my scheduled fan run time. I used it every morning for about 30min as I got ready for work. The default functionality of running so many minutes every hour is too aggressive for my taste.
Is there a work flow that I’m missing to accomplish the same thing with ST?
Two quick solutions:
Using Ecobee (no SmartThings required): Create a program that is the same as your Home program, except that it has the Fan set to On (the default Home program has the fan set to Auto). Edit your schedule to run this program at the desired time of the morning. Limitations: Can only start and end the program on the hour or half hour (Ecobee limitation)
Using SmartThings: Use WebCoRE to call fanOn() at the desired time, then have it call resumeProgram() 30 minutes later (changing the fan from Auto to On causes a Fan Hold to be set - the Hold will be in effect for the specified default Hold Action).
I’ve been asked for other time-based events, so I will add this to the backlog. It’s a little complicated by some of the SmartThings limitations on timers, but not impossible.
- Here’s a hybrid approach: Create a new SmartThings Routine that does something innocuous - turn on a light that’s always on (or create a dummy switch - the Routine needs to do something). Set the routine to run at a specific time (or on whatever initiator you want). Then create a Mode/Routine/Program Helper SmartApp from within Ecobbee (Connect). Set it to run whenever the newly-create Routine executes, and have it change the thermostat program to your normal program (e.g. Home), but with the Fan On. Set the hold type to “until next change” if you normally leave the house (and have things change to Away), or to Specified Hours / 1 hour (unfortunately I haven’t implemented minutes support yet). OR You could create another routine that runs 30 minutes after the first one, and have a separate Helper SmartApp set the Ecobee Program to Home, with Fan Auto.
Fun with Modes, Routines and Programs!