Anyone doing Omnistat automation with plugin?

[Pete]

Over the years here have let the Omnistat do it's own thing and rarely touch the settings. I do leave the HVAC fan on 24/7. I used to use set backs and do not these days. In all of these years (over 10) never have put in automation blocks for the Omnistat in the panel.

Yesterday I tried and noticed that I cannot as there are no options in the PCA automation of the Omnistat.

So went to using Rob's plugin / thermostat pieces and it works great.

Wondering if anyone else is doing this with Rob's plugin?

[lakemirror]

I'm puzzled, as I control my HVAC through both automation in PCA and events in HS using the PI.

An example from PCA. "NIGHT TEMPS" is a button that can be manually activated or set by other automation lines.

41. WHEN NIGHT TEMPS
THEN ALL THERMOSTATS COOL SETPOINT 76
42. WHEN NIGHT TEMPS
THEN MAST BEDROOM COOL SETPOINT 71

[Pete]

Thank you Tom.

So then how do I automate this?

I want the #1 temp button to be on 24/7 and use if then #2 then do #3.

1 - assign button #1 to temps

2 - when thermostat temperature equals 78

3 - then thermostat cool on.

then another and if:

4 - when thermostat temperature equals 71

5 - then thermostat cool off.

[ATTACH]61332[/ATTACH]

[lakemirror]

If I understand correctly, you want to have your thermostats go into cool mode if the temperature exceeds 77, and go into off mode if they drop below 72? IE instead of maintaining 71 you want them to turn on at 78 and off at 71?

Don't use a button as a trigger, as it will only evaluate your thermostats at the moment the button is activated. Instead, write an automation block to evaluate your thermostats every x minutes. Manually set the cool temperature to 71. See 1st photo.

If you want to be able to turn this process on and off, include a flag in an "and if" statement. I called this one "THERMOSTATS". Turn the flag on to start evaluating the thermostat and off to stop (ie use automation to turn the flag on at a certain time of day, or when you disarm the system, etc.) See photo 2.

Do this for each thermostat. You could also use the current temperature of one thermostat to control all, if you wanted (THEN ALL THERMOSTATS TO MODE COOL), but I don't know why you'd do that.

What's going to happen, though, if the flag goes to OFF while the HVAC is cooling? Without the flag on, the cool mode will never be set to off or on. Add automation to the effect of IF THERMOSTATS OFF, THEN DINING ROOM MODE OFF and IF THERMOSTATS ON, THEN DINING ROOM MODE. I've not thought that one through all the way...I'll keep thinking.

If I misunderstood your intent, reword it for me.

[Pete]

If I understand correctly, you want to have your thermostats go into cool mode if the temperature exceeds 77, and go into off mode if they drop below 72? IE instead of maintaining 71 you want them to turn on at 78 and off at 71?


yes.

Thank you Tom.

First testing will be first two blocks then later will give the on and off flag feature a try.

[lakemirror]

With the flag, you'll need to add a standalone line of automation that says WHEN THERMOSTATS OFF, THEN DINING ROOM MODE OFF. This will stop the HVAC if you set the button to off while cooling. Otherwise it will keep cooling until the room traces the thermostat cooling set point and hold it there.


Sent from my iPhone using Tapatalk

[lakemirror]

With the flag, you'll need to add a standalone line of automation that says WHEN THERMOSTATS OFF, THEN DINING ROOM MODE OFF. This will stop the HVAC if you set the button to off while cooling. Otherwise it will keep cooling until the room traces the thermostat cooling set point and hold it there.


Sent from my iPhone using Tapatalk

Reaches, not traces.


Sent from my iPhone using Tapatalk

[Pete]

Thank you Tom.