SmartThings Community

[RELEASE] Enhanced Z-Wave Thermostat Device Handler with Z-Wave Plus, Battery, Humidity, Lock Controls, Clock Set, Alarm, Swing/Temp, Deadband Configuration, new UI (CT-30/CT-50/CT-80/CT-100/CT-101/CT-110/ZTS-110/ZTS-500/GoControl/Honeywell/Universal)

Yep it’s a bug in the firmware for some CT-xx thermostats. When it’s switched remotely directly from heat to cool (or vice versa) sometimes it takes time for the thermostat to kick in. Hitting the reset button on the thermostat often fixes the issue or switch to off and then cool (or heat). Or just wait till the thermostat figures out that it’s supposed to kick in :roll_eyes:

Awesome… so is the firmware versions being different also causing the different RAW outputs? hmm… any way to update or change the firmware? Reset doesn’t fix the issue. Setting to COOL via the DH makes the CT100 never kick on. Temp just raises, was 4 degree’s off target and still nothing, waited quite some time. Doing it physical works, or setting the DH to AUTO works, just cool on DH makes it not kick on. Darn these things :frowning:

So just found out that when the thermostat reaches its cooling point and turns off. It will not kick back on when the temp raises. I had to cycle back around to auto for it to kick on cooling again. Would this be a broken thermostat? Is there a full factory reset for these things (not the zwave, but the whole unit)

This update may help workaround the firmware bug @RBoy was referring to. There is reset button on the top of the CT-xx thermostat (remove covering). For the Z-Wave models it is a black button you can press with your finger, for the Z-Wave Plus models, there is a small pin hole left of the wires section which contains the button. Don’t forget to press the refresh button after pressing the reset button or updating the code to initialize the thermostat.

Enhanced Z-Wave Thermostat with Temperature, Humidity and Auto Time setting - Version 04.00.01

  • Patch for CT-xxx firmware bug when switching from heat to cool

Key features of enhanced DTH:

  • Supports secure inclusion and encrypted communication for Z-Wave Plus thermostats
  • Battery saver option to extend battery life
  • Synchronizing SmartThings dead-band settings with thermostat (default is 1°)
  • Patches for firmware bugs
    • CT-xxx incorrect date
    • CT-xxx heat/cool switch over
  • Customize thermostat settings (CT-xxx and ZTS-xxx)
    • Temperature reporting threshold
    • Temperature swing threshold
  • Show fan state (running or off even when set to Auto mode)
  • Humidity
  • Battery
  • Clock
  • Heat/Cool temperature settings
  • Auto detect supported thermostat modes
    • Off
    • Auto
    • Heat
    • Cool
    • Emergency heat
  • Auto detect supported fan modes
    • Off
    • On
    • Auto
    • Circulate
  • Thermostat models tested:
    • CT-xxx Z-Wave
    • CT-xxx Z-Wave Plus
    • ZTS-1xx Z-Wave
    • ZTS-5xx Z-Wave
    • GoControl Z-Wave
    • Vivint Z-Wave
    • Lowes Z-Wave
    • Filtrete 3M Z-Wave
    • Honeywell Z-Wave
    • APX Z-Wave

@RBoy: I’m having two CT-100 running on C Wire but not working as a repeater. I paired the thermostats with the Smartthing hub and added the C Wire afterwards. As you described before, to have them acting as a repetaer I have to exclude the devices and then pair them again to Smartthings.

Question, I do have a lot ob webCoRE pistons which controls my thermostats. What happens with my pistons with the thermostats in my pistons, if I exlclude and repair them again? Do I have to update all thermostat related pistons (same thermostat name)

Thanks!

Yes, the C Wire needs to be connected when the thermostat is paired for it to be repeater mode. One possible way is to do a factory reset on the device. This should make the device unavailable to SmartThings and also exclude it from the hub.

To be safe, disconnect or power off your hub BEFORE doing a factory reset because some device send an event to the hub indicating a factory reset and the hub automatically then removes the device from it’s list of devices, powering it off or disconnecting will ensure it doesnt’ get that event.

Once it’s reset, power on your hub, goto your thermostat device page, click on the settings gear icon, scroll down and click on “Replace” device. It will search for the existing device and find it doesn’t communicate and will give you an option to pair a replacement. Now ensure your C-wire is connected and start the pairing process.

This should allow you to re pair the same thermostat without excluding it. Again, I’ve tried this once and it worked here in the lab but I didn’t have any attached apps to it, it was just a PoC so you may want to back up your apps/pistons to be safe before trying it.

1 Like

Thanks @RBoy for the very detailed explanantion. I will try it out and will let you know.

So as far as I know, the CT-100 does not report events back to smartthings on its own. IE, when fan kicks off/on or cooling is running or not. The only time SmartThings knows about these changes are when IT does the polling.

Do you know if this is true for all the CT-XXX? Are you aware of any thermostat that does report event changes? And then last is there a way to increase the polling rate of the thermostat so we can get a better level of history (although it would still be inaccurate, its better then the 30 minutes that smart things does now.)

Definitely not true of all CT-xxx models. Specific firmware have specific issues. Some of which have been patched in this DTH which others would require a firmware update (I.e. newer version)

The new CT-100 Z-Wave Plus model works just fine. Some of the older CT-100 Z Wave model firmware had an issue where the fan state wasn’t reported which was handled via a patch in the DTH. The CT-101 also works fine here in our labs.

It’s also possible that pairing issues leave device with a one way channel. It’s best to use the CT-XX with a C Wire attached and within 50ft if another active z wave device. You should also try to exclude and repair the device which can fix the one way communication issue.

Well the 2 CT-100’s i have do report this information, its just not done as it happens. If i change options on the physical device, you can see them update on smartthings. Say the FAN is running, and it shows that in smartthings, when the Fan kicks off it doens’t reflect a change in smartthings until the normal interval, say when it refreshes in 15-30 minutes

Are you saying that the CT-100 Z-Wave Plus reports these changes AS they happen? Fan kicks off, its updated in smarthings, Fan Kicks on, its updated in smartthings even if it is happening within minutes of each other and without sending a refresh from the app? And not just FAN on/off but also cooling/idle states.

We have the older CT100 Z-Wave which is reporting the fan state just fine here with this DTH in real time. I can see the fan state update in realtime as I turn it on and off on the physical thermostat.

This CT-100 Z-Wave Plus from @TheSmartestHouse reports the events just fine here in the lab ($80):

There’s the CT101 Z-Wave model ($35):

Thanks RBoy for checking. I too get it to update in realtime if I’m physically pushing the buttons. Where the realtime fails is when its working through out the day, normal operations.

Set the thermostat, fans on, shows on smartthings. Thermostat reaches target, kicks fan off, i can hear it is off so I check smartthings and it doesn’t show off in smartthings, if i hit refresh it then shows up. It’ll also show up whatever current state it is during the normal smartthings polling.

The reason i notice this isn’t updating in real time is i can go to the Recently tab, and last update will be a hour ago, and I know within that hour its gone off/on but its not reflected here. (if i physically go press buttons though, all that is real time, or if i press buttons in the app, all real time.) But even history is lost, as on its own it could of turned from cooling to idle to cooling and smartthings isn’t aware of every change, just periodic ones when it polled.

I know what you’re referring to, when the HVAC cooling turns on, the fan state doesn’t get reported due to a firmware quirk and we had put in a workaround/patch in the DTH some time ago. I just checked here again and it seems to be reporting it for the CT100.
However keep in mind that it also depends on the quality of the mesh. If the event is lost it’s possible that it may be reported until the next refresh. I have seen it from time to time “miss” reporting the fan event even with the patch and that’s due to the mesh quality. It works best when the CT has been paired with the C wire attached, is within 50ft of another active device and it never hurts to reboot the hub and do a Z-wave repair.

There is a bug in the new stock/standard ST thermostat DTH when using the thermostat in Celsius ( C ) scale which affects SmartApps that try to set the heating and cooling setpoints simultaneously.

Enhanced Z-Wave Thermostat with Temperature, Humidity and Auto Time setting - Version 04.01.01

  • Fix for bug in standard ST thermostat DTH when using the Celsius scale
  • Improve sync with older CT-xx thermostats firmware

Key features of enhanced DTH:

  • Supports secure inclusion and encrypted communication for Z-Wave Plus thermostats
  • Battery saver option to extend battery life
  • Synchronizing SmartThings dead-band settings with thermostat (default is 1°)
  • Fix for ST Celsius scale bug
  • Patches for firmware bugs
    • CT-xxx incorrect date
    • CT-xxx heat/cool switch over
    • CT-xxx state synchronization
  • Customize thermostat settings (CT-xxx and ZTS-xxx)
    • Temperature reporting threshold
    • Temperature swing threshold
  • Show fan state (running or off even when set to Auto mode)
  • Humidity
  • Battery
  • Clock
  • Heat/Cool temperature settings
  • Auto detect supported thermostat modes
    • Off
    • Auto
    • Heat
    • Cool
    • Emergency heat
  • Auto detect supported fan modes
    • Off
    • On
    • Auto
    • Circulate
  • Thermostat models tested:
    • CT-xxx Z-Wave
    • CT-xxx Z-Wave Plus
    • ZTS-1xx Z-Wave
    • ZTS-5xx Z-Wave
    • GoControl Z-Wave
    • Vivint Z-Wave
    • Lowes Z-Wave
    • Filtrete 3M Z-Wave
    • Honeywell Z-Wave
    • APX Z-Wave

Is there a version of these Thermostats suitable for Europe (Z-Wave)?

Is this the Vivint zwave thermostat? https://images.techhive.com/images/article/2016/12/vivint-element-thermostat-100701315-orig.jpg

@ChadCK this update should fix your issue related to the CT-xxx firmware quirk where switching to auto mode doesn’t kick in the cooler/heater.

NOTE: This also fixed a bug in the stock/standard ST thermostat DTH when using the thermostat in Celsius ( C ) scale which affects SmartApps that try to set the heating and cooling setpoints simultaneously.

Enhanced Z-Wave Thermostat with Temperature, Humidity and Auto Time setting - Version 04.02.04

  • Fixed issue with CT-xxx thermostats firmware not starting when switching to Auto mode
  • Shows C-Wire for CT-xxx thermostats if they are paired with the C-Wire connected (repeater mode)
  • Added basic support for the new ST app

It will only show C-Wire if the thermostat was paired in repeater mode (with the C-Wire connected) otherwise it shows the battery level.

Key features of enhanced DTH:

  • Supports secure inclusion and encrypted communication for Z-Wave Plus thermostats
  • Battery saver option to extend battery life
  • Synchronizing SmartThings dead-band settings with thermostat (default is 1°)
  • Fix for ST Celsius scale bug
  • Patches for firmware bugs
    • CT-xxx incorrect date
    • CT-xxx auto switch over
    • CT-xxx state synchronization
  • Customize thermostat settings (CT-xxx and ZTS-xxx)
    • Temperature reporting threshold
    • Temperature swing threshold
  • Show fan state (running or off even when set to Auto mode)
  • Humidity
  • Battery
  • Clock
  • Heat/Cool temperature settings
  • Auto detect supported thermostat modes
    • Off
    • Auto
    • Heat
    • Cool
    • Emergency heat
  • Auto detect supported fan modes
    • Off
    • On
    • Auto
    • Circulate
  • Thermostat models tested:
    • CT-xxx Z-Wave
    • CT-xxx Z-Wave Plus
    • ZTS-1xx Z-Wave
    • ZTS-5xx Z-Wave
    • GoControl Z-Wave
    • Vivint Z-Wave
    • Lowes Z-Wave
    • Filtrete 3M Z-Wave
    • Honeywell Z-Wave
    • APX Z-Wave

Does anyone know?

I just installed the latest device handler. I noticed the label for the current thermostat status (heating, cooling, idle) does not show on my app. The background color is correct. Also, the word “C-Wire” shows in two lines. How should I correct them? Please see the screenshot below.

This does seem to be working on my RCS TZ45.