Hi all, I had an Omni IIe installed in my house last month with four thermostats and 7 light switches. My primary reason was initally more for the ability to control lights and stats with my iPhone because my son, who has autism, has a tendency to fiddle with the stats and leave lights on around the house. Having played around with the automation features, I'm now hooked and I plan to add more lights and sensors. However, having a few issues I need help with.
Problem #1
I have four RC-2000 stats connected to three HVAC units. Two of the stats are connected to a single Honeywell HZ311 zone panel that controls the two zones via a damper system. One of those stats controls the main floor zone, the second controls the basement. My installer initially put settings in for both of those stats as "conventional". I have since changed them both to "zone control" -- was this correct for me to do? Currently, I have enabled the program which is available on the stat itself, but I have removed the jumper so that the buttons are disabled (again so that my son cannot fiddle with it). The problem is that the stat does not seem to turn the HVAC unit on consistently when the program reaches the appropriate time. For instance, I have it set to turn to 69 degrees at 530 in the the morning. The stat setpoint changes to 69, but for the last three days it has not switched on the unit. If I change the setpoint on PC Access or my iPhone (using iRule), it immediately changes on the stat and immediately switches the unit on. If I put the jumper back on so that the stat buttons are enabled, it immediately runs the program and turns the stat on. I realize that I can program it to automatically turn on at the desired time using PCAccess, but I haven't done that yet because I can't figure out how to make the setpoint return to the original programmed temp IF the setpoint is manually changed (using PC Access or iPhone). So the question is, why is the stat not turning the unit on? I have a common wire at both the stat and the zone panel and all the connections seem correct as far as my (limited) knowledge goes. A secondary question, perhaps best asked in the programming section, is how to create code that will make the stat revert to the programmed setpoint if it is manually changed.
Problem #2
This involves occupancy/motion sensors. I do not really want to turn on lights when a room is occupied. However, I do want to turn lights OFF when a room is NOT occupied. It seems that motion sensors would not be a good solution because they have high false alarm thresholds and if someone is sitting in a room they might not be detected. However, since this is a retrofit, I need to use wireless sensors that communicate with the Omni. Does anyone know of wireless occupancy sensors that would be compatible with the Omni? Alternatively, are there HLC/UPB switches that can communicate directly with the the Omni and still communicate wirelessly with an occupancy sensor?
Thanks in advance!!!
Problem #1
I have four RC-2000 stats connected to three HVAC units. Two of the stats are connected to a single Honeywell HZ311 zone panel that controls the two zones via a damper system. One of those stats controls the main floor zone, the second controls the basement. My installer initially put settings in for both of those stats as "conventional". I have since changed them both to "zone control" -- was this correct for me to do? Currently, I have enabled the program which is available on the stat itself, but I have removed the jumper so that the buttons are disabled (again so that my son cannot fiddle with it). The problem is that the stat does not seem to turn the HVAC unit on consistently when the program reaches the appropriate time. For instance, I have it set to turn to 69 degrees at 530 in the the morning. The stat setpoint changes to 69, but for the last three days it has not switched on the unit. If I change the setpoint on PC Access or my iPhone (using iRule), it immediately changes on the stat and immediately switches the unit on. If I put the jumper back on so that the stat buttons are enabled, it immediately runs the program and turns the stat on. I realize that I can program it to automatically turn on at the desired time using PCAccess, but I haven't done that yet because I can't figure out how to make the setpoint return to the original programmed temp IF the setpoint is manually changed (using PC Access or iPhone). So the question is, why is the stat not turning the unit on? I have a common wire at both the stat and the zone panel and all the connections seem correct as far as my (limited) knowledge goes. A secondary question, perhaps best asked in the programming section, is how to create code that will make the stat revert to the programmed setpoint if it is manually changed.
Problem #2
This involves occupancy/motion sensors. I do not really want to turn on lights when a room is occupied. However, I do want to turn lights OFF when a room is NOT occupied. It seems that motion sensors would not be a good solution because they have high false alarm thresholds and if someone is sitting in a room they might not be detected. However, since this is a retrofit, I need to use wireless sensors that communicate with the Omni. Does anyone know of wireless occupancy sensors that would be compatible with the Omni? Alternatively, are there HLC/UPB switches that can communicate directly with the the Omni and still communicate wirelessly with an occupancy sensor?
Thanks in advance!!!