The ° symbol can definitely be added (and will be done in the next version). The size and color are ST iOS rendering issues. This Enhanced DH uses the new multiAttributeTile layout. The ST app is the issue here, it is displaying the multiAttributeTiles different from the way it shows the old valueTiles. BTW this issue impacts the iOS ST app, it looks the same on the Android ST app. Report this issue on this page (along with your screenshot):
Noted on the degrees symbol, thanks. Reported the other issue as requested.
1 Like
###Z-Wave Thermostat with Temperature, Humidity and Auto Time setting - Version 2.5.2
- Added the degree symbol to the temperature
- Added support to check for updates for the device handler code
I’ve got a CT-30 and just set up this Device Handler. The onscreen options don’t seem to work. For example, pressing the up/down arrows or changing the slider has no affect on the set point.
Any hints on what I can check?
The thermostat isn’t communicating with you hub. Look at the live logs. For
each command sent there should be an acknowledgement from the hub. If it
not try a 30 min cold reboot. Turn off the hub for 30 min and then power it
on and do a network repair. exclude the device. . If that still doesn’t
work Reboot the hub and pair it again.
Thanks - in progress now…
The 30 minute cold reboot seems to have worked. Something worked, because it’s working correctly now.
It may have something to do with the new hub firmware. One of the thermostats in our lab stopped communicating. We had to exclude it and re pair it for it to start working again. The other option is the 30 min cold reboot.
@RBoy : I have a ct-50 radio thermostat and one side I have the wifi module. The second side I just received the z-wave module. Inserted the module and now both modules are showing (r1 / r2). I select the 2nd module r2 which is the z-wave, click link (or the wording below the tower) and “link” begins to flash. I attempt to +add a thing and it does not see the z-wave, add manually also does not seem to be working. Is there something that I am missing? I unplugged the 12V power and reset the wifi, no issues.
This issue being reported across the board for beaming devices (e.g. Locks
and Thermostats). Please report it to ST support. If enough folks report it
they will investigate it otherwise they are writing it off as local issues.
My suspicion is it’s related to the hub firmware update.
The only reliable solution for now is to exclude the device and pair it
again.
@Aaron FYI. I just sent you an eMail also.
Try rebooting the hub and then try it. It can get funk sometimes and take a
few tries to pair. We are seeing the same issue after the hub firmware
update last week. But it eventually worked after a few tries.
Also try to exclude the device first. Often that really helps. So what we
did was try to pair. Reboot hub. Exclude device and then try to pair again.
To exclude the device put the hub in exclusion mode and then hit the link /
mate label and you should see an exclude message on the ST app. Then try to
pair it
Some ZWave USNAP modules are problematic and can bring down the mesh network. See here.
You have to turn the thermostat on a certain way to avoid the problem. I just replaced it outright with a ecobee.
Super recommendation to reboot the hub. I rebooted, went into exclusion (immediately found the device), went to pair and also instantly worked. My guess is it could of worked w/o the exclusion but anyway it did no harm. Thanks again for the info!
1 Like
You’re welcome.
Do let ST support know your experience. They don’t seem to believe that
rebooting a hub makes it behave better when pairing and excluding devices.
Hello, All.
I am going to assume I am a dork and just can’t find the link to the most up to date CT-100 code for a control without the sliders (horrible for fat fingers!.) If someone can provide a link to the latest and greatest good code for an upgraded experience for the CT-100 I’d be very appreciative!
Thanks,
Todd
Click on Device Handlers and you’ll see the links there. Do note you’ll have to subscribe to the RBoy apps server to get access to the latest code. (See the Getting Access) link on the website.
Has anyone reported issues using this device handler with a CT-100 thermostat and trying to utilize Auto mode?
Auto mode will trigger cooling when coolingSetpoint < device.temperature, but will not trigger heating when heatingSetpoint > device.temperature.
I’ve poured over the code for a good amount of time and cannot find any reason this should not work. Auto mode works if I use the factory Z-Wave Thermostat template and make the changes found at the beginning of this thread.
Additionally, the icons for the battery and humidity tile are not showing. Not sure what to make of this either.
Forgive me if these questions have been answered. I fell asleep reading through this thread last night 
It’s a bug with the thermostat firmware. Try this. On the thermostat cycle
through the modes until you’re in Auto again and it’ll start working.
This happens sometimes when the mode is manually changed through ST and
then brought back to Auto. It will eventually start working but take time
to kick in a quick fix is what I mentioned above.