Hello! I am new to Hubitat having just transitioned over from Smartthings. Most of the transition has been fairly seamless, but I have stumbled on a small issue. I have two Zen zigbee thermostats which worked smoothly in the Smartthings environment. I was able to pair both devices to HE with little effort. To control these thermostats I am using the Thermostat Schedulers app. I have a very basic schedule. In the evening (10:00pm) change the setpoint to 68F. In the morning (5:30am), change the setpoint to 74F. The evening change appears to work fine, but I am finding a odd issue in the morning. The logs show it changes the set point to 74F, but within 0.5 seconds it sets the setpoint back to 68F, so no heating in the morning. I am attaching a portion of the log which shows this interaction. Any thoughts on what is going on?
The above log takes place at 5:31am because in trying to debug this issue, I had one thermostat scheduled 1 minute later to see if there was an issue with commands being broadcast too fast for the thermostats to react.
Go to your device page for the thermostat and verify if any other rules are attached to it. Maybe something else is setting it back.
Also do you use Alexa or something else. Not sure if Alexa can change thermostats with hunches but it has caused some issues for unexpected lights going on or off.
Maker API could do it, If that is not it check your scheduler maybe you have something in there your missing. I am not familiar with the HE scheduler app as I don't use it, If there is debug logging you can turn on in the scheduler maybe that will show you something if it is sending another command to the thermostat.
If you post your scheduler setup, I'm pretty fluent with it but I doubt it has anything to do with TS. I would look at those other Apps like MakerAPI, unless you are really using it for something, you could also try to remove it from MakerAPI and see if that resolves it.
I removed Maker API so will see tomorrow morning if maybe that was the cause. From the event log of this thermostat I see were the scheduler sends it command but it appears as the thermostat itself changes the setpoint back.
ok, doubt this has anything to do with it but you should set the mode of the thermostat (at the least on Auto if used for heating and cooling). But I would wait and see if disabling MakerAPI changes anything.
I had an issue with the same thing happening. What I ended up doing is to not use the thermostat scheduler. Instead I set up rules.
Rule 1 checks to see if we are away or home. Then, depending on the time, it sets the thermostat for our desired daytime or nighttime temperatures if we are home or to our away temperatures if we are away. If we are away and return home, it changes the mode back and sets our desired day/night temps.
Rule 2 checks on the quarter hours to make sure that if we are away, the away temperatures are set. If not, then it sets them accordingly.
Rule 3 checks on 1, 16, 31, and 46 minutes to see if night temperatures are correct and sets them if not.
Rule 4 checks on 2, 17, 32, and 47 minutes to see if day temperatures are correct and sets them if not.
I might be able to combine them, but since setting these rules up, the Zen Zigbee Edition thermostat here has been reliable. I had only one hiccough recently after the most recent upgrade, but after executing the rule manually, everything is back to reliable.
It has been a very long time since I used a Zen, so I might be mis-remembering. I think there is a setpoint separation setting in the thermostat that can be adjusted. Could it be possible that when your higher heating setpoint is called it is too close to your cooling setpoint? Just a thought.
I removed the Maker API app. Everything seemed to work fine yesterday morning, but last night one of the thermostats exhibited the problem.
This morning I noticed the temperature was cold. I checked the logs and found that thermostat didn't just alter the setpoint on its own, but the scheduler never even attempted to send the change set point commands. (That's odd)
Doing some internet searches, there are a couple of posts from a couple years back of people with Zen thermostats seeing the exact same issue when working with Hubitat, but none of the posts have follow ups detailing what they did to solve the issue.
Some ideas I am thinking of trying:
It appears the issue may be the DH for the Zen thermostat. I read somewhere that you can use any DH for a zigbee thermostat and it should work. Can anyone confirm this?
Setup a brute force set of rules like StephenH suggested. I know this would work, but seems very heavy handed.
