SmartThings Community

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


( - Make your home your butler!) #405

That’s ST polling your thermostat. If you’re running on a battery you can turn on the power save mode in the device preferences page which will reduce the frequency of polling to once in 30 minutes. If you’re running on the C wire then don’t worry about it. If you’re running on battery then you may want to consider adding a z-Wave repeater between your thermostat and hub. Also reboot your hub and repair your z-wave network, what you’re saying sounds like the thermostat and hub are having trouble communicating which typically indicates a z-wave mesh issue.

(Alix) #406

I’m not sure if this is by design, but I find it confusing that the battery percentage is being displayed in the bottom left corner next to the drops that I would associate with humidity.

(Lee Florack) #407

The green 57% in your picture IS the humidity level. The battery level is not shown on that picture but is centered at the bottom of the screen if you scroll down. It is also in green but shows a battery above it.

(Alix) #408

Right, however, I am talking about the percentage displayed in the main tile in the lower left corner, which matches my battery level.


(Lee Florack) #409

Hmm. Looks different from mine. I have an iPhone so maybe you have an Android?

(Alix) #410

Yes, I have a Nexus 6P. Actually, the other question I have is about the arrows on the right with a 0 in the middle. I assume that’s supposed to be the set temp? I like the idea, so when I look at my living room I can see just about everything without having to actually go into the device, it just doesn’t seem to be working right for me.

( - Make your home your butler!) #411

Those are issues with iOS Android app. It’s been reported to ST but feel
free to drop an email to ST support about the UI issues.

( - Make your home your butler!) #412


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

  • Updated attributes to match the new ST standards (PLEASE click Refresh to activate changes after updating code)
  • Improved syncing of Fan and HVAC operating status when settings are changed on the thermostat for non reporting thermostats
  • Support for more thermostat models
  • Remove configure button, now it’s automatic after a setting update
  • Support dynamic thermostat configuration without repairing, just click Refresh to detect new configuration

Enjoy your updated thermostat! :slight_smile:

(Clint) #413

Loaded up 3.00.00 and it seems that the “Quick Set Cooling Point” command from WebCore is no longer working. Had to change to “Set Cooling Point”.

Not even sure what the difference is, but I will have to pick through my pistons and make sure i am using the correct command.

Was there a change that can account for this?


(Uriel A Colon) #414

Thanks for the update RBOY,

Is their a way to resume schedule with this device handler?

( - Make your home your butler!) #415

That is correct, it was done to harmonize with the latest ST standards. The new ST standard has replaced them with

setHeatingSetpoint(NUMBER setpoint)
setCoolingSetpoint(NUMBER setpoint)

However, you bring up a good point, we added the two old API’s back in for compatibility purposes (quickSetCool and quickSetHeat) so it won’t break existing custom actions, you can upgrade to 03.00.01

( - Make your home your butler!) #416

The device handler doesn’t handle schedules, those are done by SmartApps like the 5-2 Day Scheduler.

(Clint) #417


Another observation on the 3.x release.

Before 3.x, I used to get almost immediate updates in logging, the ST app, Actiontiles and WebCore for my CT100 thermostat when a setpoint was changed at the thermostat or using Alexa, etc.

Now it seems to take a minute or two before I see the status come back. The weird thing is that my other thermostat (cheap GoControl) used to be that way in 2.x and I used WebCore to refresh. It now returns status much quicker that the CT100 without a refresh.

Might just be me imagining things, but thought I would bounce that off you any way.


( - Make your home your butler!) #418

It’s probably your z-Wave setup which is changing the behavior. Try exclude and repairing your thermostat and doing a Z-Wave repair. It’s taking time to respond likely the network is losing the commands or getting busy.

(Peter Venlet) #420

I am having trouble locating the updated code on your site … I have a username and password

(Alix) #421

I recently noticed that my CT-101 is no longer reporting 0.5 degrees. My thermostat displays 73.5, but everything in ST is showing 74. I have verified that I have the reporting threshold set to 0.5.

( - Make your home your butler!) #422

Browsers tend to cache the pages sometimes. Clear your cache and refresh
the page and it should show up

( - Make your home your butler!) #423

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

  • Added support for displaying current temperature with up to 0.1 degree precision when supported by thermostats

See previous post for major release details:

(Ernie) #424

Since updating, neither my routines or WebCore can change the cooling or heating setpoints on CT100.

( - Make your home your butler!) #425

ST has changed the API’s for thermostat setpoints. While the old ones
(quickSetXX) should still work with the 03.00.01 or newer version you
should update the commands in your apps. They are now