I have programmed the RC80 for times and temperatures in each mode, i.e., night, day, evening and morning. I can also enter temperature setting for each Security condition, i.e., day, night, away, etc.. Which has priority? Will the temperatures entered into the system for each security button be executed over those in the thermostat? Would the thermostat temperatures be executed if the system is in off mode? Still trying to understand all of this.
RC80 vs Omni LT priority
- Thread starter alpalmer
- Start date
I don't know about the OmniLT, but I looked it up for the Elk.
The Elk answer is to disable the thermostat's scheduling features and let the automation panel change the thermostat settings via panel programs. Personally, I'd like to have the Elk act like a manual override, so that if the Elk ever seizes up, the thermostat takes over with some sensible programme.
It wouldn't surprise me if the Omni panels work the same as the Elk.
Chris D.
The Elk answer is to disable the thermostat's scheduling features and let the automation panel change the thermostat settings via panel programs. Personally, I'd like to have the Elk act like a manual override, so that if the Elk ever seizes up, the thermostat takes over with some sensible programme.
It wouldn't surprise me if the Omni panels work the same as the Elk.
Chris D.
There is no priotity. All programs will execute as programmed, regardless of whether the program exists in the tstat's internal shcedule or in the automaiton controller. The only "exception" per say, would be the a "hold" command from controller programming.
Essentially, the tstat will respond to every prgram. For instance, suppose you have an internal tstat program scheduled to execute at 7:00 AM that sets the cool setpoint to 76 and the heat set point to 65 and you also have a program to st the cool to 80 and heat to 60 when the system is armed Away. At 7:00 AM the setpoints will go to 76/65 - if you arm the system Away at 7:01 AM, the setpoints would go to 80/60.
HAI recommends that when connecting a tstat to a home automaiton system, you diable the internal schedule and allow all programming to come from the automation controller - that way, you never have conflicting schedules.
Essentially, the tstat will respond to every prgram. For instance, suppose you have an internal tstat program scheduled to execute at 7:00 AM that sets the cool setpoint to 76 and the heat set point to 65 and you also have a program to st the cool to 80 and heat to 60 when the system is armed Away. At 7:00 AM the setpoints will go to 76/65 - if you arm the system Away at 7:01 AM, the setpoints would go to 80/60.
HAI recommends that when connecting a tstat to a home automaiton system, you diable the internal schedule and allow all programming to come from the automation controller - that way, you never have conflicting schedules.
Brian Yokum
Active Member
Todd,
That's the whole point of hold mode. It allows a user to keep the controller from changing the setpoints. Consider it a manual override, such as maintaining a special temperature during a party.
tmbrown97
Senior Member
makes sense - I had turned it on in the very beginning to stop the programs from running before I hooked the elk in (that was about a year later)... Since my wife and I work opposite schedules, the house is permanently set to 74 regardless. I also figured out that Hold seemed to mess up my auto heat/cool - I was wondering why that didn't work in the beginning, but with the elk now hooked up it's flawless.
