Why did I change thermostats?

If there is any other information I can provide, I will be happy to do so.

I thought about it and changed the driver for the thermostat to the Generic Zigbee Thermostat. If that works better, then it would isolate the problem to the Zen driver. If it is no different, then it would rule out the Zen driver. So far, we left and returned and the temperature settings changed as they should have. However, it will take longer observation to see if it makes any difference.

1 Like

Dont know its a driver issue, you reported the same issue with a completly different thermostat on a different wireless protocol.

You are, of course, correct. I wanted to see if there would be any difference in behavior. It seemed to do okay with the day/night schedule switch, but we left for an appointment and when I checked remotely, it had changed the heating setpoint but the cooling setpoint was the one for home, not away. I looked at the logs, and it had changed to the away setpoint, but then the cooling setpoint reverted to the home setpoint 9 seconds later. Here are the entries:

|heatingSetpoint|70|°F|Zen Thermostat heatingSetpoint is 70°F|DEVICE||2019-07-01 11:22:54.176 EDT
|temperature|76.3|°F|Zen Thermostat temperature is 76.3°F|DEVICE||2019-07-01 10:59:57.730 EDT|
|thermostatSetpoint|76|°F|Zen Thermostat thermostatSetpoint is 76°F|DEVICE||2019-07-01 09:54:45.313 EDT|
|coolingSetpoint|76|°F|Zen Thermostat coolingSetpoint is 76°F|DEVICE||2019-07-01 09:54:45.310 EDT|
|thermostatSetpoint|80|°F|Zen Thermostat thermostatSetpoint is 80°F|DEVICE||2019-07-01 09:54:36.283 EDT|
|coolingSetpoint|80|°F|Zen Thermostat coolingSetpoint is 80°F|DEVICE||2019-07-01 09:54:36.278 EDT|
|heatingSetpoint|55|°F|Zen Thermostat heatingSetpoint is 55°F|DEVICE||2019-07-01 09:54:36.251 EDT|
|temperature|75.4|°F|Zen Thermostat temperature is 75.4°F|DEVICE||2019-07-01 09:04:31.921 EDT|
|thermostatSetpoint|76|°F|Zen Thermostat thermostatSetpoint is 76°F|DEVICE||2019-07-01 07:30:02.811 EDT|
|coolingSetpoint|76|°F|Zen Thermostat coolingSetpoint is 76°F|DEVICE||2019-07-01 07:30:02.808 EDT|

11:22:54 is the time we arrived at home.

I changed the driver back to the Zen Thermostat driver from the Generic Zigbee Thermostat driver. I am trying one other thing. I changed the mode from auto to cool to see if the changes to away and home mode will be more reliable if it is only trying to change one setting instead of two.
@mike.maxwell

Having it set to cool only did not fix the issue. Logs from this afternoon show:

|thermostatSetpoint|76.0|°F|Zen Thermostat thermostatSetpoint was set to 76.0°F|DEVICE||2019-07-01 15:38:17.251 EDT|
|coolingSetpoint|76.0|°F|Zen Thermostat coolingSetpoint was set to 76.0°F|DEVICE||2019-07-01 15:38:17.250 EDT|
|thermostatSetpoint|79.9|°F|Zen Thermostat thermostatSetpoint was set to 79.9°F|DEVICE||2019-07-01 15:38:17.202 EDT|
|coolingSetpoint|79.9|°F|Zen Thermostat coolingSetpoint was set to 79.9°F|DEVICE||2019-07-01 15:38:17.194 EDT|
|thermostatSetpoint|76.0|°F|Zen Thermostat thermostatSetpoint was set to 76.0°F|DEVICE||2019-07-01 15:38:17.129 EDT|
|coolingSetpoint|76.0|°F|Zen Thermostat coolingSetpoint was set to 76.0°F|DEVICE||2019-07-01 15:38:17.128 EDT|
|heatingSetpoint|70.0|°F|Zen Thermostat heatingSetpoint was set to 70.0°F|DEVICE||2019-07-01 15:38:17.121 EDT|
|temperature|78.1|°F|Zen Thermostat temperature is 78.1°F|DEVICE||2019-07-01 15:08:37.938 EDT|
|temperature|77.2|°F|Zen Thermostat temperature is 77.2°F|DEVICE||2019-07-01 14:01:36.732 EDT|
|thermostatOperatingState|idle||Zen Thermostat thermostatOperatingState is idle|DEVICE||2019-07-01 13:04:25.526 EDT|
|thermostatOperatingState|fan only||Zen Thermostat thermostatOperatingState is fan only|DEVICE||2019-07-01 13:04:25.435 EDT|
|thermostatSetpoint|80.0|°F|Zen Thermostat thermostatSetpoint was set to 80.0°F|DEVICE||2019-07-01 13:04:24.130 EDT|
|coolingSetpoint|80.0|°F|Zen Thermostat coolingSetpoint was set to 80.0°F|DEVICE||2019-07-01 13:04:24.129 EDT|
|thermostatSetpoint|79.9|°F|Zen Thermostat thermostatSetpoint was set to 79.9°F|DEVICE||2019-07-01 13:04:15.892 EDT|
|coolingSetpoint|79.9|°F|Zen Thermostat coolingSetpoint was set to 79.9°F|DEVICE||2019-07-01 13:04:15.891 EDT|
|thermostatSetpoint|76.0|°F|Zen Thermostat thermostatSetpoint was set to 76.0°F|DEVICE||2019-07-01 13:04:15.012 EDT|
|coolingSetpoint|76.0|°F|Zen Thermostat coolingSetpoint was set to 76.0°F|DEVICE||2019-07-01 13:04:15.010 EDT|
|heatingSetpoint|55.0|°F|Zen Thermostat heatingSetpoint was set to 55.0°F|DEVICE||2019-07-01 13:04:15.008 EDT|
|heatingSetpoint|54.9|°F|Zen Thermostat heatingSetpoint was set to 54.9°F|DEVICE||2019-07-01 13:04:14.934 EDT|
|thermostatSetpoint|80.0|°F|Zen Thermostat thermostatSetpoint was set to 80.0°F|DEVICE||2019-07-01 13:04:14.862 EDT|
|coolingSetpoint|80.0|°F|Zen Thermostat coolingSetpoint was set to 80.0°F|DEVICE||2019-07-01 13:04:14.855 EDT|
|heatingSetpoint|55.0|°F|Zen Thermostat heatingSetpoint was set to 55.0°F|DEVICE||2019-07-01 13:04:14.764 EDT|

Auto mode on this thermostat doesn't work unless it's enabled via the advanced configuration parameters.
It's very deceiving, parameter A in the advanced configuration has two settings:
AN: Auto enabled false
and
AY: Auto enabled true

If the setting is AN, and you set the thermostat mode to auto from the driver, the thermostat will display Auto (A), however it won't update the thermostatOperatingState, so effectively you loose control over the thermostat.
If you set it to AY, then auto mode works, however the active setpoint shown on the thermostat, and what it reports to the driver are all sorts of screwed up and make no sense what so ever.

For now do not enable auto mode in the advanced configuration, and do not set the thermostat mode to auto in the driver.

You will need to manage heat/cool mode switching manually or via an automation.

With the thermostat mode set to heat or cool thermostat scheduler worked as expected.

I've been testing (on my house) the GoControl CT-101 in auto mode, which does seem to work as expected, however it appears less accurate in it's temperature reporting, which directly effects its ability to maintain a consistent ambient temperature...
This is also true when manually changing modes.
The CT-101 does have a temperature calibration setting (whole degrees F only), but I can't ever get a consistent reading from it one way or the other that matches the calibrated sensor I have next to it.

The Zen on the other hand reported within +- 0.2 degrees of my reference sensor out of the box.

1 Like

When I originally had the Zen set up, I did not use any of the advanced functions. However, in the driver, I had the mode set to auto. I changed the mode to cool today. I had hoped that would make it behave. However, when we left and returned, it still was not behaving properly as the log entries I posted above showed. It only seems to be the cooling setpoint that is doing this. I see the heating setpoint change only once but the cooling setpoint changes, then changes again.
I am considering doing a factory reset on both my C4 and C5 hubs and making the C5 hub the master hub with the thermostat and all devices other than the Iris V1 devices which would then connect to the C4 hub. However, I would prefer to avoid that drastic a step.

The other option might be to delete the Thermostat Scheduler and try figuring out how to do the functions with Rule Machine.

Edit: I just eliminated the Home/Away temperature changes in the Thermostat Scheduler. I am going to see if there is a way to implement the home/away changes in Rule Machine instead and still have the Thermostat Scheduler do the normal operation of the thermostat.

If anything, I think the problem area of the Thermostat Scheduler might be in that home/away temperature settings. If the thermostat works properly with just the wake/night temperature changes, then it may help isolate where the problem might be.

I wouldn't go that route.

Can you install a virtual thermostst, then another instance of thermostat schedular with the same configuration?, then please monitor them and see if behave the same.

1 Like

I had not thought of a virtual thermostat. I'll try that.

Edit: Okay, I tried creating a virtual thermostat, but it does not seem to do anything. The readings are "null" as it has no data. The dashboard tile I made to see this has "unknown and unknown" for temperature and state. I don't know if I am doing this correctly. OTOH, I still have my CT101 Radio Thermostat which I could put batteries in and set up, even if it would not be actually controlling anything. It was the same behavior with it that prompted me getting the Zen thermostat, hoping it was a Z-Wave issue that getting a Zigbee thermostat would fix.

@mike.maxwell I have noticed something that may or may not be pertinent. If I look at the Zigbee Child and Route info and don't see the Zen thermostat, indicating that (I believe) the thermostat is linked directly to the hub, it appears to behave better than when I see it routed through one of the Iris V2 outlets I have. Could routing be figuring into this issue? If so, would there be any way to force the thermostat to only connect directly to the Hubitat and not route through a repeater device?

Also, I had an idea to remove the CT101 thermostat from the C4 hub where I had it configured, and connect it to the C5 hub instead. I don't have a way to link it to the C4 controller hub though, as the Hub Link list of devices does not contain an entry suitable for the thermostat. I will keep a log going though so I can see if it behaves when connected to the C4 hub with an instance of Thermostat Scheduler configured on the C4 hub to control it as well.

The driver for virtual thermostat is named Virtual Thermostat, that is the device you need to create.
Let's not worry about zigbee routes or messing with the ct101 right now.
Let's set up a duplicate instance of thermostat scheduler using the same settings as your production instance and see if the setpoints in this test instance change as expected.

Okay. I had done it wrong the first time. I now have the virtual thermostat set up. How do I get a temperature reading for it? I can see where I can manually input a temperature, but how do I feed it a temperature to see if it is working? Does it matter? Am I just looking for the schedule and home/away changes with this and temperature is irrelevant?

Here is a picture of my dashboard with the Zen and Virtual-Zen thermostats side by side.

we need to leave the dashboard out of it for now, that adds another layer on top that we don't need to deal with.
The goal here is to determine if the issue is thermostat scheduler or the zen thermostat and or the zen thermostat driver.
All we're interested in right now is the setpoint changes being sent from thermostat manager to the two thermostats (zen and virtual), specifically after the mode change and time of day changes what are the resulting setpoints as shown in the driver details, we don't care if the heat and or AC actually turn on or not.

1 Like

The only reason I wanted a dashboard tile was so that I could check to see if it is changing when we are away since I would not be able to check my logs while we are not home.

ok

I can say now that both the Zen thermostat has issues. I tested the virtual and real thermostats by watching the screen while removing the battery from my Smart Fob (my wife is not home, so her key fob is registering not present already.

I observed the presence switching from home to away. I watched the thermostats (real and virtual) change from home settings to away settings and the HSM arm to away. I replaced the battery so my Smart Fob would register presence and saw the HSM disarm.

Virtual thermostat changed back from away to home mode for both heating and cooling setpoints.

Physical Zen thermostat changed heating setpoint and cooling setpoint, but the cooling setpoint then reverted to the away setting again. Log extracts below:

Physical thermostat:
|thermostatSetpoint|79.9|°F|Zen Thermostat thermostatSetpoint was set to 79.9°F|DEVICE||2019-07-03 14:24:35.444 EDT|
|coolingSetpoint|79.9|°F|Zen Thermostat coolingSetpoint was set to 79.9°F|DEVICE||2019-07-03 14:24:35.441 EDT|
|thermostatSetpoint|76.0|°F|Zen Thermostat thermostatSetpoint was set to 76.0°F|DEVICE||2019-07-03 14:24:35.412 EDT|
|coolingSetpoint|76.0|°F|Zen Thermostat coolingSetpoint was set to 76.0°F|DEVICE||2019-07-03 14:24:35.396 EDT|
|thermostatSetpoint|79.9|°F|Zen Thermostat thermostatSetpoint was set to 79.9°F|DEVICE||2019-07-03 14:24:27.071 EDT|
|coolingSetpoint|79.9|°F|Zen Thermostat coolingSetpoint was set to 79.9°F|DEVICE||2019-07-03 14:24:27.070 EDT|
|thermostatSetpoint|76.0|°F|Zen Thermostat thermostatSetpoint was set to 76.0°F|DEVICE||2019-07-03 14:24:27.040 EDT|
|coolingSetpoint|76.0|°F|Zen Thermostat coolingSetpoint was set to 76.0°F|DEVICE||2019-07-03 14:24:27.038 EDT|
|heatingSetpoint|70.0|°F|Zen Thermostat heatingSetpoint was set to 70.0°F|DEVICE||2019-07-03 14:24:26.290 EDT|

Virtual thermostat:
|thermostatSetpoint|76.0|°F|Virtual-Zen thermostatSetpoint was set to 76.0°F|DEVICE||2019-07-03 14:24:25.181 EDT|
|coolingSetpoint|76.0|°F|Virtual-Zen coolingSetpoint was set to 76.0°F|DEVICE||2019-07-03 14:24:25.179 EDT|
|heatingSetpoint|70.0|°F|Virtual-Zen heatingSetpoint was set to 70.0°F|DEVICE||2019-07-03 14:24:25.060 EDT|
|heatingSetpoint|55.0|°F|Virtual-Zen heatingSetpoint was set to 55.0°F|DEVICE||2019-07-03 14:22:36.348 EDT|
|thermostatSetpoint|80.0|°F|Virtual-Zen thermostatSetpoint was set to 80.0°F|DEVICE||2019-07-03 14:13:27.623 EDT|
|coolingSetpoint|80.0|°F|Virtual-Zen coolingSetpoint was set to 80.0°F|DEVICE||2019-07-03 14:13:27.620 EDT|
|thermostatSetpoint|76.0|°F|Virtual-Zen thermostatSetpoint was set to 76.0°F|DEVICE||2019-07-03 14:13:27.516 EDT|
|coolingSetpoint|76.0|°F|Virtual-Zen coolingSetpoint was set to 76.0°F|DEVICE||2019-07-03 14:13:27.484 EDT|
|heatingSetpoint|70.0|°F|Virtual-Zen heatingSetpoint was set to 70.0°F|DEVICE||2019-07-03 14:13:27.367 EDT|

Hopefully, this will help with the diagnosis of this problem.

Edit: I manually refreshed the Zen thermostat and the cooling setpoint then updated to the correct setting.

One other thing I will try to observe is whether the thermostat itself is updating and it is just not reporting back or reporting back something incorrect.

Edit: On second thought, since the Zen's screen blanks and then on touching, displays the current temperature, not the setpoint, I don't know if I will be able to observe the change at the thermostat. I need to go on the web site and see if there is a way to show it though the changes. The CT101 had the display on constantly so it could be observed.

two taps on the zen shows the current setpoint for the active mode, sounds like there's an issue with the driver (less likely to be something else at this point)
I've noticed a few minor issues with mine as well, We'll continue this discussion over a PM shortly

2 Likes

Okay. Thanks.

What firmware version does your Zen have? Smartthings pushed a newer version to the Zens a few months ago.

Also, my first Zen which I got second hand was all kinds of screwy regarding not maintaining settings send to it via zigbee. It would just randomly change back to previous settings after a few minutes. Sometimes!

After about a year of conversations with Zen and Smartthings, Zen provided me a new one free of charge (I’m local to them in Melbourne where they’re from). 99.9% of the weirdness went away.

The Zen I have was an early release model, likely an extra engineering sample that Zen sent to ST, and ST sent to me...
I can't imagine there's any earlier firmware versions than mine in the wild...