Thermostat: resume schedule?

Other Devices & Integrations Climate Control & Temperature Sensors
1

It doesn’t appear that Vera supports this, at least under UI4. On our Honeywells, it’d be great to be able to temporarily modify the set point, and then later, have the stat resume its scheduled program.

Is the reason this is MIA because the Z-wave commands for stats doesn’t include a “resume schedule” directive?

–Richard

2

Word is that the Danfoss Living Connect uses the Z-Wave setpoint schedule as soon as the Z-Wave setpoint schedule has been transferred to the device. Manually setting a new setpoint will suspend the schedule until the next setpoint change as defined in the Z-Wave setpoint schedule is reached.

3

We have the Honeywells, and for most stuff, are happy to let them run business-as-usual as programmed from their GUI. But sometimes we give them nudges via Vera (typically through SQC) for unusual conditions. In those cases, they stick to the manual setpoint until we tap the “schedule” key on the touch pad. I’m guessing there’s not a Z-wave command to let a stat go back onto auto-pilot, correct?

–Richard

4

Does your device support Z-Wave command class [tt]CLIMATE_CONTROL_SCHEDULE[/tt] (70) (see ‘Capabilities’ / ‘Settings’ tab)?

Z-Wave layer

COMMAND_CLASS_THERMOSTAT_MODE

Mode name:

Off
Heat
Cool
Auto
Aux Heat
Resume
Fan Only
Furnace
Dry Air
Moist Air
Auto Changeover
Heat Econ
Cool Econ
Away

COMMAND_CLASS_THERMOSTAT_SETPOINT

Setpoints:

Unused0
Heating1
Cooling1
Unused3
Unused4
Unused5
Unused6
Furnace
Dry Air
Moist Air
Auto Changeover
Heating Econ
Cooling Econ
Away Heating
Count

COMMAND_CLASS_THERMOSTAT_OPERATING_STATE

State name:

Idle
Heating
Cooling
FanOnly
Pending Heat
Pending Cool
Vent / Economizer

UPnP layer

See attachment.

Summary

There is no standard Z-Wave command for ‘Resume schedule’. There might be a proprietary Z-Wave command for your device (use [tt]SendData[/tt] to send low-level Z-Wave commands).

The Standardized UPnP SCPs for thermostats don’t seem to support ‘Resume schedule’.

If your device does support [tt]COMMAND_CLASS_CLIMATE_CONTROL_SCHEDULE[/tt], you could try to use [tt]DSS[/tt] (Danfoss Setpoint Schedule) to transfer a Z-Wave setpoint schedule to your device.

Unfortunately, MiOS doesn’t support Z-Wave setpoint schedules out of the box.

5

It doesn’t support command class 70…at least, it’s not listed. But here’s a possibly-related question: what does mode==“resume” mean? From the page here: OpenZWave · GitHub

Mode value 5 means “resume”. The only way that would make sense to me would be if the stat “resumed”, and then the value changed to what the resumed schedule mode was? What else can it mean? There’s certainly no “resume” mode that ever shows on the stat interface directly.

–Richard

6

Why not try it out (use at your own risk …)?

luup.call_action( 'urn:micasaverde-com:serviceId:ZWaveNetwork1', 'SendData', { Node='x', Data='0x40 1 5' }, 1 )

Replace [tt]x[/tt] with the Z-Wave node id of the thermostat.

[tt]http://open-zwave.googlecode.com/svn-history/r489/trunk/cpp/src/command_classes/ThermostatMode.cpp[/tt]

7

Well, that seems to put the stat into “cool” mode every time. It was worth a try.

–Richard

8

I guess I’m missing the point of all of this. Why not just have your schedules run as scenes from your vera (i.e., thermostat X goes to set point Y at time Z)? What does having schedules on the thermostats themselves buy you?

9

It makes the thermostats autonomous. They’ll work all the time, even when Vera breaks, or if you’re tinkering with it at the wrong time.

When I had Trane TStats, I ran them on their internal schedule with Vera providing overrides (Economy mode) when I left the house etc. It also means you can control the timing/schedule and overrides with a simple UI, the one on the device itself.

10

It makes the thermostats autonomous. They’ll work all the time, even when Vera breaks, or if you’re tinkering with it at the wrong time.[/quote]

I can see that. That being said, I am using the Vera only since my CA8900’s don’t have any internal programming capability, and so far I’ve not had any issues with reliability / stability controlling them with scheduled scenes.

Having not owned a Trane or a Honeywell, i can’t comment on their interface, but I remember my old White Rodgers programmable at the old house was pretty much a nightmare (though the touch screen did look cool).

11

In addition to the 'stats being autonomous, these things have a fair amount of smarts about getting your house to the desired temperature at the requested time. Some do it by using data from outdoor sensors. The Honeywells “learn” how long it took to move to a new scheduled setpoint in the recent past, and try to provide that lead time. You could do all that with scenes and a ton of Luup, but why bother if the 'stat can do it on its own?

Our modus operandi is generally to let the stats track programming. It’s really nice to be able to do overrides with Vera, since they can be done remotely. When we go on vacations, we put them on manual holds for a much lower temp than we’d want if we’re home. As we get close to being home, we nudge them back to roughly where they need to be my moving the setpoint up. But it’d be lovely to be able to just say “Honeywell, you have the helm”.

–Richard

12

I have the Honeywell YTH8320ZW1007 thermostat. I have noticed that when i change the temperature the unit stops following the schedule. I can turn the unit on, off, and set to auto but, nothing I do puts it back on schedule. A year ago i had the Schlage system and there was an option in there app to “hold” temperature and run “schedule” Is there a run schedule option or hold option that is vera related and i just have not setup?

13

I don’t have a specific answer to your question but I have mine set-up with schedules disabled on the unit itself. I then use scenes on the Vera to create a schedule (i.e. turn it down at 10:30 and then back up at 5am). I am able to manually adjust the temperature on the unit itself with no issues with it going back on the approporiate schedule.

14

thanks, can you still use the auto mode with the way you have it setup? I like using the auto mode so the unit knows when to cool and heat automatically. Is the scheduling easy to setup or did you have to use luup code?

thanks,

15

Yes, you should be able to use auto mode (I have heat only but I am able to select “auto” in the vera and the theromstat changes).

The scenes were very easy to set-up with no luup code required. I have a very simple schedule requirements:

I just have two scenes: a “Good Night” scene and a “Good Morning” scene. All you need to do is create a new scene for each one, enter the desired set point (i.e. 64 degrees) and use the schedule tab to tell it when you want it to run.

16

thanks, can you still use the auto mode with the way you have it setup? I like using the auto mode so the unit knows when to cool and heat automatically. Is the scheduling easy to setup or did you have to use luup code?

thanks,[/quote]

Thanks, I have tried what you suggested and appears to work well, any thoughts on how to put the system into HOLD remotely?

17

Hi Sdittoc,

I am in the same boat as you, I even have the same lock, I would have messaged you directly but I guess I am to “fresh” to be able to do that… :slight_smile:

I was wondering too, if and how I can get my Honeywell thermostat out of the “temporary hold” vera puts it in when I change a set temperature over the dashboard/web.

I know you can set the schedule in vera and have it control everything but I am not ready yet to do that. A simple “wiggle” out of the hold to get it back to “Following schedule” would be nice.

Let me know if you found something.

I don’t want to hijack the post, I found some other “weird” things with the Schlage lock but I will talk about that in another post.
My email is demir at bell dot net

Thanks,

18

This sounds like what @rlmalisz brought up earlier? I believe it’s unresolved.

19

Yeap, I found it later.

I first searched by Honeywell and brougt up this thread, but then, combing through the category I found the other post too.

Indeed, not solved so far

Well, not something major, but would be nice.

20

Topics are now merged.

Some questions:

  • When you change the setpoint through Vera, what is displayed on the t-stat in relation to the hold mode, if anything (e.g. ‘permanent hold’, ‘temporary hold’, etc.)?
  • Same behavior when you change the temperature locally on the t-stat?
  • Could someone post the [tt]Capabilities[/tt] string of the t-stat? (From the [tt]Settings[/tt] tab of the t-stat on Vera’s Dashboard.)