I've never really used the thermostat dashboard tile as it was always easier to use the honeywell app. I just replaced the honeywell with a radio thermostat.
It doesn't seem to be well suited to change a wide range of temperatures. Ie, move the set point from 40 to 60. Every up/down click sends a command to the thermostat which quickly overwhelms it, then the setpoint on the dashboard starts jumping around.
It'd be nice if there was a delay from once you get it to where you want it before sending the command. Or possibly a popup dialog like when clicking on a color bulb tile where you can enter a value directly.
There is a work-around you could do.
You can make a hub variable connector to take the setpoint as a number. Make a tile with it on the dashboard with the variable number template. It will act as an input tile.
Then make a simple rule to set the thermostat setpoint to that variable when it changes from you changing the number on the dashboard.
2 Likes
I got it working to set the set point.
I'm thinking I want to elaborate so the variable shows the current set point if changed by another method. But then the if changes I think will create a loop. Not sure how to work around that.
Rule:
Yes, it will. I ran into that before, so you have to make a condition that it will only update if the value of variable or the thermostat setting is not already set to what you are trying to set it to. That stops the loop when it already matches and you don't do the update again.
Happen to already have a rule like that you can show me? I feel like a total idiot sometimes trying to do stuff in rule machine 
I've always used Webcore and now code in Groovy, so I've never really played around with Rule Machine much.
Trying it out now, I think something like this will work for the condition?
Edit: This what it would look like in Webcore:
Man I hate rule machine. LOL
You can't do a conditional trigger with a variable like that. I
So I went to try the Webcore route (I use webcore more because it's easier to understand for me) however it can't access variables it seems.
I'll just use it as is. I don't change the temp via dashboard often. It's not that hard clicking in the box and typing in what I want.
The Hub variables go into the list of Webcore Global variables, with @@ in front. If you make the variable into a connector, it becomes a device that you can add to Webcore, and then you can change the variable via the "variable" attribute in the driver. So there are two ways for Webcore to use and update hub variables.
