Support for Trane/Schlage Thermostat: TZEMT400AB32MA.

Other Devices & Integrations Climate Control & Temperature Sensors
1

I submitted a support issue several weeks ago through Vera to request for support of this thermostat.

Although I’m glad that the thermostat is working now with the AUTO & ON commands in the recent version of firmware 1.0.862, the
ability to switch the fan to CYCLE mode is still absent.

Would it be possible for MCV to add this support?

2

I’m not sure. I have the RCS thermostat which is, I understand, identical to the Trane. I think Trane is OEM’ing it from RCS. I don’t see a ‘cycle fan’ option though. When I hit the ‘fan’ button, there’s just ‘on’ and ‘auto’. What’s the button sequence you use on the Trane to go into this mode.

I’m look at the latest Z-Wave spec for the thermostat fan command and there’s no “cycle mode”, which means it might be something you can only do at the panel and not through Z-Wave. However, for the thermostat mode commands there a “Fan Only – Only cycle fan to circulate air”. This might be what you want. But it precludes you from also having cool/heat because it’s an alternate mode. If you want to force your thermostat to this mode to see what it does, go to the Setup, Devices button, locate the thermostat and note the ‘Node ID’. Then copy this link into your browser substituting the actual node id for ‘x’ in Node=x, and substituting the actual ip address. You’ll see a number on the web page if it was successful. On my RCS it doesn’t do anything. But maybe it does something on the Trane.

http://ipaddress:49451/data_request?id=lu_action&DeviceNum=1&serviceId=urn:micasaverde-com:serviceId:ZWaveNetwork1&action=SendData&Node=x&Data=x40-x1-6

3

The Trane and the RCS look identical, and the instructions as far as I can tell are the same.

To enable the CYCLE mode, you have to first enter the thermostat’s “hidden” INSTALLER SETTINGS mode.

It’s a special mode that allow further configuration:
[url=http://part2.schlage.com/docs/Thermostat_User_Manual-a.pdf]http://part2.schlage.com/docs/Thermostat_User_Manual-a.pdf[/url]
It’s page 24/35 in the PDF or page 27 in the “printed page”:

ie.

  1. Go to the MENU selection screen on the thermostat by pressing the soft [MENU] button on the far left.
  2. In the MENU screen, the two inner (middle) buttons will have blank soft menus. Hold these two middle keys for several seconds until the INSTALLER SETTINGS screen appears.
  3. scroll down to the FAN CYCLER item and [SELECT] that.
  4. Set a nonzero number in the FAN ON time (and adjust the FAN OFF time as appropriate). Once a non-zero number is enters for the FAN ON time, upon returning to the main screen of the thermostat, the CYCLE option will appear in the fan selection options: AUTO, ON, CYCLE.

My guess/hope is that the COMMAND_CLASS_THERMOSTAT_FAN_MODE has an additional ID for enabling the CYCLE mode. (possibly the next one in the sequence)

Let me know if you are successful or not in getting into the installer mode.

4

MCV,

I’m wondering if you have had a chance to try enabling the CYCLE mode for the FAN?

5

There is a Z-Wave command to set the Fan to Cycle.

6

There is? I don’t see that one in my Zensys documentation? where do you see it.

7

I can see/control it with HyperTerminal and a VRZ0P. Once you have set the Fan Cycler ON time so something other than 0 (which you can also set via Z-Wave btw), you then can send the Z-Wave command to set the t-stat into Cycler mode. I have to find out if I am allowed to share the list of other things that you can control via Z-Wave.

8

There appears to be several topics regarding updating the interface to the Trane Thermostats, especially the elusive fan cycle option. ASIHome alludes that he has insiders knowledge, but doesn’t appear able to share with the wider audience. The question is why doesn’t micasaverde have this same insider knowledge? Or how can we, the community, get insight? Or have I not yet found the thread where this problem is solved (please point me in the right direction!).

I messed around and cleaned up several files (attached) for the main interface (I am running a new vera with 1.1.1047). NOTE: I did NOT update the version numbers, as they are not official releases. I am also working on cleaning up the smart phone interface (will be posted “soon”).

Fan Cycle is indicated, but doesn’t (yet) work. Changes are primarily formatting and very minor functionality.

9

@jgdurbin,
I’m in the same boat as you, I would like to be able to set the mode to “Fan Cycler” but the option is not available from the UI. I tried to work around it by using luup code and although I was able to set the Fan Mode to ON or AUTO using luup commands, I couldn’t get it to go to the CYCLE mode. I contacted tech support and they dug through the Vera logs and found that even though I was sending a “PeriodicOn” command from the luup code, the command actually going out to the thermostat was for “ContinuousOn”. Tech support created a ticket for it (ID 0001410, created on 2-17-2011) and I’ve heard nothing since.

Here are the commands if your interested:
FAN ON
luup.call_action(“urn:upnp-org:serviceId:HVAC_FanOperatingMode1”,“SetMode”,{ NewMode"ContinuousOn" },10) <-Change the 10 to match your thermostat’s ID

FAN AUTO
luup.call_action(“urn:upnp-org:serviceId:HVAC_FanOperatingMode1”,“SetMode”,{ NewMode"Auto" },10) <-Change the 10 to match your thermostat’s ID

FAN CYCLE (Doesn’t work)
luup.call_action(“urn:upnp-org:serviceId:HVAC_FanOperatingMode1”,“SetMode”,{ NewMode"PeriodicOn" },10) <-Change the 10 to match your thermostat’s ID

Maybe if enough people complain, it will get fixed. Squeaky wheel gets the grease. :slight_smile:

Regards,
kbmcguire

10

You have to set the Fan ON Time for something greater than 0 for the Fan Cycle to work properly.

11

Right. But it doesn’t seem switchable through Z-Wave (it just goes to ContinuousOn mode). Or is that working for you?

12

I would like this functionality also

13

Unfortunately, ticket 1410 is not viewable (or at least not for me); so unclear if it’s even assigned.

14

Have you tried using the numeric values for the modes instead of those text identifiers?

0 = Auto
1 = On
2 = Cycle

15

According to the UPnP specification the implementation of ‘PeriodicOn’ is optional.

Bug report #1410 doesn’t seem to exist.

16

That may be the translation that is incorrect/partially missing in the implementation.

17

@ASIHome,
Yes, I have enabled Fan Cycler Mode from the Thermostat and it works locally, just not from Z-Wave/Vera.

Yes, I tried the numeric values and it always sets the fan to ON. If I’m reading the xml file correctly, only the text identifiers are supposedly valid. The driver seems to automatically convert anything else to “ContinousOn”, regardless. I can put my name as the NewMode and it will still change the fan mode to ON.

----excerpt from S_HVAC_FanOperatingMode1.xml----

Auto
ContinuousOn
PeriodicOn

----excerpt from S_HVAC_FanOperatingMode1.xml----

Also, for anyone testing the code I posted earlier, I apologize but there was a mistake, I left out the equal sign after NewMode. Should look like this:

FAN ON
luup.call_action(“urn:upnp-org:serviceId:HVAC_FanOperatingMode1”,“SetMode”,{ NewMode=“ContinuousOn” },10) <-Change the 10 to match your thermostat’s ID

FAN AUTO
luup.call_action(“urn:upnp-org:serviceId:HVAC_FanOperatingMode1”,“SetMode”,{ NewMode=“Auto” },10) <-Change the 10 to match your thermostat’s ID

FAN CYCLE (Doesn’t work)
luup.call_action(“urn:upnp-org:serviceId:HVAC_FanOperatingMode1”,“SetMode”,{ NewMode=“PeriodicOn” },10) <-Change the 10 to match your thermostat’s ID

The bug report (ID 1410) was entered by Florin and it appears to be private for whatever reason.

Regards,
kbmcguire

18

Lets keep this topic alive!

I agree with all said. I also saw in the logs that regardless of what was sent by the code, somewhere along the line it was switched from “PeriodicOn” to “ContinuousOn”.

[Reminder: How check logs: http://wiki.micasaverde.com/index.php/Logs]

Using the .xml and .json code I included in my previous post, I get the following in the logs:

08 05/10/11 20:35:02.532 JobHandler_LuaUPnP::HandleActionRequest device: 27 service: urn:upnp-org:serviceId:HVAC_FanOperatingMode1 action: SetMode <0xe2c09>
08 05/10/11 20:35:02.533 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=27 <0xe2c09>
08 05/10/11 20:35:02.533 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:upnp-org:serviceId:HVAC_FanOperatingMode1 <0xe2c09>
08 05/10/11 20:35:02.534 JobHandler_LuaUPnP::HandleActionRequest argument action=SetMode <0xe2c09>
08 05/10/11 20:35:02.534 JobHandler_LuaUPnP::HandleActionRequest argument NewMode=PeriodicOn <0xe2c09>
08 05/10/11 20:35:02.535 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.18364556121782222 <0xe2c09>
04 05/10/11 20:35:02.817 <0x803>

@ASIHome: I don’t understand your comment. I have PeriodicOn mode working from the thermostat itself. I think we are all trying to get the thermostat to switch to this mode via ZWave commands. You earlier implied this was possible. Can you confirm definitively if this is possible? Is there anything else you could share? Code, of course, would be most welcome ;D

19

I think several folks have confirmed now that it works locally on the thermostat, and not with Vera.

A bug report was apparently created by MCV.

It appears the bug is that PeriodicOn does not get translated to value 2 being sent to the thermostat, but value 1.

@ASIHome knows it is not an issue on the thermostat side, because it can be changed through Z-Wave, just not with Vera, but it does work with the VRC0P @ASIHome used previously. (And there one probably just specifies the actual value (0,1,2), hence the comment.)

20

There is also bug 920 first reported by michaelk. However, the “Date Submitted” field is corrupted (apparently right after I added some notes and uploaded two files) and now the bug does not show up anymore when searching for “Trane” or under the “recently modified” lists.