In an earlier contribution to this discussion,
JoeJoe wrote:


Thanks for taking the time to reply, but I perhaps I didn't explain
what we were trying to achieve properly.

We (well, she... always cold...) tend to use the override feature
(i.e. turn it to "constant on" or to "1hr boost") pretty often, and
therefore we want the controls to be in a convenient position. As the
downstairs is drafty, we may end up with the stat in the upstairs
landing, so we don't want to have to use it as the main control for
the system. I agree that we could potentially use a much
cheaper/simpler wireless stat, even without any real programming -
but we got a very good deal on the 927, so we got it anyway.

The plan is to set the stat to pretty much "always on" temperature
throughout the day, and do the time/day control from the conveniently
positioned programmer. The reason we wanted a little smarter stat is
to allow us to experiment with different temperature settings for,
say, morning and evening.

Sorry for not explaining this earlier.

Does it make more sense now?

I can see what you're setting out to achieve but, in your position, I'd be
attacking the drafts first before worrying about over-complicating the CH
control.

By having another timer in series with your programmable stat you will
negate some of the features of the stat - such as its ability to act as a
frost stat in its 'off' state.

If you want to boost the temperature above the current stat setting at a
time when the main timer is on, you'll have to go to the programmable stat
anyway!
--
Cheers,
Roger
______
Email address maintained for newsgroup use only, and not regularly
monitored.. Messages sent to it may not be read for several weeks.
PLEASE REPLY TO NEWSGROUP!