CT-100 not responding to SmartApp setCoolingSetpoint, does respond to Device command from iPhone

SmartApps & Automations
1

I am working on a 5+2 Thermostat control. I can see the command from the SmartApp to set the temperature to 74, but the CT-100 responds indicating it is going to stay at 77. The second argument to setCoolingSetpoint is 30000 when it doesn’t work but 1000 when it does. I don’t seem to be able to set the second argument from the SmartApp, that might be in a lower level API? I have deleted the SmartApp and reinstalled it and the behavior is the same. Any ideas?

ba343c73-cefd-4125-a237-991d751f49dc 10:17:32 PM EDT: debug Main Level parsed 'zw device: 0C, command: 4003, payload: 02 ’ to [[name:thermostatMode, value:cool, isStateChange:false, displayed:false, linkText:Main Level, descriptionText:Main Level thermostat mode is cool], [name:thermostatSetpoint, value:77, unit:F, isStateChange:false, displayed:false, linkText:Main Level, descriptionText:Main Level thermostat setpoint is 77°F]]
ba343c73-cefd-4125-a237-991d751f49dc 10:17:29 PM EDT: trace setCoolingSetpoint(74.0, 30000)
ba343c73-cefd-4125-a237-991d751f49dc 10:17:15 PM EDT: debug Main Level parsed 'zw device: 0C, command: 4303, payload: 02 09 4D ’ to [[value:77, unit:F, displayed:false, name:coolingSetpoint, isStateChange:false, linkText:Main Level, descriptionText:Main Level cooling setpoint is 77°F], [name:thermostatSetpoint, value:77, unit:F, isStateChange:false, displayed:false, linkText:Main Level, descriptionText:Main Level thermostat setpoint is 77°F]]
ba343c73-cefd-4125-a237-991d751f49dc 10:16:45 PM EDT: trace setCoolingSetpoint(74.0, 30000)

2

Try rebooting your hub, it tends to fix most of these delay issues. The seconds parameter is a delay.

3

Thanks for the tip. I ended up having to reboot the hub and the thermostat and now everything seems to be playing together nicely.

1 Like
4

I have an interesting variation on this one. I have the RBoy device handler on a bunch of CT-100s. They all work great except for one. What’s interesting is that the DH reads changes from the device (when I push buttons on the physical thermostat) but I cannot send any commands to it.

I just tried updating the device handler and rebooting hub, no dice.

I’ve had 2 faulty thermostats I’ve had to return. Wonder if this is another one. I’m dreading removing it from Zwave network and re-adding it as I have it tied to a bunch of stuff… but thinking this might be my only option.

Anybody have an idea?

-Jared

5

Likely, I had posted about this sometime ago when the hub loses directional communication with the thermostat, i.e. it only has one way communication. You could try to hit the reset button on the thermostat and see if that fixes the issue, if not you may have to exclude and re-pair. It’s more a Z-Wave mesh issue. The best way to avoid this issue is to run the thermostats with the C-Wire connected.

6

I run all 5 with C wire. I also have lots of other Z wave devices that are powered hand have around the function to repair the Z wave Network a few times. I’ll try resetting the physical device and repairing it