Thermostat 2.3.4.134 issue

@bravenel I don't use Thermostat Scheduler. Instead, I have rules set in Rule Machine 4.0 to control modes, scheduling, etc. Today, I woke to find the house getting colder and colder. Somehow my Zen Zigbee Edition got switched from Auto mode to Cool mode. It was getting colder and colder in the house. I changed it back to Auto (took two attempts) and the house is warming up again.

I saw there was a known issue with Thermostat Scheduler. To me, it appears the issue isn't just with that app.

Well, if you aren't using Thermostat Scheduler, that could hardly be related to what happened, right?

Do any of your rules set Thermostat Mode?

Ordinarily, devices don't just set themselves without something doing it. Look at the Events for the thermostat using the Events button on its device page. Perhaps you can see when it was set to cool, and go from there to find what might have caused it. It's possible someone fat-fingered the thermostat itself.

1 Like

Okay, someone fat-fingering the thermostat is not what happened. It sits on the wall and only rarely gets touched, Checking today was the first time in probably weeks that I have touched it and my wife never touches it.

It was warm on the 17th. It apparently changed to cool mode then. I see changes in setpoints, but why it changed from auto to cool is not known to me. It got cold overnight and the thermostat was still in cool mode until I changed it to auto. It isn't something I have had to worry about since it had just been working. This seems to be when the change to cool happened.

thermostatMode cool Zen Thermostat thermostatMode is cool DEVICE Zen Thermostat
2023-01-17 20:09:45.462 EST
thermostatMode heat Zen Thermostat thermostatMode is heat DEVICE Zen Thermostat
2023-01-17 20:09:40.696 EST
thermostatMode auto Zen Thermostat thermostatMode is auto DEVICE Zen Thermostat
2023-01-17 20:09:38.302 EST
thermostatMode cool Zen Thermostat thermostatMode is cool DEVICE Zen Thermostat
2023-01-17 20:09:37.104 EST
thermostatMode heat Zen Thermostat thermostatMode is heat DEVICE Zen Thermostat
2023-01-17 20:08:54.259 EST
thermostatMode cool Zen Thermostat thermostatMode is cool DEVICE Zen Thermostat
2023-01-17 20:08:47.901 EST
thermostatOperatingState idle Zen Thermostat thermostatOperatingState is idle DEVICE Zen Thermostat
2023-01-17 19:58:59.314 EST
thermostatOperatingState fan only Zen Thermostat thermostatOperatingState is fan only DEVICE Zen Thermostat
2023-01-17 19:58:58.093 EST
thermostatMode heat Zen Thermostat thermostatMode is heat DEVICE Zen Thermostat
2023-01-17 19:58:57.343 EST
thermostatOperatingState cooling Zen Thermostat thermostatOperatingState is cooling [stage 1] DEVICE Zen Thermostat
2023-01-17 19:57:52.439 EST
thermostatMode auto Zen Thermostat thermostatMode is auto DEVICE Zen Thermostat
2023-01-10 07:55:40.304 EST
command-setThermostatMode Command called: setThermostatMode DEVICE command Hubitat® Dashboard
2023-01-10 07:55:39.717 EST

This is where I changed it back to auto from the dashboard tile:

thermostatMode auto Zen Thermostat thermostatMode is auto DEVICE Zen Thermostat
2023-01-21 12:31:52.058 EST
command-setThermostatMode Command called: setThermostatMode DEVICE command Hubitat® Dashboard
2023-01-21 12:31:49.102 EST
command-setThermostatMode Command called: setThermostatMode DEVICE command Hubitat® Dashboard
2023-01-21 12:31:39.938 EST

I am going to keep observing it to see if it happens again. I may add a rule to check the mode and make sure it stays in auto, similar to the rules I have to make sure the thermostat setpoints are correct for the mode.

Go to the actual device page where you configure it and then go to the events tab at the top of the page. That will show you anything that is interacting with the thermostat.

This is exactly what Auto mode is supposed to do on a thermostat. This sounds like you have a thermostat issue, not a hub issue. Using Auto mode puts you at the mercy of the thermostat, rather than in control of it. I keep all of my thermostats in either Heat or Cool, except for a couple of weeks when seasons change. Consider that when in Auto mode, you're basically saying it could heat at night and cool during the afternoon. That's not a common situation.

So the mystery is who / what set the thermostat mode to heat and then to cool?

My rules only change the setpoints, not the modes. How the thermostat got changed from Auto to Heat or Cool is the thing I don't know and why I posted the situation here.

The reason I like Auto is that I don't want to do the switching back and forth. The Auto setting takes care of that for me. I have seen it on very rare occasion being warm during the day and then a cold front comes through and it gets cold enough that a little heat is appreciated.

I would need to see screenshot of the Device Events from the Events button on the device page for those events. Need to see then entire width of the event shown there.

Something is changing the thermostatMode. Also show a screenshot of the In Use By section of the device page.

I thought of one possibility. I am an amateur radio operator. It could be that some transmission on the radio happened at just the right millisecond to trigger this. I have not noticed any interference with WiFi or Zigbee devices, but I can't rule out the possibility.

That being said, I think I understood what you need, so here they are:

I think this is what you are asking for. Please let me know if it isn't.

1 Like

Didn't need the Event Details, but yeah, otherwise that's what was needed.

For each of those rules that actually set the thermostat in any way, look at its App Status page (gear icon) under Settings (the top portion of that page). Find any setting that starts with "thermoMode". If there are any, that's the culprit. If you find one of those, remove that rule and redo it in Rule 5.1.

None of my rules have "thermoMode" in them. I do see "thermoMain.2, -.3, -.7, and -.9" though.

Be sure that Action logging is on in all of your rules. It is a mystery what is causing the setThermostatMode event that's in your logs.

1 Like

Does it have to be automation initiated? Could it also not be a misbehaving device?

Of course. All we know is the the device reports the event, with type "Device".

1 Like

Thanks, I was wondering if I had missed something in the posted logs.

I activated Action Logging in my rules. I just had Event Logging before. Hopefully, it won't happen again. But if it does, I stand a better chance of capturing it in my log now. Thanks.

1 Like

If none of those rules set Thermostat Mode, and none of the other apps do, that would leave two possibilities: the Dashboard and the device itself malfunctioning.

I did not see a mode change, but I did see a regression to a previous problem.

dev:2712023-01-24 07:46:02.711infoZen Thermostat thermostatSetpoint was set to 72.0°F
dev:2712023-01-24 07:46:02.706infoZen Thermostat thermostatOperatingState is heating [stage 1]
dev:2712023-01-24 07:44:52.586infoZen Thermostat thermostatSetpoint was set to 72.0°F
dev:2712023-01-24 07:44:52.575infoZen Thermostat thermostatOperatingState is pending heat [stage 1]
dev:2712023-01-24 07:44:38.064infoZen Thermostat temperature is 67.0°F
dev:2712023-01-24 07:44:37.961infoZen Thermostat thermostatSetpoint was set to 72.0°F
dev:2712023-01-24 07:44:37.959infoZen Thermostat heatingSetpoint was set to 72.0°F
dev:2712023-01-24 07:32:11.090infoZen Thermostat thermostatSetpoint was set to 68.0°F
dev:2712023-01-24 07:32:11.088infoZen Thermostat heatingSetpoint was set to 68.0°F
dev:2712023-01-24 07:32:10.970infoZen Thermostat coolingSetpoint was set to 76.0°F
dev:2712023-01-24 07:32:10.949infoZen Thermostat thermostatSetpoint was set to 72.0°F
dev:2712023-01-24 07:32:10.947infoZen Thermostat heatingSetpoint was set to 72.0°F

The temperatures were set by my rule and then the heating setpoint reverted back to my night setting I will have to look and see where the mode change from night to day settings does not show at all. That is why I set up the periodic checks. The rule for that checks at 2, 17, 32, and 47 minutes

The rule that should have changed it to the day settings shows this in the log:

app:5622023-01-24 07:30:06.974infoAction: END-IF
app:5622023-01-24 07:30:06.971infoAction: Speak on Hallway speaker: '%device% set to %value%' (skipped)
app:5622023-01-24 07:30:06.968infoAction: Thermostats: Zen Thermostat --> Heat: 68 --> Cool: 74 (skipped)
app:5622023-01-24 07:30:06.965infoAction: ELSE-IF (Mode is Night(F) [FALSE]) THEN (skipping)
app:5622023-01-24 07:30:06.830infoAction: Speak on Hallway speaker: '%device% set to %value%'
app:5622023-01-24 07:30:06.777infoAction: Thermostats: Zen Thermostat --> Heat: 72 --> Cool: 76
app:5622023-01-24 07:30:06.773infoAction: ELSE-IF (Mode is Home(T) [TRUE]) THEN
app:5622023-01-24 07:30:06.671infoAction: Speak on Hallway speaker: '%device% set to %value%' (skipped)
app:5622023-01-24 07:30:06.667infoAction: Thermostats: Zen Thermostat --> Heat: 55 --> Cool: 80 (skipped)
app:5622023-01-24 07:30:06.663infoAction: IF (Mode is Away(F) [FALSE]) THEN (skipping)
app:5622023-01-24 07:30:00.616infoAction: Set Volume on Hallway speaker to 80

The 07:30 change did not happen even though the rule executed the change. I noticed that it took 2 attempts to change the temperature when I went in to the day double-check and executed the actions manually.

I am going to re-write those rules in Rule Machine 5.1 to see if that makes any difference.

@bravenel Changing to Thermostat Scheduler and re-writing my check rules in RM-5.1 made no difference. The mode changes, but the thermostat does not change with the mode. My rules are supposed to catch this and change the thermostat's temperature settings if that happens, but that is not happening. I went into my Thermostat_Check_Day rule and used the Run Actions button. It took 3 attempts for the cooling setpoint to change. It took another 3 for the heating setpoint to change.

I am convinced now that 2.3.4.134 is the cause. It was running fine before the 2.3.4.x updates.

All fingers point to the thermostat as not functioning correctly. Have you rolled back to the prior release, to see if these problems exist there now or not? That's the next logical step. There wasn't anything in the latest release that would explain this behavior.

Another thing you should try is to reset the thermostat (without removing it from your hub) with manufacturers instructions on how to do so, and then re-join it to the hub.

I have had one Zen Thermostat fail completely, in my personal experience. I've also seen it be very flaky as to being commanded. You can't really expect it to function properly if it cannot be commanded properly. Forget using rules, just do it from its device page. They are slow to respond. If it doesn't respond at all, that's the thermostat itself.

I have rolled back the platform to 2.3.3.140. It will take a day to know whether it fixed the problem or not. If it did, it would tend to confirm that the thermostat is okay and that something changed in the platform update that is causing this. If it doesn't fix the problem, then yes, it would indicate a thermostat problem.

I did check from the device page and the thermostat does respond from there, not immediately, but within a couple of seconds the changed temperature setpoints show up on the device page.

Download the Hubitat app