I think we are on the same page. The thermostatOperatingState should be idle if the thermostat is actually idle though. The only time the thermostatOperatingState should show heating is when the furnace is actively heating the home.
If the thermostatOperatingState always shows heating when the mode is set to heat, then it sounds like a bug in the device driver.
Edit: Is it a built-in driver or a community driver? I'd like to make a feature request to get the thermostatOperatingState to reflect the appropriate value.
@ryan780 are you specifically using it with the thermostatOperatingState attribute from the Ecobee? Based on what Drew and Jason mentioned, it doesn't sound like the device is reporting the values I would have expected for the thermostatOperatingState.
The expected values for the thermostatOperatingState are:
- cooling
- fan only
- heating
- idle
- pending cool
- pending heat
- vent economizer
What has been noted so far is:
Mode
Actual State
Reported State
Expected State
Auto
Idle
Auto
Idle
Auto
Heating
Heating
Heating
Heat
Idle
Heating
Idle
Heat
Heating
Heating
Heating
Based on the screenshot in the original post, it looks like the generic/descriptive thermostat attribute contains the text 'Idle' in it, so we at least know that the thermostat device itself is reporting the idle state... just that the thermostatOperatingState isn't being updated to expected values.
@mike.maxwell any thoughts on updating the Ecobee driver (and potentially other thermostats) to report expected thermostatOperatingState values?
@Ryan780 Eh... The built in driver reports heating when heating, and cooling when cooling in thermostatOperatingState... So it reports operating state at least semi-right... It shows Auto when idle, which isn't right, but that hasn't affected much on my end.
If the Ecobee Suite port reports it faster or better, though - I'm not adverse to using it. I used it on ST...
It does not always report heating when heating and cooling when cooling no matter what mode you are in. It reports the correct state when you change the temp manually but not when it "recovers" to an already set temp.
At least thats the way it worked with the native integration 2 months ago.
Does SharpTools support this? We keep our sleep temps at 64 degrees. I used the SharpTools dashboard to bump up the heat to 69 degrees late yesterday afternoon. It put the temp change on permanent hold and I woke in the middle of the night sweating my ass off
if you change the setting On the EcoBee or in the device driver to Temporary Hold it will always revert to the next scheduled change, above that would be Sleep.
I switched over my 4 thermostats and 9 sensors to the Ecobee Suite this morning. Was fairly easy since I used ir on ST in the past.
One thing that don't work is building sensors for thermostat readings. It is in the options, but does nothing. Everything else seems to work well though.
I am using it, and that option doesn't seem to do anything as I don't have separate sensors for the thermostat temp like I did in ST. Also tried toggling it on/off.
On my install, this does nothing:
Ecobee Suite Manager --> Ecobee Suite Preferences --> Include Thermostats as a separate Ecobee sensor
In ST, that option created a new sensor type device specifically for each Thermostat temperature reading. That way you could handle all temperatures. thermostat and sensor, the same in logic/code.
Again, not that big of a deal, but I mentioned it since the options shows up yet doesn't work.
Auto
Heating
