I thought I share my experience with the Trane Thermostat --- July 4, 2013 -- did not find a TRANE discussion to post it.
1. For zwave USB stick, make sure that you have installed the siliconlabs USB driver.
2. Thermostat setup is pretty straightforward, essentially the default setting is fine, may be you want to set the Heat-Cool minimum difference “H/C Delta” from 3 degrees to a bit higher. Also a good idea is to set the max heat set point “Max Heat SP” lower from 80 to eg 75 -and the Min Cool SetPoint bit higher. With this setting the system does not cool below 70 and does not heat above 75 F.
Both are done in the “hidden” setup (press left key twice, then press and hold the 2 middle buttons for 3 seconds, then follow menu ( Hidden Installer settings → No 4)
3. The registration with the zwave USB stick is straightforward too:
-remove USB stick from MAC,
- press button,
-on Trane select join zwave network (item #4 in the menu) – You can check if it worked in menu item No 5- Thermostat Info.
- on USB press button,
-put USB stick back into MAC
4. In indigo add zwave device and pick the new thermostat. If you add to many devices before
synchronizing with the mac, you might not know which one is which device.
5. One area to be aware of is the status of heat/cool/fan status. There are several systems working in sequence and they have their own intelligence build in and don’t just pass stats through, but delay some changes and messages:
-Compressor/Heater & Fan <-> System controller <-> Trane Thermost <-> Indigo
a. Example (A) state: AC off, Fan off .. sequence of events:
i. MAC sends new temperature cool set-point that is lower than the current
ii. Trane accepts command and send signal to compressor and fan controller immediately.
They react pretty much immediately.
iii. Trane sends new status to MAC: FAN ON, AC ON
iv. Its takes about 1 second for indigo to get this set. A trigger on FAN ON or AC ON fires immediately, but the status is not updated when your actions check the status. Adding 2 seconds delay before your actions start solves that.
b. Example (B) state: FAN on, AC on.. sequence of events:
i. Trane reaches temperature target
ii. Sends FAN off and AC off to system --> compressor and FAN
iii. The system controller leaves the FAN (in my case) on for about 2 minutes to use the “cold” energy stored in the heat exchanger (and likely also if Heat is on, but I will only check this in 6 months from now.. July in Dallas
). If you want to change that setting you have to ask your AC support person to change the Honeywell system controller (in my case). But that setting actually makes sense.
iv. Trane send message to indigo: FAN off, but AC state still stays on- I believe this is a side effect of the system that tries to protect the system from cycling too frequently. The setting to impact that time is in the Trane “hidden menu” item No 6 “Min Off” time. The default is 5 Minutes.
⇒indgo BELIEVES THAT AC IS RUNNING 5 MINUTES LONGER THAN IT ACTUALLY IS and 2 MINUTES LESS FOR THE FAN
v. I would call this state: delayACoff mode:
- indigo status: AC on, Fan off …. that state actually does not make sense
- Actual status: AC is off, fan is still on.
I use this state to determine AC has gone to off state for counting measuring run-times.
vi. After about 2 minutes the FAN switches off (setting in the system controller , not the Trane)
vii. After 5 minutes (this can be set in the TRANE hidden setup No 6) TRANE send message “AC off” to indigo.
viii. indigo needs about 1 second before all status is set properly.
An AC ON/OFF event triggers faster than the device states get changed (add a delay of ~ 2 seconds before your actions start, by then the device status is updated)
After understanding the sequence all actions work fine and eg times of what is on/off etc works fine
Karl
ps machomestore was very helpful. One of the tranes was dead on arrival, I got that replaced within hours.