Error in controlling Ecobee/HVAC fan based on temps > overrides cooling setpoint as well- ideas on how to fix?

🛎️ Get Help
1

So I've got an Ecobee thermostat with remote temp sensors and a Hubitat rule set up to run the HVAC's fan when a temp threshold is met to circulate cool air up from the basement.

The rule engages as expected based on temps, but the impact on the Ecobee is flawed; it turns the fan from AUTO to ON as expected, but it also puts an indefinite hold on the current Ecobee cooling setpoint that even overrides the scheduled changes. So if the rule turns the fan on, it holds whatever cooling setpoint it's currently at constant, even if a schedule is set to lower the cooling setpoint later in the day.

Any idea on how to get hubitat to only affect the fan setting from AUTO to ON and not put a hold on the cooling setpoint as well?

2

I'd be curious too. The Ecobee support is imperfect, and this is one of the issues I've noticed.

3

Yeah I was hopeful to cut down on A/C use with this rule, but it didn't shake out how I wanted it to.

4

Can you post a screenshot of your rule?

5

Here is the rule:

image
image.png720×473 13.3 KB

and here is the setting for the thermostat

image
image.png716×530 7.69 KB

As best as I can tell, I'm only affectting the fan setting, which is what I'd like to have happen.

It kicks the thermostat into a 'XX temp and holding' mode, and then it doesn't shift into future scheduled temperatures so long as the rule is still true:

image
image.jpg540×640 75.4 KB

6

Go to your Ecobee in Devices. Scroll down to set Hold Type to Temporary. The temp will then reset on your next Time threshold.