Steigs Posted December 28, 2012 Share Posted December 28, 2012 Greetings fellow ISYers, I have a tstat for upstairs and one for downstairs. The upstairs hallway is open to, and overlooks, the 2 story den and in this hallway is where the 2nd floor tstat is placed. In order to keep the master bedroom warm, the upstairs stat has to be run about 2-3 degrees above the 1st floor unit. Normally during the day, it's not an issue. But at night if that offset hasn't been active, the master is the coldest room in the house. I'd like to find a way to track changes on the 1st floor tstat and then update the 2nd floor tstat appropriately. Can I load the current temp into a variable somehow and then run a program that adds 2 and sends that to the 2nd floor unit? Any suggestions appreciated. Link to comment
ISYhbsh01 Posted December 28, 2012 Share Posted December 28, 2012 Let me make sure I understand this correctly. You want your upstairs heat setpoint to always be 2 degrees higher than the downstairs setpoint? And instead of changing each setpoint individually every time, you want to set the downstairs heat setpoint and the upstairs setpoint should automatically change to 2 degrees higher? Sent from my SPH-D710 using Tapatalk 2 Link to comment
Steigs Posted December 28, 2012 Author Share Posted December 28, 2012 Exactly. In an ideal world, I'd also be able to enable or disable the offset 'mode' with a program. Link to comment
ISYhbsh01 Posted December 28, 2012 Share Posted December 28, 2012 Hopefully one day we will be able with just a single program to set a variable with whatever the setpoint is & then it would be pretty easy to setup what you are trying to do using variables. Unfortunately that is not possible today. See the discussion here: http://forum.universal-devices.com/viewtopic.php?t=9420 So currently, if you would be using variables to accomplish what you are trying to do, you would need to make a separate program for every possible setpoint in your range to set the variable. So you are not gaining anything from using a variable, you are just going to have to use two programs for every possible setpoint. So instead you should just make a separate program for every possible degree in your range which should look like the following: If Status 'Tstat1 - Main' is 70° (Heat Setpoint) Then Set 'Tstat2 - Main' 72° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') And so on for every possible setpoint. If you want to be able to enable/disable this mode you would just add an appropriate condition to every program. For example, if you want to use a KPL button which would activate/de-activate this mode, you would make a program let’s call it “Auto Heat Offset†as follows: If Status 'KPL-1-H' is On Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') Then you would add a condition in each of the programs for each setpoint as follows: If Status 'Tstat1 - Main' is 70° (Heat Setpoint) And Program 'Auto Heat Offset' is True Then Set 'Tstat2 - Main' 72° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') Link to comment
Steigs Posted December 28, 2012 Author Share Posted December 28, 2012 .. you are just going to have to use two programs for every possible setpoint. That was my initial thought, but I was hoping maybe there was a method a bit cleaner. Bummer. Off to do some repetitive code.. Thanks! Link to comment
ISYhbsh01 Posted December 28, 2012 Share Posted December 28, 2012 Actually in my example if u r going to use a KPL button as the trigger u don't need the seperate "auto heat offset" program. You can just add the "if KPL status is on" condition directly in the programs you will be making for every setpoint. If you want to enable/disable this mode some other way, then the "Auto heat offset" program might be needed. Sent from my SPH-D710 using Tapatalk 2 Link to comment
Nuttycomputer Posted December 30, 2012 Share Posted December 30, 2012 Actually in my example if u r going to use a KPL button as the trigger u don't need the seperate "auto heat offset" program. You can just add the "if KPL status is on" condition directly in the programs you will be making for every setpoint. If you want to enable/disable this mode some other way, then the "Auto heat offset" program might be needed. I would recommend if you need to disable an entire suite of programs instead of trying to keep track of the variables in each program it might also be easier to put the programs in a folder and then add conditions to the folder. Link to comment
ISYhbsh01 Posted December 30, 2012 Share Posted December 30, 2012 Actually in my example if u r going to use a KPL button as the trigger u don't need the seperate "auto heat offset" program. You can just add the "if KPL status is on" condition directly in the programs you will be making for every setpoint. If you want to enable/disable this mode some other way, then the "Auto heat offset" program might be needed. I would recommend if you need to disable an entire suite of programs instead of trying to keep track of the variables in each program it might also be easier to put the programs in a folder and then add conditions to the folder. Yes I agree you are right. It would be easier to just use a condition on the folder. This would save the OP from having to use the condition in every program for each setpoint. Sent from my SPH-D710 using Tapatalk 2 Link to comment
Recommended Posts