Two Thermostat Questions

[broconne]

(1) Is it possible to trigger an automation block off of a temperature? I would like to turn fans off and on, perhaps set the mode from auto to cycle based on temperature and time and alarm status.

(2) When we arm the system I want to set the thermostat to hold and perform a setback on the thermostat which is easy enough to do. However, on return after I remove the hold I see no way to ask the thermostat to return to its scheduled temperature. Is there a way to do that?

 

[Desert_AIP]

1) You can have setpoints on temperature sensors. When the sensor is above the high setpoint or below the low setpoint it will report "NOT READY". Inside the setpoint band it will report "SECURE". You can wire one temperature sensor to many zones and program setpoints for each zone. A setpoint of 0 disables the setpoint, so you can set just a high temp or low temp trigger by setting the other setpoint to 0.

The trigger would be

 WHEN Outdoor Temperature Sensor NOT READY

2)
If you use the RC-2000 thermostats, you can set the program mode to "Occupancy". The setpoints will be Day, Night, Away, Vacation. Those setpoints will automatically change based on the security setting. OFF uses the Day setpoints. You can also send setpoints to the thermostats programmatically, based on time or other triggers. Return the thermostat to "AUTO" to use the setpoints.

 

[broconne]

1) You can have setpoints on temperature sensors. When the sensor is above the high setpoint or below the low setpoint it will report "NOT READY". Inside the setpoint band it will report "SECURE". You can wire one temperature sensor to many zones and program setpoints for each zone. A setpoint of 0 disables the setpoint, so you can set just a high temp or low temp trigger by setting the other setpoint to 0.

The trigger would be

 WHEN Outdoor Temperature Sensor NOT READY

Thanks. I was trying to do it based on the temperature reported by the thermostat. Can you set setpoints on that?

2)
If you use the RC-2000 thermostats, you can set the program mode to "Occupancy". The setpoints will be Day, Night, Away, Vacation. Those setpoints will automatically change based on the security setting. OFF uses the Day setpoints. You can also send setpoints to the thermostats programmatically, based on time or other triggers. Return the thermostat to "AUTO" to use the setpoints.

I have looked at that a bit and it is what I will end up having to do if there are no other options. I will lose a lot of WAF if she can't adjust the program herself.

 

[Desert_AIP]

I'm not sure if the thermostats report "SECURE" or "NOT READY".
You may be able to trigger off of modes. Since if the HVAC system was off then the T-stat would be "SECURE" since the temperature would be between the setpoints. I don't have access to my software or equipment right now, so I can't verify.


If you keep the front controls active on the thermostats, you can make real time comfort adjustments to the setpoints just like a dumb/non-connected thermostat.
If you have touch screens, the T-stat adjustments made there will also override the setpoints. You can also use User Settings for temps that will be uploaded to the T-stats and readily changeable.

If you don't use the "Occupancy" program mode then you need to use the "None" program and do all of the programming in PCAccess. I believe you can use the "Schedule" program on the T-stat, but it really defeats the purpose of having a connected T-Stat.

I sat down and thought out how I wanted the system to act while we were awake, asleep, away or on vacation. Then I programmed the setpoints and user buttons to match this.

HAI Knowledgebase
http://kb.homeauto.com/default.asp?id=397&Lang=1&SID={32BCABFE-1E9F-4505-B883-2530DC7FBDAC}

I'll post my HVAC code when I get a chance. I just installed a two zone (with a third pending) system and am workign out the bugs. I use a combination of time, occupancy and other event triggers to modify the setpoints/modes.

 

[broconne]

I'm not sure if the thermostats report "SECURE" or "NOT READY".
You may be able to trigger off of modes. Since if the HVAC system was off then the T-stat would be "SECURE" since the temperature would be between the setpoints. I don't have access to my software or equipment right now, so I can't verify.


If you keep the front controls active on the thermostats, you can make real time comfort adjustments to the setpoints just like a dumb/non-connected thermostat.
If you have touch screens, the T-stat adjustments made there will also override the setpoints. You can also use User Settings for temps that will be uploaded to the T-stats and readily changeable.

If you don't use the "Occupancy" program mode then you need to use the "None" program and do all of the programming in PCAccess. I believe you can use the "Schedule" program on the T-stat, but it really defeats the purpose of having a connected T-Stat.

I sat down and thought out how I wanted the system to act while we were awake, asleep, away or on vacation. Then I programmed the setpoints and user buttons to match this.

HAI Knowledgebase
http://kb.homeauto.c...3-2530DC7FBDAC}

I'll post my HVAC code when I get a chance. I just installed a two zone (with a third pending) system and am workign out the bugs. I use a combination of time, occupancy and other event triggers to modify the setpoints/modes.

I was essentially trying to get the "best of both worlds here". My wife can set the temps with time triggers on the thermostat while the alarm is off and we can do auto setback when the alarm is on. If I go the way proposed, I will have to set the time triggers and corresponding temps and she can't adjust the programming (certainly she can override current). Just a minor ding on the WAF.

 

[Desert_AIP]

If you want to use the timed program on the T-stat you can, the thermostat still responds to Omni commands.
I think they warn against it because the setpoints may change based on time rather than conditions and end users won't know (or remember) why.

Program a hold when arming away and an auto when returning or remaining home.

1.	WHEN AWAY
			THEN ALL THERMOSTATS HEAT SETPOINT 60
			THEN ALL THERMOSTATS COOL SETPOINT 80
			THEN ALL THERMOSTATS HOLD ON
2.	WHEN OFF
	WHEN ARM DAY
	WHEN ARM NIGHT
			THEN ALL THERMOSTATS HOLD OFF
			THEN ALL THERMOSTATS MODE AUTO

ETA: This is much easier to do now that I'm at home and have PC Access available. :wacko:

 

[AnthonyZ]

A way to activate programming via temperature without using additional zones for multiple set points would be to use "Every"

For example...

Every 5 Minutes IF temp____ > ____
Do _____
Every 1 minute IF temp____ = ____
Do _____

 

[cornutt]

I don't use the schedules on the thermostats; all setpoint changes are commanded by the controller. This lets me do a lot of different things; for example, I can anticipate heat or cool based on outdoor temperature:

18.	TIMED 5:00 AM MTWTF--
	TIMED 7:00 AM -----SS
		AND IF Outdoor Temp Sensor CURRENT READING IS LESS THAN 20 
			THEN RUN Morning Thermostat Settings
19.	TIMED 5:30 AM MTWTF--
	TIMED 7:30 AM -----SS
		AND IF Outdoor Temp Sensor CURRENT READING IS LESS THAN 35 
			THEN RUN Morning Thermostat Settings
21.	TIMED 5:51 AM MTWTF--
			THEN RUN Morning Thermostat Settings

"Morning Thermostat Settings" is a button. Here's what it does:

45.	WHEN Morning Thermostat Settings
		AND IF Sleeping in CURRENT VALUE IS 0 
		AND IF House is unoccupied CURRENT VALUE IS 0 
			THEN Main Floor Tstat HEAT SETPOINT 70
			THEN Main Floor Tstat COOL SETPOINT 83
			THEN Top Floor Tstat COOL SETPOINT 85
			THEN RUN Morning Top Floor Set

48.	WHEN Morning Top Floor Set
		AND IF Guests in upstairs bedrooms CURRENT VALUE IS NOT 0 
			THEN Top Floor Tstat HEAT SETPOINT 70

"Sleeping in", "Guests in upstairs bedrooms", and "House is unoccupied" are flags that we used to tell the system about current and near-future occupancy. Each one is set to the number of days that the condition is applicable; they get decremented at noon each day. I built a screen on my touch screen where they can be set.

I've got similar code built to control day, evening, and overnight thermostat settings. I've done a bunch of tweaks to it to adapt to our preferences. For example, the night code raises most of the cool setpoints; however, if we are at home, it lowers the main floor cool setpoint because we like to sleep in a cool room. Early in the morning, before we wake up, it raises the setpoint back up so the A/C isn't running when we get up.

Finally, I have this bit, which alerts us if it detects that the three systems are fighting each other:

12.	EVERY 5 MINUTES
		AND IF Basement Tstat SYSTEM STATUS IS HEATING 
		AND IF Main Floor Tstat SYSTEM STATUS IS COOLING 
			THEN SHOW Heat/Cool Conflict Alert WITH BEEP
			THEN LOG Heat/Cool Conflict Alert
13.	EVERY 5 MINUTES
		AND IF Basement Tstat SYSTEM STATUS IS COOLING 
		AND IF Main Floor Tstat SYSTEM STATUS IS HEATING 
			THEN SHOW Heat/Cool Conflict Alert WITH BEEP
			THEN LOG Heat/Cool Conflict Alert
14.	EVERY 5 MINUTES
		AND IF Main Floor Tstat SYSTEM STATUS IS HEATING 
		AND IF Top Floor Tstat SYSTEM STATUS IS COOLING 
			THEN SHOW Heat/Cool Conflict Alert WITH BEEP
			THEN LOG Heat/Cool Conflict Alert
15.	EVERY 5 MINUTES
		AND IF Main Floor Tstat SYSTEM STATUS IS HEATING 
		AND IF Top Floor Tstat SYSTEM STATUS IS COOLING 
			THEN SHOW Heat/Cool Conflict Alert WITH BEEP
			THEN LOG Heat/Cool Conflict Alert

 

[rsw686]

If you use the RC-2000 thermostats, you can set the program mode to "Occupancy". The setpoints will be Day, Night, Away, Vacation. Those setpoints will automatically change based on the security setting. OFF uses the Day setpoints. You can also send setpoints to the thermostats programmatically, based on time or other triggers. Return the thermostat to "AUTO" to use the setpoints.

Bringing back an old thread. I have the thermostat configured for scheduled setpoints. Programmatically I send setpoints to override the schedule. However I can't figure out how to get the thermostat to immediate return to the scheduled setpoints. I have tried sending mode auto like you suggested and even tried changing mode to off then back to auto. The thermostat just waits until the next scheduled time to change the setpoint. This is annoying as the programming has no way of storing the current setpoint in a flag so I can manually revert it. Any thoughts?

 

[Desert_AIP]

Bringing back an old thread. I have the thermostat configured for scheduled setpoints. Programmatically I send setpoints to override the schedule. However I can't figure out how to get the thermostat to immediate return to the scheduled setpoints. I have tried sending mode auto like you suggested and even tried changing mode to off then back to auto. The thermostat just waits until the next scheduled time to change the setpoint. This is annoying as the programming has no way of storing the current setpoint in a flag so I can manually revert it. Any thoughts?

Sorry, I thinks confused you because I was in a rush and I mixed things together.

By OFF, I meant the security mode, not the t-stat mode.
If you change the set points and want to go back to the stored set points easily, just change or re-arm the security mode.
I.e., if you are in NIGHT mode and change the set points and then want to go back to the stored set points, just arm in NIGHT mode again.
If you are in OFF mode, programmatically arm in DAY and add a 1 second flag, and after the flag shuts off programmatically set OFF mode.

 

[rsw686]

That makes sense. I don't like the idea of changing security modes just to set the temp. I ended up setting the thermostat to program: none and hard coding the temps into the HAI program for buttons. I have a button for HVAC Day, HVAC Night, HVAC Away. I am running the buttons based on time or changes to the security state. I would have preferred the temps to be easily editable, but I didn't want to eat up half the user settings.

Really if HAI will just allow overriding the occupancy state on the thermostat it would be the best of both. I have basically recreated what the occupancy mode does, but am able to change the temps based on time as well.