Is there a way to test if EcoMode is already enabled?
Can you provide more information? EcoMode on what device?
1 Like
Thermostat
I'll play along. Which thermostat? What driver? Information is important.
1 Like
The Ecomode in the thermostat scheduler. Not sure why the actual device is important but itās a Honeywell Z-wave that is cloud dependent. Donāt have the actual model number handy.
It is important because i could tell you to look and see if you see the green eco text in the tachometer section of the instrument panel on a equinox and that is a valid answer. Context is always important if you want a answer relevant to your question.
6 Likes
I donāt think anyone actually understood you were referring to the thermostat scheduler app til you stated that 
.
If I wanted to know if thermostat scheduler was in eco mode, I would browse to the appās settings page and check there. Like this:
1 Like
Wait - which Honeywell zwave thermostat is cloud dependent?!!
Are you not directly pairing it to Hubitat?
Okay I guess I did a lousy job explaining this to begin with.
The Honeywell thermostat is one that uses the Total Comfort API C driver. I'm trying to figure out if you can tell if EcoMode was on in Rule Machine so I could do an IF EcoMode = True kind of test. I have worked around it at this point but would still be curious if it was something we could test for in Rule Machine.
So in this case, the thermostat device itself is irrelevant.
The question is whether rule machine can use Thermostat schedulerās eco mode as a condition?
1 Like
No, there is no way to do this. But, the circumstances that led to eco mode are repeatable, and those could be used in RM.
2 Likes
Ya what I run into is since my thermostat is cloud based and it's Honeywell depending on timing sometimes it misses the command to go into our out of ecomode and then if the circumstances repeat to set it again it can result it a double adjustment. Example:
Set to 77 with 8 degree offset. It triggers and is set to 85. Then the trigger to undo it happens but the stupid API doesn't take it if it happened too soon (within a few minutes). Then the trigger to set it occurs again and now it goes from 85 to 93. Then when that resets it only goes back to 85.
If there was an option for the offset to be a specific setting if the system was in cool mode and another value if in heat mode then it would keep that from happening as it could not "creep". I'll see about using RM to set that up.
FWIW, there are plenty of zwave and zigbee thermostats that work with Hubitat, including from Honeywell.
It's on my list. 
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
