I have a CT101 on a C4 hub with a driver from tmastersmart, all of which I have had for years. The CT101 is controlled by Rule Machine rules that have been running for years.
Yesterday I realized a routine didn't run as expected and when I looked in the logs, the command to change the temperature ran as expected but the thermostat did not change the setpoint. I rebooted the hub thinking that might clear it up. Today a different rule which had successfully worked yesterday using the same command but was earlier in the day than the rule that failed yesterday also failed to get the thermostat to change the setpoint.
I have power cycled the CT101 tonight (pulled the C wire) and the next time the rule ran, it successfully changed the setpoint.
Any suggestions on what to look for in troubleshooting this or is it as simple as the device might need to reconnect to the zwave network every once in a while?
Do I understand that rebooting the CT101 resolved the issue, and that this is the first and only time it happened? If so, I suspect it may have partially locked-up for some reason. If it consistently happened, then maybe a regular reboot of the device or replacing it might be in order, but otherwise, monitoring would likely be the thing to do for now.
Unfortunately, it failed again today. I looked into my rule some more and wondered if maybe a command that occurs later was happening too fast and preventing the one that wasn't taking place from completing. I put a delay in and it seems to be working well now. I'm not sure why this wasn't a problem in the past, but hopefully this solves the issue.
Did you press the reset button. You should not have to remove power. .
Reboot the hub power it down and restart it so the zwave radio gets rebooted
do zwave repair.
see what happens
I have seen that before sometimes mine will run 2 years before you have to press reset.
