I have been using CT101 Z-Wave Thermostat for several years without any problems. This years I have had problems with communication and now I can’t get any of my routines to work. They act like they are working but the temperature never changes and the event logs never show the activity.
Are others having issues with their CT100/101 thermostats? Is this due to the groovy changes Samsung did?
I am trying to figure out if I am going to need a new thermostat to work with Smartthings. That is usually a problem because my furnace does not have a C wire.
Thoughts and suggestions welcome. (FYI, already tried the rests and exclude options without any success.)
Probably not. Groovy is going away at the end of the year, so devices should still be working OK.
I suggest that you check if your thermostat device is still on a DTH (device type handler) or already on an edge driver, and switch to edge if you can. You can tell by hitting the tree dots in the upper right of the device in the app. If Driver is a menu choice, the driver is now edge. If not, still old DTH.
Thanks @BartschLabs for the reply. The device is still using a DTH. Is there anyway to force it to use a new driver? I am surprised it is not working with the DTH since it has worked great for about 3-4 years and then failed this heating season. I tried toggling the DTN by editing the device, switching it to draft clicking update. Then doing the same and switching it to published but I am still having the same issues.
If there is an edge driver for it, you’ll have to remove the device from SmartThings (which will probably delete your routines, BTW), and rediscover it, for the edge driver to be applied.
I found some information online and tried to update the hub with the 2gig CT100 driver but unfortunately it didn’t recognize the device even though the CT101 and CT100 should use the same drivers.
hmmm I am using a ST v2 hub and it doesn’t like the device handlers I had been using for several years. It started giving a network error any time I tried to change the temperature.
I’ve been using a CT-101 for 5 or 6 years now, and twice I’ve had it stop responding to SmartThings, similar to what you’re describing. Both times I followed R-Boy’s quick fix and it solved my issue in no time.
I don’t know if it’s exactly the same issue you’re having, but I hope it helps!
@kajoyce has a 2gig CT101 z-wave thermostat that is not being discovered by the z-wave thermostat edge driver. @kajoyce says it is almost identical to the CT100 thermostat, which is supported by the z-wave thermostat edge driver. What would be needed to add support for the CT101?
I am not sure how to get the fingerprint of the CT101 as you are requesting? I can provide the data and raw description from the API:
Data | - manufacturer: Radio Thermostat Company of America (RTC) - networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE - productId: 12 - productTypeId: 25857 |
It looks like ST moved my thermostats to an edge Driver yesterday, and now I am having some issues.
I have 2 CT101 thermostats and 1 CT 100 thermostat. ST v3 hub
The thermostat works fine, if I manually control it at the physical thermostat itself. For example, if I lower the thermostat setting by 2 degrees at the physical thermostat, this is reflected in the ST app. It works perfectly.
I can also control the thermostat using Amazon Alexa. For example, if I ask Alexa to lower the thermostat by 2 degrees, this is reflected on the physical thermostat and in the ST app. It works perfectly.
I can also use the Alexa app to adjust the thermostat temperature setting.
The problem is controlling the thermostat from the ST iPhone app. In the app, I can monitor the furnace actions. I can also change the mode, from heat to cool to off, etc.
The issue is trying to increase or decrease the thermostat temperature setting. For example, when I try to decrease the thermostat temperature and I press the minus key in the app, it errors out. But, the thermostat actually changes the temperature setting.
Say the heat setting is 70. If I press the minus key, the app after about 30 seconds errors out and tells me there is a network issue and shows the settings still at 70 degrees. But the thermostat will actually now be set at 69 decrees (when I look at the physical thermostat).
@plgill99 I use a V2 hub and have similar issues but with the old device Z-Wave thermostat handler. I can’t even get the beta drivers to recognise my CT101 thermostat to try the new driver. I also don’t use Alexa for controlling the thermostat. I only use the actual thermostat and the Smartthings app.
Trying to use the old CT100 device handler fail with the error for changing the temperature but it does NOT change the temperature on the thermostat. While I am using the Z Wave Thermostat handler I can change the temperature but can’t run any routines and if I change the temperature on the thermostat it is never reported to Smartthing in the temperature control section of the app. It does show in the actual room temperature that the temperature is registered.
This all used to work fine under the old CT100 device handler but broke sometime between April and November this year.
Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
And we would also need you to send Hub Logs. If you don’t know how to send those logs the procedure is the following:
Enter the corresponding Hub and go to “view utilities”
Click on “send” below “send hub logs”
And please let us know which Samsung Account you’re using and if you have more than one Hub, the name of the one where the device is paired. This last piece of information can be sent by DM to me directly, so you don’t have to share it publicly.
Also, please confirm the email address associated with your Samsung Account.
You can send this last information on a DM to myself.