Thermostat delayed temperature update

I have a T40K thermostat that is not promptly recognizing when ambient temperature has changed. Specifically, when the stat calls for heat, it will keep running well past set point temp, resulting in the room being uncomfortably warm. So far, I’ve been around to catch this and manually lower the set point to stop the heating, after which point it seems to update the temp and accurately show that it has run past the set point. Anything I should try to troubleshoot or is this a defective unit?

So that we can best assist, what is the name of the thermostat causing the trouble? It looks like there may be a few T40Ks.

Are you using temperature sensors to average the current temp? Does this happen during both schedules and when the thermostat target is manually set?

West Wing Thermostat is the troublemaker.

I’ve only noticed the issue during schedules, and without using sensors to average temps. This accounts for 80% of my use cases.

It has a 1 degree overshoot value, but I assume you mean it goes well beyond that, right? How far past the set point is it running?

Can you provide a rough time or date when you last noticed this so we can check history?

I would try deleting that thermostat from the panel, then factory resetting that thermostat at this time and relearning it into the panel as a z-wave device.

To reset:

  1. Tap the menu icon on the display.
  2. Tap Installer Settings.
  3. In Installer Settings, tap OK.
  4. Tap Reset to Default.
  5. In Confirm Action, tap OK.
  6. The display will cycle through and show a confirmation message when the reset is complete.

It just happened again right now. Set point was 70 and it ran up to 75 before cycling off.

The highest I’ve seen is it run up to is 77 versus a 70 set point.

I will wait to reset in case you discover anything.

One thing I just noticed is the app showed the 75 temp first. It took the stat several minutes longer to update, at which point it shut off.

Stat is calling for heat again. Stat is showing 69 temp while app shows 73. Set point is 70. Based on how it feels, I believe the app. No way it’s 69 in here.

And approximately 2 minutes later, stat cycles off and shows 73. Obviously the temp did not go up 4 degrees in such a short period of time. Something is wrong with this stat.

Yeah, please factory reset that thermostat.

After removing it, factory resetting it, then adding it again, does the temperature readings function as expected?

Ok, I’ve now had the same problem occur on another one, Upstairs Thermostat. I’ve since reset and re-learned both devices. They are not showing properly in the app. Are you able to refresh the thermostat device list for me so I can see those?

I’ve run a check for new equipment and a link quality test on your Z-wave devices.

Let me know if you see any difference. I would recommend running a network rediscovery at your panel however, a lot of devices just reported a poor link quality and it may help to remap routes with a rediscovery.

Thank you, I am seeing the thermostats now. I removed and relocated a few z-wave repeaters and light switches around today, which is probably why you’re seeing poor link quality. Working to get everything back in order.

I have run rediscovery after moving things around. Based on my past experience, it sometimes takes the network a day or so to kind of settle down and figure out the best routes for everything even after running rediscovery. I dunno, that may not make a lot of sense in theory, but it does seem to be the case in practice.

I’ll be monitoring these thermostats over the weekend. Have to admit, I’m a bit discouraged that two of these new stats that have ignored setpoint. There is a total of five of these in my house.

After over a week, the reset appears to have resolved the issue on both stats. Hopefully this was a one time issue. Thanks as always for your help.

Unfortunately this problem with the thermostats running past setpoint temperature continues to resurface. And it has occurred on 4 of the 5 touchscreen thermostats that I have. It seems to happen once every month or two. I admittedly have not followed up enough. Any similar reports out there and additional troubleshooting steps I should take? As a reminder, I have already factory reset and re-learned them.

Just to confirm and understand the setup, can you provide a description of the HVAC setup with these thermostats so we can best assist?

Are any of the thermostats controlling independent HVAC systems or is it one zoned system?

Which 4 thermostats exhibit the behavior?

Upstairs Thermostat controls an independent system and has exhibited the behavior several times, most recently yesterday which prompted me to make this posting. Set point was 72 but it kept running up to 80 degrees, as confirmed by the app and by my wife complaining that she was burning up. The stat’s displayed temperature kept showing 70 degrees. I was only able to stop it by dropping set point below 70.

The other four stats control a zoned system. All except Family Room have exhibited this behavior at various times in the past.

I should note that Family Room does not run as frequently as the other stats because that room is supplemented with a radiant heating system that is controlled by the older non-touchscreen stat on my account. So that more sporadic runtime could be a reason why it has yet to exhibit the behavior. The older stat has also not exhibited the behavior.

As a reminder, one of the stats in question (Living Room) is about 5 feet from the main panel.

One more fun fact that may or may not be helpful….

The family room stat makes a subtle grinding noise when you interact with the touch screen, almost like an old school hard drive in a PC. The other stats don’t do that. It was the first of the five I purchased. Might it be a slightly different iteration?