Occasional Issue with RM and CT100 Thermostat

tsviper · October 17, 2018, 10:03pm

Many thanks!

keithcroshaw · October 17, 2018, 10:50pm

Wow I currently get around 9 months... I'll have to weigh that into the equation.

drew.covi · November 1, 2020, 6:32pm

drewcovi/Hubitat/blob/master/Drivers/Remotec ZTS-100/Remotec ZTS-100

/**
 *  Remotec ZTS-100 driver for Hubitat
 *
 *  Copyright 2020 Drew Covi
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 *  Version 1.0 - 11/01/2020     Initial Version
 */
metadata {
	definition (name: "Remotec ZTS-100", namespace: "drewcovi", author: "Drew Covi") {
		capability "Refresh"
        capability "Battery"

This file has been truncated. show original

I’m in your boat, and just released a draft based on a related driver for ZTS-500 (but adjusted for proper parameter mappings etc)

kahn-hubitat · November 1, 2020, 7:28pm

i have 5 ct100 is one house and a couple newer xwave plus.. and see similair issues with missed setpoint.. i just check again .. it seems to be if yhou try to raise it too many degrees too quickly..

tsviper · November 2, 2020, 1:48am

Thank you @drew.covi. So far this driver is working well on my zts-110. Love having all the confit settings available. Thanks for sharing!

tsviper · November 3, 2020, 3:08pm

@drew.covi
I spoke too soon. The driver is working for controlling the thermostat and it gets status updates when controlling from the thermostat buttons, however if I control it from Hubitat the status in Hubitat does not update. Very strange. Also the reset filter doesn't do anything for me. I have the ZTS-110 so maybe that is why its not working for me.
When I go back to the generic z-wave driver I still experience the same issue so I think it may have something to do with the association settings that were applied when I hit the configure button after assigning your driver.

Here is the manual for the 110 if it helps: Connecting...

drew.covi · November 3, 2020, 4:05pm

If you were having issues when changing setpoint, then my latest update should resolve that. Inherited a lot of the driver code from the 500 series thermostat and for whatever reason that driver doesn’t quickly check the value after setting it (it does so for almost every other characteristic).

drew.covi · November 3, 2020, 4:43pm

@tsviper just a heads up I’ve also resolved the typo for resetFilter.

There’s a bit of math going on under the hood since most folks don’t calculate filter replacement in hundreds of hours with a max of 4000.

tsviper · November 3, 2020, 11:27pm

Thank you @drew.covi.

When I set the mode from Hubitat it doesn't update the mode status in the driver. I'm no coder but I was able to add the line below to refresh the mode after it is set and it works now.

Also pressing the Reset Filter button still doesn't clear the Filter text on my thermostat screen. Not that big of a deal as I can reset it from the thermostat although I have to turn off "easy mode" first.

Thanks again for this great driver.

Code:
def setThermostatMode(value) {
if (logEnable) log.debug "Executing 'setThermostatMode'"
if (logEnable) log.debug "value: " + value
def cmds =
switch (value) {
case "auto":
if (logEnable) log.debug "Switching to auto mode..."
cmds << zwave.thermostatModeV2.thermostatModeSet(mode: 3).format()
break
case "off":
if (logEnable) log.debug "Switching to off mode..."
cmds << zwave.thermostatModeV2.thermostatModeSet(mode: 0).format()
break
case "heat":
if (logEnable) log.debug "Switching to heat mode..."
cmds << zwave.thermostatModeV2.thermostatModeSet(mode: 1).format()
break
case "cool":
if (logEnable) log.debug "Switching to cool mode..."
cmds << zwave.thermostatModeV2.thermostatModeSet(mode: 2).format()
break
case "emergency heat":
if (logEnable) log.debug "Switching to emergency heat mode..."
cmds << zwave.thermostatModeV2.thermostatModeSet(mode: 4).format()
break
}
cmds << zwave.thermostatOperatingStateV1.thermostatOperatingStateGet().format()
cmds << zwave.thermostatModeV2.thermostatModeGet().format()
return delayBetween(cmds, 1000)
}