Yes - that is in fact a mistake on the part of the Hubitat driver, IMHO.
I mean, it's not like they have to try to deduce that the fan is running or not...because the Ecobee API does in fact return equipmentStatus with one or more of the following values:
Furthermore, it really has nothing to do with thermostatMode or thermostatFanMode. -- if the equipmentStatus is "fan" and nothing else, then the Hubitat Ecobee driver should set thermostatOperatingState to "fan only".
And yes, the API says the fan is running even if the thermostatMode is "off"...or when it is doing its internally-controlled "circulation" - there's no excuse for not reporting "fan only".
I am truly surprised that it doesn't...even SmartThings got that part right
Since you have done this, it is doable. I am confuse as to why the built-in drivers does everything else with ecobee tstat but not fan only? Is it not just another API call, or some extra parsing of the values returned?
I hope someone at Hubitat is reading this question. If it is too complicated and not worth the time/effort I will understand and be willing to pay for it.
I am not asking for a scheduler, enhanced functionality, just 1 other value/status from the device Hubitat supports with a built-in driver.
I am pretty sure I would not be the only one here who would benefit from having this.
It provides access to ALL Ecobee attributes, and comes with a variety of Helper apps that you can use with your Ecobee as well.
As to "why" the native driver doesn't support Fan Only, nobody really knows. Send an email to Hubitat Support with the question, and you may get an answer...
@bravenel, @bobbyD, Can you answer this question as to why the built-in ecoBee driver does not support Fan Only when the custom user drivers do? ecoBee systems use the Fan Only feature to improve overall home effeciency and not having it to control vents is a much needed status. Thanks for you help.
I can set the system to fan only, but when the ecobee sets itself to fan only the driver is not getting the state change. I think it maybe in the thermostatOperatingState setting.
Hopefully @yracine66 or @storageanarchy maybe kind enough to shed more accurate help on this. Please!