Not using the ecobee suite here, so it may be a little different since I am using the default. However, in my experience, you would want to use "until I change it" as the hold settings and then use a resume to return to the scheduled settings. Otherwise, you could try setting both the fan and the temperature using the dashboard if you need to change either.
@storageanarchy, would it be possible to add support for local API like HA does?
Even if that requires running some software outside the hub, I would prefer it over cloud API which is not reliable.
I'm having problems with the cloud approach. Sometimes a thermostat is in heating state (operating state, not mode) for example, at the same time the device on Hubitat shows the operating state idle.
This makes it impossible to have proper, reliable automations.
In my case it is even worse, because my thermostats are not connected to any equipment, I use the device state variables to control equipments via automations (floor heating and AC).
For example, when operatingState changes to heating, my automation turns on floor heating which is controlled via Zigbee switch.
I have set this up 3 weeks ago, and so far I had 4 problems. They made it impossible to use automations, and worse, sometimes kept equipment running when they shouldn't. Luckily I was not traveling and could notice after some hours.
Problems:
- Ecobee cloud outage for several hours (once)
- Mismatch between thermostat states and Hubitat device states, even while Ecobee's cloud API was online and my Internet was free of any issues (3 times so far).
There is a way to do local but you need home assistant and then use the home assistant bridge to bring the events into Hubitat. With this approach you don't need to use the Ecobee Suite.
I think he was asking if there was a way to add the homekit integration that Home Assistant uses to pull them in locally in a way that is native to hubitat (so he does not have to use Home assistant.)
I started up a home assistant instance on my Synology for just this purpose (and the My Subaru app integration). I can see why they do not do the My Subaru App on HE (the only way is via cloud, which is not really the intent of Hubitat). But, I am curious if it is a hardware limitation preventing the ability to pull in the HomeKit stuff as well. Not sure what a raspberry PI and a synology NAS have that Hubitat could not do also. (My guess is lack of numbers of users needing/wanting it?)
Edited to add... Looks like this may have JUST been addressed in the latest update IF YOU HAVE A C8 PRO(so possibly a hardware/memory issue reason)
1 Like
I sent a message to his post about how thermostats would be handled in this update. No reply yet. I guess we may have to by a C8 and try it out. But with me being unemployed right now can't afford to do it.
I believe that will eliminate the need to run something outside the hub to mimic a Homekit controller, making the change on Ecobee Suite to support local integration somewhat easier. My hub is C8 Pro by the way 
1 Like
If you decide to upgrade your hub, please make sure you buy a C-8 PRO hub, not a C-8, as the C-8 Pro has the necessary RAM and CPU upgrades to handle the additional workload.
1 Like
Has anyone looked into integration of the ecobee smart security?
Since simplisafe broke the API so long ago, I've been looking for a new monitored alarm that can integrate to hubitat.
I have noticed for a while, but I haven't posted until today. I have speech devices and I attempt to use Alexa (Amazon Echo) to make speech announcements, but it says "Simon says skill is not available right now". This application is the only application that does this. All the other applications seem to be working (weather and other apps). Has anyone else seen this?
I'm assuming no one else has seen this issue.
This appears to be the only application affected by this issue.
Is this still being supported? Great application, thank you for creating.
It is no longer supported but still works.
Oh, thank you!
I have looked at the built-in one to see how it is different. I'm assuming it is the basics.
There are now two built-in Ecobee integrations. One uses the Ecobee cloud API, similar to this community integration. As you mentioned, it has fewer features, but is probably a little more lightweight in terms of resource usage on the HE hub.
The other option Hubitat has for local (I.e. non-cloud) integration of the Ecobee thermostats is using the recently added HomeKit Controller on the C8-Pro hubs.
I am definitely not saying either of the built-in solutions are as full-featured as the Ecobee Suite integration. Just wanted to make sure you were aware of the options.
2 Likes
Thank you very much for the information. It is greatly appreciated. I'll try to see if I can run both simultaneously.
1 Like
Just a heads up I am still using this integration for some edge cases. As for the HomeKit integration I have tried 4 times now and still broken with some Ecobee's where you can't complete the pairing. Also there is the Native/Cloud API that Hubitat has had forever that is still out there.
Some odd thing has been hppening for many months now. I have a routine that circulates air overnight every hour for about 20min each time. BUT every few days it stops working and I have to open Ecobee Suite Manage and just press DONE and my circulations now work again. This is very annoying.
Anyone else have a similar issue?
No solution for you...
Question for you though - there is a feature built into the Ecobee thermostats to do exactly what you are using Hubitat and a custom cloud integration to accomplish. Why not simply configure the thermostat to do this directly?
2 Likes
I sometimes trigger it manually either by a Sharptools button or by a button beside my bed.
1 Like
