- May 30, 2012
- 2,228
- Pool Size
- 17000
- Surface
- Vinyl
- Chlorine
- Salt Water Generator
- SWG Type
- Hayward Turbo Cell (T-CELL-5)
I'm asking this here because we have quite a few automation / tech minded people and maybe somebody can answer.
I had a Nest thermostat installed (by my HVAC guy, he was was here anyway, so why not - so this was installed by somebody who knows what they are doing) sometime over the summer (maybe August). It has been working just fine since then. Cools when I need cooling, heats when I need heating. Does that Nest thing when it determines that despite what I set it to, I would save money at a different temp, etc.
I have separate heating and cooling systems. I have a boiler with hydronic heat, and a standard forced air AC system.
Last night, I am sitting in my living room, enjoying the comfortable heat of my hydronic system, when all of a sudden "why did the AC just turn on?" The Nest was triggering both the heat and the AC at the same time.
The Nest was also set to "Heat" (Not Cool, not Heat & Cool, just Heat). I killed the breaker for the air handler and compressor, which stopped the AC (Naturally) but then the Nest freaked out because "something is wrong, there is no voltage on your Y1 wire". (As an aside, what a great design, in the middle of January you detect something is amiss with the AC, so you lock up entirely). So, to make the Nest happy I put the breakers for the air handler back on, figuring that would stop it freaking out about the Y1 wire, but at least my compressor would not be running. Well that seems to fix it. The Nest was happy about the Y1 wire, and went back to heating things, and not running my AC.
This is next to impossible to google, because all of the searches are about what to do when your Nest runs the AC instead of heat just after an install. I can't find anything about after working nicely for 6 months, it suddenly decides you want both heat and AC at the same time in January in the Northeast.
Anybody ever hear about anything like this? Maybe it was a one time glitch (I hope).
I had a Nest thermostat installed (by my HVAC guy, he was was here anyway, so why not - so this was installed by somebody who knows what they are doing) sometime over the summer (maybe August). It has been working just fine since then. Cools when I need cooling, heats when I need heating. Does that Nest thing when it determines that despite what I set it to, I would save money at a different temp, etc.
I have separate heating and cooling systems. I have a boiler with hydronic heat, and a standard forced air AC system.
Last night, I am sitting in my living room, enjoying the comfortable heat of my hydronic system, when all of a sudden "why did the AC just turn on?" The Nest was triggering both the heat and the AC at the same time.
The Nest was also set to "Heat" (Not Cool, not Heat & Cool, just Heat). I killed the breaker for the air handler and compressor, which stopped the AC (Naturally) but then the Nest freaked out because "something is wrong, there is no voltage on your Y1 wire". (As an aside, what a great design, in the middle of January you detect something is amiss with the AC, so you lock up entirely). So, to make the Nest happy I put the breakers for the air handler back on, figuring that would stop it freaking out about the Y1 wire, but at least my compressor would not be running. Well that seems to fix it. The Nest was happy about the Y1 wire, and went back to heating things, and not running my AC.
This is next to impossible to google, because all of the searches are about what to do when your Nest runs the AC instead of heat just after an install. I can't find anything about after working nicely for 6 months, it suddenly decides you want both heat and AC at the same time in January in the Northeast.
Anybody ever hear about anything like this? Maybe it was a one time glitch (I hope).