Strange Thermostat Behavior with WDTC-20

Ok since the most recent revision I have been seeing that when you set a heat or cool set point, the other field get populated with the same value.

example: I set the heat point at 66 degrees. Wait a few minutes come back and look at the dash board the cool set point is now 66 also.

Anyone else seeing this?

Can we get an explanation for this?

Vera is the only controller that does this that I have used.

Mistro - Glad I am not alone in this one. I noticed this started happening with the current revision.

I have the same thing happen on my WDTC-20

Anyone know what is going on?

Out of curiosity, do your thermostats support scheduling? If yes, do you use the thermostat’s scheduling or do you use Vera?

I just put in an RCS TZ43.

Thanks,
D.

I do not use the Scheduling as I believe them to conflict with VERA or any controller.
We usually disable the feature when we install a system.

As far as I can tell, the only way to disable scheduling is by setting this thermostat to Hold. Does that sound familiar?

I am having problems with the thermostat taking commands. I just removed and re-added it, so I’ll see how it goes. It did report the current settings/temp - it just wouldn’t take a new setting. I also had some weirdness where it reported the current settings at -6C for a little while. I also noted that Vera logs say that a cooling point was set, even when you are changing the heating point. I opened a ticket to check on that one.

D.

If you place most stats on HOLD that will disable Zwave commands on some products.

I’ll look at the docs give me a couple of mins

From What I read on the TZ43 manual is that as long as the stat is in hold the Remote network has control.

the HAI version you have to do a program change as the Hold button Locks the Zwave from control.

In either case you need to keep the button in the correct position in order to keep control of the stat by Zwave.

Good Luck

The temp setting both heat and cold has been fixed!

Yes, the independent setting of the heat and cool points seems to have been fixed in the latest revision (yesterday).

However, the WDTC-20 still has the interesting action of taking a set point at 1 degree off of the assigned value. At common temps, this seems to default to an odd temperature for the thermostat. Bug in the tstat or Vera?

RandyS

in another thread is MCV states that its because of conversion from deg C to F.
This is the only controller that seems to do this!