[Solved] Problem setting thermostat setpoint via RM

I am trying to cut over from Vera to Hubitat in two locations. Both will be managing lights and thermostats, along with some basic automation.

The first location went fine so far. I used Thermostat Controller and Thermostat Scheduler for thermostat control, and that turned out to be simpler than what I had implemented in Vera so I was encouraged to go ahead with the second deployment.

On the second one, my temperature control is much simpler. One thing I want to do is set back three thermostats based on a trigger (testing a virtual "switch" for now). I created a Rule Machine rule triggered by a change in the switch and am simply trying to change the setpoint on each of three thermostats (which happen to be Trane thermostats from circa 2012). What I've found is that using the RM to change the setpoint fails. When trying to change the setpoint to 60, it sends a command the thermostat to change it to 2 degrees.

If I open the device and use the Commands tab to change the setpoint (e.g. to 65), it works correctly.

What driver are you using? Also post a screenshot of the rule you used that set it to 2 degrees and a screen shot of the log when this happened.

Kind of hard to make any suggestions without more info.

1 Like

Yeah, sorry. Was looking for how to add screenshots and clicked to add the new topic prematurely.

Let me know if there is more I can look at or provide.

Screenshot Hubitat Log

I just noticed that the current rule is setting the setpoint via a Thermostat Controller - that was a test I did (without success). The logging is from an attempt to set it directly via the thermostat device, which is my intent. I can re-do the rule if you think it is important, but it shouldn't be - same logic.

Please post the logs for that rule. (events, triggers, actions).

Ok, changed the rule to set just a single thermostat directly to avoid any unnecessary complexity.

Here's the rule, setting one thermostat to 61:

And the logging for the rule and device from a test I just did:

Screenshot Log1

And logging for using Commands tab to set the temp to 62 for comparison:

Screenshot Log2

Post logs for the app running (events, triggers, actions). The logs you've posted are not useful in debugging the issue.

It was in there (app:4), but note that I simply used "Run actions" to trigger that. I just flipped the switch to have the rule triggered naturally. Logging for both methods included below. is this what you're looking for, or is there something missing?

So that shows that the app is working as expected.

What thermostat is this (brand/model)? And what driver is it using?

FWIW, I recreated your rule. And triggered it. Here are the logs, and my thermostat gets set as expected.

I think this eliminates the possibility that Rule Machine isn't working as expected. So let's focus on the device and the driver - and figure out what's going on with them.

1 Like

It is interesting that the device Controls is setting the thermostat correctly, but not the app. Is it possible that RM is using a different interface to the driver than the device Controls tab?

In any case, the thermostats are Trane TZEMT400BB32, and I'm not sure how to determine which driver is in use unless that's visible on the Device Info screenshot I pasted above (see first screenshot in this thread). I've only a couple of days experience with Hubitat, so let me know where I can find the driver info.

And I just noticed the Events page (I was thinking everything was on the Log page). Here's the info from that from my two earlier tests.

No. I don’t know enough about that device. Is it a zwave thermostat? Or is it a WiFi device?

zwave.

1 Like

Click "device info" tab and it's listed under "type"

1 Like

Looks like this is a really old z-wave device. Try changing the driver to "Generic Z-Wave Thermostat" and hit the "Configure" button on the device page.

See if that works better than the driver currently in use (Generic Z-Wave DT Thermostat General).

That appears to have worked!

Screenshot Log4

Can you offer any explanation (or pointer to info I can look at) re: the difference between the two drivers? I'm not sure if these are documented anywhere.

In any case, thanks very much for your time this evening in helping look at this. I'll continue with the intended configuration now that it appears to be working.

1 Like