@storageanarchy Any thoughts on this? They thought it wouldn’t require any code changes on your end either. Just would require ecobee to add your apikey to their whitelist for new authentication.
Again, really appreciate all of your work on this app!
I am working with Ecobee Developer Support...hopefully I can resolve shortly.
What’s the best way to create a switch or switches to change the thermostat modes (home/away/night)?
Just be careful flipping switches - it can take a minute or two for the program change to be effected (due to the round trip timing to the Ecobee Cloud).
Thank you @storageanarchy. I tried this and it seemed overly complex and figured there was a better way.
I have four modes:
This is in sync with the alarm with presence so if everyone leaves the house, the alarm turns on and the thermostat changes to away mode. Likewise with the other options.
If the kids are home, I used the ‘work from home’ option to set it to cool the upstairs at night if they are there (we/parents are downstairs).
I also want to manually set the modes if we deviate from the normal hour programmed routine.
Here is what I did:
This seems a bit unwieldy since I will have to the same for the downstairs thermostat as well.
Am I missing something?
Edit: also of note - when the house mode changes on presence or timing, ecobee suite programs will respond accordingly and flip the responding switch ‘On’ (day/sleep/etc). What’s interesting is thankfully the ecobee suite flipping the switch to on doesn’t also trigger the ecobee suite to run into a loop....but I’m not exactly sure why. I had assumed it would.
You can simplify by having the switches change the Location Mode instead of the Thermostat Program - just create two different Night Modes. The thermostat will change when the location mode changes.
Also, you could use momentary virtual switches, set to turn off by themselves after a few seconds, to avoid the "turn off all other" rules.
Turning on the switches (as described in your Edit) probably DOES cause the ES Helper to run again, but it checks if the condition is already true and exits silently if it is.
True. I set it up that way because I can look at the switches and see what mode each thermostat is.
You can also see the actual thermostat program by looking at the attribute "schedule" for each thermostat.
How would you expose the attribute as a separate device?
I don't know about ActionTiles, but in Hubitat Dashboard, you can create a tile that displays ANY attribute for ANY device.
Sorry....should have shared that I'm pushing everything to the homekit via makerapi and homebridge. You are right....in a dashboard you just specify the attribute you want. That doesn't quite work for homekit - but i'm looking into how that can be done....
Any luck? Appreciate you looking into this!
Fixes & enhancements:
demandResponsePreheat and demandResponsePrecool eventsThese updates are recommended for all users
Thank you, Barry! I was able to enable it just now. As I mentioned a few weeks back in the SmartThings thread, I was just forced to enable ecobee 2FA to use their SmartCamera.
YES!!! So excited for the new Authentication! It works great! Thank you for doing that!
Did something change with thermostat driver? I do not seem to have a set thermostat setpoint button / command in the ui anymore.
edit to tag @storageanarchy
Thank you for this amazing app! Definitely going on load this up on my C7
I needed some clarification on this part of the documentation
One side-effect of the updated approach is that during the inital startup period update cycles will generally take longer, as the initial datapoints are saved for future changes comparisons. After this startup period (usually 10-20 minutes, dependent on the number of devices you have), things will stabilize and generally cycle times will shorten significantly.
It talks about startup period of 10-20 minutes. Is it referring to hub startup? Will just installing this app cause massive slow downs in hub reboot times?
The quoted discussion is regarding the VERY FIRST INSTALLATION, when Ecobee Suite has to initialize its internal states and variables. After 10-20 minutes, you should see cycle times of around 2-5000ms (2-5 seconds) - you can watch this in Live Logging for Ecobee Suite Manager.
The code has been extensively optimized to place the least load possible on your hub, and it should not noticeably lengthen reboot times. That said, the suite has a storage footprint that undoubtedly will increase the size of the backups (and a backup is made each time you reboot). If it turns out to be too much for your liking, you can simply disable and remove everything.
I haven't noticed any significant slow down after the initial matching process.
A+
well i read the documentation and it is not part of the driver. I must be missing something as using set cooling setpoint seems to set incorrectly.
Download the Hubitat app
