To get email notification when someone adds to a thread you're following, click on the star in the thread's header and it will turn yellow; click again to turn it off. To edit your profile, click on the gear.
The Wall has a powerful search engine that will go all the way back to 2002. Use "quotation marks" around multiple-word searches. RIGHT-CLICK on the results and choose Open Link In New Window so you'll be able to get back to your results. Happy searching!
In fairness to all, we don't discuss pricing on the Wall. Thanks for your cooperation.
Thermostats (Honeywell and EcoBee)
I currently have a Honeywell FocusPro 6000 thermostat which seems to do regular thermostat things well (schedule, detecting temperature, anticipating when the system should come on, etc.). Although I don't use much of that since I just set the temperature to 67 and hold.
However, the cycles-per-hour setting and determining when to stop the call-for-heat seem to be all wrong.
What a cycle looks like:
T=00 - call for heat
T+18 - system reaches 3oz pressure and vaporstat cuts out. radiators are all ~90% full which is where I would want them to stop getting steam on this vapor/orifice system.
T+18 to T+25 - system pressure reduces to 1oz and vaporstat allows burner to fire again. 30 seconds off then 90 seconds on
T+25 - call for heat satisfied
T+60 - call for heat
What seems odd to me is:
1) the call-for-heat is exactly 25 minutes every time now. earlier in the season (before the cold got COLD) the call for heat was exactly 20 minutes. so is the Honeywell relying on time to kill the call-for-heat instead of the sensed temperature in the room?
2) the second call-for-heat is exactly 60 minutes after the first call for heat. so is the Honeywell using the 1CPH as a rule instead of a maximum? I think the alternate explanation would be that the room loses all of the heat in the 35 minute off time and therefore needs to call-for-heat right when the CPH setting allows it to. In which case, setting CPH=2 might be an interesting test?
I know that the newage 'smart' thermostats aren't really liked around here because none of them (Nest in particular) seem to have a CPH setting. However, I stumbled across the ecobee (https://www.ecobee.com/) thermostat that looks to be a bit more interesting because it looks as though it is programmable through a software API (Application Programming Interface). Has anyone - specifically any software engineers like myself looked into this ecobee and found anything interesting about it?
What I think I want is a very dumb thermostat along with a control that stops the boiler from firing after being on for 18 minutes and then a control that allows another call for heat after 20 minutes of the radiators giving up heat. I know that MarkS (http://www.heatinghelp.com/forum-thread/129949/Temperature-based-cut-in-for-a-Vaporstat) has experimented with a time-delay relay after the vaporstat cuts out which might actually be the perfect solution for me.
Anyone else using a similar but different solution?
MarkS, if you're listening, are you still using your time-delay relay and is it successful like you thought it would be?