Thermostat Scheduler restrictions clarification

I've been using the Thermostat Scheduler for sometime now but recently attempting to use the restrictions function. My intention is that TRV setpoints are set high (heat) at scheduled times IF there is a demand for heating. If, however, there is no demand for heat the TRV setpoints are set low (turned off)


So i initally understood that how this (see screen shot) is set would "restrict" the schedule from running and instead turn the thermostats OFF when my "heating request flag" is off.

Reading it again, could it mean that the "restriction" is "disabled" as opposed to disabling the scheduler. Perhaps i am reading this too literally?

Your setting means that Thermostat Scheduler is disabled when HeatingRequest_Flag is off. It looks like it should also turn the thermostat off when that restriction is in place (an option I didn't know existed -- but, yes, without that, it would just stop the schedules from changing anything).

If this isn't what you're seeing, I'd enable all logging and provide that output here.

thanks- i only discovered the "turn thermostat off when restricted" option a few days ago.
What the "thermostat off" state is, i am not sure as i only usually control the heating setpoint.

a bit of digging in the logs reveals that, as intended, the TRV was set to 23 degrees at 6am yesterday, as scheduled. the 7:30am schedule never came into effect (no demand for heat) and TRVs set to OFF.
at 4pm the "request for heating flag" was manually engaged which led the thermostat scheduler to kick in and set the TRV to 23 degrees (its last-sent automated setting) but i wanted it to be set to the last scheduled time 7:30 value of 17 degrees (which it appears to have bypassed likely due to the restrictions).

I only want the temperatures set high when there is a demand for heating but i always want to set the setpoints set low (or TRV off) on schedule regardless of the demand for heat.
I could probably do this with TWO thermostat schedulers per TRV (one to set high and the other to set low), which seems a bit counter productive
Any suggestions?

Two is what I was thinking, but maybe someone else has more creative ideas. :slight_smile: I don't make much use of this app myself so only know the bits I've used -- and things I've tested to answer questions. So it's quite possible someone will!