I created a Rule to switch on the fan for 15mn when temperature is over 25 degres outside.
But everytime the rule runs, it changes the requested temperature to the current one.
I tried to add resumeProgram() after switching back the fan to auto but it doesn't change the fact that it holds a new temperature.
is there a function to go back to the default ecobee settings ?
The Ecobee internal settings take precedent over their 3rd party integrations. You should be able to set up how your preferred 3rd party changes are handled within your thermost's settings.
But I thought that ResumeProgram() will have resumed my schedule. Which looks like is not the case.
Do you know if there is a way to change a value and then resume to the current schedule and temperature value ?
Go to Ecobee and set the thermostat to "until the next scheduled activity"
https://www.ecobee.com/consumerportal/index.html#/devices
Yes that's my current setting. But as my next activity is at 10PM it means that just by switching on the fan for 15mn it will hold a new temperature setting for the day.
I was in the hope to have a way to reset back to normal
I just bumped into this same error. What's weird is I got it to work one time when experimenting by switching between using the option "FanOn" to "SetThermostatFanMode", but that had nothing to do with it because either option triggers the same problem again.
I set up a routine to run the fan if one room's temperature gets a few degrees hotter than the other.
Instead of the thermostat just displaying "Fan is Running" like what it would do if you turned on the fan from the thermostat, it instead behaves as if I've changed the thermostat temperature to the current temperature.
The fan does run, but it erases the previously manually set desired temperature. I already have it set to temporary hold, so it will go back to program eventually, but something's not working properly with the fan control any more.
For me, resumeProgram does bring it back to the schedule, but the fan stops running.
fanCirculate seems to do nothing, so any of the options just change the state thermostatFanMode - so I don't think there's any way for me to turn on just the fan via Hubitat that's working
I took some photos to show the issue.
If you set the fan to run from the thermostat, here's what it shows:
'
If you set the fan to run from Hubitat, it behaves differently (but the fan does run)
'
But if a temperature is requested on the stat:
'
and Hubitat sets the fan to 'on', it appears to clear the temperature request
Are we the only 2 people with this issue?!
I was wondering why my ecobee was showing a hold temperature seemingly at random until I went and investigated my rules.
Same idea, same symptoms-- I want it to turn on the fan (and make no other changes) if the temperature in the main room gets warm (I have a wood stove there). However, doing so turns on the fan and causes a temperature hold.
Have you guys found any work around?
1 Like
Sadly not!! I was expecting this would have been fixed since we're using the official integration but perhaps not many people are using the fan-only feature.
My Ecobee integration with HE is done via Home Assistant (BTW, 100% local, plus HADB. For some reason (and who knows why) Ecobee goes into Hold mode immediately after anything is/was charged either manually right from the touch screen or by command(s). It looks like this is known behavior because Home Assistant has a "Thermostat Clear Hold" button:
My work around is a very simple rule running on HA which is pressing that magic button when Thermostat reports any changes. There is an extra switch to Enable/Disable this rule in case I want Hold to be active.
1 Like
Unless I've misunderstood, I'm just not sure if that's the same.
HE lets you choose how long to hold for when you set a temperature (and this setting is also available on the thermostat i.e. forever, or until the next scheduled program), is that what you're talking about?
On the stat itself, if you set a temperature and then manually turn on the fan, the fan runs and the requested temperature remains.
On HE, if you set a temperature and then manually turn on the fan, the fan runs but it changes the requested temperature to the detected 'current' temperature.
Maybe I misunderstood as well.
In my case any changes maid to tstat (either locally or via command) immediately turns on "Hold" mode which is absolutely not desired. So I created a little rule which turns it off.
For what it is worth, changing fan modes via Homekit also puts the Ecobee thermostat in hold mode. So it is not specific to Hubitat.
I have to do a clear/cancel hold to clear it after I'm done manually running my fan (see two posts above, that's basically how I do it too).
This looks like an Ecobee Tstats feature and sure, it is not HE related.
I am only doing this on a small scale and for a short time, but there is my work-around. I happen to use webCoRE, so I use "piston" to describe a "rule". Still room for improvement, but it has been able to reliably recover from a mix of situations this morning.
Piston Summary
Piston #1: Sets the current thermostat program (in my case: sleep, home, away, office) based on a number of triggers and conditions. This is stored as a hub variable string. This piston calls Piston #2.
Piston #2: Reads the current program ID from Ecobee. If current program ID does not equal the hub variable (i.e. "hold"), then set the program to be the hub variable.
Piston #3: Sets the Ecobee minimum fan on time per hour based on various triggers.
Piston #4: Set the Ecobee fan to stay on for a fixed time based on various triggers. When the fan turns off, it calls Piston #2.
Edited for grammar.
I guess this must be a change that Ecobee made and it's out of Hubitat's control, then. I might message Ecobee support at some point, then!
I'm probably being dumb, but it looks like to me that if you set the stat to a temperature other than your set program, the temperature the stat is calling for after you've had the fan on, would still be lost. I guess you could maybe set a rule to 'capture' the stat and then restore it once the fan is done running, but you still can't force the fan to run and call for heating or cooling at the same time with either workaround it seems.
In my case (tstat is controlling fancoil air exchanger in apartment building) fan is always running as soon as there is a call for colling (no heating in south Florida). Plus I set fan to run at least for 20 min/hour even if there is no call for colling.
You are not being dumb at all. The ecobee simply doesn't handle this situation very well. All indications are that third-party integrations were an afterthought for them. Some variation of capture-and-restore is the only workaround that I know.
It is rare for us to manually adjust the temperature, so I don't have experience with how the ecobee handles that.
