You can change thermostat modes, ie, off, heat, cool, auto.
You can change fan modes.
You can change set point temperature, but only until the next thermostat program change, ie, no hold indefinitely/choice.
I've read of potentially using geofencing to change temps-but again, it would be just until the next program change, right?
Depends on how you have manual temp/hold changes configured.
Hold Duration Options:
Until the next scheduled activity:
The hold will automatically end when the thermostat's schedule changes to a different activity or Comfort Setting.
2 hours / 4 hours:
The hold will automatically end after the specified duration.
Until I change it:
The hold will remain in effect indefinitely until you manually cancel it by adjusting the temperature again or selecting "Resume Schedule".
Decide at the time of change:
You will be prompted to choose a hold duration each time you manually adjust the temperature.
I just had a new AC compressor and air handler installed. One of my 2 units died last week. Long story, but I think it was the Nest thermostat I was running without a C wire that killed it. During the install, I asked to have the C wires connected to my air handlers so I could finally run Ecobee thermostats. I got a deal at Home Depot on 2 Ecobee Premiums and immediately got them installed and configured.
I did not use the Homekit integration to add them to Hubitat, but rather the community Ecobee Suite. I did add them to a dashboard, but to be honest, it is more so that I can quickly glance over and see what the thermostats are doing at any given time. I really don't find a need to control anything from the dashboard, once I had my schedules setup.
It sounds like your schedules are in the thermostat? You could try not using the schedules in the thermostat and just use the Thermostat Schedulers app instead?
Is there a way to set a hold in the driver, even if it is not exposed by the Thermostat Tile? Maybe you could use a button controller to make a hold button for the dashboard?
Just throwing stuff out there, I don't have Homekit or Ecobees.
You can use it with any thermostat, many thermostats do not have all the options someone may want for schedules. It is just an option if it gives you more functionality, or if you want to be able to update schedules from Hubitat. I wrote my own thermostat scheduler app that I use with T6 Pros, and I just turn off the thermostat schedules on the thermostats.
On an Ecobee, you can't technically disable schedules. You can set the thermostat to adjust the hold settings rather than directly disabling the schedule. By setting the hold action to "Until I change it," the thermostat will maintain the current temperature indefinitely, overriding the programmed schedule.
I used to use T6s, so I know how they work. Once the T6 is paired/joined to a Z-Wave controller/network, the built-in schedule is disabled.
"This thermostat will function as a normal programmable thermostat with the default program schedule if not included in a Z-Wave network. Once you include the thermostat in to Z-Wave network, it assumes to be programmed from your Z-Wave controller and the program schedule on the thermostat is turned OFF by default."
Yes, Thermostat Scheduler works perfectly with that kind of t-stat. Ecobee (which I now use), Nest (which I've previously used), etc., work best with their built-in schedules.
The temp up and down arrows are only good 'til the next thermostat change.
I wouldn't want to leave HVAC operation up to Hubitat, but more dashboard control could be nice.
They are not intended to be controlled by a hub/controller like a paired T6.
Thermostats like Ecobee and Nest are designed to essentially be set and forget schedule wise. They also can "learn" a schedule based on temperature changes made at the thermostat or via their respective apps.
This could be due to limitations of the Homekit integration. As I mentioned above, how manual temp change/holds are controlled is determined by how you configure that for each thermostat.