Is there a way to adjust the hold time for a specific thermostat via Rules Machine?
I have my thermostats set to ask if I change the temp at the thermostat. I have a default hold time set to 4 hours in the Suite settings which works well for 3 out of 4 thermostats. For the fourth it would be ideal if I could select the hold time from one of my Rules when that rule changes the temp. Is that possible?
Thanks!
Tom G.
Excellent suggestion.
The setThermostatProgram() call already supports specifying the hold time, but the calls to adjust the specific setpoints do not.
I think I can add a setThermostatHoldHours() call that updates/changes the settings/preference for the thermostat device. You would call that before changing the setpoints, since it uses the thermostat's preference as the hold time.
I was hoping that you could simply do <thermostat_device>.settings.myHoldHours = '6', but I don't think an app is permitted to directly change a device's settings.
Might be a couple of days before I get around to this...
That would be great! Thanks for all the time and effort you put into this!!!
Sorry if I missed it, but I did a search an couldn't find the answer. I have several Ecobee room sensors and they report battery level to the Ecobee thermostat. I this something you can pull in as well?
I don't know what Ecobee has done with their ECO+ mode but I have a room that is 3 degrees warmer than other rooms and it's unoccupied. It used to run the fan to balance out the temperature but now it's not doing this at all. Also they moved the run the fan "x minutes" per hour out of the basic settings and put them into ECO+ so if you disable ECO+ and try to set the "run for x minutes" option it gives a message the setting is now in ECO+ which I cannot find the run "x minutes" in their ECO+ section. I will be making a support call today to find out what is going on.
To make matters worse the UI on the Thermostat and Web Site do not align with the UI in the app and there is no way of managing the ECO+ settings there you have to use the app. If you use the Web Site to make changes that have been take over by ECO+ it will confuse their services in ECO+ in the app.
I don't see where the sensor battery levels are reported to the thermostat - can you share a screen shot showing that?
I'm pretty sure that the thermostat only suggests that the battery might be low/dead when the sensor stops reporting data...
Yup - they made LOTS of changes that have impacted the normal operations of the thermostat, including breaking fanMinOnTime such that changes to the value have no impact unless you hold/unhold the thermostat.
Hopefully support will give you some more insight into the issue...
OK - try this version of Ecobee Suite Thermostat. It supports a new custom command "setThermostatHoldHours", and you pass it the (integer) number of hours you want the default hold to be. You can enter any integer, but I can't guarantee that all Ecobee thermostats support any value.
Let me know if this works for you ...
You could be right. I have just replace all my batteries so will have to wait to see what the message is in the future.
Thanks! I just updated the driver and modified my rules to use the new custom command. I'm going to let it run a couple times and see what happens. I'll let you know either way.
Again, Thanks!
I've noticed that my Keen vents will occasionally wind up in a state that is opposite to what my hub (and Ecobee Suite Manager) thinks they are in. For instance, the device in the hub shows Open: 100% and the ESM reports the same. However, the vent is actually closed. If I set the level on the vent to something similar (96, 98, etc.), the vent will immediately open. This happened to me back when i was on SmartThings, too.
I was wondering if it might be possible to send a similar level command to the vent, even if the hub thinks it is already in the state it needs to be in. For instance, if it wants the vent to be open and the hub reports it at 98% open, send it a command to set it to 97% so that the vent "refreshes" its state and moves to the proper orientation? I have no idea why my Keen vents get themselves in this state every once in a while, but I think this "hack" would be a workaround to avoid it. Thoughts?
Sounds like a problem with the Keen Vent device driver you are using. I'd rather not do the hack you suggest, because it will cause the vents to consume batteries faster, even for those that aren't having any issues.
A better hack might be to write a Rule Machine rule that calls refresh() on the vent(s) hourly, or perhaps even when the thermostat reports thermostatOperatingState == "idle".
You could also try enabling "always adjust" - that will send (slightly) more commands to the vent, possibly overcoming the issue...
Thank you for your response. I enabled "always adjust" last time this happened, in hopes that it would workaround the issue. Would I be better off using a generic dimmer driver for these vents, in stead of the Keen device driver? I will try the rule machine refresh idea and see if that helps as well.
Yes, you could try using the "generic dimmer " setting in the helper.
Also, are you using MY Keen vent driver, or the native Hubitat one? If it is mine, I could add some double-check logic to the driver...
I'm using jscgs350's keen vent driver code. I'm not sure I knew you had a driver (unless that's you). These drivers were last updated in 2018, so perhaps I should consider a newer/better driver.
Where are your Keen vent drivers posted? I'd be happy to try them out instead.
you can find my drivers here: https://raw.githubusercontent.com/SANdood/Ecobee-Suite/master/HubConnect/Universal/Custom-Drivers/Keen%20Home%20Smart%20Vent.groovy
Thanks! I'll switch to that driver now. As it turns out, I was using the native Hubitat driver. I had the other driver I mentioned above installed, but it was not in use.
After switching to your drivers, 3/7 of my vents show "obstructed" when they are not. Clear obstruction does not cycle the vanes. If I pull the battery and replace it, I get the green blinking light and the vanes cycle freely. But the device still shows "obstructed." Also, the temperature readings are all over the map (40F to 100F within 20 seconds). Reverting back to the native driver allows the vent to be controlled.
I've also noticed that with the native driver, if I tell it to switch "off", the vanes close, but the level remains at 100. I suspect that's how i'm winding up in the situation I was originally in.
I tried to build a rule to refresh the vents when the furnace is idle, but the Vents don't show up in the list of devices if I choose "Refresh" or "Poll" as the action. They may show up when I use your driver, but I reverted back to the native driver because of the obstruction issue. The only way I can get them to show up in the list is if I do a "custom action" and choose to refresh the dimmer status of them.
Custom action is the correct path to get the native driver to do a refresh().
Sorry my driver didn't work for you - I don't have any Keen vents any more, so I can't debug the issues. Best you stick with the native, and try the refresh route.
Thank you for your help. I've implemented the rule to refresh the vents when the thermostat goes idle. Hopefully that resolves my issue.
Download the Hubitat app
