Has anybody had problems with the possible values of the ThermostatOperatingState capability? I have noticed that PendingCool, PendingHeat and VentEconomizer do not work?
I realized this because I need to add some values. Is it possible to add values to a capability attribute type enum? If yes, how would you do it?
My workaround is to convert the capability into an attribute in the device properties…
Many thanks!
At this time, JavaScript Plugins only support Cooling, Heating, Idle, & FanOnly for ThermostatOperatingState. I’ll try to get those other values added in the next release. For the time being, use a custom Attribute just as you are currently doing.
Bill, thanks for your answer. In fact, I do not need those values, I just discover they do not work because I need new values for the Nest thermostats.
I just discover a way to know if the thermostats are in ECO mode due to the fact that the house is in AWAY mode, which unfortunately Google still does not provide a way to know it! This method works fine if the ECO temperatures are different from the HEAT and COOL temperatures, which they normally are.
For example, if a thermostat is in COOL mode and the ThermostatCoolingSetpoint = ThermostatEcoCool (attribute I created) then the house is in AWAY mode and the thermostat should show the leaf icon. Otherwise cooling might be off and the tile will still show the system as cooling…
In fact it would be nice to add “Away-Heating”, “Away-Cooling” and “Away-Idle” to the “ThermostatOperatingState” capability attribute and “Eco-Heat” and “Eco-Cool” to the “ThermostatMode” capability attribute.
Just to give you more information, I only added “Eco” to the “SupportedThermostatModes” so as to be able to select “Eco” from the details tile and make the thermostat to start Eco mode automatically according to whether it was heating or cooling.
Do you think it would be possible to add/create more attribute values to the existing capabilities? Like leave the “Possible values” list editable?
Many thanks again Bill!